Opened 18 years ago
Closed 18 years ago
#6207 closed defect (duplicate)
Resync issue when relocating an empty subversion repository
| Reported by: | Owned by: | Christopher Lenz | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | admin/console | Version: | 0.10.3 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I had to move our Trac environment from one server with an old directory structure to a new server with a different directory structure and for one of our Trac projects (call it B), the Subversion repository was completely empty. I changed both project settings in trac.ini but for the B project, the trac-admin resync did not update the new repository path and the webpages always showed the trace, requesting the resync operation. For project A, everything went fine.
I managed to solve this problem by importing a dummy file into the original repository to reach Revision 1, them moving it to the new place and finally doing the resync - and it works now, but unfortunately I cannot reproduce the trace with error message.
We use Trac version packaged for the debian distribution: 0.10.3-1etch2.
Known issue, fixed in 0.10.4: see #4937.