--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [copyright-format] English proofreading.
- From: Charles Plessy <plessy@debian.org>
- Date: Fri, 11 Nov 2011 08:36:14 +0900
- Message-id: <20111110233614.GA17469@merveille.plessy.net>
- In-reply-to: <20111110172813.GA11644@xibalba.demon.co.uk>
- References: <20111110140844.GA16389@merveille.plessy.net> <20111110172813.GA11644@xibalba.demon.co.uk>
Package: debian-policy
Version: 3.9.2
Severity: wishlist
X-Debbugs-CC: debian-l10n-english@lists.debian.org
Dear Justin and everybody,
thanks a lot Justin for the proofreading. I read it in details and agree with
all the changes you propose. I therefore propose to the debian-policy team to
apply your patch. To consolidate related changes, let's wait however a little
for additional propositions. For instance, I would like to suggest to replace
“dash” by “hyphen”, so that grepping the source files of the debian-policy
package would conveniently return only lines about the shell called “dash”.
Have a nice day,
-- Charles Plessy, Tsurumi, Kanagawa, Japan
Le Thu, Nov 10, 2011 at 05:28:13PM +0000, Justin B Rye a écrit :
> Charles Plessy wrote:
> > Subject: Re: Can you proofread DEP 5 ?
>
> No space before a question mark! Okay; inline comments, attached
> patch and modified version.
>
> > <?xml version="1.0" encoding="utf-8"?>
> > <?xml-stylesheet type="text/xsl"
> > href="http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl";?>
> [...]
> > <abstract>
> > <para>
> > This specification was drafted as <ulink
> > url="http://dep.debian.net/deps/dep5/";>DEP-5</ulink>, to establish a
> > standard, machine-readable format for
> > <filename>debian/copyright</filename> files within packages and
> > facilitate automated checking and reporting of licenses for packages and
> > sets of packages.
> > </para>
> > </abstract>
> > </articleinfo>
>
> I suppose "was drafted" is valid, it's just a pity that getting
> drafted is also something that happens to people in wartime. I would
> suggest using "was drawn up".
>
> It would be slightly easier to keep track of the syntax with an extra
> "to": "to establish [...] and ^to^ facilitate [...]".
>
> > <section id="rationale">
> [...]
> > <para>
> > A user might want to have a way to avoid software with certain licenses
> > they have a problem with, even if the licenses are DFSG-free. For example,
> > the Affero GPL.
> > </para>
>
> I think after all the paragraphs about conflict-spotting this one
> would fit in more smoothly with a bit of shuffling:
>
> <para>
> Even where licenses are DFSG-free and mutually compatible, users might want
> a way to avoid software with certain licenses, for example if they have a
> problem with the Affero GPL.
> </para>
>
> Then in the syntax section at last we get a definite syntax error:
>
> > <para>
> > There are four kinds values for fields. Each field specifies which kind
> > is allowed.
> > </para>
>
> "Four kinds of values". But I'm not sure I follow this, unless it
> simply means:
>
> <para>
> Each field must have one of the following four types of value.
> </para>
>
> > <section id="single-line">
> > <title>Single-line values</title>
> > <para>
> > A single-line value means that the whole value of a field must fit on a
> > single line. For example, the <varname>Format</varname> field has a
> > single line value specifying the version of the machine-readable format
> > that is used.
> > </para>
> > </section>
>
> A single-line value doesn't mean that; the term "single-line value"
> means that. Or to simplify, "This means..."
>
> And I suppose since I'm here to nitpick I should make this
> consistently hyphenated as "single-line".
>
> > <section id="white-space-lists">
> > <title>White space separated lists</title>
> > <para>
> > A white space separated list means that the field value may be on one
> > line or many, but values in the list are separated by one or more white
> > space characters (including space, TAB, and newline). For example, the
> > <varname>Files</varname> field has a list of filename patterns.
> > </para>
> > </section>
>
> Again, "This means". And you mean "Whitespace-separated" (here and
> elsewhere); "white space" is a graphic design term, not a category of
> character.
>
> > <section id="line-based-lists">
> > <title>Line based lists</title>
> > <para>
> > Another kind of list value has one value per line. For example,
> > <varname>Copyright</varname> can list many copyright statements, one per
> > line.
> > </para>
> > </section>
>
> Again, "line-based" (also where this format is mentioned below).
>
> > <section id="formatted-text">
> > <title>Text formatted like package long descriptions</title>
> > <para>
> > Formatted text fields use the same rules as the long description in a
> > package's <varname>Description</varname> field, possibly also using the
> > first line as a synopsis, like <varname>Description</varname> uses it
> > for the short description. See Debian Policy's section 5.6.13, <ulink
> > url="http://www.debian.org/doc/debian-policy/ch-controlfields#s-f-Description";><quote>Description</quote></ulink>,
> > for details. For example, <varname>Disclaimer</varname> has no special
> > first line, whereas <varname>License</varname> does.
> > </para>
> > </section>
> > </section>
>
> That use of "like" plus verb phrase (i.e. as in the <para> but not the
> <title>) is sometimes deprecated as colloquial; substitute "just as".
>
> > <section id="paragraphs">
> > <title>Paragraphs</title>
> > <para>
> > There are three kinds of paragraphs: the first one is called the
> > <link linkend="header-paragraph">header paragraph</link>. Every other
> > paragraph is either a <link linkend="files-paragraph">Files</link>
> > paragraph or a <link linkend="stand-alone-license-paragraph">stand-alone
> > license</link> paragraph. This is similar to source and binary package
> > paragraphs in <filename>debian/control</filename> files.
> > </para>
>
> I'd be inclined to say "standalone", and in fact I see that used below.
>
> >
> > <section id="header-paragraph">
> > <title>Header paragraph (Once)</title>
>
> That should be uncapitalised "(once)".
>
> > <section id="format-header-field">
> > <title><varname>Format</varname></title>
> > <para>
> > Required single line: URI of the format specification, such as:
> > <literal>http://www.debian.org/doc/copyright-format/1.0</literal>
> > </para>
> > </section>
>
> Multiple colons isn't as bad as it sounds, but still, drop the second.
>
> [...]
> > <section id="source-header-field">
> > <title><varname>Source</varname></title>
> > <para>
> > Optional formatted text, no synopsis: an explanation from where the
> of
> > upstream source came from. Typically this would be a URL, but it might
>
> [...]
> > <section id="license-header-field">
> > <title><varname>License</varname></title>
> > <para>
> > Optional formatted text, with synopsis: in the header paragraph
> > (no <varname>Files</varname> specification), this field gives the
> > license information for the package as a whole, which may be different
> > or simplified from a combination of all the per-file license
> > information. <varname>License</varname> below in the <link
> > linkend="files-paragraph">Files paragraph</link> section.
> > </para>
> > </section>
>
> I think there's a missing "See also" in the final sentence.
>
> [...]
> > <section id="files-paragraph">
> > <title>Files paragraph (Repeatable)</title>
>
> Again, uncapitalised: "(repeatable)".
>
> > <para>
> > The declaration of copyright and license for files is done in one or
> > more paragraphs. In the simplest case, a single paragraph can be used
> > which applies to all files and lists all applicable copyrights and
> > licenses.
> > </para>
>
> "Is done" is a slightly odd way of phrasing it. How about "may
> consist of"?
>
> [...]
> > <para>
> > Multiple <varname>Files</varname> paragraphs are allowed. The last
> > paragraph that matches a particular file applies to it.
> > </para>
> > <para>
> > Exclusions are done by having multiple <varname>Files</varname>
> > paragraphs.
> > </para>
> > </section>
>
> I take it this means something like:
>
> Exclusions are only supported by adding <varname>Files</varname>
> paragraphs to override the previous match.
>
> [...]
> > <para>
> > Remaining lines: if left blank here, the file
> > <emphasis>must</emphasis> include a stand-alone
> > <varname>License</varname> paragraph matching each license short
> > name listed on the first line (see the <link
>
> s/if left blank here/if these are omitted/, because it isn't the file
> that's left blank and the lines that are omitted aren't here.
>
> [...]
> > <section id="stand-alone-license-paragraph">
> > <title>Standalone License Paragraph (Optional, Repeatable)</title>
>
> An outbreak of surplus capitalisation.
>
> > <para>
> > Where a set of files are dual (tri, etc) licensed, or when the same
> > license occurs multiple times, you can use a single line
> > <varname>License</varname> field and standalone
> > <varname>License</varname> paragraphs to expand the license short names.
> > </para>
>
> "Dual-licensed" ought to be hyphenated, which leads to trouble with
> the intervening parenthesis. Perhaps it should be
>
> Where a set of files are covered by multiple licenses, or one
> license occurs multiple times, you can use a single line
>
> [...]
> > <para>
> > For licenses which have multiple versions in use, the version number is
> > added, using a dash as a separator. If omitted, the lowest version
> > number is implied. When the license grant permits using the terms of any
> > later version of that license, the short name is finished with a plus
> > sign. For <link linkend="spdx">SPDX</link> compatibility, trailing
> > <emphasis>dot-zeroes</emphasis> are considered to be equal to plainer
> > version (e.g., <quote>2.0.0</quote> is considered equal to
> > <quote>2.0</quote> and <quote>2</quote>).
> > </para>
>
> "Plainer version" isn't entirely self-explanatory; I suppose with the
> examples it's fair enough, but I would prefer something like "versions
> with trailing <emphasis>dot-zeroes</emphasis> are considered to be
> equivalent to versions without".
>
> [...]
> > <row>
> > <entry>
> > CC-BY-SA
> > </entry>
> > <entry>
> > Creative Commons Attribution Share Alike license
> > <ulink url="http://spdx.org/licenses/CC-BY-SA-1.0";>1.0</ulink>,
> > <ulink url="http://spdx.org/licenses/CC-BY-SA-2.0";>2.0</ulink>,
> > <ulink url="http://spdx.org/licenses/CC-BY-SA-2.5";>2.5</ulink>,
> > <ulink url="http://spdx.org/licenses/CC-BY-SA-3.0";>3.0</ulink>.
> > </entry>
> > </row>
>
> spdx.org is down just now, but creativecommons.org consistently
> expands this as "Attribution-ShareAlike", ND as "NoDerivs", and NC as
> "NonCommercial". Then again, creativecommons.org seems to spell
> CC-BY-SA etc without the first hyphen, and nobody pays any attention
> to that, so never mind.
>
> [...]
> > <para>
> > Exceptions and clarifications are signaled in plain text, by appending
> > <literal>with <varname><replaceable>keywords</replaceable></varname>
> > exception</literal> to the short name. This document provides a list of
> > keywords that refer to the most frequent exceptions.
> > </para>
>
> If we're standardising to en_GB that's "signalled".
>
> [...]
>
> > For more information, see <ulink
> > url="http://www.gnome.org/~markmc/openssl-and-the-gpl";>The -OpenSSL License and
> > The GPL</ulink> by Mark
>
> Oops, surplus hyphen; plain "OpenSSL".
>
> [...]
> > For the most complex cases, the comma is used to disambiguate the
> > priority of <literal>or</literal>s and <literal>and</literal>s
>
> Should there be a break (maybe just a semicolon) here?
>
> > <literal>and</literal> has the priority over <literal>or</literal>,
> > unless preceded by a comma. For instance:
> [...]
>
> --
> JBR with qualifications in linguistics, experience as a Debian
> sysadmin, and probably no clue about this particular package
--- copyright-format_copyright-format.xml.pristine 2011-11-10 14:56:55.883165353 +0000
+++ copyright-format_copyright-format.xml 2011-11-10 17:23:08.967498468 +0000
@@ -25,10 +25,10 @@
</legalnotice>
<abstract>
<para>
- This specification was drafted as <ulink
+ This specification was drawn up as <ulink
url="http://dep.debian.net/deps/dep5/";>DEP-5</ulink>, to establish a
standard, machine-readable format for
- <filename>debian/copyright</filename> files within packages and
+ <filename>debian/copyright</filename> files within packages and to
facilitate automated checking and reporting of licenses for packages and
sets of packages.
</para>
@@ -81,9 +81,9 @@
no way to know how much of Debian should be stripped from such a system.
</para>
<para>
- A user might want to have a way to avoid software with certain licenses
- they have a problem with, even if the licenses are DFSG-free. For example,
- the Affero GPL.
+ Even where licenses are DFSG-free and mutually compatible, users might want
+ a way to avoid software with certain licenses, for example if they have a
+ problem with the Affero GPL.
</para>
</section>
@@ -121,32 +121,31 @@
avoid conflicting specifications for widely used extra fields.
</para>
<para>
- There are four kinds values for fields. Each field specifies which kind
- is allowed.
+ Each field must have one of the following four types of value.
</para>
<section id="single-line">
<title>Single-line values</title>
<para>
- A single-line value means that the whole value of a field must fit on a
+ This means that the whole value of a field must fit on a
single line. For example, the <varname>Format</varname> field has a
- single line value specifying the version of the machine-readable format
+ single-line value specifying the version of the machine-readable format
that is used.
</para>
</section>
<section id="white-space-lists">
- <title>White space separated lists</title>
+ <title>Whitespace-separated lists</title>
<para>
- A white space separated list means that the field value may be on one
- line or many, but values in the list are separated by one or more white
- space characters (including space, TAB, and newline). For example, the
+ This means that the field value may be on one
+ line or many, but values in the list are separated by one or more
+ whitespace characters (including space, TAB, and newline). For example, the
<varname>Files</varname> field has a list of filename patterns.
</para>
</section>
<section id="line-based-lists">
- <title>Line based lists</title>
+ <title>Line-based lists</title>
<para>
Another kind of list value has one value per line. For example,
<varname>Copyright</varname> can list many copyright statements, one per
@@ -159,7 +158,7 @@
<para>
Formatted text fields use the same rules as the long description in a
package's <varname>Description</varname> field, possibly also using the
- first line as a synopsis, like <varname>Description</varname> uses it
+ first line as a synopsis, just as <varname>Description</varname> uses it
for the short description. See Debian Policy's section 5.6.13, <ulink
url="http://www.debian.org/doc/debian-policy/ch-controlfields#s-f-Description";><quote>Description</quote></ulink>,
for details. For example, <varname>Disclaimer</varname> has no special
@@ -174,17 +173,17 @@
There are three kinds of paragraphs: the first one is called the
<link linkend="header-paragraph">header paragraph</link>. Every other
paragraph is either a <link linkend="files-paragraph">Files</link>
- paragraph or a <link linkend="stand-alone-license-paragraph">stand-alone
+ paragraph or a <link linkend="stand-alone-license-paragraph">standalone
license</link> paragraph. This is similar to source and binary package
paragraphs in <filename>debian/control</filename> files.
</para>
<section id="header-paragraph">
- <title>Header paragraph (Once)</title>
+ <title>Header paragraph (once)</title>
<section id="format-header-field">
<title><varname>Format</varname></title>
<para>
- Required single line: URI of the format specification, such as:
+ Required single line: URI of the format specification, such as
<literal>http://www.debian.org/doc/copyright-format/1.0</literal>
</para>
</section>
@@ -199,7 +198,7 @@
<section id="upstream-contact-header-field">
<title><varname>Upstream-Contact</varname></title>
<para>
- Optional line based list: the preferred address(es) to reach the
+ Optional line-based list: the preferred address(es) to reach the
upstream project. May be free-form text, but by convention will
usually be written as a list of RFC5322 addresses or URIs.
</para>
@@ -208,7 +207,7 @@
<section id="source-header-field">
<title><varname>Source</varname></title>
<para>
- Optional formatted text, no synopsis: an explanation from where the
+ Optional formatted text, no synopsis: an explanation of where the
upstream source came from. Typically this would be a URL, but it might
be a free-form explanation. The Debian Policy section <ulink
url="http://www.debian.org/doc/debian-policy/ch-docs#s-copyrightfile";>12.5</ulink>
@@ -247,7 +246,7 @@
(no <varname>Files</varname> specification), this field gives the
license information for the package as a whole, which may be different
or simplified from a combination of all the per-file license
- information. <varname>License</varname> below in the <link
+ information. See also <varname>License</varname> below in the <link
linkend="files-paragraph">Files paragraph</link> section.
</para>
</section>
@@ -255,7 +254,7 @@
<section id="copyright-header-field">
<title><varname>Copyright</varname></title>
<para>
- Optional line based list: in the header paragraph (no
+ Optional line-based list: in the header paragraph (no
<varname>Files</varname> specification), this field gives the
copyright information for the package as a whole, which may be
different or simplified from a combination of all the per-file
@@ -286,9 +285,9 @@
</section>
<section id="files-paragraph">
- <title>Files paragraph (Repeatable)</title>
+ <title>Files paragraph (repeatable)</title>
<para>
- The declaration of copyright and license for files is done in one or
+ The declaration of copyright and license for files may consistof one or
more paragraphs. In the simplest case, a single paragraph can be used
which applies to all files and lists all applicable copyrights and
licenses.
@@ -297,7 +296,7 @@
<section id="files-files-field">
<title><varname>Files</varname></title>
<para>
- Required white space separated list: list of patterns indicating files
+ Required whitespace-separated list: list of patterns indicating files
covered by the license and copyright specified in this paragraph.
</para>
<para>
@@ -360,15 +359,15 @@
paragraph that matches a particular file applies to it.
</para>
<para>
- Exclusions are done by having multiple <varname>Files</varname>
- paragraphs.
+ Exclusions are only supported by adding <varname>Files</varname>
+ paragraphs to override the previous match.
</para>
</section>
<section id="copyright-files-field">
<title><varname>Copyright</varname></title>
<para>
- Required line based list: one or more free-form copyright
+ Required line-based list: one or more free-form copyright
statement(s), one per line, that apply to the files matched by the
above pattern. If a work has no copyright holder (i.e., it is in
the public domain), that information should be recorded here.
@@ -413,8 +412,8 @@
copyright file.
</para>
<para>
- Remaining lines: if left blank here, the file
- <emphasis>must</emphasis> include a stand-alone
+ Remaining lines: if these are omitted, the file
+ <emphasis>must</emphasis> include a standalone
<varname>License</varname> paragraph matching each license short
name listed on the first line (see the <link
linkend="stand-alone-license-paragraph">Standalone License
@@ -467,10 +466,10 @@
</section>
<section id="stand-alone-license-paragraph">
- <title>Standalone License Paragraph (Optional, Repeatable)</title>
+ <title>Standalone license paragraph (optional, repeatable)</title>
<para>
- Where a set of files are dual (tri, etc) licensed, or when the same
- license occurs multiple times, you can use a single line
+ Where a set of files are covered by multiple licenses, or one
+ license occurs multiple times, you can use a single-line
<varname>License</varname> field and standalone
<varname>License</varname> paragraphs to expand the license short names.
</para>
@@ -541,7 +540,7 @@
<filename>debian/copyright</filename>, nor any requirements in the
license of the work regarding reproduction of legal notices. This
information must still be included in the <varname>License</varname>
- field, either in a stand-alone license paragraph or in the relevant
+ field, either in a standalone license paragraph or in the relevant
files paragraph.
</para>
<para>
@@ -549,9 +548,9 @@
added, using a dash as a separator. If omitted, the lowest version
number is implied. When the license grant permits using the terms of any
later version of that license, the short name is finished with a plus
- sign. For <link linkend="spdx">SPDX</link> compatibility, trailing
- <emphasis>dot-zeroes</emphasis> are considered to be equal to plainer
- version (e.g., <quote>2.0.0</quote> is considered equal to
+ sign. For <link linkend="spdx">SPDX</link> compatibility, versions with trailing
+ <emphasis>dot-zeroes</emphasis> are considered to be equivalent to
+ versions without (e.g., <quote>2.0.0</quote> is considered equal to
<quote>2.0</quote> and <quote>2</quote>).
</para>
<para>
@@ -885,7 +884,7 @@
matches.
</para>
<para>
- Exceptions and clarifications are signaled in plain text, by appending
+ Exceptions and clarifications are signalled in plain text, by appending
<literal>with <varname><replaceable>keywords</replaceable></varname>
exception</literal> to the short name. This document provides a list of
keywords that refer to the most frequent exceptions.
@@ -910,7 +909,7 @@
The GPL <literal>OpenSSL</literal> exception gives permission to link GPL-licensed
code with the OpenSSL library, which contains GPL-incompatible clauses.
For more information, see <ulink
-url="http://www.gnome.org/~markmc/openssl-and-the-gpl";>The -OpenSSL License and
+url="http://www.gnome.org/~markmc/openssl-and-the-gpl";>The OpenSSL License and
The GPL</ulink> by Mark
McLoughlin and the message <ulink
url="http://lists.debian.org/debian-legal/2004/05/msg00595.html";>middleman
@@ -981,7 +980,7 @@
This is for a file that has both GPL and classic BSD code in it:
<programlisting>License: GPL-2+ and BSD</programlisting>
For the most complex cases, the comma is used to disambiguate the
- priority of <literal>or</literal>s and <literal>and</literal>s
+ priority of <literal>or</literal>s and <literal>and</literal>s;
<literal>and</literal> has the priority over <literal>or</literal>,
unless preceded by a comma. For instance:
</para>
--- End Message ---
--- Begin Message ---
Source: debian-policy
Source-Version: 3.9.3.0
We believe that the bug you reported is fixed in the latest version of
debian-policy, which is due to be installed in the Debian FTP archive:
debian-policy_3.9.3.0.dsc
to main/d/debian-policy/debian-policy_3.9.3.0.dsc
debian-policy_3.9.3.0.tar.gz
to main/d/debian-policy/debian-policy_3.9.3.0.tar.gz
debian-policy_3.9.3.0_all.deb
to main/d/debian-policy/debian-policy_3.9.3.0_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 648387@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Russ Allbery <rra@debian.org> (supplier of updated debian-policy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 22 Feb 2012 19:40:36 -0800
Source: debian-policy
Binary: debian-policy
Architecture: source all
Version: 3.9.3.0
Distribution: unstable
Urgency: low
Maintainer: Debian Policy List <debian-policy@lists.debian.org>
Changed-By: Russ Allbery <rra@debian.org>
Description:
debian-policy - Debian Policy Manual and related documents
Closes: 23712 89038 498300 532120 578421 593533 609162 617315 617516 619275 620870 621479 623050 626338 626408 626779 626796 627490 628540 633797 637614 640735 640737 641071 643690 644230 646119 646166 648387 649674 651020 658209
Changes:
debian-policy (3.9.3.0) unstable; urgency=low
.
[ Russ Allbery ]
* Update the copyright format document to the version of DEP-5 from the
DEP web site and apply additional changes from subsequent discussion
in debian-devel and debian-project. Revise for clarity, to add more
examples, and to update the GFDL license versions. Thanks, Steve
Langasek, Charles Plessy, Justin B Rye, and Jonathan Nieder.
(Closes: #658209, #648387)
* Publish the copyright format specification as copyright-format-1.0 so
that later versions can be added without removing previous versions of
the standard. Patch from Charles Plessy. (Closes: #646119)
* Policy: Improve Architecture field in source package
Wording: Raphaël Hertzog <hertzog@debian.org>
Seconded: Russ Allbery <rra@debian.org>
Seconded: Charles Plessy <plessy@debian.org>
Seconded: Guillem Jover <guillem@debian.org>
Closes: #626779
* Policy: Initial Debian maintainers need not be listed in copyright
Wording: Charles Plessy <plessy@debian.org>
Seconded: Russ Allbery <rra@debian.org>
Seconded: Raphaël Hertzog <hertzog@debian.org>
Seconded: Andrew McMillan <andrew@morphoss.com>
Closes: #593533
* Policy: Document cron job file naming restrictions
Wording: Karl E. Jorgensen <karl@jorgensen.org.uk>
Wording: Russ Allbery <rra@debian.org>
Seconded: Russ Allbery <rra@debian.org>
Seconded: Dominic Hargreaves <dom@earth.li>
Seconded: Javier Fernández-Sanguino Peña <jfs@computer.org>
Closes: #609162
* Policy: Document issues with conflicting packages sharing a conffile
Wording: Russ Allbery <rra@debian.org>
Seconded: Cyril Brulebois <kibi@debian.org>
Seconded: Raphaël Hertzog <hertzog@debian.org>
Closes: #23712
* Policy: Add /run FHS exception, clarify rules for /run and /var/run
Wording: Russ Allbery <rra@debian.org>
Seconded: Steve Langasek <vorlon@debian.org>
Seconded: Roger Leigh <rleigh@codelibre.net>
Closes: #620870, #532120
* Policy: Architecture restrictions in a dependency must be non-empty
Wording: Stefano Zacchiroli <zack@debian.org>
Seconded: Russ Allbery <rra@debian.org>
Seconded: Julien Cristau <jcristau@debian.org>
Seconded: Colin Watson <cjwatson@debian.org>
Closes: #498300
* MIME Policy: Retire this document and merge it with Policy
Wording: Ben Finney <ben+debian@benfinney.id.au>
Seconded: Russ Allbery <rra@debian.org>
Seconded: Raphaël Hertzog <hertzog@debian.org>
Seconded: Andrew McMillan <andrew@morphoss.com>
Closes: #89038
* Consistently use "Debian source control file" for *.dsc files and
"Source package control file" for debian/control files. Patch from
Charles Plessy. (Closes: #626796)
* Clarify that continuation lines of the Description control field must
contain at least one non-whitespace character. Thanks, Guillem Jover.
(Closes: #627490)
* Fix the example of creating a /usr/local subdirectory to not fail if
the chown or chmod fail. Thanks, Joey Hess. (Closes: #617315)
* Clarify the requirements for symlinks from inside one top-level
directory to another and add examples and a rationale. Thanks,
Carsten Hey. (Closes: #626338)
* Clarify that Perl Policy 2.4 is for packages built from the perl
source package and the manual page extensions are different for
separate module packages. Thanks, Steve Langasek. (Closes: #643690)
* Say that packages in main may also not recommend packages in non-free,
bringing the main text in line with the list of fields and in line
with the long-standing release goal. (Closes: #646166)
* Resynchronize the archive section list with ftp-master, adding
education, introspection, and metapackages. Patch from Charles
Plessy. (Closes: #651020)
* Clarify that packages in main may not declare Pre-Depends or
Build-Depends-Indep relationships outside of main either. Partly
addresses #587279.
* Fix typo in the version numbers in the dpkg-divert examples. Thanks,
Slavko.
* Add the release date of 3.9.2.0 to upgrading-checklist.
* Fix ordering of the last entries in the 3.9.2.0 upgrading-checklist.
* Fix typo in upgrading-checklist entry for multiarch paths. Thanks,
Michael Dorrington. (Closes: #626408)
* Add id tags for each version entry in upgrading-checklist so that,
when eventually published somewhere, other Debian web sites can link
to specific entries. Patch from Charles Plessy.
* Add AGPL-3 to tools/license-count.
* Update tools/license-count to work with the new Lintian lab layout.
* Add build-arch and build-indep targets to debian/rules.
.
[ Bill Allombert ]
* Policy: Link relationship fields (7.1) to architecture specification
strings (11.1).
Patch from Charles Plessy in #628174.
* Policy: Retire legacy Motif policy (11.8.8)
Proposed by: Justin B Rye
Wording: Russ Allbery <rra@debian.org>
Seconded: Jakub Wilk <jwilk@debian.org>
Seconded: Steve Langasek <vorlon@debian.org>
Seconded: Charles Plessy <plessy@debian.org>
Closes: #621479
* copyright-format: Fix URL for the Eiffel Forum License.
Reported by Thomas Preud'homme, patch by Charles Plessy.
Closes: #623050
* copyright-format: Update SPDX link to point to the SPDX license registry.
Patch by Charles Plessy. Closes: #628540
* copyright-format: Correct or add links to SPDX.
Wording: Charles Plessy <plessy@debian.org>
Seconded: Gregor Herrmann <gregoa@debian.org>
Closes: #641071
* Policy: Clarify that 'machine-extractable' referer the copyright
files (12.5)
Wording: Charles Plessy <plessy@debian.org>
Seconded: Bill Allombert <ballombe@debian.org>
Seconded: Jakub Wilk <jwilk@debian.org>
Closes: #617516
* copyright-format: remove drivers from abstract and useless appendix
Wording: Lars Wirzenius <liw@liw.fi>
Seconded: Charles Plessy <plessy@debian.org>
Seconded: Jakub Wilk <jwilk@debian.org>
Closes: #640735
* copyright-format: Fix syntax of examples.
Proposed by: Charles Plessy <plessy@debian.org>
Wording: Jonathan Nieder <jrnieder@gmail.com>
Closes: #649674
* copyright-format: Clarify specification of multiple license exception:
Wording: Steve Langasek <vorlon@debian.org>
Seconded: Craig Small <csmall@debian.org>
Seconded: Gregor Herrmann <gregoa@debian.org>
Seconded: Jakub Wilk <jwilk@debian.org>
Seconded: Jonas Smedegaard <dr@jones.dk>
Closes: #633797
* copyright-format: Specify URL on www.debian.org
Wording: Charles Plessy <plessy@debian.org>
Seconded: David Prévot <taffit@debian.org>
Seconded: Gregor Herrmann <gregoa@debian.org>
Closes: #640737
* Perl policy: Document major version upgrade trigger
Wording: Dominic Hargreaves <dom@debian.org>
Seconded: Russ Allbery <rra@debian.org>
Seconded: Niko Tyni <ntyni@debian.org>
Seconded: Gregor Herrmann <gregoa@debian.org>
Closes: #619275
* Virtual: change ttf-japanese-{mincho, gothic} to
fonts-japanese-{mincho, gothic}.
Proposed by: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
Seconded: Charles Plessy <plessy@debian.org>
Seconded: Bill Allombert <ballombe@debian.org>
Closes: #644230
* Virtual: Retire java-compiler, java2-compiler, and java-virtual-machine.
Proposed by: Niels Thykier <niels@thykier.net>
Seconded: tony mancill <tmancill@debian.org>
Seconded: Bill Allombert <ballombe@debian.org>
Closes: #578421
* Policy 9.10: No more recommend to call install-docs for doc-base.
Wording: Charles Plessy <plessy@debian.org>
Seconded: Robert Luberda <robert@debian.org>
Seconded: Raphael Hertzog <hertzog@debian.org>
Closes: #637614
Checksums-Sha1:
f09d426468f56b6049b9125da20653929839ab3d 1518 debian-policy_3.9.3.0.dsc
ccf8018f8d0bd2e362c9af50622ddd003ea52ac7 692844 debian-policy_3.9.3.0.tar.gz
ee6c63e2c39db3cb1478ebe4115fc856a455d92b 1926768 debian-policy_3.9.3.0_all.deb
Checksums-Sha256:
5466d21ba0c6ede59969da1092d140eb0039e2d0fcc73911db2fcf41d193a80a 1518 debian-policy_3.9.3.0.dsc
3d04d02064329136765d0e5926aca956d9d55ca171ad12efcbb890cffaad4a73 692844 debian-policy_3.9.3.0.tar.gz
e456bf496aeb792c90cbbf7a8192c8cb13e5421252779d5f9cb6114a47321c3e 1926768 debian-policy_3.9.3.0_all.deb
Files:
d2c6604b9c75c57536ac42b04abb3eba 1518 doc optional debian-policy_3.9.3.0.dsc
01d3630a3393d484ad765d53aca0f0fc 692844 doc optional debian-policy_3.9.3.0.tar.gz
88e00d9c8508884a9403ae403332325a 1926768 doc optional debian-policy_3.9.3.0_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJPRbldAAoJEH2AMVxXNt51FqYH/222GABCa953WNu1SRxP7s7k
HttTjAFekZkxGz+EfjujDteiJg3j6ep0ebOSQXSDm2EoTJY4RtpzmSigTqw0wGC4
+uv4StQTZTK/SJD8BYq3gkrxTy2YvzmVnfh1JIr8xLy3+l7jK7zykIDlg2nwUann
rUk5mY5x0Us8XK7U6TEjyudhPqppinARoolS+bSLBlkpGokOqXILRN2V6S5q1sAN
5I0YfL3coD/b2CEpJnieSMQagsO8H0Vn0n2RgT4T8L2fXuKo2dKCWfFAv3XlwPb0
RwmIz/pl8kqsdf+fJnUGXGqxfpy+TdUAdTlPIYQTaM5dn5E1i3oH8r2hOkEHQYU=
=AEmv
-----END PGP SIGNATURE-----
--- End Message ---