Comment 4 for bug 378828

Thanks for fixing that.

On Wed, 2009-05-20 at 22:33 +0000, Celso Providelo wrote:
> There were 2 build records in inconsistent state blocking the `buildd-
> retry-depwait` script:
>
> https://edge.launchpad.net/~cdekter/+archive/ppa/+build/1032562
> https://edge.launchpad.net/~cdekter/+archive/ppa/+build/1032563
>
> (source originally targeted to 'contrib' was deleted before and left 2
> depwait builds behind)

How did that happen? I see it in debian/control, but aren't PPA uploads
automatically overridden to main? The source is in main - is this some
strangeness with the magic option to follow primary archive components?
But I don't see autokey in Debian or Ubuntu.

> First, we should setup a proper cronscript watch for it (we should have
> been warned if the didn't run each hour). Second we should support this
> scenario, it's legitimate.

How is it legitimate? A build with a component not in its archive's
distribution doesn't make sense.

--
William Grant