Thursday, 5 December 2013

Re: Process bug: Silent -proposed migration failures

On Thu, Dec 05, 2013 at 04:26:50PM +0000, Iain Lane wrote:
> On Thu, Dec 05, 2013 at 11:22:22AM -0500, Barry Warsaw wrote:
> > On Dec 05, 2013, at 10:20 AM, Barry Warsaw wrote:

> > >The most serious is that no email notification is sent.

> > pitti says on IRC that we used to have email notifications for autopkgtest
> > failures, but they've been broken since the DC move. So, that's on the radar
> > and once it's fixed it'll address the most serious problem.

> It's only one reason packages fail to migrate, so it only partially
> solves the problem.

The three major causes of package migration failures are:

- package failing to build
- autopkgtest failures
- packages would be uninstallable if migrated

The first two of these should generate mails to the uploader (one does
currently, the other doesn't but that's a known bug that should be fixed).
The third is largely the responsibility of the release team and the +1
maintenance team to sort out; there's no sense in having proposed-migration
send periodic mails to say "your package hasn't migrated yet" when this
isn't something we expect the uploader to take action on.

Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer