<?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>
</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>
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>
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>
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