launchpad-dev team mailing list archive

[Martin Pool <mbp@xxxxxxxxxxxxx>]

On 19 May 2011 12:05, Jelmer Vernooij <jelmer.vernooij@xxxxxxxxxxxxx> wrote:
> Hi,
>
> Various import branches in Launchpad are currently still imported to
> older formats of Bazaar. This makes it tricky to use them inside of
> recipes, and much slower to fetch. For example, there are a fair number
> of GNOME upstream branches that are still in a pre-2a format, making it
> harder to do daily builds of GNOME.
>
> The problem with recipes is that they will fall over if e.g. the root
> branch format doesn't support rich roots but one of the other branches
> that is merged in does.
>
> The main risk in upgrading will be that there could still be users that
> are running older (pre bzr-1.16) versions of bzr who can not fetch
> branches in the 2a format. Of the currently supported Ubuntu releases,
> only Dapper and Hardy ship a version of bzr that can't read this format.

Those old clients are not going to be able to read the majority of
branches on Launchpad.  We need to help users move forward (eg
advertising and supporting the ppa), not hold back a fairly arbitrary
set of branches.

> Would it be reasonable to have some of these branches upgraded to the 2a
> format,

Yes.

> and what can I do do make this happen?

I don't know how this maps to Launchpad's current process.  Non-code
issues are not meant to be in bugs, but this also does not seem like
the kind of thing a losa could just do from an RT without developer
involvement.  Raising it here was a good step - thanks.

Martin