Edgewall Software

Opened 12 years ago

Closed 12 years ago

#6210 closed defect (duplicate)

Major problem with out of synch Trac and SVN Repository.

Reported by: kphayward@… Owned by: Jonas Borgström
Priority: high Milestone:
Component: general Version:
Severity: major Keywords:
Cc: Branch:
Release Notes:
API Changes:

Description (last modified by Emmanuel Blot)

We have just had to restore a server from backup which held our Trac Python engine and SVN Repository on its C: drive. The physical SVN Folders and PostgreSQL database (Trac) are on a seperate E: drive.

The end result is that the SVN repo. only holds information up to the last backup/snapshot at Oct 17th 9:25 am, while the actual files on E: are the latest commits performed up until Oct 18th at approx. 4:00pm. So Trac appears to be pretty upset with not being able to see the latest SVN Changeset in the now out of date Repository. Hence we see the error message below, everytime we try to access our Trac project.

I know that this is mostly an SVN Repo. problem but I thought it worth while to let you see the Python Traceback and hope that someone may have had to deal with this sort of problem before.

Python Traceback

Traceback (most recent call last):
  File "C:\Python24\Lib\site-packages\trac\web\main.py", line 387, in dispatch_request
  File "C:\Python24\Lib\site-packages\trac\web\main.py", line 191, in dispatch
    chosen_handler = self._pre_process_request(req, chosen_handler)
  File "C:\Python24\Lib\site-packages\trac\web\main.py", line 263, in _pre_process_request
    chosen_handler = f.pre_process_request(req, chosen_handler)
  File "C:\Python24\Lib\site-packages\trac\versioncontrol\api.py", line 73, in pre_process_request
    self.get_repository(req.authname) # triggers a sync if applicable
  File "C:\Python24\Lib\site-packages\trac\versioncontrol\api.py", line 101, in get_repository
    repos = self._connector.get_repository(rtype, rdir, authname)
  File "C:\Python24\Lib\site-packages\trac\versioncontrol\svn_fs.py", line 260, in get_repository
    crepos = CachedRepository(self.env.get_db_cnx(), repos, None, self.log)
  File "C:\Python24\Lib\site-packages\trac\versioncontrol\cache.py", line 34, in __init__
  File "C:\Python24\Lib\site-packages\trac\versioncontrol\cache.py", line 78, in sync
    current_rev = self.repos.next_rev(youngest_stored)
  File "C:\Python24\Lib\site-packages\trac\versioncontrol\svn_fs.py", line 393, in next_rev
    rev = self.normalize_rev(rev)
  File "C:\Python24\Lib\site-packages\trac\versioncontrol\svn_fs.py", line 334, in normalize_rev
    raise NoSuchChangeset(rev)
NoSuchChangeset: No changeset 1515 in the repository

Attachments (0)

Change History (1)

comment:1 by Emmanuel Blot, 12 years ago

Description: modified (diff)
Milestone: not applicable
Resolution: duplicate
Status: newclosed

Try upgrading to 0.10.4.

If it still occurs, you might want to try the latest 0.10-stable branch

Search for "nosuchchangeset" on Trac site, there are several duplicate entries that have already been addressed (#5449, #5423, …)

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from Jonas Borgström to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.