[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#824038: marked as done (PGP keyring maintenance is unclear about further references and updates)

Your message dated Sat, 28 Oct 2017 12:33:59 +0000
with message-id <E1e8QJL-00048l-Fr@fasolo.debian.org>
and subject line Bug#824038: fixed in developers-reference 3.4.19
has caused the Debian Bug report #824038,
regarding PGP keyring maintenance is unclear about further references and updates
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 owner@bugs.debian.org
immediately.)


-- 
824038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824038
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: developers-reference
Severity: normal
Tags: patch

I was trying to figure out how to update keys in the debian keyring,
specifically after expiry. I read what seemed to be the right section
to me here:

https://www.debian.org/doc/manuals/developers-reference/ch03.en.html#key-maint

But this refers mostly to complete replacements, and not updates:

http://keyring.debian.org/replacing_keys.html

It also refers to "the documentation of the debian-keyring package"
without any direct link or more clearer reference. After looking at
the debian-keyring git repository, I suppose this could be construed
as the documentation:

https://anonscm.debian.org/cgit/keyring/keyring.git/tree/cheatsheets/keyring

... but it's not installed as part of the debian-keyring package, so
I'm not sure what to do with that.

It turns out that the keyring site has all the answers I needed,
namely that you just push your keys to the keyserver and updates are
processed once a month:

http://keyring.debian.org/

So the first patch I would suggest is:

diff --git a/developer-duties.dbk b/developer-duties.dbk
index 1b5643f..389cba3 100644
--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -172,7 +172,8 @@ apply.
 <para>
 You can find a more in-depth discussion of Debian key maintenance in the
 documentation of the <systemitem role="package">debian-keyring</systemitem>
-package.
+package and the <ulink
+url="http://&keyserver-host;/";>http://&keyserver-host;/</ulink> site.
 </para>
 </section>
 
to clearly link to that host.

Then the following patch imports that critical part of the keyring
page:

--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -155,7 +155,9 @@ lost.
 <para>
 If you add signatures to your public key, or add user identities, you can
 update the Debian key ring by sending your key to the key server at
-<literal>&keyserver-host;</literal>.
+<literal>&keyserver-host;</literal>. Updates are processed at least
+once a month by the <systemitem
+role="package">debian-keyring</systemitem> package maintainers.
 </para>
 <para>
 If you need to add a completely new key or remove an old key, you need to get

One has to wonder why we have that duplication - wouldn't it be better
for the debian-keyring folks to maintain their stuff directly in the
devel-ref and point their docs here?

-- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable'), (1, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Source: developers-reference
Source-Version: 3.4.19

We believe that the bug you reported is fixed in the latest version of
developers-reference, 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 824038@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hideki Yamane <henrich@debian.org> (supplier of updated developers-reference 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@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 28 Oct 2017 20:46:22 +0900
Source: developers-reference
Binary: developers-reference developers-reference-de developers-reference-fr developers-reference-ja developers-reference-ru developers-reference-it
Architecture: source all
Version: 3.4.19
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers <debian-policy@lists.debian.org>
Changed-By: Hideki Yamane <henrich@debian.org>
Description:
 developers-reference - guidelines and information for Debian developers
 developers-reference-de - guidelines and information for Debian developers, in German
 developers-reference-fr - guidelines and information for Debian developers, in French
 developers-reference-it - guidelines and information for Debian developers, in Italian
 developers-reference-ja - guidelines and information for Debian developers, in Japanese
 developers-reference-ru - guidelines and information for Debian developers, in Russian
Closes: 824038
Changes:
 developers-reference (3.4.19) unstable; urgency=medium
 .
   [ Hideki Yamane ]
   * debian/control
     - set Build-Depends: debhelper (>= 10)
   * debian/compat
     - set 10
   * update translation template and Japanese translation
 .
   [ Antoine Beaupré ]
   * clarify PGP keyring maintenance updates (Closes: #824038)
   * clarify that we use the literal codename in stable updates
   * clarify how the patch should be made for p-u
   * clarify what the p-u changelog should contain
   * clarify that the release team wants a source debdiff
 .
   [ Paul Wise ]
   * Use mkdir -p instead of ignoring mkdir exit codes
 .
   [ Boyuan Yang ]
   * Add information about debmake-doc in section 2.1.
   * d/control: Bump Standards-Version to 4.1.1.
   * Use ddtp2.d.n instead of ddtp.d.n since the latter one is dead.
Checksums-Sha1:
 4c2c9c93c0f8f8062d16f21934e6d45553a86655 2499 developers-reference_3.4.19.dsc
 05504d5ac99f0e0a33238b840e0eb8f0349ea747 649256 developers-reference_3.4.19.tar.xz
 cc6935dde0ec5dd15b460b5f45a8edfa1441bf71 914580 developers-reference-de_3.4.19_all.deb
 9ab32c75e0c9b0bf2626c8a0c8b745a04c2df3c4 889244 developers-reference-fr_3.4.19_all.deb
 33e4b23fba258faa6319373ed10be4c5388fa8c5 868776 developers-reference-it_3.4.19_all.deb
 97f6c7d748f899f68bab6c6fdcd60fe9db0dc9e4 1327860 developers-reference-ja_3.4.19_all.deb
 82065e5ae5ea6b219080a4fa07ce5764ec1e847c 980124 developers-reference-ru_3.4.19_all.deb
 29bcf1f7a028b3d9e0af7f1c1b1f1295f63b40fb 818740 developers-reference_3.4.19_all.deb
 a2b0ca18df0e44d292a7e12aac7ce54d20874d18 11887 developers-reference_3.4.19_amd64.buildinfo
Checksums-Sha256:
 fb624c42e54e92d05af57a7b56c672b562d0d0914b4afa18271fea060d6872e4 2499 developers-reference_3.4.19.dsc
 34530f0c00db53dab3396835c1b2edbbc9f5bbcc5364a497dac90f2ab52ce87a 649256 developers-reference_3.4.19.tar.xz
 6b62bab68ce8b37f590043ba201527da058877742fe4109da27790df0e0ce456 914580 developers-reference-de_3.4.19_all.deb
 01a9108eb772ac4cf4c493805d86b7e4d85432cfa58cbf5ec51e798d5d892167 889244 developers-reference-fr_3.4.19_all.deb
 b75d532415da7d38ccf5968b7d3b7983aa9d04ae58ccd7f60410b1d15fae3a7d 868776 developers-reference-it_3.4.19_all.deb
 2f70e7c5536835808859e1b6c9ed18b29232ff689a75ae14a3d3a49a32d37dc3 1327860 developers-reference-ja_3.4.19_all.deb
 e74c76bc2daa08d14dedd4d8d2834403cf2154a6fd5f1f718b6740433084f4e8 980124 developers-reference-ru_3.4.19_all.deb
 bb55a3676ed27b3c2b092d97dbc23298971ec88d69e1b039771d3d37dc6980e8 818740 developers-reference_3.4.19_all.deb
 38f089287397451f8005974b0ea47efc4632524daecf6e588475d2c2dd32f51b 11887 developers-reference_3.4.19_amd64.buildinfo
Files:
 d14a59d3dadec24ee5ba60063bd0883c 2499 doc optional developers-reference_3.4.19.dsc
 0e74f49caf16372492795161e4ed1377 649256 doc optional developers-reference_3.4.19.tar.xz
 9bf9b0c6598d16abe4e5fcd4c58abbdf 914580 doc optional developers-reference-de_3.4.19_all.deb
 82abf6eeef4bbd5fe00725140a3ee4b3 889244 doc optional developers-reference-fr_3.4.19_all.deb
 231a50f412c75e62546bbb9ae9ed9afd 868776 doc optional developers-reference-it_3.4.19_all.deb
 784127cf7b2e95e91050857f23ffa913 1327860 doc optional developers-reference-ja_3.4.19_all.deb
 1e3b0846b00b272a406eee8bc878a5f4 980124 doc optional developers-reference-ru_3.4.19_all.deb
 00c1482098439baa9ae38612042ff8cb 818740 doc optional developers-reference_3.4.19_all.deb
 3cfcde23b3f980485831849924c43b6a 11887 doc optional developers-reference_3.4.19_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJHBAEBCgAxFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAln0dU8THGhlbnJpY2hA
ZGViaWFuLm9yZwAKCRBdMo0IKqqxQHzND/4oBfGaE1mLbSNfmbSuZ1652tzQ9sGT
6k7FL6LZsUq4cCsZN/jfvf+GYVMScKOccP4UpVQ6nGqfkvknQ7U3G+/iFd2qQ+rc
OZD2CFRXn3BlaiMWr5HztkVZfcXITcsDCW0YpOuNEDoYmGtQBmqPwEkJxuQPYtD7
zuUoYqM3774nox6O4B9+wSB0CP7l3IsphaJknMMbnjX2fMnTGyaJFkd4qiEtwQtR
Cmq/KIOo+d4qNhCiS+8bNDZF9CTvjOLbTjKGlSsekaDI4PbVT14Tzgt29WoizRMK
BHmilD+pwHWRtBGALXdXTJAG8bTFHOWbibpa3E9KS46784xfsm9uq1oLTd0lTELL
itZ2H4NHU4cbki0tR6DTb6rHRNu/lDp8oFochGBx70DLQjDTArB+hKxK/CROQbYb
u8U/YnbscjgIUTZig+5tBpAYkY5dmf8VG+qwIXsD8qPCEPMhu20kHJOR9g9oFCHc
OWx9zERdSlxjTSs3tECaEmvu0e74aE6YVfWgTDKHoYC1rI9VLHEAKTkJn3JKDYF2
Sq53xnC7XUMRFsuzjXQN6o3M2/4pJidnSixRSs7SlYstGa3mJU4beuHlxfsqdORZ
eUQH2VKmve1mHUCvmqoJpgU/ci/OYpzxhzq+uk2Dxz2gHDG6HhFxlhlNUXU27VN8
qTJx35m6QRARNQ==
=s4oO
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: