Comment 6 for bug 672389

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 672389] Re: bzr fast-import crashes on a dump produced by bzr fast-export

On Mon, 2010-11-08 at 10:57 +0000, Eric S. Raymond wrote:
> Jelmer Vernooij <email address hidden>:
> > On Mon, 2010-11-08 at 09:19 +0000, Eric S. Raymond wrote:
> > > Jelmer Vernooij <email address hidden>:
> > > > bzr fast-import crashes on a dump produced by bzr fast-export
> > > > https://bugs.launchpad.net/bugs/672389
> > > > You received this bug notification because you are a direct subscriber
> > > > of the bug.
> > >
> > > Where can I pull a version with the fix committed?
> > Of course, it helps when I actually remember to push the revision with
> > the fix... sorry about that.
> >
> > The fix should be present in lp:python-fastimport now (revision 294),
> > which I've just pushed.
>
> OK, I see that this is on a bzr branch. But I don't know how to install it.
> Is there a ppa I can subscribe to? If not, can you set one up?
I have a PPA with some bzr plugins packaged here:

https://code.launchpad.net/~jelmer/+archive/bzr-dailies

I've just requested new builds for python-fastimport and bzr-fastimport
that should hopefully kick off in the next hour. There are just packages
for Maverick at the moment, if you're running something else please let
me know and I'll add builds for that series as well.

> Explanation: I'm actually working on this:
>
> http://freshmeat.net/projects/reposurgeon
>
> I tripped over this bug while trying to extend reposurgeon support to
> bzr. I'd like to (a) verify this fix, and (b) finish the bzr suppport.
Ah, nice!

Since you're working on fastimport/fastexport streams you might also be
interested in the "VCS fast import/export developers" list at
https://launchpad.net/~vcs-fast-import-devs. The authors of the bzr, hg
and git fastexport/fastimport plugins hang out there. I wasn't aware of
reposurgeon and I'm not sure if the others are.

> If you're interested, I can also tell you how to make bzr-fast-export's
> version of the export stream format more closely compatible with git's.
> You don't have the whitespace in the format exactly right, but I can
> tell you how to fix that. (The difference shows up in my regression tests.)
As far as I know we're compliant with the spec, though I would be
interested to know in what way we're different from git's
fastexport/fastimport.

Cheers,

Jelmer