#7023 closed defect (duplicate)
SubversionException when adding svn repository after Trac installation.
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | version control | Version: | 0.10.3 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I installed Trac without initially specifying the subversion repository. I then added some plugins:
- Bitten-0.6dev-py2.4.egg
- TracWebAdmin-0.1.2dev_r6060-py2.4.egg
- IniAdmin-0.1-py2.4.egg
When adding Bitten I did have to run
trac-admin /trac/mytrac upgrade
Everything (including all plugins) was working fine at this point.
Then I created the subversion respository and added it to the trac.ini file using IniAdmin. repository_dir = /var/svn/myrepo
Trac now failed with (sorry did not make copy of original traceback) that finished with
SubversionException: ('No such revision:1')
I found ticket #3875 and #4132 and tried:
trac-admin /trac/mytrac resync Resyncing repository history... (this will take a time proportional to the number of your changesets) Command failed: ('No such revision 1', 160006)
I got around the problem by creating branches, tags, and trunk directories in the repository and everything works fine. i.e. svn revision is now 1
I deleted the repository (trying to recreate the original traceback) and get a slightly different traceback
Traceback (most recent call last): File "/var/lib/python-support/python2.4/trac/web/main.py", line 387, in dispatch_request dispatcher.dispatch(req) File "/var/lib/python-support/python2.4/trac/web/main.py", line 191, in dispatch chosen_handler = self._pre_process_request(req, chosen_handler) File "/var/lib/python-support/python2.4/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.4/trac/versioncontrol/api.py", line 73, in pre_process_request self.get_repository(req.authname) # triggers a sync if applicable File "/var/lib/python-support/python2.4/trac/versioncontrol/api.py", line 101, in get_repository repos = self._connector.get_repository(rtype, rdir, authname) File "/var/lib/python-support/python2.4/trac/versioncontrol/svn_fs.py", line 260, in get_repository crepos = CachedRepository(self.env.get_db_cnx(), repos, None, self.log) File "/var/lib/python-support/python2.4/trac/versioncontrol/cache.py", line 39, in __init__ self.sync() File "/var/lib/python-support/python2.4/trac/versioncontrol/cache.py", line 73, in sync raise TracError("The 'repository_dir' has changed, " TracError: The 'repository_dir' has changed, a 'trac-admin resync' operation is needed.
Ok this time it recognizes it is a different repository (i.e. the SNV UUID has changed) from data stored in system table. but still
trac-admin /trac/mytrac resync Password: Resyncing repository history... (this will take a time proportional to the number of your changesets) Command failed: ('No such revision 1', 160006)
I can reset system table youngest_rev|0 But still get 'No such revision 1'
The resync always seems to want to start at 1 not 0.
Usually I create svn repos first then create the trac site and specify the repo when trac created and have not seen this problem.
Only in this case where I added repo to Trac after creation and adding eggs did I see this problem.
Attachments (0)
Change History (3)
comment:1 by , 17 years ago
Keywords: | needinfo added |
---|
comment:2 by , 17 years ago
Keywords: | SubversionException resync needinfo removed |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Version: | 0.10.4 → 0.10.3 |
Actually, this is a duplicate. From the traceback, you're running something between 0.10.3rc1 and 0.10.3.1. An upgrade should fix it.
Double-check your version. This sounds like a duplicate of #4937 which was fixed for 0.10.4.