Re: wanna-build access to schedule binNMUs for Go packages
On 01.02.2018 06:45, Salvatore Bonaccorso wrote:
> On Wed, Jan 31, 2018 at 09:04:09PM +0100, Michael Stapelberg wrote:
>> binNMUs for unstable.
>
> Why, if that is for unstable, permissions for embargoed
> queues/security would be needed? Is that due to implementtation on
> accessing wanna-build?
>
> Access to information about embargoed information would not be ok.
This is nothing new. It has always been that way. As soon as you have
write access to wanna-build, you can inspect all suites. Yes, that's
somewhat sad, but at the same time it shouldn't give you access to the
actual source packages.
The granularity that is still implemented but only used for ports are
per-arch access. wb_security implies access to all arches (wb_all) and
generally everyone who should be able to schedule binNMUs across
architectures needs to be in wb_all.
Precedent here was set by nomeata (at least), who schedules binNMUs for
OCaml and Haskell in unstable and hence required access across all
architectures. As long as we add persons relatively sparingly (the
request is for nother single person), I think we should be fine?
Kind regards and thanks
Philipp Kern
Reply to: