debian-policy_4.4.0.0_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jul 2019 15:40:41 +0100 Source: debian-policy Architecture: source Version: 4.4.0.0 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Closes: 761219 897217 917431 920355 928199 930666 Changes: debian-policy (4.4.0.0) unstable; urgency=medium . [ Sean Whitton ] * Policy: Recommend use of dh Wording: Russ Allbery Wording: Sean Whitton Seconded: Sam Hartman Closes: #930666 * Policy: Permit -b in Vcs-Hg as well as Vcs-Git Wording: Chris Lamb Seconded: Holger Levsen Seconded: Sean Whitton Closes: #897217, #920355 * Policy: Document versioned Provides: Wording: Dominic Hargreaves Seconded: Sean Whitton Seconded: gregor herrmann Closes: #761219 * virtual-package-names-list: Add logind, default-logind Wording: Adam Borowski Seconded: Jonathan Nieder Seconded: Holger Levsen Closes: #917431 * Add text to header of the virtual packages list describing the "(versioned)" annotation. * Fix reference to FHS section in Policy 9.1.2. Thanks to Juuso "Linda" Lapinlampi for the patch. * Process: Rewrite description of 'obsolete' usertag. * Process: Add 'stalled' usertag. * Add footnote to 2.3 with a list of licenses thought not to require the copying of all copyright notices into the package's copyright file (Closes: #928199). This was based on discussion between myself and FTP team members. . [ Russ Allbery ] * Fix formatting of the debian_revision explanation in Policy 5.6.12. Thanks to Emmanuel Arias for the patch. Checksums-Sha1: 1d47b9dafb23f4884e6c85917f09392bd4525288 2023 debian-policy_4.4.0.0.dsc 8ff498c1af2fdff05655e25b0ad27e1295a08112 534372 debian-policy_4.4.0.0.tar.xz Checksums-Sha256: ee28303c6baa55ff26f59ec03e51a09ff45ac38e496562d3b63164feb4b6ea8c 2023 debian-policy_4.4.0.0.dsc 64ff2272e32ea1077cdd996a052cbe865bb589a5dc08733559b9d0feb79950df 534372 debian-policy_4.4.0.0.tar.xz Files: 5f2ca57de66982a6871d86d3433c90e5 2023 doc optional debian-policy_4.4.0.0.dsc 2e2323b31177e50efa1e8a981cf48ab6 534372 doc optional debian-policy_4.4.0.0.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAl0iCZMACgkQaVt65L8G YkCEXQ/8CNluZq2wvYEqUaZkruRScYjEvpDEhPNT3xNkK0euIIWeXFuOIhYs7Z0t bb+c/tPudwu3RZlt2v891HYmy3kGxNmfD9EZSDsUWrS2fFqIBYwCCzx+g23gt9Lg d/UDhjrvrxvKYdtC6SYWKlMnoIClxoo9J/g+/yLz6S8o3sBzcdLYknjsQUQjp53R CY+GLOutO1QQmixxUYRxo4ub2Rm0PWF0SZ3GKLQDAlslB3li1D0okBoP4gD4ViFg od5iUd5Ssbz03b28Dv8GsxCDJhSUpfww6Knzz4Tei6EnafpJl/5csPM3hQKUPDs2 P2+JqFimNKGrU90iBuKhYG+Es6nnWnOzKKQ0Bys9dK/LDFIYd8/OA7jOhODwq+uh 3Q6DEc3M/ptdhxV97or7t1xid04nMxFw/ygq/eIo04yOVmry6OX2jv2Xqo6ylfsS XhoaP9GBOsZZA+AOufR/spY8mIwt+h2ZRJ7QrE3dPrXAePiD83ojQsg7QPrNFXrJ ja2/bo4skoojDy79wLEN7sPzvyJmwOSieEHWDpRbq9wi5BHvt8UB4UqpJN3O/SM+ O0S2L1H6VBNA4F2MPjxCp0ZNh7zCizTJTmKN4w7C4xLY8RiAMFdqQHy3eEvvcv/W SYDBbWeRxRifuv+qypsRHt8AGmXVYg+NStl9dSCZLSYMbwWexz0= =atuX -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#897217: marked as done (debian-policy: Vcs-Hg should support -b too)
Your message dated Sun, 07 Jul 2019 15:34:50 + with message-id and subject line Bug#920355: fixed in debian-policy 4.4.0.0 has caused the Debian Bug report #920355, regarding debian-policy: Vcs-Hg should support -b too to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-policy Version: 4.1.4.1 Severity: normal Hello, In 5.6.26, one can read about Vcs-: "In the case of Git, the value consists of a URL, optionally followed by the word -b the name of a branch in the indicated repository, following the syntax of the git clone command". It would be useful to have the same for Hg, for instance: "In the case of Git and Hg, the value consists of a URL, optionally followed by the word -b the name of a branch in the indicated repository, following the syntax of the git clone and hg clone commands". Samuel -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debian-policy depends on: ii libjs-sphinxdoc 1.6.7-2 debian-policy recommends no packages. Versions of packages debian-policy suggests: pn doc-base -- no debconf information -- Samuel Je suis maintenant possesseur d'un ordinateur portable Compaq Armada 1592DT avec port infra-rouge. Auriez-vous connaissance de programmes suceptibles d'utiliser ce port afin de servir de télécommande ? -+- JN in NPC : ben quoi, c'est pas à ça que ça sert ? --- End Message --- --- Begin Message --- Source: debian-policy Source-Version: 4.4.0.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. 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jul 2019 15:40:41 +0100 Source: debian-policy Architecture: source Version: 4.4.0.0 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Closes: 761219 897217 917431 920355 928199 930666 Changes: debian-policy (4.4.0.0) unstable; urgency=medium . [ Sean Whitton ] * Policy: Recommend use of dh Wording: Russ Allbery Wording: Sean Whitton Seconded: Sam Hartman Closes: #930666 * Policy: Permit -b in Vcs-Hg as well as Vcs-Git Wording: Chris Lamb Seconded: Holger Levsen Seconded: Sean Whitton Closes: #897217, #920355 * Policy: Document versioned Provides: Wording: Dominic Hargreaves Seconded: Sean Whitton Seconded: gregor herrmann Closes: #761219 * virtual-package-names-list: Add logind, default-logind Wording: Adam Borowski Seconded: Jonathan Nieder Seconded: Holger Levsen Closes: #917431 * Add text to header of the virtual packages list describing the "(versioned)" annotation. * Fix reference to FHS section in Policy 9.1.2. Thanks to Juuso "Linda" Lapinlampi for the patch. * Process: Rewrite description of 'obsolete' usertag. * Process: Add 'stalled' usertag. * Add footnote to 2.3 with a list of licenses thought not to require the copying of all copyright notices into the package's copyright file (Closes: #928199). This was based on discussion between myself and FTP team members. . [ Russ Allbery ] * Fix formatting of the debian_revision explanation in Policy 5.6.12. Thanks to Emmanuel Arias for the
Bug#920355: marked as done (debian-policy: Permit branch specifications ("-b") in Mercurial Vcs-Hg headers)
Your message dated Sun, 07 Jul 2019 15:34:50 +
with message-id
and subject line Bug#920355: fixed in debian-policy 4.4.0.0
has caused the Debian Bug report #920355,
regarding debian-policy: Permit branch specifications ("-b") in Mercurial
Vcs-Hg headers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
920355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-policy
Version: 4.3.0.1
Severity: minor
Hi,
Policy §5.6.26 permits "-b" only in the case of Vcs-Git:
In the case of Git, the value consists of a URL, optionally
followed by the word -b and the name of a branch in the
indicated repository.
However, Mercurial (ie. "Vcs-Hg") supports this too in its
equivalent "hg clone" command. This change was triggered via
#920314 in Lintian.
A simple patch (also attached) might be:
commit 3e66c9e470053fcc77169efa82833252971d211c
Author: Chris Lamb
Date: Thu Jan 24 16:55:21 2019 +0100
Permit branch specifications ("-b") in Mercurial Vcs-Hg headers too,
not just Vcs-Git. (Closes: #-1)
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 44080c9..013aae4 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -973,10 +973,11 @@ repository where the Debian source package is
developed.
- Mtn (Monotone)
- Svn (Subversion)
-In the case of Git, the value consists of a URL, optionally followed
-by the word ``-b`` and the name of a branch in the indicated
-repository, following the syntax of the ``git clone`` command. If no
-branch is specified, the packaging should be on the default branch.
+In the case of Git and Mercurial, the value consists of a URL,
+optionally followed by the word ``-b`` and the name of a branch in
+the indicated repository, following the syntax of the ``git clone``
+or ``hg clone`` command. If no branch is specified, the packaging
+should be on the default branch.
More than one different VCS may be specified for the same package.
Thank you for maintaining Policy.
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org chris-lamb.co.uk
`-
From 3e66c9e470053fcc77169efa82833252971d211c Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: Thu, 24 Jan 2019 16:55:21 +0100
Subject: [PATCH] Permit branch specifications ("-b") in Mercurial Vcs-Hg
headers too, not just Vcs-Git. (Closes: #-1)
---
policy/ch-controlfields.rst | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 44080c9..013aae4 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -973,10 +973,11 @@ repository where the Debian source package is developed.
- Mtn (Monotone)
- Svn (Subversion)
-In the case of Git, the value consists of a URL, optionally followed
-by the word ``-b`` and the name of a branch in the indicated
-repository, following the syntax of the ``git clone`` command. If no
-branch is specified, the packaging should be on the default branch.
+In the case of Git and Mercurial, the value consists of a URL,
+optionally followed by the word ``-b`` and the name of a branch in
+the indicated repository, following the syntax of the ``git clone``
+or ``hg clone`` command. If no branch is specified, the packaging
+should be on the default branch.
More than one different VCS may be specified for the same package.
--
2.20.1
--- End Message ---
--- Begin Message ---
Source: debian-policy
Source-Version: 4.4.0.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.
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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sean Whitton (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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 07 Jul 2019 15:40:41 +0100
Bug#928199: marked as done (List of licenses that don't require gathering all copyright notices)
Your message dated Sun, 07 Jul 2019 15:34:50 + with message-id and subject line Bug#928199: fixed in debian-policy 4.4.0.0 has caused the Debian Bug report #928199, regarding List of licenses that don't require gathering all copyright notices to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 928199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-policy Version: 4.3.0.3 Severity: normal User: debian-pol...@packages.debian.org Usertags: informative Tags: patch Hello, I've written a patch to add a footnote with a list of licenses that are thought not to require the copying of all copyright notices into Debian's copyright file. This does not need seconding, because footnotes are not normative, but I haven't committed this patch yet because I wanted to see if others have reasons not to include something like this in the Policy Manual. diff --git a/debian/changelog b/debian/changelog index 7878523..5abe5bb 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,6 +2,9 @@ debian-policy (4.3.0.4) UNRELEASED; urgency=medium * Fix reference to FHS section in Policy 9.1.2. Thanks to Juuso "Linda" Lapinlampi for the patch. + * Add footnote to 2.3 with a list of licenses thought not to require the +copying of all copyright notices into the package's copyright file. +This was based on discussion between myself and FTP team members. -- Sean Whitton Tue, 09 Apr 2019 10:20:30 -0700 diff --git a/policy/ch-archive.rst b/policy/ch-archive.rst index 72764a9..b8ba081 100644 --- a/policy/ch-archive.rst +++ b/policy/ch-archive.rst @@ -192,7 +192,7 @@ information to be excluded from distributions of binaries built from the source. In such cases, a verbatim copy of its copyright information should normally still be included, but need not be if creating and maintaining a copy of that information involves -significant time and effort. +significant time and effort. [#]_ See :ref:`s-copyrightfile` for further details. @@ -369,6 +369,13 @@ management tools. is unable to meet, for example, if the source is unavailable. These situations will need to be handled on a case-by-case basis. +.. [#] + Licenses that are not thought to require the copying of all + copyright notices into Debian's copyright file include Apache-2.0 + and the Boost Software License, version 1.0. Final determination + as to whether a package's copyright file is sufficient lies with + the FTP team. + .. [#] This is an important criterion because we are trying to produce, amongst other things, a free Unix. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: debian-policy Source-Version: 4.4.0.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. 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jul 2019 15:40:41 +0100 Source: debian-policy Architecture: source Version: 4.4.0.0 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Closes: 761219 897217 917431 920355 928199 930666 Changes: debian-policy (4.4.0.0) unstable; urgency=medium . [ Sean Whitton ] * Policy: Recommend use of dh Wording: Russ Allbery Wording: Sean Whitton Seconded: Sam Hartman Closes: #930666 * Policy: Permit -b in Vcs-Hg as well as Vcs-Git Wording: Chris Lamb Seconded: Holger Levsen Seconded: Sean Whitton Closes: #897217, #920355 * Policy: Document versioned Provides: Wording: Dominic Hargreaves Seconded: Sean Whitton Seconded: gregor herrmann Closes: #761219 * virtual-package-names-list: Add logind, default-logind Wording: Adam Borowski Seconded: Jonathan Nieder Seconded: Holger Levsen Closes: #917431 * Add text to header of the virtual
Bug#930666: marked as done (Please document consensus on use of dh sequencer)
Your message dated Sun, 07 Jul 2019 15:34:50 + with message-id and subject line Bug#930666: fixed in debian-policy 4.4.0.0 has caused the Debian Bug report #930666, regarding Please document consensus on use of dh sequencer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 930666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: debian-policy Dear policy team: I just published a consensus call on a discussion we had to canvas the project on the use of Debhelper's dh sequencer. https://lists.debian.org/msgid-search/tslmuif7pwy@suchdamage.org I'd like to ask the policy editors to facilitate using the normal process to document this consensus in policy. My understanding is that the editors already have some ideas about how that might work. Obviously I'm available to help as desired. In the interest of setting expectations, if this issue is still open in December, I plan to check in and see whether I think the approach of going through the normal policy process still makes sense. signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: debian-policy Source-Version: 4.4.0.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. 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 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jul 2019 15:40:41 +0100 Source: debian-policy Architecture: source Version: 4.4.0.0 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Closes: 761219 897217 917431 920355 928199 930666 Changes: debian-policy (4.4.0.0) unstable; urgency=medium . [ Sean Whitton ] * Policy: Recommend use of dh Wording: Russ Allbery Wording: Sean Whitton Seconded: Sam Hartman Closes: #930666 * Policy: Permit -b in Vcs-Hg as well as Vcs-Git Wording: Chris Lamb Seconded: Holger Levsen Seconded: Sean Whitton Closes: #897217, #920355 * Policy: Document versioned Provides: Wording: Dominic Hargreaves Seconded: Sean Whitton Seconded: gregor herrmann Closes: #761219 * virtual-package-names-list: Add logind, default-logind Wording: Adam Borowski Seconded: Jonathan Nieder Seconded: Holger Levsen Closes: #917431 * Add text to header of the virtual packages list describing the "(versioned)" annotation. * Fix reference to FHS section in Policy 9.1.2. Thanks to Juuso "Linda" Lapinlampi for the patch. * Process: Rewrite description of 'obsolete' usertag. * Process: Add 'stalled' usertag. * Add footnote to 2.3 with a list of licenses thought not to require the copying of all copyright notices into the package's copyright file (Closes: #928199). This was based on discussion between myself and FTP team members. . [ Russ Allbery ] * Fix formatting of the debian_revision explanation in Policy 5.6.12. Thanks to Emmanuel Arias for the patch. Checksums-Sha1: 1d47b9dafb23f4884e6c85917f09392bd4525288 2023 debian-policy_4.4.0.0.dsc 8ff498c1af2fdff05655e25b0ad27e1295a08112 534372 debian-policy_4.4.0.0.tar.xz Checksums-Sha256: ee28303c6baa55ff26f59ec03e51a09ff45ac38e496562d3b63164feb4b6ea8c 2023 debian-policy_4.4.0.0.dsc 64ff2272e32ea1077cdd996a052cbe865bb589a5dc08733559b9d0feb79950df 534372 debian-policy_4.4.0.0.tar.xz Files: 5f2ca57de66982a6871d86d3433c90e5 2023 doc optional debian-policy_4.4.0.0.dsc 2e2323b31177e50efa1e8a981cf48ab6 534372 doc optional debian-policy_4.4.0.0.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAl0iCZMACgkQaVt65L8G YkCEXQ/8CNluZq2wvYEqUaZkruRScYjEvpDEhPNT3xNkK0euIIWeXFuOIhYs7Z0t bb+c/tPudwu3RZlt2v891HYmy3kGxNmfD9EZSDsUWrS2fFqIBYwCCzx+g23gt9Lg d/UDhjrvrxvKYdtC6SYWKlMnoIClxoo9J/g+/yLz6S8o3sBzcdLYknjsQUQjp53R CY+GLOutO1QQmixxUYRxo4ub2Rm0PWF0SZ3GKLQDAlslB3li1D0okBoP4gD4ViFg
Bug#761219: marked as done (debian-policy: document versioned Provides)
Your message dated Sun, 07 Jul 2019 15:34:50 + with message-id and subject line Bug#761219: fixed in debian-policy 4.4.0.0 has caused the Debian Bug report #761219, regarding debian-policy: document versioned Provides to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 761219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-policy Version: 3.9.5.0 Severity: wishlist dpkg 1.17.11 and apt 1.0.7 recently implemented support for versioned provides. From the dpkg changelog: * Add versioned Provides support: - Add a new dpkg --assert-versioned-provides command. - Packages can provide a specific version, “virtual (= 1.0)” which will be honored, previously it would just be accepted when parsing. - Non-versioned virtual packages will not satisfy versioned dependencies. - Versioned virtual packages will satisfy non-versioned dependencies. This seems useful for at least perl packages [0], where we'd like to start using them after jessie is released, if possible. Quoting section 7.5 (Virtual packages - `Provides') of the current policy: If a relationship field has a version number attached, only real packages will be considered to see whether the relationship is satisfied (or the prohibition violated, for a conflict or breakage). In other words, if a version number is specified, this is a request to ignore all `Provides' for that package name and consider only real packages. The package manager will assume that a package providing that virtual package is not of the "right" version. A `Provides' field may not contain version numbers, and the version number of the concrete package which provides a particular virtual package will not be considered when considering a dependency on or conflict with the virtual package name.[1] [...] [1] It is possible that a future release of `dpkg' may add the ability to specify a version number for each virtual package it provides. This feature is not yet present, however, and is expected to be used only infrequently. This clearly needs an update. No proposed wording yet, sorry. [0] perl/perl-modules Provide a dozen or so virtual packages of bundled modules that also exist as separate packages in the archive with a newer version. Packages that need at least a specified version of such a module currently need to do things like Depends: perl (>=y) | libfoo-bar-perl (>=x) and the expressions may even need changes with newer perl releases. See https://lintian.debian.org/tags/versioned-dependency-satisfied-by-perl.html -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: debian-policy Source-Version: 4.4.0.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. 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 761...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jul 2019 15:40:41 +0100 Source: debian-policy Architecture: source Version: 4.4.0.0 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Closes: 761219 897217 917431 920355 928199 930666 Changes: debian-policy (4.4.0.0) unstable; urgency=medium . [ Sean Whitton ] * Policy: Recommend use of dh Wording: Russ Allbery Wording: Sean Whitton Seconded: Sam Hartman Closes: #930666 * Policy: Permit -b in Vcs-Hg as well as Vcs-Git Wording: Chris Lamb Seconded: Holger Levsen Seconded: Sean Whitton Closes: #897217, #920355 * Policy: Document versioned Provides: Wording: Dominic Hargreaves Seconded: Sean Whitton Seconded: gregor herrmann Closes: #761219 * virtual-package-names-list: Add logind, default-logind Wording: Adam Borowski Seconded: Jonathan Nieder Seconded: Holger Levsen Closes: #917431
Bug#897217: marked as done (debian-policy: Vcs-Hg should support -b too)
Your message dated Sun, 07 Jul 2019 15:34:50 + with message-id and subject line Bug#897217: fixed in debian-policy 4.4.0.0 has caused the Debian Bug report #897217, regarding debian-policy: Vcs-Hg should support -b too to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-policy Version: 4.1.4.1 Severity: normal Hello, In 5.6.26, one can read about Vcs-: "In the case of Git, the value consists of a URL, optionally followed by the word -b the name of a branch in the indicated repository, following the syntax of the git clone command". It would be useful to have the same for Hg, for instance: "In the case of Git and Hg, the value consists of a URL, optionally followed by the word -b the name of a branch in the indicated repository, following the syntax of the git clone and hg clone commands". Samuel -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages debian-policy depends on: ii libjs-sphinxdoc 1.6.7-2 debian-policy recommends no packages. Versions of packages debian-policy suggests: pn doc-base -- no debconf information -- Samuel Je suis maintenant possesseur d'un ordinateur portable Compaq Armada 1592DT avec port infra-rouge. Auriez-vous connaissance de programmes suceptibles d'utiliser ce port afin de servir de télécommande ? -+- JN in NPC : ben quoi, c'est pas à ça que ça sert ? --- End Message --- --- Begin Message --- Source: debian-policy Source-Version: 4.4.0.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. 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 897...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jul 2019 15:40:41 +0100 Source: debian-policy Architecture: source Version: 4.4.0.0 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Closes: 761219 897217 917431 920355 928199 930666 Changes: debian-policy (4.4.0.0) unstable; urgency=medium . [ Sean Whitton ] * Policy: Recommend use of dh Wording: Russ Allbery Wording: Sean Whitton Seconded: Sam Hartman Closes: #930666 * Policy: Permit -b in Vcs-Hg as well as Vcs-Git Wording: Chris Lamb Seconded: Holger Levsen Seconded: Sean Whitton Closes: #897217, #920355 * Policy: Document versioned Provides: Wording: Dominic Hargreaves Seconded: Sean Whitton Seconded: gregor herrmann Closes: #761219 * virtual-package-names-list: Add logind, default-logind Wording: Adam Borowski Seconded: Jonathan Nieder Seconded: Holger Levsen Closes: #917431 * Add text to header of the virtual packages list describing the "(versioned)" annotation. * Fix reference to FHS section in Policy 9.1.2. Thanks to Juuso "Linda" Lapinlampi for the patch. * Process: Rewrite description of 'obsolete' usertag. * Process: Add 'stalled' usertag. * Add footnote to 2.3 with a list of licenses thought not to require the copying of all copyright notices into the package's copyright file (Closes: #928199). This was based on discussion between myself and FTP team members. . [ Russ Allbery ] * Fix formatting of the debian_revision explanation in Policy 5.6.12. Thanks to Emmanuel Arias for the
Bug#920355: marked as done (debian-policy: Permit branch specifications ("-b") in Mercurial Vcs-Hg headers)
Your message dated Sun, 07 Jul 2019 15:34:50 +
with message-id
and subject line Bug#897217: fixed in debian-policy 4.4.0.0
has caused the Debian Bug report #897217,
regarding debian-policy: Permit branch specifications ("-b") in Mercurial
Vcs-Hg headers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
897217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-policy
Version: 4.3.0.1
Severity: minor
Hi,
Policy §5.6.26 permits "-b" only in the case of Vcs-Git:
In the case of Git, the value consists of a URL, optionally
followed by the word -b and the name of a branch in the
indicated repository.
However, Mercurial (ie. "Vcs-Hg") supports this too in its
equivalent "hg clone" command. This change was triggered via
#920314 in Lintian.
A simple patch (also attached) might be:
commit 3e66c9e470053fcc77169efa82833252971d211c
Author: Chris Lamb
Date: Thu Jan 24 16:55:21 2019 +0100
Permit branch specifications ("-b") in Mercurial Vcs-Hg headers too,
not just Vcs-Git. (Closes: #-1)
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 44080c9..013aae4 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -973,10 +973,11 @@ repository where the Debian source package is
developed.
- Mtn (Monotone)
- Svn (Subversion)
-In the case of Git, the value consists of a URL, optionally followed
-by the word ``-b`` and the name of a branch in the indicated
-repository, following the syntax of the ``git clone`` command. If no
-branch is specified, the packaging should be on the default branch.
+In the case of Git and Mercurial, the value consists of a URL,
+optionally followed by the word ``-b`` and the name of a branch in
+the indicated repository, following the syntax of the ``git clone``
+or ``hg clone`` command. If no branch is specified, the packaging
+should be on the default branch.
More than one different VCS may be specified for the same package.
Thank you for maintaining Policy.
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org chris-lamb.co.uk
`-
From 3e66c9e470053fcc77169efa82833252971d211c Mon Sep 17 00:00:00 2001
From: Chris Lamb
Date: Thu, 24 Jan 2019 16:55:21 +0100
Subject: [PATCH] Permit branch specifications ("-b") in Mercurial Vcs-Hg
headers too, not just Vcs-Git. (Closes: #-1)
---
policy/ch-controlfields.rst | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
index 44080c9..013aae4 100644
--- a/policy/ch-controlfields.rst
+++ b/policy/ch-controlfields.rst
@@ -973,10 +973,11 @@ repository where the Debian source package is developed.
- Mtn (Monotone)
- Svn (Subversion)
-In the case of Git, the value consists of a URL, optionally followed
-by the word ``-b`` and the name of a branch in the indicated
-repository, following the syntax of the ``git clone`` command. If no
-branch is specified, the packaging should be on the default branch.
+In the case of Git and Mercurial, the value consists of a URL,
+optionally followed by the word ``-b`` and the name of a branch in
+the indicated repository, following the syntax of the ``git clone``
+or ``hg clone`` command. If no branch is specified, the packaging
+should be on the default branch.
More than one different VCS may be specified for the same package.
--
2.20.1
--- End Message ---
--- Begin Message ---
Source: debian-policy
Source-Version: 4.4.0.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.
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 897...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sean Whitton (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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 07 Jul 2019 15:40:41 +0100
Bug#917431: marked as done (debian-policy: virtual packages: logind, default-logind)
Your message dated Sun, 07 Jul 2019 15:34:50 + with message-id and subject line Bug#917431: fixed in debian-policy 4.4.0.0 has caused the Debian Bug report #917431, regarding debian-policy: virtual packages: logind, default-logind to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 917431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-policy Version: 4.3.0.1 Severity: wishlist Tags: patch Hi! As discussed in bug #915407, we'd want a virtual package for logind implementations. At present, two packages implement this functionality: libpam-systemd and libpam-elogind. This has been discussed, including a formal proposal on debian-devel, and no objections have been raised. Thus, the wording would be (as proposed by fsateler): logind: an org.freedesktop.login1 D-Bus API implementation default-logind: should be provided by the distribution's default logind provider (currently pam-systemd) Background: currently libpam-systemd provides two features currently used by third parties: one is the necessary hooks to start the systemd implementation of login1. The second is hooking up the systemd --user service manager. This virtual package attempts to disentangle the two so that packages that only require logind can use an alternative implementation. = If you prefer a more terse wording for default-, it could be just: logind: an org.freedesktop.login1 D-Bus API implementation default-logind: distribution's default logind provider Meow! --- End Message --- --- Begin Message --- Source: debian-policy Source-Version: 4.4.0.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. 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 917...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton (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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jul 2019 15:40:41 +0100 Source: debian-policy Architecture: source Version: 4.4.0.0 Distribution: unstable Urgency: medium Maintainer: Debian Policy Editors Changed-By: Sean Whitton Closes: 761219 897217 917431 920355 928199 930666 Changes: debian-policy (4.4.0.0) unstable; urgency=medium . [ Sean Whitton ] * Policy: Recommend use of dh Wording: Russ Allbery Wording: Sean Whitton Seconded: Sam Hartman Closes: #930666 * Policy: Permit -b in Vcs-Hg as well as Vcs-Git Wording: Chris Lamb Seconded: Holger Levsen Seconded: Sean Whitton Closes: #897217, #920355 * Policy: Document versioned Provides: Wording: Dominic Hargreaves Seconded: Sean Whitton Seconded: gregor herrmann Closes: #761219 * virtual-package-names-list: Add logind, default-logind Wording: Adam Borowski Seconded: Jonathan Nieder Seconded: Holger Levsen Closes: #917431 * Add text to header of the virtual packages list describing the "(versioned)" annotation. * Fix reference to FHS section in Policy 9.1.2. Thanks to Juuso "Linda" Lapinlampi for the patch. * Process: Rewrite description of 'obsolete' usertag. * Process: Add 'stalled' usertag. * Add footnote to 2.3 with a list of licenses thought not to require the copying of all copyright notices into the package's copyright file (Closes: #928199). This was based on discussion between myself and FTP team members. . [ Russ Allbery ] * Fix formatting of the debian_revision explanation in Policy 5.6.12. Thanks to Emmanuel Arias for the patch. Checksums-Sha1: 1d47b9dafb23f4884e6c85917f09392bd4525288 2023 debian-policy_4.4.0.0.dsc 8ff498c1af2fdff05655e25b0ad27e1295a08112 534372 debian-policy_4.4.0.0.tar.xz Checksums-Sha256: ee28303c6baa55ff26f59ec03e51a09ff45ac38e496562d3b63164feb4b6ea8c 2023 debian-policy_4.4.0.0.dsc 64ff2272e32ea1077cdd996a052cbe865bb589a5dc08733559b9d0feb79950df 534372 debian-policy_4.4.0.0.tar.xz Files: 5f2ca57de66982a6871d86d3433c90e5 2023 doc optional
Processing of debian-policy_4.4.0.0_source.changes
debian-policy_4.4.0.0_source.changes uploaded successfully to localhost along with the files: debian-policy_4.4.0.0.dsc debian-policy_4.4.0.0.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#930666: Please document consensus on use of dh sequencer
On Sat, Jul 06, 2019 at 08:58:26PM -0700, Russ Allbery wrote: > Here is an updated patch incorporating Sean's wording changes as well as > other changes discussed elsewhere on the thread. This reverts most of my > unrelated informative changes for clarity (they can be discussed or made > separately) and drops the sample dh makefile in favor of just referencing > the debhelper documentation. It does keep some minor wording and > formatting fixes in the first two paragraphs. > > This also removes the word "new" from the discussion of using another > packaging helper as an example, to make it a bit more obvious that the > cdbs maintainer using cdbs is one of the expected exceptions. > > diff --git a/policy/ch-source.rst b/policy/ch-source.rst > index ee9270d..93beb4a 100644 > --- a/policy/ch-source.rst > +++ b/policy/ch-source.rst > @@ -259,13 +259,33 @@ files, sockets or setuid or setgid files.. [#]_ > Main building script: ``debian/rules`` > -- > > -This file must be an executable makefile, and contains the > -package-specific recipes for compiling the package and building binary > -package(s) from the source. > - > -It must start with the line ``#!/usr/bin/make -f``, so that it can be > -invoked by saying its name rather than invoking ``make`` explicitly. > -That is, invoking either of ``make -f debian/rules args...`` or > ``./debian/rules args...`` must result in identical behavior. > +This file must be an executable makefile. It contains the > +package-specific recipes for compiling the source (if required) and > +constructing one or more binary packages. > + > +``debian/rules`` must start with the line ``#!/usr/bin/make -f``, so that > +it can be invoked by saying its name rather than invoking ``make`` > +explicitly. That is, invoking either of ``make -f debian/rules args...`` > +or ``./debian/rules args...`` must result in identical behavior. > + > +The recommended way to implement the build process of a Debian package, in > +the absence of a good reason to use a different approach, is the ``dh`` > +tool. This includes the contents of the ``debian/rules`` building script. > +``dh`` is the most common packaging helper tool in Debian. Using it will > +usually save effort in complying with the rules in this document, because > +``dh`` will automatically implement many of them without requiring > +explicit instructions. > + > +There are sometimes good reasons to use a different approach. For > +example, the standard tools for packaging software written in some > +languages may use another tool; some rarer packaging patterns, such as > +multiple builds of the same software with different options, are easier to > +express with other tools; and a packager working on a different packaging > +helper might want to use their tool. The recommendation to use ``dh`` > +does not always apply, and use of ``dh`` is not required. > + > +For more information about how to use ``dh``, see the documentation in the > +debhelper package, most notably the dh(1) manual page. > > The following targets are required and must be implemented by > ``debian/rules``: ``clean``, ``binary``, ``binary-arch``, > Thanks Russ, this is much nicer this way. Cheers, -- Bill. Imagine a large red swirl here.
Bug#930666: Please document consensus on use of dh sequencer
Hello, On Sat 06 Jul 2019 at 08:58PM -07, Russ Allbery wrote: > diff --git a/policy/ch-source.rst b/policy/ch-source.rst > index ee9270d..93beb4a 100644 > --- a/policy/ch-source.rst > +++ b/policy/ch-source.rst > @@ -259,13 +259,33 @@ files, sockets or setuid or setgid files.. [#]_ > Main building script: ``debian/rules`` > -- > > -This file must be an executable makefile, and contains the > -package-specific recipes for compiling the package and building binary > -package(s) from the source. > - > -It must start with the line ``#!/usr/bin/make -f``, so that it can be > -invoked by saying its name rather than invoking ``make`` explicitly. > -That is, invoking either of ``make -f debian/rules args...`` or > ``./debian/rules args...`` must result in identical behavior. > +This file must be an executable makefile. It contains the > +package-specific recipes for compiling the source (if required) and > +constructing one or more binary packages. > + > +``debian/rules`` must start with the line ``#!/usr/bin/make -f``, so that > +it can be invoked by saying its name rather than invoking ``make`` > +explicitly. That is, invoking either of ``make -f debian/rules args...`` > +or ``./debian/rules args...`` must result in identical behavior. > + > +The recommended way to implement the build process of a Debian package, in > +the absence of a good reason to use a different approach, is the ``dh`` > +tool. This includes the contents of the ``debian/rules`` building script. > +``dh`` is the most common packaging helper tool in Debian. Using it will > +usually save effort in complying with the rules in this document, because > +``dh`` will automatically implement many of them without requiring > +explicit instructions. > + > +There are sometimes good reasons to use a different approach. For > +example, the standard tools for packaging software written in some > +languages may use another tool; some rarer packaging patterns, such as > +multiple builds of the same software with different options, are easier to > +express with other tools; and a packager working on a different packaging > +helper might want to use their tool. The recommendation to use ``dh`` > +does not always apply, and use of ``dh`` is not required. > + > +For more information about how to use ``dh``, see the documentation in the > +debhelper package, most notably the dh(1) manual page. > > The following targets are required and must be implemented by > ``debian/rules``: ``clean``, ``binary``, ``binary-arch``, Seconded, and applied to 'next'. Thank you! -- Sean Whitton signature.asc Description: PGP signature
Bug#930666: Please document consensus on use of dh sequencer
My second still applies to the following diff; I agree this is consistent with the discussion so far. diff --git a/policy/ch-source.rst b/policy/ch-source.rst index ee9270d..93beb4a 100644 --- a/policy/ch-source.rst +++ b/policy/ch-source.rst @@ -259,13 +259,33 @@ files, sockets or setuid or setgid files.. [#]_ Main building script: ``debian/rules`` -- -This file must be an executable makefile, and contains the -package-specific recipes for compiling the package and building binary -package(s) from the source. - -It must start with the line ``#!/usr/bin/make -f``, so that it can be -invoked by saying its name rather than invoking ``make`` explicitly. -That is, invoking either of ``make -f debian/rules args...`` or ``./debian/rules args...`` must result in identical behavior. +This file must be an executable makefile. It contains the +package-specific recipes for compiling the source (if required) and +constructing one or more binary packages. + +``debian/rules`` must start with the line ``#!/usr/bin/make -f``, so that +it can be invoked by saying its name rather than invoking ``make`` +explicitly. That is, invoking either of ``make -f debian/rules args...`` +or ``./debian/rules args...`` must result in identical behavior. + +The recommended way to implement the build process of a Debian package, in +the absence of a good reason to use a different approach, is the ``dh`` +tool. This includes the contents of the ``debian/rules`` building script. +``dh`` is the most common packaging helper tool in Debian. Using it will +usually save effort in complying with the rules in this document, because +``dh`` will automatically implement many of them without requiring +explicit instructions. + +There are sometimes good reasons to use a different approach. For +example, the standard tools for packaging software written in some +languages may use another tool; some rarer packaging patterns, such as +multiple builds of the same software with different options, are easier to +express with other tools; and a packager working on a different packaging +helper might want to use their tool. The recommendation to use ``dh`` +does not always apply, and use of ``dh`` is not required. + +For more information about how to use ``dh``, see the documentation in the +debhelper package, most notably the dh(1) manual page. The following targets are required and must be implemented by ``debian/rules``: ``clean``, ``binary``, ``binary-arch``, signature.asc Description: PGP signature
Bug#931548: Migration to Sphinx
Package: src:developers-reference Version: 3.4.25 Severity: wishlist Tags: patch Patch is provided as rest8 branch. https://salsa.debian.org/debian/developers-reference/tree/rest8 ├── debian │ ├── changelog │ ├── control │ ├── copyright │ ├── developers-reference-de.doc-base │ ├── developers-reference-de.docs │ ├── developers-reference.doc-base │ ├── developers-reference.docs │ ├── developers-reference-fr.doc-base │ ├── developers-reference-fr.docs │ ├── developers-reference-it.doc-base │ ├── developers-reference-it.docs │ ├── developers-reference-ja.doc-base │ ├── developers-reference-ja.docs │ ├── developers-reference-ru.doc-base │ ├── developers-reference-ru.docs │ ├── rules │ ├── source │ │ └── format │ ├── tocsubstvars │ └── TODO ├── Makefile ├── README.contributing ├── source │ ├── best-pkging-practices.rst │ ├── beyond-pkging.rst │ ├── conf.py │ ├── developer-duties.rst │ ├── index.rst │ ├── l10n.rst │ ├── locales │ │ ├── de │ │ │ └── LC_MESSAGES │ │ │ ├── best-pkging-practices.po │ │ │ ├── beyond-pkging.po │ │ │ ├── developer-duties.po │ │ │ ├── index.po │ │ │ ├── l10n.po │ │ │ ├── new-maintainer.po │ │ │ ├── pkgs.po │ │ │ ├── resources.po │ │ │ ├── scope.po │ │ │ └── tools.po │ │ ├── fr │ │ │ └── LC_MESSAGES │ │ │ ├── best-pkging-practices.po │ │ │ ├── beyond-pkging.po │ │ │ ├── developer-duties.po │ │ │ ├── index.po │ │ │ ├── l10n.po │ │ │ ├── new-maintainer.po │ │ │ ├── pkgs.po │ │ │ ├── resources.po │ │ │ ├── scope.po │ │ │ └── tools.po │ │ ├── it │ │ │ └── LC_MESSAGES │ │ │ ├── best-pkging-practices.po │ │ │ ├── beyond-pkging.po │ │ │ ├── developer-duties.po │ │ │ ├── index.po │ │ │ ├── l10n.po │ │ │ ├── new-maintainer.po │ │ │ ├── pkgs.po │ │ │ ├── resources.po │ │ │ ├── scope.po │ │ │ └── tools.po │ │ ├── ja │ │ │ └── LC_MESSAGES │ │ │ ├── best-pkging-practices.po │ │ │ ├── beyond-pkging.po │ │ │ ├── developer-duties.po │ │ │ ├── index.po │ │ │ ├── l10n.po │ │ │ ├── new-maintainer.po │ │ │ ├── pkgs.po │ │ │ ├── resources.po │ │ │ ├── scope.po │ │ │ └── tools.po │ │ └── ru │ │ └── LC_MESSAGES │ │ ├── best-pkging-practices.po │ │ ├── beyond-pkging.po │ │ ├── developer-duties.po │ │ ├── index.po │ │ ├── l10n.po │ │ ├── new-maintainer.po │ │ ├── pkgs.po │ │ ├── resources.po │ │ ├── scope.po │ │ └── tools.po │ ├── new-maintainer.rst │ ├── pkgs.rst │ ├── resources.rst │ ├── scope.rst │ ├── _static │ └── tools.rst └── sphinx-multi You can build HTML and PDF with "make". debian/* still needs to be polished as of this posting. The conversion process is completely recorded in the history. If main branch is update, we can rebase most of rest8 and do the operation as in the commit message to get conversion for the updated master if needed. Maybe, now I think Sphinx expert can take over to get proper packaging. Osamu -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
