gnupg instead of pgp

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@3940 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/common.ent b/common.ent
index 6f19749e8299e967e75e377c1f1b9cf311896623..afce3c1578b12f3707ca2182b23d7e427a7cce18 100644 (file)
--- a/common.ent
+++ b/common.ent
@@ -191,7 +191,6 @@
      misc, non-debian
   -->
 <!ENTITY pgp-keyserv "<tt>subkeys.pgp.net</tt>">
-<!ENTITY file-keyservs "<file>/usr/share/doc/pgp/keyserv.doc</file>">
 
 <!ENTITY sample-dist-dirtree "<example>
 dists/stable/main/

diff --git a/debian/changelog b/debian/changelog
index e3a5951aff42dba85b7ce354b2459b0f7b088b8e..667ff34850f0d3edcac71fbe037d8cf944db4513 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,8 @@ developers-reference (3.3.8) unstable; urgency=low
   * mia-history is replaced by mia-query. Thanks, Christoph Berg.
     Closes: #350792
   * fix missing quite. Thanks, Franks Küster. Closes: #365994
+  * use gnugp instead of gpg. Thanks, Justin Pryzby, Jon Dowland.
+    Closes: #376411
 
  -- Andreas Barth <aba@not.so.argh.org>  Sat, 11 Nov 2006 10:55:44 -0700
 

diff --git a/developers-reference.sgml b/developers-reference.sgml
index bd7d010fdddafd61ed16c95bc2b93cb379f050f2..36f0880a42a27c99e808fa8310b045c8d09dc96a 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -7,7 +7,7 @@
   <!ENTITY % dynamicdata  SYSTEM "dynamic.ent" > %dynamicdata;
 
   <!-- CVS revision of this document -->
-  <!ENTITY cvs-rev "$Revision: 1.293 $">
+  <!ENTITY cvs-rev "$Revision: 1.294 $">
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
@@ -267,7 +267,8 @@ have an older key you may have to manually add those signatures.
 </footnote>
        <p>
 If your public key isn't on public key servers such as &pgp-keyserv;,
-please read the documentation available locally in &file-keyservs;.
+please read the documentation available at
+<url id="&url-newmaint-id;" name="NM Step 2: Identification">.
 That document contains instructions on how to put your key on the
 public key servers.  The New Maintainer Group will put your public key
 on the servers if it isn't already there.