Bug#775165: nmu: binutils-mingw-w64_2 (wheezy-security, wheezy-p-u)
On Mon, January 12, 2015 20:18, Ansgar Burchardt wrote:
> Hi,
>
> Thijs Kinkhorst <thijs@debian.org> writes:
>> Op maandag 12 januari 2015 19:18:28 schreef Adam D. Barratt:
>>> On Mon, 2015-01-12 at 19:15 +0100, Thijs Kinkhorst wrote:
>>> > This is not something we do very routinely, so I'd like to confirm:
>>> if
>>> > these binNMU's are triggered for stable-security, do they still end
>>> up
>>> > in the security-master queue so they can be released in a coordinated
>>> > way?
>>>
>>> I think so, but it's nothing something I've any experience with for the
>>> security archive either; might be worth confirming with ftp-master?
>>
>> Can you confirm: when triggering binNMU's for the security archive, do
>> these
>> end up in the embargoed queue so they can be released at a given moment
>> by
>> new-security-install, or are they installed immediately?
>
> They should[1] end up in the policy queue as long as no package with the
> same version number has been accepted yet (which can happen with binNMU
> version skew between architectures). In the latter case, you just have
> to make sure there are no ACCEPT(ED) comments for the uploads.
>
> Note that the archive requires the source package to already be in the
> target suite (or a base suite in case of overlays like p-u or
> experimental). In particular this means you cannot schedule binNMUs for
> the security archive for source packages not present there.
Thanks for the explanation. I'll add it to our documentation.
Stephen: the last sentence makes it clear that we'll need a sourceful
upload to security-master. Can you arrange for that?
Cheers,
Thijs
Reply to: