X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=resources.dbk;h=0591af7c587fd90f6564e2ad7ce2f18c1c752d1e;hp=78aaab720c3e02879b2f103e214b734f17e0d16f;hb=1a3c57034ada63e6ca12243296044e38beea49fd;hpb=c860a39ea13f7d552fc940a546b01be70c09b3a0
diff --git a/resources.dbk b/resources.dbk
index 78aaab7..0591af7 100644
--- a/resources.dbk
+++ b/resources.dbk
@@ -638,9 +638,10 @@ literally unstable.
The testing distribution is generated
-automatically by taking packages from unstable if they satisfy certain
-criteria. Those criteria should ensure a good quality for packages within
-testing. The update to testing is launched each day after the new packages
+automatically by taking packages from unstable if they
+satisfy certain criteria. Those criteria should ensure a good quality for
+packages within testing. The update to testing
+ is launched twice each day, right after the new packages
have been installed. See .
@@ -687,8 +688,8 @@ place in parallel with testing.
More information about the testing distribution
-Packages are usually installed into the `testing' distribution after they have
-undergone some degree of testing in unstable.
+Packages are usually installed into the testing distribution
+after they have undergone some degree of testing in unstable.
For more details, please see the information about
@@ -700,7 +701,8 @@ the testing distribution.
Experimental
The experimental distribution is a special distribution.
-It is not a full distribution in the same sense as `stable' and `unstable' are.
+It is not a full distribution in the same sense as stable,
+testing and unstable are.
Instead, it is meant to be a temporary staging area for highly experimental
software where there's a good chance that the software could break your system,
or software that's just too unstable even for the unstable
@@ -753,9 +755,10 @@ An alternative to experimental is to use your personal web
space on people.debian.org.
-When uploading to unstable a package which had bugs fixed in experimental,
-please consider using the option -v to
-dpkg-buildpackage to finally get them closed.
+When uploading to unstable a package which had bugs fixed
+in experimental, please consider using the option
+-v to dpkg-buildpackage to finally get
+them closed.
@@ -765,22 +768,29 @@ please consider using the option -v to
Release code names
Every released Debian distribution has a code name: Debian
-1.1 is called `buzz'; Debian 1.2, `rex'; Debian 1.3, `bo'; Debian 2.0, `hamm';
-Debian 2.1, `slink'; Debian 2.2, `potato'; Debian 3.0, `woody'; Debian 3.1,
-sarge; Debian 4.0, etch. There is also a ``pseudo-distribution'', called
-`sid', which is the current `unstable' distribution; since packages are moved
-from `unstable' to `testing' as they approach stability, `sid' itself is never
-released. As well as the usual contents of a Debian distribution, `sid'
-contains packages for architectures which are not yet officially supported or
-released by Debian. These architectures are planned to be integrated into the
-mainstream distribution at some future date.
+1.1 is called buzz; Debian 1.2, rex;
+Debian 1.3, bo; Debian 2.0, hamm;
+Debian 2.1, slink; Debian 2.2, potato;
+Debian 3.0, woody; Debian 3.1, sarge;
+Debian 4.0, etch; Debian 5.0, lenny
+and the next release will be called squeeze.
+There is also a ``pseudo-distribution'', called
+sid, which is the current unstable
+distribution; since packages are moved from unstable to
+testing as they approach stability, sid
+itself is never released. As well as the usual contents of a Debian
+distribution, sid contains packages for architectures which
+are not yet officially supported or released by Debian. These architectures
+are planned to be integrated into the mainstream distribution at some future
+date.
Since Debian has an open development model (i.e., everyone can participate and
-follow the development) even the `unstable' and `testing' distributions are
-distributed to the Internet through the Debian FTP and HTTP server network.
-Thus, if we had called the directory which contains the release candidate
-version `testing', then we would have to rename it to `stable' when the version
+follow the development) even the unstable and
+testing distributions are distributed to the Internet through the
+Debian FTP and HTTP server network. Thus, if we had called the directory which
+contains the release candidate version testing, then we
+would have to rename it to stable when the version
is released, which would cause all FTP mirrors to re-retrieve the whole
distribution (which is quite large).
@@ -875,11 +885,11 @@ script is called to ask all the primary mirrors to update themselves.
The archive maintenance software will also send the OpenPGP/GnuPG signed
.changes file that you uploaded to the appropriate mailing
lists. If a package is released with the Distribution: set
-to `stable', the announcement is sent to
+to stable, the announcement is sent to
&email-debian-changes;. If a package is released with
-Distribution: set to `unstable' or `experimental', the
-announcement will be posted to &email-debian-devel-changes;
-instead.
+Distribution: set to unstable or
+experimental, the announcement will be posted to
+&email-debian-devel-changes; instead.
Though ftp-master is restricted, a copy of the installation is available to all
@@ -962,28 +972,30 @@ a given package at the URL
-
-The <command>madison</command> utility
+
+The <command>dak ls</command> utility
-madison is a command-line utility that is available on
-&ftp-master-host;, and on the mirror on
-&ftp-master-mirror;. It uses a single argument corresponding
-to a package name. In result it displays which version of the package is
-available for each architecture and distribution combination. An example will
-explain it better.
+dak ls is part of the dak suite of tools, listing
+available package versions for all known distributions and architectures.
+The dak tool is available on &ftp-master-host;
+, and on the mirror on &ftp-master-mirror;.
+It uses a single argument corresponding to a package name. An example will
+explain it better:
-$ madison libdbd-mysql-perl
-libdbd-mysql-perl | 1.2202-4 | stable | source, alpha, arm, i386, m68k, powerpc, sparc
-libdbd-mysql-perl | 1.2216-2 | testing | source, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
-libdbd-mysql-perl | 1.2216-2.0.1 | testing | alpha
-libdbd-mysql-perl | 1.2219-1 | unstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
+$ dak ls evince
+evince | 0.1.5-2sarge1 | oldstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
+evince | 0.4.0-5 | etch-m68k | source, m68k
+evince | 0.4.0-5 | stable | source, alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc
+evince | 2.20.2-1 | testing | source
+evince | 2.20.2-1+b1 | testing | alpha, amd64, arm, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc
+evince | 2.22.2-1 | unstable | source, alpha, amd64, arm, armel, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
In this example, you can see that the version in unstable
differs from the version in testing and that there has
-been a binary-only NMU of the package for the alpha architecture. Each version
-of the package has been recompiled on most of the architectures.
+been a binary-only NMU of the package for all architectures. Each version
+of the package has been recompiled on all architectures.