Per-pocket upload permissions

Scott Kitterman ubuntu at kitterman.com
Thu Jun 14 14:09:30 UTC 2012


On Thursday, June 14, 2012 12:37:46 PM Iain Lane wrote:
> Hi there,
> 
> On Thu, Jun 14, 2012 at 12:24:07PM +0100, Colin Watson wrote:
> > Hi folks,
> > 
> > My fix to https://bugs.launchpad.net/launchpad/+bug/914779 (second time
> > lucky) will hopefully be rolled out tomorrow, or failing that on Monday.
> > Once that's in place, I would like to add the following upload
> > 
> > permissions as suggested by Iain Lane:
> >   -backports: ~ubuntu-backporters
> >   -security: ~ubuntu-security
> > 
> > Iain also suggested -proposed/-updates: ~ubuntu-sru, but I don't think
> > that makes so much sense; ~ubuntu-sru has more of a queue admin kind of
> > role, so I'd prefer that to wait until I get round to a bit of follow-up
> > work to allow per-pocket queue admins.
> 
> Thanks for the work — this is a nice improvement. :-)
> 
> On this point, I can't be entirely sure (it was some time ago), but I
> suppose I was thinking that it would be good to ensure that SRU team
> members can use sru-release themselves, which requires upload privileges
> due to the use of copyPackage via the API if I'm not mistaken (only
> -updates would be needed here, not -proposed.  -proposed is probably not
> so useful, except if we want to ensure that they can sponsor all SRUs
> too).
> 
> If there's also another UNAPPROVED step there then just being able to
> upload doesn't gain much: queue admin would also be required.

Not that I get a vote, but I'm glad to see this landing.

I do think the ~ubuntu-sru ought to be able to accept to -proposed and copy to 
-updates for current/supported releases.  This would remove the need to make 
~ubuntu-sru members part of ~ubuntu-archive solely for the purpose of 
performing SRU processing.  I'm 100% agnostic on implementation.

Similarly (and I swear we've discussed this before and it's an an LP bug, but 
I can't find it) I think ~ubuntu-release ought to be able to accept to -release 
and -proposed, but only for the development release.  Similarly, that would 
remove the need for ~ubuntu-release members to be added to ~ubuntu-archive to 
process the queue during freezes.  My agnosticism about implementation applies 
to this as well.

Scott K



More information about the technical-board mailing list