incorrect revision number for imported SVN
launchpad had a difficult time importing https:/
The repository updates fine, but the lp revision number does not match the sourceforge.net revision. There's an offset of 1,855 revisions. I.e. lp 2126 = sf 3981. Is there a way to correct the lp revision?
Thanks,
Tom
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Max Bowsher
- Solved:
- 2011-08-24
- Last query:
- 2011-08-24
- Last reply:
- 2011-08-23
| William Grant (wgrant) said : | #1 |
Subversion's revision numbers are global across the whole repository, while Bazaar's are local within a particular branch. There are only 2126 revisions in trunk's mainline history.
Is there a way to force the Bazaar revision to report the same as the original SVN revision?
| William Grant (wgrant) said : | #3 |
You should see "svn revno: 1234 (on /trunk)" in the output of "bzr log" if you have bzr-svn installed. You can also do eg. "bzr diff -csvn:1234" to see the changes in svn r1234.
| Stefan Handschuh (handschuh) said : | #4 |
So the answer to #2 is 'no'?!
This is also a bit confusing, if one is using the revision number in recipes for daily builds.
Apparently. I created this branch and gave up trying to use it because revision offset makes it impossible for me to track changes with the original. Sad.
|
|
#6 |
Yes, the answer to #2 is 'no'.
Subversion and Bazaar are quite differently structured, and define the concept of a revision number in different ways. Mercurial has yet another different definition of revision number.
Then this branch is useless for my purposes.
