<!ENTITY % commondata SYSTEM "common.ent" > %commondata;
]>
<chapter id="resources">
-<title>Resources for Debian Developers</title>
+<title>Resources for Debian Developers and Debian Maintainers</title>
<para>
In this chapter you will find a very brief road map of the Debian mailing
lists, the Debian machines which may be available to you as a developer, and
Subject: header. The nick should be registered: <ulink
url="http://freenode.net/faq.shtml#nicksetup">Nick Setup Page</ulink>. The
mail needs to be signed by a key in the Debian keyring. Please see <ulink
-url="http://freenode.net/faq.shtml#projectcloak">Freenodes
+url="http://freenode.net/faq.shtml#projectcloak">Freenode
documentation</ulink> for more information about cloaks.
</para>
</section>
If you have a problem with the operation of a Debian server, and you think that
the system operators need to be notified of this problem, you can check
the list of open issues in the DSA queue of our request tracker at <ulink
-url="&url-rt;" /> (you can login with user "guest" and password "readonly").
+url="&url-rt;" /> (you can login with user "debian", its password is available at
+<filename>master.debian.org:&file-debian-rt-password;</filename>).
To report a new problem, simply send a mail to &email-rt-dsa; and make
sure to put the string "Debian RT" somewhere in the subject.
</para>
<title>The VCS servers</title>
<para>
If you need to use a Version Control System for any of your Debian work,
-you can use one the existing repositories hosted on Alioth or you can
+you can use one of the existing repositories hosted on Alioth or you can
request a new project and ask for the VCS repository of your choice.
Alioth supports CVS (cvs.alioth.debian.org/cvs.debian.org), Subversion
(svn.debian.org), Arch (tla/baz, both on arch.debian.org), Bazaar
<literal>hurd</literal> and <literal>kfreebsd</literal>.
</para>
<para>
-&debian-formal; 1.3 was only available as <literal>i386</literal>. Debian
+Debian GNU/Linux 1.3 was only available as <literal>i386</literal>. Debian
2.0 shipped for <literal>i386</literal> and <literal>m68k</literal>
architectures. Debian 2.1 shipped for the <literal>i386</literal>,
<literal>m68k</literal>, <literal>alpha</literal>, and
<literal>sparc</literal> architectures. Since then Debian has grown hugely.
-Debian 5 supports a total of twelve architectures: <literal>alpha</literal>,
-<literal>amd64</literal>, <literal>arm</literal>,
-<literal>armel</literal>, <literal>hppa</literal>,
-<literal>i386</literal>, <literal>ia64</literal>, <literal>mips</literal>,
+Debian 6 supports a total of nine Linux architectures (<literal>amd64</literal>,
+<literal>armel</literal>, <literal>i386</literal>,
+<literal>ia64</literal>, <literal>mips</literal>,
<literal>mipsel</literal>, <literal>powerpc</literal>,
-<literal>s390</literal>, <literal>sparc</literal>.
+<literal>s390</literal>, <literal>sparc</literal>) and two kFreeBSD architectures
+(<literal>kfreebsd-i386</literal> and <literal>kfreebsd-amd64</literal>).
</para>
<para>
Information for developers and users about the specific ports are available at
file or both an <filename>.orig.tar.gz</filename> and a
<filename>.diff.gz</filename> file;</para></listitem>
<listitem><para>with format “3.0 (quilt)”, it has a mandatory
-<filename>.orig.tar.{gz,bz2,lzma}</filename> upstream tarball,
-multiple optional <filename>.orig-<replaceable>component</replaceable>.tar.{gz,bz2,lzma}</filename>
+<filename>.orig.tar.{gz,bz2,xz}</filename> upstream tarball,
+multiple optional <filename>.orig-<replaceable>component</replaceable>.tar.{gz,bz2,xz}</filename>
additional upstream tarballs and a mandatory
-<filename>debian.tar.{gz,bz2,lzma}</filename> debian
+<filename>debian.tar.{gz,bz2,xz}</filename> debian
tarball;</para></listitem>
<listitem><para>with format “3.0 (native)”, it has only
-a single <filename>.tar.{gz,bz2,lzma}</filename> tarball.</para></listitem>
+a single <filename>.tar.{gz,bz2,xz}</filename> tarball.</para></listitem>
</itemizedlist>
</para>
<para>
If a package is developed specially for Debian and is not distributed
outside of Debian, there is just one
-<filename>.tar.{gz,bz2,lzma}</filename> file which contains the sources of
+<filename>.tar.{gz,bz2,xz}</filename> file which contains the sources of
the program, it's called a “native” source package. If a package is
distributed elsewhere too, the
-<filename>.orig.tar.{gz,bz2,lzma}</filename> file stores the so-called
+<filename>.orig.tar.{gz,bz2,xz}</filename> file stores the so-called
<literal>upstream source code</literal>, that is the source code that's
distributed by the <literal>upstream maintainer</literal> (often the
author of the software). In this case, the <filename>.diff.gz</filename>
-or the <filename>debian.tar.{gz,bz2,lzma}</filename> contains the changes
+or the <filename>debian.tar.{gz,bz2,xz}</filename> contains the changes
made by the Debian maintainer.
</para>
<para>
<para>
Active development is done in the <literal>unstable</literal> distribution
(that's why this distribution is sometimes called the <literal>development
-distribution</literal>). Every Debian developer can update his or her
+distribution</literal>). Every Debian developer can update their
packages in this distribution at any time. Thus, the contents of this
distribution change from day to day. Since no special effort is made to make
sure everything in this distribution is working properly, it is sometimes
The <link linkend="testing">testing</link> distribution is generated
automatically by taking packages from <literal>unstable</literal> if they
satisfy certain criteria. Those criteria should ensure a good quality for
-packages within <literal>testing</literal>. The update to <literal>testing
-</literal> is launched twice each day, right after the new packages
-have been installed. See <xref linkend="testing"/>.
+packages within <literal>testing</literal>. The update to
+<literal>testing</literal> is launched twice each day, right after the new
+packages have been installed. See <xref linkend="testing"/>.
</para>
<para>
After a period of development, once the release manager deems fit, the
new copy is created for the new <literal>testing</literal>, and the previous
<literal>stable</literal> is renamed to <literal>oldstable</literal> and
stays there until it is finally archived. On archiving, the contents are moved
-to <literal>&archive-host;</literal>).
+to <literal>&archive-host;</literal>.
</para>
<para>
This development cycle is based on the assumption that the
<filename>proposed-updates</filename> directory. Those packages in
<filename>proposed-updates</filename> that pass muster are periodically moved
as a batch into the stable distribution and the revision level of the stable
-distribution is incremented (e.g., ‘3.0’ becomes ‘3.0r1’, ‘2.2r4’
-becomes ‘2.2r5’, and so forth). Please refer to
+distribution is incremented (e.g., ‘6.0’ becomes ‘6.0.1’, ‘5.0.7’
+becomes ‘5.0.8’, and so forth). Please refer to
<link linkend="upload-stable">uploads to the <literal>stable</literal>
distribution</link> for details.
</para>
packages from <literal>unstable</literal> are expected to propagate to
<literal>testing</literal> and thus to <literal>stable</literal>. You
should not be afraid to use <literal>experimental</literal> since it does not
-cause any pain to the ftpmasters, the experimental packages are automatically
+cause any pain to the ftpmasters, the experimental packages are periodically
removed once you upload the package in <literal>unstable</literal> with a
higher version number.
</para>
Debian 1.3, <literal>bo</literal>; Debian 2.0, <literal>hamm</literal>;
Debian 2.1, <literal>slink</literal>; Debian 2.2, <literal>potato</literal>;
Debian 3.0, <literal>woody</literal>; Debian 3.1, <literal>sarge</literal>;
-Debian 4.0, <literal>etch</literal>; Debian 5.0, <literal>lenny</literal>
-and the next release will be called <literal>squeeze</literal>.
+Debian 4.0, <literal>etch</literal>; Debian 5.0, <literal>lenny</literal>;
+Debian 6.0, <literal>squeeze</literal>
+and the next release will be called <literal>wheezy</literal>.
There is also a ``pseudo-distribution'', called
<literal>sid</literal>, which is the current <literal>unstable</literal>
distribution; since packages are moved from <literal>unstable</literal> to
signed <filename>*.changes</filename>-files are moved together with their
corresponding files to the <filename>unchecked</filename> directory. This
directory is not visible for most Developers, as ftp-master is restricted; it
-is scanned every 15 minutes by the <command>katie</command> script, which
-verifies the integrity of the uploaded packages and their cryptographic
+is scanned every 15 minutes by the <command>dak process-upload</command> script,
+which verifies the integrity of the uploaded packages and their cryptographic
signatures. If the package is considered ready to be installed, it is moved
-into the <filename>accepted</filename> directory. If this is the first upload
+into the <filename>done</filename> directory. If this is the first upload
of the package (or it has new binary packages), it is moved to the
<filename>new</filename> directory, where it waits for approval by the
ftpmasters. If the package contains files to be installed by hand it is moved
<para>
<command>dak ls</command> is part of the dak suite of tools, listing
available package versions for all known distributions and architectures.
-The <command>dak</command> tool is available on <literal>&ftp-master-host;
-</literal>, and on the mirror on <literal>&ftp-master-mirror;</literal>.
-It uses a single argument corresponding to a package name. An example will
-explain it better:
+The <command>dak</command> tool is available on
+<literal>&ftp-master-host;</literal>, and on the mirror on
+<literal>&ftp-master-mirror;</literal>. It uses a single argument
+corresponding to a package name. An example will explain it better:
</para>
<screen>
$ dak ls evince
<term><literal>upload-source</literal></term>
<listitem>
<para>
-The email notification from <command>katie</command> when an uploaded source
+The email notification from <command>dak</command> when an uploaded source
package is accepted.
</para>
</listitem>
<term><literal>katie-other</literal></term>
<listitem>
<para>
-Other warning and error emails from <command>katie</command> (such as an
+Other warning and error emails from <command>dak</command> (such as an
override disparity for the section and/or the priority field).
</para>
</listitem>
</section>
<section id="developer-misc">
-<title>Goodies for Developers</title>
+<title>Goodies for Debian Developers and Debian Maintainers</title>
<section id="lwn">
<title>LWN Subscriptions</title>
<para>
Since October of 2002, HP has sponsored a subscription to LWN for all
-interested Debian developers. Details on how to get access to this benefit are
+interested Debian Developers and Debian Maintainers.
+Details on how to get access to this benefit are
in <ulink
url="http://&lists-host;/debian-devel-announce/2002/10/msg00018.html"></ulink>.
</para>
</section>
-<section id="gandi">
-<title>Gandi.net Hosting Discount</title>
-<para>
-As of November 2008, Gandi.net offers a discount rate on their VPS
-hosting for Debian Developers. See
-<ulink url="http://&lists-host;/debian-devel-announce/2008/11/msg00004.html"></ulink>.
+<section id="steam">
+<title>Valve games on Steam</title>
+<para>
+Since January 2014, Valve has sponsored free subscribtions to all past and present
+Valve games on the Steam game distribution service for all interested Debian Developers
+and Debian Maintainers.
+Since Steam and Valve games are not Free Software, please avoid using your Debian
+development machines for using Steam and playing games from Steam.
+See <ulink url="http://&lists-host;/debian-devel-announce/2014/01/msg00006.html"></ulink>.
</para>
</section>