A flaw in the Daily Builds PPA concept

[Jelmer Vernooij]

On Thu, 2011-02-10 at 08:58 +0000, Max Bowsher wrote:
> On 10/02/11 08:40, Jelmer Vernooij wrote:
> > bOn Thu, 2011-02-10 at 08:17 +0000, Max Bowsher wrote:
> >> I've just realized a flaw in the Daily Builds PPA conceptually...
> >>
> >> It tries daily builds of bzr core, and of plugins, into the same PPA.
> >>
> >> Once you do a daily build of bzr.dev, it's incompatible with the trunk
> >> of most plugins. Oops.
> 
> > In what way do you mean? We should deprecate APIs first if they're used
> > by plugins, so a daily build of a newer revision of bzr.dev shouldn't be
> > able to break plugins.
> The breakage occurs for plugins that could probably work fine with
> bzr.dev, but declare a strict API requirement otherwise. The strict API
> requirement will usually be echoed in debian/control Build-Depends such
> that the package never actually builds at all.
The API requirements should no longer be strict - they should just cause
warnings rather than be strict errors.

If we hit package dependencies that are out of date we should fix them.

> > Besides one of the goals of the PPA being to provide nightly builds for
> > users, it's also to make sure that the packaging is complete (all
> > dependencies present, testsuite passing, etc).
> 
> Agreed, it's great for detecting bugs in the packaging of plugins
> themselves, but we don't want failed builds just because plugins' trunks
> haven't been marked as compatible with the latest incarnation of bzr.dev
> yet, because that will swamp us in irritating build failures which
> distract from real issues.
That's a valuable thing to know about, which we can fix in the packaging
branch.

Cheers,

Jelmer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110210/3463c2c7/attachment.pgp>