launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #04543
Re: Results: derived distro mock-up testing round 2
On Wed, 1 Sep 2010 08:59:59 +0200, Michael Nelson <michael.nelson@xxxxxxxxxxxxx> wrote:
> I've not heard it discussed... but that could be a great idea. I think
> the soyuz diff generation was assumed because its what has always been
> used for package diffs (pre-dating package branches)... and I'd
> wrongly assumed we'd need diffs between the lucid and derilucid
> version).
Note that there may be some tweaks required to loggerhead to get the
features we need.
> The unknown factors for me so far are:
> 1) When a new version of a src package is published, are we
> guaranteed that the version is already committed to a bzr branch (for
> derived distros also) (for build from branch of course it is, but
> normal uploads?)
Guaranteed? No. The importer is quicker than the publisher, so it should
generally be true for distributions that it imports.
> 2) If I have a source publishing record in Launchpad, can I get
> directly to the bzr branch and rev number even if it hasn't been built
> via a recipe but is a standard upload (I'll follow that up if no-one
> beats me to it).
No, Launchpad has no facility to store that data as far as I know. It's
a simple mapping from (package, series, version) to (branch, tag)
though.
Thanks,
James
References