launchpad-dev team mailing list archive

[Michael Hudson-Doyle <michael.hudson@xxxxxxxxxxxxx>]

On Thu, 19 May 2011 12:05:48 +0100, 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.
> 
> 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?

For imports that are being done by bzr-git or bzr-svn, file RTs to get
the sysadmins to remove the cached copy of the bzr branch from escudero
(if that's still where they are).  If they are svn being done by cscvs,
probably they should be deleted and recreated as bzr-svn imports, for
cvs I guess the cached copy of the branch needs to have bzr upgrade run
on it.  The LOSAs should have docs on how to do all of these things
AIUI.

Cheers,
mwh