On Thu, 2011-04-14 at 01:18 +0000, Andrew Cowie wrote:
> Just received bzr-git 0.6.0 via PPA, so tried again per comment #7. It
> still crashes with:
>
> AssertionError: Invalid sha for <Commit
> 87a5d4f4faa9b24bace2bd1d74cbbbfbc87c5e95>:
> c8df83a2fee148d871b36ca5ac742dc566c64612
>
> You can presumably duplicate this if you do:
>
> $ bzr clone git://git.gnome.org/gtk+
>
> It's a public respository.
As I mentioned earlier, I can't reproduce this when cloning into a fresh
repository:
So the problem is most likely revisions that already are present in your
shared repository. Can you reproduce this problem outside of a shared
repository?
On Thu, 2011-04-14 at 01:18 +0000, Andrew Cowie wrote: bace2bd1d74cbbb fbc87c5e95> : 871b36ca5ac742d c566c64612 gnome.org/ gtk+
> Just received bzr-git 0.6.0 via PPA, so tried again per comment #7. It
> still crashes with:
>
> AssertionError: Invalid sha for <Commit
> 87a5d4f4faa9b24
> c8df83a2fee148d
>
> You can presumably duplicate this if you do:
>
> $ bzr clone git://git.
>
> It's a public respository.
As I mentioned earlier, I can't reproduce this when cloning into a fresh
repository:
charis:~/tmp% BZR_PDB=1 bzr clone git://git. gnome.org/ gtk+
Branched 23346 revision(s).
So the problem is most likely revisions that already are present in your
shared repository. Can you reproduce this problem outside of a shared
repository?
status incomplete
Cheers,
Jelmer