Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 27 Dec 2017 22:13:55 +
Source: debian-policy
Binary: debian-policy
Architecture: all source
Version: 4.1.3.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Policy Editors
Changed-By: Sean Whitton
C
debian-policy_4.1.3.0_multi.changes uploaded successfully to localhost
along with the files:
debian-policy_4.1.3.0.dsc
debian-policy_4.1.3.0.tar.xz
debian-policy_4.1.3.0_all.deb
debian-policy_4.1.3.0_i386.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#882628: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #882628,
regarding base-files: Please ship CC0 in /usr/share/common-licences
to be marked as done.
This means that you claim that the pro
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#874095: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #874095,
regarding copyright-format: Use the “synopsis” term established in the
definition
to be marked as done.
This means that you cla
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#885219: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #885219,
regarding /lib64 provision added in 9.1.1 prohibits multilib libc
to be marked as done.
This means that you claim that the probl
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#882628: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #882628,
regarding debian-policy: Please add CC0-1.0 to common-licenses
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#688251: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #688251,
regarding Built-Using description too aggressive
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#874090: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #874090,
regarding debian-policy: Clarify wording of some passages
to be marked as done.
This means that you claim that the problem has b
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#661496: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #661496,
regarding Standardize how to disable an init script
to be marked as done.
This means that you claim that the problem has been de
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#859649: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #859649,
regarding base-files: Please ship CC0 in /usr/share/common-licences
to be marked as done.
This means that you claim that the pro
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#880992: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #880992,
regarding debian-policy should not recommend running editor using absolute path
to be marked as done.
This means that you claim
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#859649: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #859649,
regarding debian-policy: Please add CC0-1.0 to common-licenses
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#810381: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #810381,
regarding Update wording of 5.6.26 VCS-* fields to recommend encryption
to be marked as done.
This means that you claim that the
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#601455: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #601455,
regarding standard for disabling daemons in /etc/default
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#661496: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #661496,
regarding standard for disabling daemons in /etc/default
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#601455: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #601455,
regarding Standardize how to disable an init script
to be marked as done.
This means that you claim that the problem has been de
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#661496: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #661496,
regarding Standardize how to disable an init script
to be marked as done.
This means that you claim that the problem has been de
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#601455: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #601455,
regarding Standardize how to disable an init script
to be marked as done.
This means that you claim that the problem has been de
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#522163: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #522163,
regarding Standardize how to disable an init script
to be marked as done.
This means that you claim that the problem has been de
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#522163: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #522163,
regarding standard for disabling daemons in /etc/default
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 27 Dec 2017 22:48:45 +
with message-id
and subject line Bug#522163: fixed in debian-policy 4.1.3.0
has caused the Debian Bug report #522163,
regarding Standardize how to disable an init script
to be marked as done.
This means that you claim that the problem has been de
Sean Whitton writes:
> On Wed, Dec 27 2017, Russ Allbery wrote (to 601...@bugs.debian.org):
>> Tiny formatting nit: I usually prefer to put the double-colon at the
>> end of the previous paragraph when the literal text is introduced
>> explicitly by that package, instead of on a line by itself.
Bill Allombert writes:
> The point is that if there are licenses not in common-licenses that are
> much more common than CC0, it would make more sense to add them rather
> than CC0.
license-count says that CC0-1.0 looks pretty good. Here are the complete
results with patterns for CC0-1.0 added.
Jonathan Nieder writes:
> Markus Koschany wrote:
>> as discussed on debian-devel [1] I would like to request that more DFSG
>> licenses are added to /usr/share/common-licenses and that package
>> maintainers are allowed to reference them.
>>
>> License: OFL-1.1
>> Source: https://opensource.org/l
Jonathan Nieder writes:
> Markus Koschany wrote:
>> as discussed on debian-devel [1] I would like to request that more DFSG
>> licenses are added to /usr/share/common-licenses and that package
>> maintainers are allowed to reference them.
>> License: CC-BY-3.0
>> Source: https://creativecommons.
Jonathan Nieder writes:
> Markus Koschany wrote:
>> as discussed on debian-devel [1] I would like to request that more DFSG
>> licenses are added to /usr/share/common-licenses and that package
>> maintainers are allowed to reference them.
>> License: CC-BY-4.0
>> Source: https://creativecommons.
Bill Allombert writes:
> The time will be about the same. The real time is spent look at all the
> source files checking whether they do not carry different licences or
> license grants that the main file, which is actually very common, for
> example aclocal.m4. (yes, the ftp masters do that).
>
control: tag 601455 -patch +pending
Hello,
On Wed, Dec 27 2017, Russ Allbery wrote (to 601...@bugs.debian.org):
> Tiny formatting nit: I usually prefer to put the double-colon at the
> end of the previous paragraph when the literal text is introduced
> explicitly by that package, instead of on a
Processing control commands:
> tag 601455 -patch +pending
Bug #601455 [debian-policy] Standardize how to disable an init script
Bug #522163 [debian-policy] standard for disabling daemons in /etc/default
Bug #661496 [debian-policy] Standardize how to disable an init script
Removed tag(s) patch.
Rem
Processing control commands:
> tag -1 -patch +pending
Bug #688251 [debian-policy] Built-Using description too aggressive
Removed tag(s) patch.
Bug #688251 [debian-policy] Built-Using description too aggressive
Added tag(s) pending.
--
688251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688
control: tag -1 -patch +pending
Hello,
On Wed, Dec 27 2017, Jonathan Nieder wrote:
> Is this part just a line-wrapping change? If so, feel free to check
> it in directly to make the normative diff easier to review.
No: s/required part of the complete source/part of the complete source/.
I can
Sean Whitton writes:
> diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst
> index 7d9e20a..193e3d1 100644
> --- a/policy/ch-opersys.rst
> +++ b/policy/ch-opersys.rst
> @@ -537,6 +537,29 @@ and in your ``postrm``
> update-rc.d package remove
> fi
> +The default behaviour is
Control: tags -1 = pending
Jonathan Nieder writes:
> Russ Allbery wrote:
>> Allow libc to install files in /lib64
>> diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst
>> index 7d9e20a..d7c4956 100644
>> --- a/policy/ch-opersys.rst
>> +++ b/policy/ch-opersys.rst
>> @@ -35,7 +35,8 @@
Processing control commands:
> tags -1 = pending
Bug #885219 [debian-policy] /lib64 provision added in 9.1.1 prohibits multilib
libc
Added tag(s) pending; removed tag(s) patch.
--
885219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885219
Debian Bug Tracking System
Contact ow...@bugs.debi
Russ Allbery wrote:
> Allow libc to install files in /lib64
>
> diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst
> index 7d9e20a..d7c4956 100644
> --- a/policy/ch-opersys.rst
> +++ b/policy/ch-opersys.rst
> @@ -35,7 +35,8 @@ Debian Policy. The following exceptions to the FHS apply:
>
Hi,
Sean Whitton wrote:
> --- a/policy/ch-relationships.rst
> +++ b/policy/ch-relationships.rst @@ -598,17 +598,26 @@ earlier for
> binary packages) in order to invoke the targets in
> Additional source packages used to build the binary - ``Built-Using``
> --
Hello Sean,
On Wed, Dec 27, 2017 at 12:05:15PM +, Sean Whitton wrote:
[...]
> Andreas, Russ -- please considering seconding this updated text.
[...]
Seconded.
Regards,
Andreas Henriksson
control: tag -1 +patch
Hello,
Thank you to those who reviewed my patch and especially to Felipe for
patching init-system-helpers, and to Russ for writing the /etc/default
text (which I've tweaked only slightly).
I realised that a dependency on init-system-helpers (>= 1.5.0) is needed
if you're g
Processing control commands:
> tag -1 +patch
Bug #601455 [debian-policy] Standardize how to disable an init script
Bug #522163 [debian-policy] standard for disabling daemons in /etc/default
Bug #661496 [debian-policy] Standardize how to disable an init script
Added tag(s) patch.
Added tag(s) patch
Hello Andreas,
On Sun, Sep 10 2017, Andreas Henriksson wrote:
> I can't help myself but repeat that I'd prefer seeing more passive
> wording eg. instead of "instead add to your postinst" use something
> like "the postinst should contain" + a footnote about this normally
> being added by dh_... M
40 matches
Mail list logo
