problem after recreating subversion repository

[meinholz@…]

I am using trac 0.10.4 and python 2.5.1 on ubuntu. I am using the debian/ubuntu pkgs that have been installed using apt-get.

I had to delete and recreate a subversion repository after associating a trac project with the repository. I have run the command:

trac-admin /path/to/tracproj resync

This partially works. My wiki seems to be recovered and I can edit a page. However, after I have edited a wiki page, submitted the change and then attempt a second edit, I get the following error:

Python Traceback

Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/var/lib/python-support/python2.5/trac/web/main.py", line 191, in dispatch
    chosen_handler = self._pre_process_request(req, chosen_handler)
  File "/var/lib/python-support/python2.5/trac/web/main.py", line 263, in _pre_process_request
    chosen_handler = f.pre_process_request(req, chosen_handler)
  File "/var/lib/python-support/python2.5/trac/versioncontrol/api.py", line 73, in pre_process_request
    self.get_repository(req.authname).sync()
  File "/var/lib/python-support/python2.5/trac/versioncontrol/cache.py", line 82, in sync
    raise TracError("The 'repository_dir' has changed, "
TracError: The 'repository_dir' has changed, a 'trac-admin resync' operation is needed.

If I re-run the trac-admin resync, I am able to do another edit before the problem recurs.

[ThurnerRupert]

of #5788

[Christian Boos]

No, #5788 is about a "No such revision message" error. Here it's a different story:

The 'repository_dir' has changed, a 'trac-admin resync' operation is needed.

In the trac log, at INFO level, there must be a line like:

repository_dir' has changed from /a/b/c to /x/y/z

Can you tell from that what's wrong?

(e.g. that could be a trac-admin resync performed on a different environment than the one used by the web application, when both are sharing the same db but have different 'repository_dir' settings in their trac.ini)

[meinholz@…]

This problem has failed to repeat itself. I'm sorry, but I am not sure what I have done to resolve the problem. The issue seems to have resolved itself after a system reboot, which surprises me because I would have thought restart apache would have been sufficient. Thanks for the help.