Opened 19 years ago
Closed 19 years ago
#2107 closed defect (fixed)
Trac "remembers" old subversion changesets when migrating from one repo to another
| Reported by: | anonymous | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.9 |
| Component: | version control/changeset view | Version: | 0.8.4 |
| Severity: | minor | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
This is an initial setup issue. I set up Trac and Subversion with a test repo. I then removed the old subversion repo, and then installed the new production one. Trac showed in the Timeline page changesets from the initial testing repo.
The problem is that Trac stores this info in its own internal tables, node_change and revision. Deleting all the rows from these tables solved this problem. There should be some way of doing this from the admin interface.
Attachments (2)
Change History (11)
comment:1 by , 19 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
by , 19 years ago
| Attachment: | warn-if-repository_dir-changed.patch added |
|---|
Provide an explicit warning in case the repository_dir was changed but trac-admin resync has not been called
comment:2 by , 19 years ago
| Milestone: | → 0.9 |
|---|---|
| Resolution: | worksforme |
| Status: | closed → reopened |
I actually had some code around which checked for that situation: attachment:warn-if-repository_dir-changed.patch
comment:3 by , 19 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → new |
comment:4 by , 19 years ago
Looks like there's a duplicate call to repos.sync() in that patch. Also, Matt suggested on IRC that we can use INSERT OR REPLACE INTO ... instead of the two separate SQL statements.
comment:5 by , 19 years ago
Maybe we should use the repository uuid instead of the path to detect new repositories.
by , 19 years ago
| Attachment: | warn-if-repository_dir-changed.2.patch added |
|---|
Updated patch, taking into account the above comments
comment:6 by , 19 years ago
| Priority: | low → normal |
|---|---|
| Status: | new → assigned |
comment:9 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Applied a slightly reworked patch in r2312:
- check earlier for the Subversion API version
- adapt the Repository Mock object in
versioncontrol/tests/cache.py
You need to do a
trac-admin resyncto fix the timeline.