Modify ↓
Opened 11 years ago
Closed 11 years ago
#11081 closed defect (cantfix)
After a 'TracAdmin resync' call is still the svn history in the ticket off by 4
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 1.0.1 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I have merged one svn repros into another and called 'TracAdmin resync' on the merged repository.
Everything seem to look finde all the old changes and the new can be found in the matching trac reprository but the ticket history has an offset by -4.
The ticket hystory looks like this:
ssi_ext1_clk as camera master clock added.
A click on the [565] is leading to correct changeset [565]. But this isn't the correct changset for the ticket #303. By manually changing the web link to …/changeset/569 is showing the correct changeset for the ticket #303.
How can I fix this?
Attachments (0)
Note:
See TracTickets
for help on using tickets.
If the changeset numbers have changed during the merge, all changeset links will be wrong. That's unfortunate, but there's nothing Trac can do about it. How should Trac guess what the new changeset number should be for each old number?
Your best bet is to keep the old repository around as a (possibly hidden) default repository, to avoid breaking the links, and to add the new (merged) repository as a named repository.
You could also run some SQL magic on all the relevant tables to fix the references, provided you have a consistent formula for mapping from old to new number. But this will include searching for and substituting more or less arbitrary strings within arbitrary strings, so I would advise against it. At least, make sure you have a backup before trying.