Sean Whitton writes:
> On Sun 17 Nov 2019 at 10:10AM -08, Russ Allbery wrote:
>> +* The term *may* and the adjective *optional* are sometimes used to
>> + clarify cases where it may otherwise appear that Policy is specifying a
>> + requirement or recommendation. These words describe decisions t
Hello,
On Sun 17 Nov 2019 at 10:29AM -08, Russ Allbery wrote:
> How about:
>
> This field should only be used when there are license or DFSG
> requirements to retain the referenced source package. It should not
> be added solely as a way to locate packages that need to be rebuilt
>
Hello Russ,
Thanks for this.
On Sun 17 Nov 2019 at 10:10AM -08, Russ Allbery wrote:
> +* The term *may* and the adjective *optional* are sometimes used to
> + clarify cases where it may otherwise appear that Policy is specifying a
> + requirement or recommendation. These words describe decisio
Russ Allbery writes:
> I think the current approach in the entirety of 9.11 no longer makes
> sense, but there are two possible alternative approaches and which to
> pick will depend on the results of the current GR. Therefore, I think
> we should for the results of the GR rather than doing work
Ansgar writes:
>>> 9.11 states:
>>>
>>> +---
>>> > Alternative init implementations must support running SysV init
>>> > scripts as described at System run levels and init.d scripts for
>>> > compatibility.
>>> +---
> Thinking a bit more about this, I think this requirement should just be
> rem
Guillem Jover writes:
> There's this text in section §9.2.1:
> ,---
> Packages other than "base-passwd" must not modify "/etc/passwd",
> "/etc/shadow", "/etc/group" or "/etc/gshadow".
> `---
> It's not clear to me, whether this refers to the packaging or any
> program provided by that p
Bastian Blank writes:
> On Sun, Nov 17, 2019 at 10:10:11AM -0800, Russ Allbery wrote:
>> +The Release Team may, at their discretion, downgrade a Policy requirement
>> +to a Policy recommendation for a given release of the Debian distribution.
>> +This may be done for only a specific package or fo
On Sun, Nov 17, 2019 at 10:10:11AM -0800, Russ Allbery wrote:
> +The Release Team may, at their discretion, downgrade a Policy requirement
> +to a Policy recommendation for a given release of the Debian distribution.
> +This may be done for only a specific package or for the archive as a
> +whole.
Control: tags -1 pending
Guillem Jover writes:
> Found this markup issue while going over the policy:
> - chapter 4, footnote [6], rendered as:
> ,---
> listed in the :ref:"`Maintainer" <#s-f-Maintainer` or "`Uploaders"
> ` control fields of the package), the first line of
>
Processing control commands:
> tags -1 pending
Bug #944332 [src:debian-policy] debian-policy: Broken markup in policy source
Added tag(s) pending.
--
944332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> reassign -1 python3-sphinx
Bug #944331 [debian-policy] debian-policy: Spurious space after dash in plain
text output
Bug reassigned from package 'debian-policy' to 'python3-sphinx'.
No longer marked as found in versions 4.4.1.
Ignoring request to alter fixed version
Control: reassign -1 python3-sphinx
Control: retitle -1 Spurious space after dash in plain text output
Control: affects -1 debian-policy
Guillem Jover writes:
> Noticed the following instances of spurious spaces after a dash, while
> skimming over the plain text policy document:
This seems to b
Control: reassign -1 python3-sphinx
Control: retitle -1 No way to disable line breaks at hyphens for text output
Control: affects -1 debian-policy
Guillem Jover writes:
> The rendering to plain text contain many technical terms, program
> names, email addresses, make rule names, etc., that have
Processing control commands:
> reassign -1 python3-sphinx
Bug #944330 [debian-policy] debian-policy: Hyphenation damage on plain text
output
Bug reassigned from package 'debian-policy' to 'python3-sphinx'.
No longer marked as found in versions 4.4.1.
Ignoring request to alter fixed versions of bu
Sean Whitton writes:
> diff --git a/policy/ch-relationships.rst b/policy/ch-relationships.rst
> index 140fdf1..8e4d98a 100644
> --- a/policy/ch-relationships.rst
> +++ b/policy/ch-relationships.rst
> @@ -661,11 +661,10 @@ field in its control file:
> Built-Using: grub2 (= 1.99-9), loadlin (
On Sun, Nov 17, 2019 at 10:10:11AM -0800, Russ Allbery wrote:
> Changes:
>
> * Add "prohibited" to the terms for requirements
> * Add another tier (Policy advice) using encouraged and discouraged
> * Stop confusing may and optional with wishlist bugs
> * Add terms for the collective set of Policy
Package: debian-policy
Version: 4.4.1.1
Severity: normal
In attempting to revise recent GRs to use the same terminology as
Policy, I got frustrated again by the lack of precision of our current
language. This is an attempt to make a minor improvement. It doesn't
go all the way to using all-caps
17 matches
Mail list logo
