From 9a70ca7ec95c1cb9ce91b2c36d1a831a39e08353 Mon Sep 17 00:00:00 2001
From: aph <aph@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Tue, 27 Mar 2001 15:41:19 +0000
Subject: [PATCH] expunge url-pkg-manual

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@1159 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 common.ent                |  3 ++-
 developers-reference.sgml | 28 +++++++++++++---------------
 2 files changed, 15 insertions(+), 16 deletions(-)

diff --git a/common.ent b/common.ent
index 8f6ce4d..c04e027 100644
--- a/common.ent
+++ b/common.ent
@@ -29,7 +29,8 @@
 <!entity keyserver-host "keyring.debian.org">
 
 <!entity url-debian-policy "http://&www-debian-org;/doc/debian-policy/">
-<!entity url-pkg-manual "http://&www-debian-org;/doc/packaging-manuals/packaging.html/">
+<!-- deprecate, this is dead
+  <!entity url-pkg-manual "http://&www-debian-org;/doc/packaging-manuals/packaging.html/"> -->
 <!entity url-social-contract "http://&www-debian-org;/social_contract">
 <!entity url-dfsg "&url-social-contract;#guidelines">
 <!entity url-debian-lists-subscribe "http://&www-debian-org;/MailingLists/subscribe">
diff --git a/developers-reference.sgml b/developers-reference.sgml
index a163155..7261437 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -5,7 +5,7 @@
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.50 $">
+  <!entity cvs-rev "$Revision: 1.51 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -76,12 +76,10 @@ discussion of resources which can help maintainers with the quality of
 their packages (<ref id="tools">).
       <p>
 It should be clear that this reference does not discuss the technical
-details of the Debian package nor how to generate Debian packages;
-that information is discussed in the <url id="&url-pkg-manual;"
-name="Debian Packaging Manual">.  Nor does this reference detail the
-standards to which Debian software must comply; that information can
-be found in the <url id="&url-debian-policy;" name="Debian Policy
-Manual">.
+details of the Debian package nor how to generate Debian packages.
+Nor does this reference detail the standards to which Debian software
+must comply.  All of such information can be found in the <url
+id="&url-debian-policy;" name="Debian Policy Manual">.
       <p>
 Furthermore, this document is <em>not an expression of formal
 policy</em>.  It contains documentation for the Debian system and
@@ -929,9 +927,9 @@ The changes file is a control file with the following fields:
 &control-file-fields;
 	  <p>
 All of these fields are mandatory for a Debian upload.  See the list
-of control fields in the <url id="&url-pkg-manual;" name="Debian
-Packaging Manual"> for the contents of these fields.  You can close
-bugs automatically using the <tt>Description</tt> field, see <ref
+of control fields in the <url id="&url-debian-policy;" name="Debian
+Policy Manual"> for the contents of these fields.  You can close bugs
+automatically using the <tt>Description</tt> field, see <ref
 id="upload-bugfix">.  Only the <tt>Distribution</tt> field is
 discussed in this section, since it relates to the archive maintenance
 policies.
@@ -1522,7 +1520,7 @@ of things you should check or be aware of.
 	    <item>
 Don't set architecture to a value other than ``all'' or ``any'' unless
 you really mean it.  In too many cases, maintainers don't follow the
-instructions in the <url id="&url-pkg-manual;" name="Debian Packaging
+instructions in the <url id="&url-debian-policy;;" name="Debian Policy
 Manual">.  Setting your architecture to ``i386'' is usually incorrect.
 	    <item>
 Make sure your source package is correct.  Do <tt>dpkg-source -x
@@ -1711,8 +1709,8 @@ belongs in.
 	<p>
 If you need to change the section for one of your packages, change the
 package control information to place the package in the desired
-section, and re-upload the package (see the <url id="&url-pkg-manual;"
-name="Debian Packaging Manual"> for details).  Carefully examine the
+section, and re-upload the package (see the <url id="&url-debian-policy;"
+name="Debian Policy Manual"> for details).  Carefully examine the
 installation log sent to you when the package is installed into the
 archive.  If for some reason the old location of the package remains,
 file a bug against <tt>ftp.debian.org</tt> asking that the old
@@ -1753,8 +1751,8 @@ announce list (either &email-debian-changes; or
 Sometimes you made a mistake naming the package and you need to rename
 it.  In this case, you need to follow a two-step process.  First, set
 your <file>debian/control</file> file to replace and conflict with the
-obsolete name of the package (see the <url id="&url-pkg-manual;"
-name="Debian Packaging Manual"> for details).  Once you've uploaded
+obsolete name of the package (see the <url id="&url-debian-policy;"
+name="Debian Policy Manual"> for details).  Once you've uploaded
 that package, and the package has moved into the archive, file a bug
 against <tt>ftp.debian.org</tt> asking to remove the package with the
 obsolete name.
-- 
2.30.2