X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;ds=sidebyside;f=tools.dbk;h=25d61a0ffca7b49402cb00c90f4cc57f40381d03;hb=c81927355fe51c8a09827d098d0caad05a052d67;hp=de5cfd4b13f639da4e42fd3772aa6ed29a1f28b9;hpb=a178c5d1e5a28aba66fa3f2ed84e2173c20cd2fd;p=developers-reference.git

diff --git a/tools.dbk b/tools.dbk
index de5cfd4..25d61a0 100644
--- a/tools.dbk
+++ b/tools.dbk
@@ -1,6 +1,8 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
-    "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+    "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
+  <!ENTITY % commondata  SYSTEM "common.ent" > %commondata;
+]>
 <appendix id="tools">
 <title>Overview of Debian Maintainer Tools</title>
 <para>
@@ -104,7 +106,7 @@ use Lintian.
 </para>
 <para>
 You can also see a summary of all problems reported by Lintian on your packages
-at <ulink url="http://lintian.debian.org/"></ulink>.  These reports contain the
+at <ulink url="&url-lintian;"></ulink>.  These reports contain the
 latest <command>lintian</command> output for the whole development distribution
 (unstable).
 </para>
@@ -134,13 +136,13 @@ help you prevent various accidents.
 You can run it over a pair of binary packages:
 </para>
 <screen>
- package_1-1_arch.deb package_2-1_arch.deb
+debdiff package_1-1_arch.deb package_2-1_arch.deb
 </screen>
 <para>
 Or even a pair of changes files:
 </para>
 <screen>
- package_1-1_arch.changes package_2-1_arch.changes
+debdiff package_1-1_arch.changes package_2-1_arch.changes
 </screen>
 <para>
 For more information please see <citerefentry>
@@ -314,7 +316,7 @@ It can use chrooted environments as well.  It can be used stand-alone, or as
 part of a networked, distributed build environment.  As the latter, it is part
 of the system used by porters to build binary packages for all the available
 architectures.  See <xref linkend="buildd"/> for more information, and <ulink
-url="http://buildd.debian.org/"></ulink> to see the system in action.
+url="&url-buildd;"></ulink> to see the system in action.
 </para>
 </section>
 
@@ -457,7 +459,7 @@ process through <command>dpkg-depcheck</command> will provide you with a good
 first approximation of the build-dependencies.  For example:
 </para>
 <screen>
--depcheck -b debian/rules build
+dpkg-depcheck -b debian/rules build
 </screen>
 <para>
 <command>dpkg-depcheck</command> can also be used to check for run-time