[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#885167: marked as done (release.debian.org: queue-viewer: ability to specify expected architectures for binNMUs)

Your message dated Tue, 03 Jul 2018 20:04:05 +0100
with message-id <1530644645.3658.37.camel@adam-barratt.org.uk>
and subject line Re: Bug#885167: release.debian.org: queue-viewer: ability to specify expected architectures for binNMUs
has caused the Debian Bug report #885167,
regarding release.debian.org: queue-viewer: ability to specify expected architectures for binNMUs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
885167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885167
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: tools
Severity: wishlist

When scheduling binNMUs in stable, it would be useful to be able to
indicate in some fashion which architectures were scheduled, so that
queue-viewer can make the usual missing / complete decisions while the
uploads are in stable-new. (Currently it assumes that a binNMU for any
single architecture is sufficient for acceptance.)

Regards,

Adam

--- End Message ---
--- Begin Message --- 
On Mon, 2017-12-25 at 17:30 +0300, Adam D. Barratt wrote:
> When scheduling binNMUs in stable, it would be useful to be able to
> indicate in some fashion which architectures were scheduled, so that
> queue-viewer can make the usual missing / complete decisions while
> the
> uploads are in stable-new. (Currently it assumes that a binNMU for
> any
> single architecture is sufficient for acceptance.)
> 

This can now be done by specifying an "expect_arches" metadata key in a
comment file (i.e. after the sig-sep in the file).

The value is expected to be a space-separated list of architectures for
which the binNMU has been scheduled.

Regards,

Adam

--- End Message ---
Reply to: