debian-policy_4.4.1.2_source.changes ACCEPTED into unstable

2019-11-29 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Nov 2019 18:09:12 -0700 Source: debian-policy Architecture: source Version: 4.4.1.2 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Closes: 941194 941835 9438

Processing of debian-policy_4.4.1.2_source.changes

2019-11-29 Thread Debian FTP Masters
debian-policy_4.4.1.2_source.changes uploaded successfully to localhost along with the files: debian-policy_4.4.1.2.dsc debian-policy_4.4.1.2.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#941835: marked as done (debian-policy: drop mentioning of legacy manual in package description)

2019-11-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Nov 2019 01:34:08 + with message-id and subject line Bug#941835: fixed in debian-policy 4.4.1.2 has caused the Debian Bug report #941835, regarding debian-policy: drop mentioning of legacy manual in package description to be marked as done. This means that you claim

Bug#944407: marked as done (debian-policy: typo: multple → multiple)

2019-11-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Nov 2019 01:34:09 + with message-id and subject line Bug#944407: fixed in debian-policy 4.4.1.2 has caused the Debian Bug report #944407, regarding debian-policy: typo: multple → multiple to be marked as done. This means that you claim that the problem has been deal

Bug#944332: marked as done (debian-policy: Broken markup in policy source)

2019-11-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Nov 2019 01:34:09 + with message-id and subject line Bug#944332: fixed in debian-policy 4.4.1.2 has caused the Debian Bug report #944332, regarding debian-policy: Broken markup in policy source to be marked as done. This means that you claim that the problem has bee

Bug#944325: marked as done (please fix this unclear and obtuse phrasing in §7.8 (suggestion provided))

2019-11-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Nov 2019 01:34:09 + with message-id and subject line Bug#944325: fixed in debian-policy 4.4.1.2 has caused the Debian Bug report #944325, regarding please fix this unclear and obtuse phrasing in §7.8 (suggestion provided) to be marked as done. This means that you c

Bug#943880: marked as done (debian-policy: extraneous whitespace in chapter 9 footnote )

2019-11-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Nov 2019 01:34:09 + with message-id and subject line Bug#943880: fixed in debian-policy 4.4.1.2 has caused the Debian Bug report #943880, regarding debian-policy: extraneous whitespace in chapter 9 footnote to be marked as done. This means that you claim that the p

Bug#941194: marked as done (initscripts: remove some implementation details)

2019-11-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Nov 2019 01:34:08 + with message-id and subject line Bug#941194: fixed in debian-policy 4.4.1.2 has caused the Debian Bug report #941194, regarding initscripts: remove some implementation details to be marked as done. This means that you claim that the problem has b

Bug#944325: please fix this unclear and obtuse phrasing in §7.8 (suggestion provided)

2019-11-29 Thread Sean Whitton
control: tag -1 +pending Hello Nicholas, On Fri 29 Nov 2019 at 01:26PM -05, Nicholas D Steeves wrote: > At any rate, I've submitted an update MR here (see previous email for > extended rationale): > > https://salsa.debian.org/sten-guest/policy/merge_requests/3 Thank you for preparing a patch.

Processed: Re: Bug#944325: please fix this unclear and obtuse phrasing in §7.8 (suggestion provided)

2019-11-29 Thread Debian Bug Tracking System
Processing control commands: > tag -1 +pending Bug #944325 [debian-policy] please fix this unclear and obtuse phrasing in §7.8 (suggestion provided) Added tag(s) pending. -- 944325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944325 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#944325: please fix this unclear and obtuse phrasing in §7.8 (suggestion provided)

2019-11-29 Thread Nicholas D Steeves
Hi Sean, Sean Whitton writes: > Hello Nicholas, > > I am not sure what is going on with your (1), (2) and (3). Perhaps you > could propose your change in the form of a patch. > Those numbers refer to annotations in the quoted portion. IIRC you're also using notmuch mode, so [ x more citati

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2019-11-29 Thread Russ Allbery
Guillem Jover writes: > As I mentioned on debian-devel, I think major parts of this and of the > sysuser stuff fall under dpkg realm. And my plan is to implement this > kind of functionality natively in dpkg, regardless of whatever the > outcome of that GR is. > Of course some parts of the funct

Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2019-11-29 Thread Guillem Jover
On Fri, 2019-11-22 at 10:12:06 -0800, Russ Allbery wrote: > Ansgar writes: > > I think no option says we shouldn't use services that don't rely on > > systemd as pid-1 (which also includes widely used things like udev). > > I agree, but if, say, Sam's option 3 wins, we can directly incorporate >

developers-reference_11.0.7_source.changes ACCEPTED into unstable

2019-11-29 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 29 Nov 2019 11:33:47 +0100 Source: developers-reference Architecture: source Version: 11.0.7 Distribution: unstable Urgency: medium Maintainer: Developers Reference Maintainers Changed-By: Holger Levsen Closes:

Processing of developers-reference_11.0.7_source.changes

2019-11-29 Thread Debian FTP Masters
developers-reference_11.0.7_source.changes uploaded successfully to localhost along with the files: developers-reference_11.0.7.dsc developers-reference_11.0.7.tar.xz developers-reference_11.0.7_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#623707: marked as done (Outdated section on l10n)

2019-11-29 Thread Debian Bug Tracking System
Your message dated Fri, 29 Nov 2019 11:19:21 + with message-id and subject line Bug#623707: fixed in developers-reference 11.0.7 has caused the Debian Bug report #623707, regarding Outdated section on l10n to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#904246: marked as done (developers-reference: section 6.4 should recommend command -v, not which)

2019-11-29 Thread Debian Bug Tracking System
Your message dated Fri, 29 Nov 2019 11:19:21 + with message-id and subject line Bug#904246: fixed in developers-reference 11.0.7 has caused the Debian Bug report #904246, regarding developers-reference: section 6.4 should recommend command -v, not which to be marked as done. This means that