Wednesday, 13 November 2013

Re: Giving developers access to requeue package imports [Was: Ubuntu Platform developers BOF session?]

On Wed, Nov 13, 2013 at 07:17:56PM +0000, Dmitrijs Ledkovs wrote:
> On 13 November 2013 17:39, Andrew Starr-Bochicchio <[email protected]> wrote:
> > On Fri, Nov 8, 2013 at 1:33 PM, Andrew Starr-Bochicchio
> > <[email protected]> wrote:
> >> Though since we're talking about it, the one stop gap fix that would
> >> make me happy would be if all Ubuntu Developers could trigger the
> >> equivalent of the local 'requeue_package.py --full' command that UDD
> >> admins can run. Some history might get lost, but at least out of date
> >> branches could be made usable.

> > This seems to have been the topic that has generated the most
> > interest. It seems to be a bit of an overkill to have a vUDS session
> > on it, especially if we don't have the right people in the room. So
> > maybe we can try to hammer out the requirements here?

> > Currently you need shell access to Jubany in order to run the command.
> > [0] I know that this request has come up in the past, but my Google-fu
> > is failing me now. Adding the (seemingly dormant) UDD list to the
> > conversation in hopes of catching the right person.

> > [0] https://bugs.launchpad.net/udd/+bug/713719

> I requeue packages from time to time, upon request. But I don't keep a
> track of packages for which full requeue doesn't help.
> Nor have a good way to process such requests.

> Maybe a request wiki page? I'd subscribe to it, and would comment
> which one requeued and whether that fixes / not fixes the branch.

I would suggest using https://bugs.launchpad.net/udd/ itself for tracking
this.

But I think it would be more interesting to get a permanent fix for this
bug:

https://bugs.launchpad.net/udd/+bug/714622

This accounts for the problem people have mentioned, that core packages are
much more likely to have failed imports. The importer badly needs fixed to
not throw up its hands when the revision ID of a tag has changed; it should
only care about this when the branch contents are wrong.

This single bug accounts for just under half of all importer failures, and
is a failure scenario that the importer *could*, with sufficient smarts,
resolve automatically.

--
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 http://www.debian.org/
[email protected] [email protected]