<!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
<para>
Much of the conversation between Debian developers (and users) is managed
through a wide array of mailing lists we host at <literal><ulink
-url="http://&lists-host;/">&lists-host;</ulink></literal>.
+url="https://&lists-host;/">&lists-host;</ulink></literal>.
To find out more on how to subscribe or unsubscribe, how to post and how not to
post, where to find old posts and how to search them, how to contact the list
maintainers and see various other information about the mailing lists, please
</itemizedlist>
<para>
There are other mailing lists available for a variety of special topics; see
-<ulink url="http://&lists-host;/"></ulink> for a list.
+<ulink url="https://&lists-host;/"></ulink> for a list.
</para>
</section>
To get a cloak on freenode, you send Jörg Jaspert <joerg@debian.org> a
signed mail where you tell what your nick is. Put cloak somewhere in the
Subject: header. The nick should be registered: <ulink
-url="http://freenode.net/faq.shtml#nicksetup">Nick Setup Page</ulink>. The
+url="https://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="https://freenode.net/faq.shtml#projectcloak">Freenode
documentation</ulink> for more information about cloaks.
</para>
</section>
<para>
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").
-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.
+the list of open issues in the DSA (Debian System Administration) Team's queue
+of our request tracker at <ulink 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 in the request tracker, simply send a mail to &email-rt-dsa; and
+make sure to put the string "Debian RT" somewhere in the subject. To contact
+the DSA team by email, use <email>dsa@debian.org</email> for anything that
+contains private or privileged information and should not be made public, and
+<email>debian-admin@lists.debian.org</email> otherwise. The DSA team is also
+present on the <literal>#debian-admin</literal> IRC channel on OFTC.
</para>
<para>
If you have a problem with a certain service, not related to the system
the Bug Tracking System (BTS).
</para>
<para>
-It is restricted; a mirror is available on <literal>merkel</literal>.
-</para>
-<para>
If you plan on doing some statistical analysis or processing of Debian bugs,
this would be the place to do it. Please describe your plans on
&email-debian-devel; before implementing anything, however, to
end up on this server, see <xref linkend="upload"/>.
</para>
<para>
-It is restricted; a mirror is available on <literal>merkel</literal>.
+It is restricted; a mirror is available on <literal>&ftp-master-mirror;</literal>.
</para>
<para>
Problems with the Debian FTP archive generally need to be reported as bugs
bug against the pseudo-package, <systemitem
role="package">www.debian.org</systemitem>. Remember to check whether or not
someone else has already reported the problem to the <ulink
-url="http://&bugs-host;/&www-debian-org;">Bug Tracking System</ulink>.
+url="https://&bugs-host;/&www-debian-org;">Bug Tracking System</ulink>.
</para>
</section>
web, you can do this by putting material in the
<filename>public_html</filename> directory under your home directory on
<literal>people.debian.org</literal>. This will be accessible at the URL
-<literal>http://people.debian.org/~<replaceable>your-user-id</replaceable>/</literal>.
+<literal>https://people.debian.org/~<replaceable>your-user-id</replaceable>/</literal>.
</para>
<para>
You should only use this particular location because it will be backed up,
<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
+(e.g. inside the collab-maint project) 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>
The <filename>.dsc</filename> file lists all the files in the source package
-together with checksums (<command>md5sums</command>) and some additional info
+together with checksums (<command>md5sums</command>, <command>sha1sums</command>,
+<command>sha256sums</command>) and some additional info
about the package (maintainer, version, etc.).
</para>
</section>
<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>
An alternative to <literal>experimental</literal> is to use your personal web
space on <literal>people.debian.org</literal>.
</para>
-<para>
-When uploading to <literal>unstable</literal> a package which had bugs fixed
-in <literal>experimental</literal>, please consider using the option
-<literal>-v</literal> to <command>dpkg-buildpackage</command> to finally get
-them closed.
-</para>
</section>
</section>
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>; Debian 7.0, <literal>wheezy</literal>;
+and the next release will be called <literal>jessie</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
maintainer and closes all the bugs marked as fixed by the upload, and the
auto-builders may start recompiling it. The package is now publicly accessible
at <ulink url="&url-incoming;"></ulink> until it is really
-installed in the Debian archive. This happens only once a day (and is also
+installed in the Debian archive. This happens four times a day (and is also
called the `dinstall run' for historical reasons); the package is then removed
from incoming and installed in the pool along with all the other packages.
Once all the other updates (generating new <filename>Packages</filename> and
<para>
The archive maintenance software will also send the OpenPGP/GnuPG signed
<filename>.changes</filename> file that you uploaded to the appropriate mailing
-lists. If a package is released with the <literal>Distribution:</literal> set
+lists. If a package is released with the <literal>Distribution</literal> set
to <literal>stable</literal>, the announcement is sent to
&email-debian-changes;. If a package is released with
-<literal>Distribution:</literal> set to <literal>unstable</literal> or
+<literal>Distribution</literal> set to <literal>unstable</literal> or
<literal>experimental</literal>, the announcement will be posted to
-&email-debian-devel-changes; instead.
+&email-debian-devel-changes; or &email-debian-experimental-changes; instead.
</para>
<para>
Though ftp-master is restricted, a copy of the installation is available to all
<title>On the web</title>
<para>
Each package has several dedicated web pages.
-<literal>http://&packages-host;/<replaceable>package-name</replaceable></literal>
+<literal>https://&packages-host;/<replaceable>package-name</replaceable></literal>
displays each version of the package available in the various distributions.
Each version links to a page which provides information, including the package
description, the dependencies, and package download links.
<para>
The bug tracking system tracks bugs for each package. You can view the bugs of
a given package at the URL
-<literal>http://&bugs-host;/<replaceable>package-name</replaceable></literal>.
+<literal>https://&bugs-host;/<replaceable>package-name</replaceable></literal>.
</para>
</section>
<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>
<title>The PTS web interface</title>
<para>
The PTS has a web interface at <ulink
-url="http://&pts-host;/"></ulink> that puts together a lot of
+url="https://&pts-host;/"></ulink> that puts together a lot of
information about each source package. It features many useful links (BTS, QA
stats, contact information, DDTP translation status, buildd logs) and gathers
much more information from various places (30 latest changelog entries, testing
<para>
You can jump directly to the web page concerning a specific source package with
a URL like
-<literal>http://&pts-host;/<replaceable>sourcepackage</replaceable></literal>.
+<literal>https://&pts-host;/<replaceable>sourcepackage</replaceable></literal>.
</para>
<para>
This web interface has been designed like a portal for the development of
</section>
<section id="developer-misc">
-<title>Goodies for Developers</title>
-<section id="lwn">
-<title>LWN Subscriptions</title>
+<title>Goodies for Debian Developers and Debian Maintainers</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
-in <ulink
-url="http://&lists-host;/debian-devel-announce/2002/10/msg00018.html"></ulink>.
+Benefits available to Debian Developers and Debian Maintainers are documented on <ulink
+ url="https://wiki.debian.org/MemberBenefits"></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>.
-</para>
-</section>
-
</section>
</chapter>
~ianmdlvl / developers-reference.git / blobdiff