launchpad-dev team mailing list archive

[Max Bowsher <maxb@xxxxxxx>]

Barry Warsaw wrote:
> 2. "different rich-roots" nightmare
> 
> So I do the most obvious thing possible:
> 
> % bzr init-repo launchpadlib
> % cd launchpadlib
> % bzr branch lp:launchpadlib
> % bzr branch launchpadlib fix-thing
> % cd fix-thing
> % <hack> <hack> <hack>
> % bzr commit
> % bzr push lp:~barry/launchpadlib/fix-thing
> <some ugly output, then...>
> different rich-root-support
> and BOOM!
> 
> The problem is caused by the first step, where I inadvertently created a
> --2a repo, and by the third step where an apparently incompatible format
> branch was transparently upgraded.  By the time I try to publish my
> branch, I've already been screwed but I don't know it.  Of course by now
> I've spent all the time I could spare just getting the code working and
> now I'm dead in the water with no way out.  A normal person will have no
> idea how to repair the problem and will likely just abandon this nice
> helpful fix they've got.  Everyone loses.
> 
> I know I've complained about this before, but I fear that if we do not
> address this problem, we're going to piss off a lot of developers, and
> worse simply (and probably silently) lose lots of good contributions to
> the open source ecosystem.
> 
> Is there anything on the horizon to fix this issue?  I'm happy to file
> bugs if it will help.

Surely this is a pure Bazaar problem, rather than anything unique to
Launchpad?

Hmm... it would be nifty if "bzr init-repo" would create a repository
with format "undecided" which would lazily transform into pack-0.92 or
2a depending on the rich-root-ness of the first revision being entered
into it :-)

Max.

Attachment: signature.asc
Description: OpenPGP digital signature