vila: Good catch! That does seem likely. Here's the cross-check output for dsdo:
$ bzr cross-check $(for urlpart in $( (for ubu in breezy dapper edgy feisty gutsy hardy intrepid jaunty karmic lucid maverick natty ; do echo ubuntu/$ubu/dsdo/$ubu; done) ; (for deb in sid squeeze; do echo debian/$deb/dsdo/$deb; done) ); do echo http://bazaar.launchpad.net/~ubuntu-branches/$urlpart; done)
17 common revisions to check (23 seen)
17 common inventories to check (23 seen)
disagree id_to_entry for <email address hidden>: StaticTuple('sha1:61cb883b87b4ff8f95117463cca5eff890639e83',) StaticTuple('sha1:53f99dc4dd7e3d7d3ed9f26f6994c9b6c8554681',)
Which is exactly the sort of error that bug produced.
For some reason when I scanned the NEWS entries for relevant fixes since 2.1.1 I missed that one.
So: next step is to get 2.1.1 upgraded to 2.1.3 (or 2.2.1 or 2.3) on that system. I'll file an RT.
Then we can either reset those imports again, or run "bzr reconcile --canonicalize-chks $repo" on all the affected repos with bzr 2.3. The latter is probably less disruptive if we can run 2.3 on the package-import system.
It's possible, perhaps likely, that other imports have old revisions with this inconsistency. It's probably good enough to just 'bzr reconcile --canonicalize-chks' those if/when they turn up.
vila: Good catch! That does seem likely. Here's the cross-check output for dsdo:
$ bzr cross-check $(for urlpart in $( (for ubu in breezy dapper edgy feisty gutsy hardy intrepid jaunty karmic lucid maverick natty ; do echo ubuntu/ $ubu/dsdo/ $ubu; done) ; (for deb in sid squeeze; do echo debian/ $deb/dsdo/ $deb; done) ); do echo http:// bazaar. launchpad. net/~ubuntu- branches/ $urlpart; done) 'sha1:61cb883b8 7b4ff8f95117463 cca5eff890639e8 3',) StaticTuple( 'sha1:53f99dc4d d7e3d7d3ed9f26f 6994c9b6c855468 1',)
17 common revisions to check (23 seen)
17 common inventories to check (23 seen)
disagree id_to_entry for <email address hidden>: StaticTuple(
Which is exactly the sort of error that bug produced.
For some reason when I scanned the NEWS entries for relevant fixes since 2.1.1 I missed that one.
So: next step is to get 2.1.1 upgraded to 2.1.3 (or 2.2.1 or 2.3) on that system. I'll file an RT.
Then we can either reset those imports again, or run "bzr reconcile --canonicalize-chks $repo" on all the affected repos with bzr 2.3. The latter is probably less disruptive if we can run 2.3 on the package-import system.
It's possible, perhaps likely, that other imports have old revisions with this inconsistency. It's probably good enough to just 'bzr reconcile --canonicalize- chks' those if/when they turn up.