On Mon, Nov 16, 2009 at 03:38:52AM +0100, Jelmer Vernooij wrote:
> What sort of problems did you hit the second time around?
It dies with:
bzr: ERROR: Revision {[('term/i386/pc/at__keyboard.c',
'svn-v3-single1-dHJ1bmsvZ3J1YjI.:d0de0278-0dc1-4c01-8a07-af38b3205e46:trunk%2Fgrub2:2613')]}
not present in "KnitVersionedFiles(_KnitGraphIndex(CombinedGraphIndex()),
<bzrlib.knit._DirectPackAccess object at 0x3241590>)".
> Were all of the bzr: revision and file properties before you had problems
> with this repository the second time, and were all of the caches/old bzr
> repositories removed? Perhaps this was just another problem created by the
> invalid data set by the older version of bzr-svn?
Yes. We were careful not to merge anything from the broken repositories.
In case you want to check, a snapshot of the server after second breakage
is available:
http://people.debian.org/~rmh/grub/bzr-backup2/
Should I file a new bug in upstream?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
