Bug#824495: Use of the Build-Conflicts field

Hello, On Fri 15 Feb 2019 at 08:59PM -0700, Sean Whitton wrote: > Use of the Build-Conflicts field is currently mostly optional, but Ian > Jackson and I have been working on text for Debian Policy that would > require its use in certain cases. See #824495 for the discussion. > > There are two ca

developers-reference_3.4.23_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 17 Feb 2019 13:44:03 +0100 Source: developers-reference Architecture: source Version: 3.4.23 Distribution: unstable Urgency: medium Maintainer: Developers Reference Maintainers Changed-By: Holger Levsen Closes:

Bug#483232: marked as done (developers-reference: Section 7.1.1 - please mention mass-bug)

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#483232: fixed in developers-reference 3.4.23 has caused the Debian Bug report #483232, regarding developers-reference: Section 7.1.1 - please mention mass-bug to be marked as done. This means that you claim th

Bug#430889: marked as done (developers-reference: Please don't suggest vim as an example to follow)

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#430889: fixed in developers-reference 3.4.23 has caused the Debian Bug report #430889, regarding developers-reference: Please don't suggest vim as an example to follow to be marked as done. This means that you

Bug#817914: marked as done (developers-reference: globally change "new maintainer" into "new member")

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#817914: fixed in developers-reference 3.4.23 has caused the Debian Bug report #817914, regarding developers-reference: globally change "new maintainer" into "new member" to be marked as done. This means that

Bug#839885: marked as done (developers-reference: reintroducing packages: update security issue metadata)

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#839885: fixed in developers-reference 3.4.23 has caused the Debian Bug report #839885, regarding developers-reference: reintroducing packages: update security issue metadata to be marked as done. This means t

Bug#908155: marked as done (Coordination with upstream developers not universally applied)

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#908155: fixed in developers-reference 3.4.23 has caused the Debian Bug report #908155, regarding Coordination with upstream developers not universally applied to be marked as done. This means that you claim th

Bug#855320: marked as done (developers-reference: Please do not recommend debrsign)

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#855320: fixed in developers-reference 3.4.23 has caused the Debian Bug report #855320, regarding developers-reference: Please do not recommend debrsign to be marked as done. This means that you claim that the

Bug#775740: marked as done (developers-reference: please clarify the recipients when sending to 123-submitter@b.d.o)

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#775740: fixed in developers-reference 3.4.23 has caused the Debian Bug report #775740, regarding developers-reference: please clarify the recipients when sending to 123-submitter@b.d.o to be marked as done. T

Bug#494470: marked as done (please mention dch/debchange in the appendix about debian maintainer tools)

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#494470: fixed in developers-reference 3.4.23 has caused the Debian Bug report #494470, regarding please mention dch/debchange in the appendix about debian maintainer tools to be marked as done. This means tha

Bug#376590: marked as done (developers-reference: suggests to test downgrading)

Your message dated Sun, 17 Feb 2019 13:34:11 + with message-id and subject line Bug#376590: fixed in developers-reference 3.4.23 has caused the Debian Bug report #376590, regarding developers-reference: suggests to test downgrading to be marked as done. This means that you claim that the prob

Processing of developers-reference_3.4.23_source.changes

developers-reference_3.4.23_source.changes uploaded successfully to localhost along with the files: developers-reference_3.4.23.dsc developers-reference_3.4.23.tar.xz developers-reference_3.4.23_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)