Your message dated Sun, 04 Mar 2012 23:17:30 +0000 with message-id <e1s4kge-00017c...@franck.debian.org> and subject line Bug#622263: fixed in debian-policy 3.9.3.1 has caused the Debian Bug report #622263, regarding debian-policy: Phrasing of 5.6.25 (DMUA) is confusing 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.) -- 622263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: debian-policy Version: 3.9.2.0 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi dear policy maintainers, We just had a short discussion on IRC (#debian-python, 2011-04-11) about the phrasing of the new 5.6.25 paragraph (which documents the DMUA field). The current phrasing makes it sound that adding the DM-Upload-Allowed field to each source package is required (where AFAIK it isn't). I propose the following rephrasing: - --- policy_orig.sgml 2011-04-11 16:33:25.000000000 +0200 +++ policy.sgml 2011-04-11 16:45:52.000000000 +0200 @@ -3700,11 +3700,11 @@ <heading><tt>DM-Upload-Allowed</tt></heading> <p> - - The most recent version of a package uploaded to unstable or - - experimental must include the field <tt>DM-Upload-Allowed: - - yes</tt> in the source section of its source control file for - - the Debian archive to accept uploads signed with a key in the - - Debian Maintainer keyring. See the General + The Debian archive will accept uploads signed with a key in + the Debian Maintainer keyring for a given package if and only + if the previous upload of said package had the + <tt>DM-Upload-Allowed: yes</tt> field included in the source + section of its source control file. See the General Resolution <url id="http://www.debian.org/vote/2007/vote_003"; name="Endorse the concept of Debian Maintainers"> for more details. Thanks for your consideration, cheers, OdyX === IRC discussion abstract === [16:17] <jtaylor> standard 3.9.2 says one *must* set DM-Upload-Allowed yes, is that also the stance of the python modules team? [16:19] <OdyX> jtaylor: "must" in what sense ? [16:20] <jwilk> "... to accept uploads signed with a key in the Debian Maintainer keyring." - that's quite an important part. [16:20] <jwilk> I don't get why it had to be written in the Policy, but meh... [16:21] <tumbleweed> It seems sensible to have non-X fields in the policy [16:22] <morph_work> sure, but it seems to be required for every package [16:22] <jtaylor> odyx: must is the wording of the policy [16:22] <jtaylor> no should [16:23] <jtaylor> I always though that field was something set by the sponsor [16:24] <OdyX> jtaylor: read the entire phrase. It could be reformulated as "a DM whose key is in the debian-maintainers keyring can upload package if and only if this package has previously been uploaded to experimental or unstable with the DMUA flag set to yes." [16:24] <tumbleweed> such a rephrasing would probably be sensible [16:24] <jtaylor> ah [16:24] <jtaylor> yes [16:24] <morph_work> and clearer [16:25] <OdyX> who fires reportbug ? [16:25] <jtaylor> I as relative new to debian packaging did not know that sponsored packages are signed with the sponsors key [16:25] <jtaylor> so I misunderstood that :( - -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash debian-policy depends on no packages. debian-policy recommends no packages. Versions of packages debian-policy suggests: ii doc-base 0.10.1 utilities to manage online documen - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iJwEAQECAAYFAk2jFgMACgkQKA1Vt+jBwDg6CgP+OnCmG8cBsi0cJpAlIDsLFJG1 kf3RgHheY9aontNhOzCM3X6k6IfqLn4mzkoP20w2XFgiSsQ9GDUQlAXYz/l81y12 uwICp8xRa1Pphc/d+Pe+iJ6oJZ2Qh7rusijHAS9siIuHGVXOMbmnbFJkRPqHYMR+ dGWRhPl9Qz8/QwRF9Kk= =D49w -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---Source: debian-policy Source-Version: 3.9.3.1 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.1.dsc to main/d/debian-policy/debian-policy_3.9.3.1.dsc debian-policy_3.9.3.1.tar.gz to main/d/debian-policy/debian-policy_3.9.3.1.tar.gz debian-policy_3.9.3.1_all.deb to main/d/debian-policy/debian-policy_3.9.3.1_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 622...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Russ Allbery <r...@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 ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 04 Mar 2012 15:02:12 -0800 Source: debian-policy Binary: debian-policy Architecture: source all Version: 3.9.3.1 Distribution: unstable Urgency: low Maintainer: Debian Policy List <debian-policy@lists.debian.org> Changed-By: Russ Allbery <r...@debian.org> Description: debian-policy - Debian Policy Manual and related documents Closes: 490604 601839 622263 638060 647645 658009 661412 Changes: debian-policy (3.9.3.1) unstable; urgency=low . * Fix cross-reference to control field syntax in Policy 5.4 (source package control files). Thanks, Jakub Wilk. (Closes: #661412) * Additional wording improvements to copyright-format 1.0 for clarity. Also mention that the Files pattern syntax is the same as fnmatch(3) and GNU find -path without [] patterns. Thanks, Jonathan Nieder and Ben Finney. * Suggest checkbashisms from devscripts or the posh shell for checking whether /bin/sh scripts are Policy-compliant rather than recommending dash. Thanks, Raphael Geissert. (Closes: #490604) * Remove the ambiguous word "installed" when requiring that the location of files and directories follow the FHS. (Closes: #638060) * Clarify the syntax of field names to make it clear that they may not contain spaces. Thanks, Charles Plessy. (Closes: #647645) * Clarify that only one of build-arch or build-indep may be provided (currently, at least) and that build should depend on whichever exist or perform the equivalent actions. Thanks to Jonathan Nieder for some of the wording. (Closes: #601839) * Clearly state that "yes" is the only valid value of DM-Upload-Allowed and rewrite its description to be less indirect. (Closes: #622263) * Update the dpkg-buildpackage -r documentation in the appendix to reflect the current behavior of using fakeroot. Wording from Sam Morris. (Closes: #658009) * Fix the legal notice in copyright-format to not refer to a nonexistent copyright notice. * Embed the Debian Policy version and build date in the debconf specification and the copyright-format document. We'll make non-normative changes without updating other version numbers, and it's good to know which version one is looking at. * Fix some whitespace issues in the debconf specification articleinfo. * Install the HTML version of upgrading-checklist in the policy.html directory as upgrading-checklist.html so that it can be deployed on www.debian.org in a way that will allow links to Policy sections to work easily. Thanks, Charles Plessy. (Partly addresses #639663) * Ship the copyright-format source as copyright-format.xml.tar.gz without a version, since it will include all of the versions, not just the current version. * Fix mistaken word choice (prefix instead of suffix) in the upgrading checklist entry for 3.9.3.0. * Add some missing entries to the virtual package names list changelog. * Expand package long description to include all documents. * Remove unused substitution variable generated by the build. Thanks, Charles Plessy. * Strip down and reformat debian/rules to remove unused variables, references to old files no longer included, use a more standard layout and standardize variable names, and add comments for better maintainability. * Convert debian/copyright to copyright-format 1.0, and in the process add the license information for the documents other than Policy itself and the FHS. Note the implication of the GPL source code requirement for distributing generated versions of the Policy documents. Checksums-Sha1: facc8349c136cbb6f3aafc89eb6c38d41b82e4ac 1518 debian-policy_3.9.3.1.dsc 4d50df8a4ab4ea3fa41de573b199405cb25de159 695368 debian-policy_3.9.3.1.tar.gz 290907ae9f5bcef60eaa1d0205ca34b045ded39d 1935694 debian-policy_3.9.3.1_all.deb Checksums-Sha256: ade0195864ada6010c12d154261e1fe19e4b13ac215dea41aa0d29f02ed19296 1518 debian-policy_3.9.3.1.dsc 9be84a774b077eea8c823df7974d14d2cdd0cf77bc979e95741ba6651fed30f9 695368 debian-policy_3.9.3.1.tar.gz bc8ddab8fd9d4a8195683ca3e3b7d7fc3a738e03f662308929decbe67759366b 1935694 debian-policy_3.9.3.1_all.deb Files: 1cacf0efcbec59f4c082a6d3dcc11773 1518 doc optional debian-policy_3.9.3.1.dsc 1c06d13e08b9fb2d50b5adb1225c4890 695368 doc optional debian-policy_3.9.3.1.tar.gz 815acad144d6e711eb5aa44c0cb61a93 1935694 doc optional debian-policy_3.9.3.1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJPU/YKAAoJEH2AMVxXNt51El4IAJ1KfMBdeCVEZ+OO4onMTbrL oBPsgkXM6Nbbb1Wx2y5Dh6O2i9UsxTXdQuvGMsDdLWy+Az3Ee5eq2AZ/TwFjIbkJ K+9FPhxoqqbl+c3h+2tq/ViQy8QvQv/bzNBslFYFGMiWDoLDhRocs0iArOPE0c6q G62ts3b9yTrZmuIASZPgRsP8eo7N2yriRrUFuGJdv8dQNXiEIw9IxyFz2/YyWB13 OuxxFO3AMRLIBBQoBM2FQ7u7FL+9MX8faLLlvKS8tAocI7nRnC8/UbF+SdKGI+eO YET4Yq8iojXaPg6RAaQF0B2URymMiXzGORd24ODlsibkG+x6ikCxoaYNgsAF+a0= =mh73 -----END PGP SIGNATURE-----
--- End Message ---
