</para>
<para>
Assuming no one else is already working on your prospective package, you must
-then submit a bug report (<xref linkend="submit-bug"/> ) against the
+then submit a bug report (<xref linkend="submit-bug"/>) against the
pseudo-package <systemitem role="package">wnpp</systemitem> describing your
plan to create a new package, including, but not limiting yourself to, a
description of the package, the license of the prospective package, and the
current URL where it can be downloaded from.
</para>
<para>
-You should set the subject of the bug to <literal>ITP:
+You should set the subject of the bug to <literal>ITP:
<replaceable>foo</replaceable> -- <replaceable>short
description</replaceable></literal>, substituting the name of the new
-package for <replaceable>foo</replaceable>.
+package for <replaceable>foo</replaceable>.
The severity of the bug report must be set to <literal>wishlist</literal>.
Please send a copy to &email-debian-devel; by using the X-Debbugs-CC
header (don't use CC:, because that way the message's subject won't
indicate the bug number). If you are packaging so many new packages (>10)
-that notifying the mailing list in seperate messages is too disruptive,
-do send a summary after filing the bugs to the debian-devel list instead.
+that notifying the mailing list in separate messages is too disruptive,
+send a summary after filing the bugs to the debian-devel list instead.
This will inform the other developers about upcoming packages and will
allow a review of your description and package name.
</para>
<para>
-Please include a <literal>Closes:
-bug#<replaceable>nnnnn</replaceable></literal> entry in the changelog of the
-new package in order for the bug report to be automatically closed once the new
-package is installed in the archive (see <xref linkend="upload-bugfix"/> ).
+Please include a <literal>Closes: #<replaceable>nnnnn</replaceable></literal>
+entry in the changelog of the new package in order for the bug report to
+be automatically closed once the new package is installed in the archive
+(see <xref linkend="upload-bugfix"/>).
</para>
<para>
If you think your package needs some explanations for the administrators of the
-NEW package queue, include them in your changelog, send to ftpmaster@debian.org
+NEW package queue, include them in your changelog, send to &email-ftpmaster;
a reply to the email you receive as a maintainer after your upload, or reply to
the rejection email in case you are already re-uploading.
</para>
<para>
-When closing security bugs include CVE numbers as well as the Closes: #nnnnn.
+When closing security bugs include CVE numbers as well as the
+<literal>Closes: #<replaceable>nnnnn</replaceable></literal>
This is useful for the security team to track vulnerabilities. If an upload is
made to fix the bug before the advisory ID is known, it is encouraged to modify
the historical changelog entry with the next upload. Even in this case, please
The <filename>debian/changelog</filename> file conforms to a certain structure,
with a number of different fields. One field of note, the
<literal>distribution</literal>, is described in <xref
-linkend="distribution"/> . More information about the structure of this file
+linkend="distribution"/>. More information about the structure of this file
can be found in the Debian Policy section titled
<filename>debian/changelog</filename>.
</para>
<para>
Changelog entries can be used to automatically close Debian bugs when the
-package is installed into the archive. See <xref linkend="upload-bugfix"/> .
+package is installed into the archive. See <xref linkend="upload-bugfix"/>.
</para>
<para>
It is conventional that the changelog entry of a package that contains a new
<para>
There are tools to help you create entries and finalize the
<filename>changelog</filename> for release — see <xref linkend="devscripts"/>
-and <xref linkend="dpkg-dev-el"/> .
+and <xref linkend="dpkg-dev-el"/>.
</para>
<para>
-See also <xref linkend="bpp-debian-changelog"/> .
+See also <xref linkend="bpp-debian-changelog"/>.
</para>
</section>
</para>
<para>
For more information on <command>lintian</command>, see <xref
-linkend="lintian"/> .
+linkend="lintian"/>.
</para>
</listitem>
<listitem>
<para>
-Optionally run <xref linkend="debdiff"/> to analyze changes from an older
+Optionally run <command>debdiff</command> (see <xref linkend="debdiff"/>) to analyze changes from an older
version, if one exists.
</para>
</listitem>
Copy the source package in a different directory and try unpacking it and
rebuilding it. This tests if the package relies on existing files outside of
it, or if it relies on permissions being preserved on the files shipped inside
-the .diff.gz file.
+the <filename>.diff.gz</filename> file.
</para>
</listitem>
</itemizedlist>
<listitem>
<para>
the (more common) packages where there's an original source tarball file
-accompanied by another file that contains the patches applied for Debian
+accompanied by another file that contains the changes made by Debian
</para>
</listitem>
</itemizedlist>
<para>
For the native packages, the source package includes a Debian source control
file (<literal>.dsc</literal>) and the source tarball
-(<literal>.tar.gz</literal>). A source package of a non-native package
+(<literal>.tar.{gz,bz2,lzma}</literal>). A source package of a non-native package
includes a Debian source control file, the original source tarball
-(<literal>.orig.tar.gz</literal>) and the Debian patches
-(<literal>.diff.gz</literal>).
+(<literal>.orig.tar.{gz,bz2,lzma}</literal>) and the Debian changes
+(<literal>.diff.gz</literal> for the source format “1.0” or
+<literal>.debian.tar.{gz,bz2,lzma}</literal> for the source format “3.0 (quilt)”).
</para>
<para>
-Whether a package is native or not is determined when it is built by
-<citerefentry> <refentrytitle>dpkg-buildpackage</refentrytitle>
-<manvolnum>1</manvolnum> </citerefentry>. The rest of this section relates
-only to non-native packages.
+With source format “1.0”, whether a package is native or not was determined
+by <command>dpkg-source</command> at build time. Nowadays it is recommended
+to be explicit about the desired source format by putting either “3.0 (quilt)”
+or “3.0 (native)” in <filename>debian/source/format</filename>.
+The rest of this section relates only to non-native packages.
</para>
<para>
The first time a version is uploaded which corresponds to a particular upstream
<para>
By default, <command>dpkg-genchanges</command> and
<command>dpkg-buildpackage</command> will include the original source tar file
-if and only if the Debian revision part of the source version number is 0 or 1,
-indicating a new upstream version. This behavior may be modified by using
+if and only if the current changelog entry has a different upstream version
+from the preceding entry. This behavior may be modified by using
<literal>-sa</literal> to always include it or <literal>-sd</literal> to always
leave it out.
</para>
</para>
<para>
Please notice that, in non-native packages, permissions on files that are not
-present in the .orig.tar.gz will not be preserved, as diff does not store file
-permissions in the patch.
+present in the .orig.tar.{gz,bz2,lzma} will not be preserved, as diff does not store file
+permissions in the patch. However when using source format “3.0 (quilt)”,
+permissions of files inside the <filename>debian</filename> directory are
+preserved since they are stored in a tar archive.
</para>
</section>
Each upload needs to specify which distribution the package is intended for.
The package build process extracts this information from the first line of the
<filename>debian/changelog</filename> file and places it in the
-<literal>Distribution</literal> field of the <literal>.changes</literal> file.
+<literal>Distribution</literal> field of the <filename>.changes</filename> file.
</para>
<para>
There are several possible values for this field: <literal>stable</literal>,
<literal>unstable</literal>.
</para>
<para>
-Actually, there are two other possible distributions: <literal>stable-security
-</literal> and <literal>testing-security</literal>, but read
+Actually, there are two other possible distributions: <literal>stable-security</literal>
+and <literal>testing-security</literal>, but read
<xref linkend="bug-security"/> for more information on those.
</para>
<para>
time.
</para>
<section id="upload-stable">
-<title>Special case: uploads to the <literal>stable</literal> and
+<title>Special case: uploads to the <literal>stable</literal> and
<literal>oldstable</literal> distributions</title>
<para>
-Uploading to <literal>stable</literal> means that the package will transfered
+Uploading to <literal>stable</literal> means that the package will transferred
to the <literal>proposed-updates-new</literal> queue for review by the stable
release managers, and if approved will be installed in
<filename>stable-proposed-updates</filename> directory of the Debian archive.
running <literal>stable</literal>, so that their dependencies are limited to
the libraries (and other packages) available in <literal>stable</literal>;
for example, a package uploaded to <literal>stable</literal> that depends on
-a library package that only exists in <literal>unstable</literal> will be
+a library package that only exists in <literal>unstable</literal> will be
rejected. Making changes to dependencies of other packages (by messing with
-<literal>Provides</literal> or <literal>shlibs</literal> files), possibly
+<literal>Provides</literal> or <filename>shlibs</filename> files), possibly
making those other packages uninstallable, is strongly discouraged.
</para>
<para>
Uploads to the <literal>oldstable</literal> distributions are possible as
-long as it hasn't been archived. The same rules as for <literal>stable
-</literal> apply.
+long as it hasn't been archived. The same rules as for <literal>stable</literal>
+apply.
</para>
</section>
<title>Uploading to <literal>ftp-master</literal></title>
<para>
To upload a package, you should upload the files (including the signed changes
-and dsc-file) with anonymous ftp to <literal>&ftp-master-host;</literal> in
+and dsc-file) with anonymous ftp to <literal>&ftp-upload-host;</literal> in
the directory <ulink
-url="ftp://&ftp-master-host;&upload-queue;">&upload-queue;</ulink>.
+url="ftp://&ftp-upload-host;&upload-queue;">&upload-queue;</ulink>.
To get the files processed there, they need to be signed with a key in the
Debian Developers keyring or the Debian Maintainers keyring
(see <ulink url="&url-wiki-dm;"></ulink>).
changes file and see that not all files have been uploaded.
</para>
<para>
-You may also find the Debian packages <xref linkend="dupload"/> or <xref
-linkend="dput"/> useful when uploading packages. These handy programs help
-automate the process of uploading packages into Debian.
+You may also find the Debian packages <link linkend="dupload">dupload</link>
+or <link linkend="dput">dput</link> useful when uploading packages.These
+handy programs help automate the process of uploading packages into Debian.
</para>
<para>
-For removing packages, please see the README file in that ftp directory, and
-the Debian package <xref linkend="dcut"/> .
+For removing packages, please see
+<ulink url="ftp://&ftp-upload-host;&upload-queue;README"/> and
+the Debian package <link linkend="dcut">dcut</link>.
</para>
</section>
<para>
It is sometimes useful to upload a package immediately, but to want this
package to arrive in the archive only a few days later. For example,
-when preparing a <link linkend="nmu">Non-maintainer Upload</link>,
+when preparing a <link linkend="nmu">Non-Maintainer Upload</link>,
you might want to give the maintainer a few days to react.
</para>
<para>
An upload to the delayed directory keeps the package in
-<ulink url="http://ftp-master.debian.org/deferred.html">
-the deferred uploads queue"</ulink>.
+<ulink url="http://ftp-master.debian.org/deferred.html">the deferred uploads queue</ulink>.
When the specified waiting time is over, the package is moved into
the regular incoming directory for processing.
This is done through automatic uploading to
-<literal>&ftp-master-host;</literal> in upload-directory
+<literal>&ftp-upload-host;</literal> in upload-directory
<literal>DELAYED/[012345678]-day</literal>. 0-day is uploaded
-multiple times per day to <literal>&ftp-master-host;</literal>.
+multiple times per day to <literal>&ftp-upload-host;</literal>.
</para>
<para>
With dput, you can use the <literal>--delayed <replaceable>DELAY</replaceable></literal>
<title>Security uploads</title>
<para>
Do <emphasis role="strong">NOT</emphasis> upload a package to the security
-upload queue (<literal>oldstable-security</literal>, <literal>stable-security
-</literal>, etc.) without prior authorization from the security team. If the
+upload queue (<literal>oldstable-security</literal>, <literal>stable-security</literal>,
+etc.) without prior authorization from the security team. If the
package does not exactly meet the team's requirements, it will cause many
problems and delays in dealing with the unwanted upload. For details, please
-see section <xref linkend="bug-security"/> .
+see <xref linkend="bug-security"/>.
</para>
</section>
<section id="s5.6.5">
<title>Other upload queues</title>
<para>
-The scp queues on <literal>&ftp-master-host;</literal>, and <literal>
-security.debian.org</literal> are mostly unusable due to the login restrictions
-on those hosts.
+There is an alternative upload queue in Europe at <ulink
+url="ftp://&ftp-eu-upload-host;&upload-queue;"/>. It operates in
+the same way as <literal>&ftp-upload-host;</literal>, but should be faster
+for European developers.
</para>
<para>
-The anonymous queues on ftp.uni-erlangen.de and ftp.uk.debian.org are currently
-down. Work is underway to resurrect them.
-</para>
-<para>
-The queues on master.debian.org, samosa.debian.org, master.debian.or.jp, and
-ftp.chiark.greenend.org.uk are down permanently, and will not be resurrected.
+Packages can also be uploaded via ssh to
+<literal>&ssh-upload-host;</literal>; files should be put
+<literal>/srv/upload.debian.org/UploadQueue</literal>. This queue does
+not support <link linkend="delayed-incoming">delayed uploads</link>.
</para>
</section>
For the most part, uploads are automatically handled on a daily basis by the
archive maintenance tools, <command>katie</command>. Specifically, updates to
existing packages to the <literal>unstable</literal> distribution are handled
-automatically. In other cases, notably new packages, placing the uploaded
+automatically. In other cases, notably new packages, placing the uploaded
package into the distribution is handled manually. When uploads are handled
manually, the change to the archive may take up to a month to occur. Please
be patient.
<para>
Note that the <literal>Section</literal> field describes both the section as
well as the subsection, which are described in <xref
-linkend="archive-sections"/> . If the section is main, it should be omitted.
+linkend="archive-sections"/>. If the section is main, it should be omitted.
The list of allowable subsections can be found in <ulink
url="&url-debian-policy;ch-archive.html#s-subsections"></ulink>.
</para>
<para>
Every developer has to be able to work with the Debian <ulink
url="&url-bts;">bug tracking system</ulink>. This includes
-knowing how to file bug reports properly (see <xref linkend="submit-bug"/> ),
+knowing how to file bug reports properly (see <xref linkend="submit-bug"/>),
how to update them and reorder them, and how to process and close them.
</para>
<para>
<para>
When responding to bugs, make sure that any discussion you have about bugs is
sent both to the original submitter of the bug, and to the bug itself (e.g.,
-<email>123@&bugs-host;</email>). If you're writing a new mail and you
+<email><replaceable>123</replaceable>@&bugs-host;</email>). If you're writing a new mail and you
don't remember the submitter email address, you can use the
-<email>123-submitter@&bugs-host;</email> email to contact the submitter
+<email><replaceable>123</replaceable>-submitter@&bugs-host;</email> email to contact the submitter
<emphasis>and</emphasis> to record your mail within the bug log (that means you
-don't need to send a copy of the mail to <email>123@&bugs-host;</email>).
+don't need to send a copy of the mail to <email><replaceable>123</replaceable>@&bugs-host;</email>).
</para>
<para>
If you get a bug which mentions FTBFS, this means Fails to build from source.
<para>
Once you've dealt with a bug report (e.g. fixed it), mark it as
<literal>done</literal> (close it) by sending an explanation message to
-<email>123-done@&bugs-host;</email>. If you're fixing a bug by changing
+<email><replaceable>123</replaceable>-done@&bugs-host;</email>. If you're fixing a bug by changing
and uploading the package, you can automate bug closing as described in <xref
-linkend="upload-bugfix"/> .
+linkend="upload-bugfix"/>.
</para>
<para>
You should <emphasis>never</emphasis> close bugs via the bug server
you should ask for help on <link linkend="irc-channels">IRC</link> or
on &email-debian-devel;. Please inform the maintainer(s) of the package
you reassign the bug to, for example by Cc:ing the message that does the
-reassign to <email>packagename@packages.debian.org</email> and explaining
+reassign to <email><replaceable>packagename</replaceable>@packages.debian.org</email> and explaining
your reasons in that mail. Please note that a simple reassignment is
<emphasis>not</emphasis> e-mailed to the maintainers of the package
being reassigned to, so they won't know about it until they look at
<listitem>
<para>
If you have fixed a bug in your local copy, or if a fix has been committed to
-the CVS repository, you may tag the bug as <literal>pending</literal> to let
+the VCS repository, you may tag the bug as <literal>pending</literal> to let
people know that the bug is corrected and that it will be closed with the next
upload (add the <literal>closes:</literal> in the
<filename>changelog</filename>). This is particularly useful if you are
We prefer the <literal>closes: #<replaceable>XXX</replaceable></literal>
syntax, as it is the most concise entry and the easiest to integrate with the
text of the <filename>changelog</filename>. Unless specified different by the
-<replaceable>-v</replaceable>-switch to <command>dpkg-buildpackage</command>,
+<literal>-v</literal>-switch to <command>dpkg-buildpackage</command>,
only the bugs closed in the most recent changelog entry are closed (basically,
exactly the bugs mentioned in the changelog-part in the
<filename>.changes</filename> file are closed).
</para>
<para>
-Historically, uploads identified as <link linkend="nmu">Non-maintainer
+Historically, uploads identified as <link linkend="nmu">non-maintainer
upload (NMU)</link> were tagged <literal>fixed</literal> instead of being
closed, but that practice was ceased with the advent of version-tracking. The
same applied to the tag <literal>fixed-in-experimental</literal>.
to the bug tracking system's control address,
&email-bts-control;. To close any remaining bugs that were
fixed by your upload, email the <filename>.changes</filename> file to
-<email>XXX-done@&bugs-host;</email>, where <replaceable>XXX</replaceable>
-is the bug number, and put Version: YYY and an empty line as the first two
+<email><replaceable>XXX</replaceable>-done@&bugs-host;</email>, where <replaceable>XXX</replaceable>
+is the bug number, and put Version: <replaceable>YYY</replaceable> and an empty line as the first two
lines of the body of the email, where <replaceable>YYY</replaceable> is the
first version where the bug has been fixed.
</para>
Bear in mind that it is not obligatory to close bugs using the changelog as
described above. If you simply want to close bugs that don't have anything to
do with an upload you made, do it by emailing an explanation to
-<email>XXX-done@&bugs-host;</email>. Do <emphasis
+<email><replaceable>XXX</replaceable>-done@&bugs-host;</email>. Do <emphasis
role="strong">not</emphasis> close bugs in the changelog entry of a version if
the changes in that version of the package don't have any bearing on the bug.
</para>
<para>
For general information on how to write your changelog entries, see <xref
-linkend="bpp-debian-changelog"/> .
+linkend="bpp-debian-changelog"/>.
</para>
</section>
<listitem>
<para>
Which versions of the package are known to be affected by the bug. Check each
-version that is present in a supported Debian release, as well as
+version that is present in a supported Debian release, as well as
<literal>testing</literal> and <literal>unstable</literal>.
</para>
</listitem>
<listitem>
<para>
Any information needed for the advisory (see <xref
-linkend="bug-security-advisories"/> )
+linkend="bug-security-advisories"/>)
</para>
</listitem>
</itemizedlist>
<title>The Security Tracker</title>
<para>
The security team maintains a central database, the
-<ulink url="http://security-tracker.debian.net/">Debian Security Tracker</ulink>.
+<ulink url="http://security-tracker.debian.org/">Debian Security Tracker</ulink>.
This contains all public information that is known about security issues:
which packages and versions are affected or fixed, and thus whether stable,
testing and/or unstable are vulnerable. Information that is still confidential
be sure to mention this fact.
</para>
<para>
-Please note that if secrecy is needed you may not upload a fix to
+Please note that if secrecy is needed you may not upload a fix to
<literal>unstable</literal> (or
anywhere else, such as a public CVS repository). It is not sufficient to
obfuscate the details of the change, as the code itself is public, and can (and
</para>
<para>
The Security Team has a PGP-key to enable encrypted communication about
-sensitive issues. See the <ulink url="http://www.debian.org/security/faq.en.html#contact">Security Team FAQ</ulink> for details.
+sensitive issues. See the <ulink url="http://www.debian.org/security/faq#contact">Security Team FAQ</ulink> for details.
</para>
</section>
<systemitem role="package">patchutils</systemitem> package and
<command>debdiff</command> from <systemitem
role="package">devscripts</systemitem> are useful tools for this, see <xref
-linkend="debdiff"/> ).
+linkend="debdiff"/>).
</para>
<para>
Be sure to verify the following items:
<emphasis role="strong">Target the right distribution</emphasis>
in your <filename>debian/changelog</filename>.
For <literal>stable</literal> this is <literal>stable-security</literal> and
-for testing this is <literal>testing-security</literal>, and for the previous
+for <literal>testing</literal> this is <literal>testing-security</literal>, and for the previous
stable release, this is <literal>oldstable-security</literal>. Do not target
<replaceable>distribution</replaceable><literal>-proposed-updates</literal> or
<literal>stable</literal>!
</listitem>
<listitem>
<para>
-Make sure the <emphasis role="strong">version number</emphasis> is proper.
+Make sure the <emphasis role="strong">version number</emphasis> is proper.
It must be greater than the current package, but less than package versions in
later distributions. If in doubt, test it with <literal>dpkg
--compare-versions</literal>. Be careful not to re-use a version number that
you have already used for a previous upload, or one that conflicts with a
binNMU. The convention is to append
<literal>+</literal><replaceable>codename</replaceable><literal>1</literal>, e.g.
-<literal>1:2.4.3-4+etch1</literal>, of course increasing 1 for any subsequent
+<literal>1:2.4.3-4+lenny1</literal>, of course increasing 1 for any subsequent
uploads.
</para>
</listitem>
role="strong">with full upstream source</emphasis> (<literal>dpkg-buildpackage
-sa</literal>). If there has been a previous upload to
<literal>security.debian.org</literal> with the same upstream version, you may
-upload without upstream source (<literal> dpkg-buildpackage -sd</literal>).
+upload without upstream source (<literal>dpkg-buildpackage -sd</literal>).
</para>
</listitem>
<listitem>
<para>
Be sure to use the <emphasis role="strong">exact same
-<filename>*.orig.tar.gz</filename></emphasis> as used in the
+<filename>*.orig.tar.{gz,bz2,lzma}</filename></emphasis> as used in the
normal archive, otherwise it is not possible to move the security fix into the
main archives later.
</para>
Build the package on a <emphasis role="strong">clean system</emphasis> which only
has packages installed from the distribution you are building for. If you do not
have such a system yourself, you can use a debian.org machine (see
-<xref linkend="server-machines"/> ) or setup a chroot (see
-<xref linkend="pbuilder"/> and <xref linkend="debootstrap"/> ).
+<xref linkend="server-machines"/>) or setup a chroot (see
+<xref linkend="pbuilder"/> and <xref linkend="debootstrap"/>).
</para>
</listitem>
</itemizedlist>
<title>Uploading the fixed package</title>
<para>
Do <emphasis role="strong">NOT</emphasis> upload a package to the security
-upload queue (<literal>oldstable-security</literal>, <literal>stable-security
-</literal>, etc.) without prior authorization from the security team. If the
-package does not exactly meet the team's requirements, it will cause many
+upload queue (<literal>oldstable-security</literal>, <literal>stable-security</literal>,
+etc.) without prior authorization from the security team. If the
+package does not exactly meet the team's requirements, it will cause many
problems and delays in dealing with the unwanted upload.
</para>
<para>
-Do <emphasis role="strong">NOT</emphasis> upload your fix to <literal>
-proposed-updates</literal> without coordinating with the security team.
+Do <emphasis role="strong">NOT</emphasis> upload your fix to
+<literal>proposed-updates</literal> without coordinating with the security team.
Packages from <literal>security.debian.org</literal> will be copied into
the <literal>proposed-updates</literal> directory automatically. If a package
with the same or a higher version number is already installed into the archive,
Once you have created and tested the new package and it has been approved by
the security team, it needs to be uploaded so that it can be installed in the
archives. For security uploads, the place to upload to is
-<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</literal> .
+<literal>ftp://security-master.debian.org/pub/SecurityUploadQueue/</literal>.
</para>
<para>
Once an upload to the security queue has been accepted, the package will
the package (see the <ulink
url="&url-debian-policy;">Debian Policy Manual</ulink> for
details). You must ensure that you include the
-<filename>.orig.tar.gz</filename> in your upload (even if you are not uploading
+<filename>.orig.tar.{gz,bz2,lzma}</filename> in your upload (even if you are not uploading
a new upstream version), or it will not appear in the new section together with
the rest of the package. If your new section is valid, it will be moved
automatically. If it does not, then contact the ftpmasters in order to
of one of your packages (e.g., ``devel'', ``admin''), the procedure is slightly
different. Correct the subsection as found in the control file of the package,
and re-upload that. Also, you'll need to get the override file updated, as
-described in <xref linkend="override-file"/> .
+described in <xref linkend="override-file"/>.
</para>
</section>
old compatibility library which is no longer required), you need to file a bug
against <literal>ftp.debian.org</literal> asking that the package be removed;
as all bugs, this bug should normally have normal severity.
-The bug title should be in the form <literal>RM: <replaceable>package
-</replaceable> <replaceable>[architecture list]</replaceable> --
+The bug title should be in the form <literal>RM: <replaceable>package</replaceable>
+<replaceable>[architecture list]</replaceable> --
<replaceable>reason</replaceable></literal>, where <replaceable>package</replaceable>
is the package to be removed and <replaceable>reason</replaceable> is a
-short summary of the reason for the removal request.
+short summary of the reason for the removal request.
<replaceable>[architecture list]</replaceable> is optional and only needed
if the removal request only applies to some architectures, not all. Note
that the <command>reportbug</command> will create a title conforming
<para>
Note that removals can only be done for the <literal>unstable
</literal>, <literal>experimental</literal> and <literal>stable
-</literal> distribution. Packages are not removed from
+</literal> distribution. Packages are not removed from
<literal>testing</literal> directly. Rather, they will be removed
automatically after the package has been removed from
<literal>unstable</literal> and no package in <literal>testing
you wish to replace the upstream source tarball of your package, you will need
to upload it with a different version. An easy possibility is to replace
<filename>foo_1.00.orig.tar.gz</filename> with
-<filename>foo_1.00+0.orig.tar.gz</filename>. This restriction gives each file
-on the ftp site a unique name, which helps to ensure consistency across the
-mirror network.
+<filename>foo_1.00+0.orig.tar.gz</filename> or
+<filename>foo_1.00.orig.tar.bz2</filename>. This restriction gives each
+file on the ftp site a unique name, which helps to ensure consistency
+across the mirror network.
</para>
</section>
It is not OK to simply take over a package that you feel is neglected — that
would be package hijacking. You can, of course, contact the current maintainer
and ask them if you may take over the package. If you have reason to believe a
-maintainer has gone AWOL (absent without leave), see <xref linkend="mia-qa"/> .
+maintainer has gone AWOL (absent without leave), see <xref linkend="mia-qa"/>.
</para>
<para>
Generally, you may not take over the package without the assent of the current
<filename>debian/control</filename> are set properly. The best way to validate
this is to use the <systemitem role="package">debootstrap</systemitem> package
to create an <literal>unstable</literal> chroot environment (see <xref
-linkend="debootstrap"/> ).
+linkend="debootstrap"/>).
Within that chrooted environment, install the <systemitem
role="package">build-essential</systemitem> package and any package
dependencies mentioned in <literal>Build-Depends</literal> and/or
<literal>Build-Depends-Indep</literal>. Finally, try building your package
within that chrooted environment. These steps can be automated by the use of
the <command>pbuilder</command> program which is provided by the package of the
-same name (see <xref linkend="pbuilder"/> ).
+same name (see <xref linkend="pbuilder"/>).
</para>
<para>
If you can't set up a proper chroot, <command>dpkg-depcheck</command> may be of
-assistance (see <xref linkend="dpkg-depcheck"/> ).
+assistance (see <xref linkend="dpkg-depcheck"/>).
</para>
<para>
See the <ulink url="&url-debian-policy;">Debian Policy
</listitem>
<listitem>
<para>
-Don't set architecture to a value other than <literal>all</literal> or
+Don't set architecture to a value other than <literal>all</literal> or
<literal>any</literal> unless you really mean it. In too many cases,
-maintainers don't follow the instructions in the <ulink
+maintainers don't follow the instructions in the <ulink
url="&url-debian-policy;">Debian Policy Manual</ulink>. Setting your
architecture to only one architecture (such as <literal>i386</literal>
or <literal>amd64</literal>) is usually incorrect.
<listitem>
<para>
Make sure your debian/rules contains separate <literal>binary-arch</literal>
-and <literal>binary-indep</literal> targets, as the Debian Policy Manual
+and <literal>binary-indep</literal> targets, as the Debian Policy Manual
requires. Make sure that both targets work independently, that is, that you
can call the target without having called the other before. To test this,
try to run <command>dpkg-buildpackage -B</command>.
<para>
Sometimes the initial porter upload is problematic because the environment in
which the package was built was not good enough (outdated or obsolete library,
-bad compiler, ...). Then you may just need to recompile it in an updated
+bad compiler, etc.). Then you may just need to recompile it in an updated
environment. However, you have to bump the version number in this case, so
that the old bad package can be replaced in the Debian archive
(<command>dak</command> refuses to install new packages if they don't have a
appended to the package version number, following the form <literal>
b<replaceable>number</replaceable></literal>.
For instance, if the latest version you are recompiling against was version
-<literal>2.9-3</literal>, your binary-only NMU should carry a version of
+<literal>2.9-3</literal>, your binary-only NMU should carry a version of
<literal>2.9-3+b1</literal>. If the latest version was <literal>3.4+b1
</literal> (i.e, a native package with a previous recompilation NMU), your
binary-only NMU should have a version number of <literal>3.4+b2</literal>.
-<footnote><para> In the past, such NMUs used the third-level number on the
+<footnote><para> In the past, such NMUs used the third-level number on the
Debian part of the revision to denote their recompilation-only status;
however, this syntax was ambiguous with native packages and did not allow
proper ordering of recompile-only NMUs, source NMUs, and security NMUs on
release managers decide and announce which architectures are candidates.
</para>
<para>
-If you are a porter doing an NMU for <literal>unstable</literal>, the above
+If you are a porter doing an NMU for <literal>unstable</literal>, the above
guidelines for porting should be followed, with two variations. Firstly, the
acceptable waiting period — the time between when the bug is submitted to
the BTS and when it is OK to do an NMU — is seven days for porters working
<para>
Secondly, porters doing source NMUs should make sure that the bug they submit
to the BTS should be of severity <literal>serious</literal> or greater. This
-ensures that a single source package can be used to compile every supported
+ensures that a single source package can be used to compile every supported
Debian architecture by release time. It is very important that we have one
version of the binary and source package for all architectures in order to
comply with many licenses.
<title>Porter tools</title>
<para>
Descriptions of several porting tools can be found in <xref
-linkend="tools-porting"/> .
+linkend="tools-porting"/>.
</para>
</section>
<systemitem role="package">wanna-build</systemitem> is not yet available as a
package; however, all Debian porting efforts are using it for automated
package building. The tool used to do the actual package builds, <systemitem
-role="package">sbuild</systemitem> is available as a package, see its
-description in <xref linkend="sbuild"/> . Please note that the packaged
+role="package">sbuild</systemitem> is available as a package, see its
+description in <xref linkend="sbuild"/>. Please note that the packaged
version is not the same as the one used on build daemons, but it is close
-enough to reproduce problems.
+enough to reproduce problems.
</para>
<para>
Most of the data produced by <systemitem role="package">wanna-build
In order to prevent autobuilders from needlessly trying to build your package,
it must be included in <filename>packages-arch-specific</filename>, a list used
by the <command>wanna-build</command> script. The current version is available
-as <ulink
-url="&url-cvsweb;srcdep/Packages-arch-specific?cvsroot=dak"></ulink>;
+as <ulink url="&url-buildd-p-a-s;"/>;
please see the top of the file for whom to contact for changes.
</para>
</listitem>
The way to version NMUs differs for native and non-native packages.
</para>
<para>
-If the package is a native package (without a debian revision in the version number),
+If the package is a native package (without a debian revision in the version number),
the version must be the version of the last maintainer upload, plus
<literal>+nmu<replaceable>X</replaceable></literal>, where
<replaceable>X</replaceable> is a counter starting at <literal>1</literal>.
In both cases, if the last upload was also an NMU, the counter should
be increased. For example, if the current version is
<literal>1.5+nmu3</literal> (a native package which has already been
-NMUed), the NMU would get version <literal>1.5+nmu4</literal>. .
+NMUed), the NMU would get version <literal>1.5+nmu4</literal>.
</para>
<para>
A special versioning scheme is needed to avoid disrupting the maintainer's
</section>
+<section id="nmu-team-upload">
+<title>NMUs vs team uploads</title>
+
+<para>
+Sometimes you are fixing and/or updating a package because you are member of a
+packaging team (which uses a mailing list as Maintainer or Uploader, see <xref
+linkend="collaborative-maint"/>) but you don't want to add yourself to Uploaders
+because you do not plan to contribute regularly to this specific package. If it
+conforms with your team's policy, you can perform a normal upload without
+being listed directly as Maintainer or Uploader. In that case, you should
+start your changelog entry with the following line: <code> * Team upload.</code>.
+</para>
+
+</section>
+
</section>
<section id="collaborative-maint">
Setup the co-maintainer with access to the sources you build the package from.
Generally this implies you are using a network-capable version control system,
such as <command>CVS</command> or <command>Subversion</command>. Alioth (see
-<xref linkend="alioth"/> ) provides such tools, amongst others.
+<xref linkend="alioth"/>) provides such tools, amongst others.
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
-Using the PTS (<xref linkend="pkg-tracking-system"/> ), the co-maintainers
+Using the PTS (<xref linkend="pkg-tracking-system"/>), the co-maintainers
should subscribe themselves to the appropriate source package.
</para>
</listitem>
</para>
</listitem>
</orderedlist>
+
<para>
In any case, it is a bad idea to automatically put all team members in the
-Uploaders field. It clutters the Developer's Package Overview listing (see
-<xref linkend="ddpo"/> ) with packages one doesn't really care for, and creates
-a false sense of good maintenance.
+Uploaders field. It clutters the Developer's Package Overview listing (see
+<xref linkend="ddpo"/>) with packages one doesn't really care for, and creates
+a false sense of good maintenance. For the same reason, team members do
+not need to add themselves to the Uploaders field just because they are
+uploading the package once, they can do a “Team upload” (see <xref
+linkend="nmu-team-upload"/>). Conversely, it it a bad idea to keep a
+package with only the mailing list address as a Maintainer and no
+Uploaders.
</para>
</section>
or 10 days, depending on the urgency (high, medium or low). Please note that
the urgency is sticky, meaning that the highest urgency uploaded since the
previous <literal>testing</literal> transition is taken into account. Those
-delays may be doubled during a freeze, or <literal>testing</literal>
+delays may be doubled during a freeze, or <literal>testing</literal>
transitions may be switched off altogether;
</para>
</listitem>
<listitem>
<para>
It must not have new release-critical bugs (RC bugs affecting the version
-available in <literal>unstable</literal>, but not affecting the version in
+available in <literal>unstable</literal>, but not affecting the version in
<literal>testing</literal>);
</para>
</listitem>
different versions in <literal>unstable</literal> for the release architectures
(except for the architectures in fuckedarches; fuckedarches is a list of
architectures that don't keep up (in <filename>update_out.py</filename>), but
-currently, it's empty). outdated has nothing whatsoever to do with the
+currently, it's empty). outdated has nothing whatsoever to do with the
architectures this package has in <literal>testing</literal>.
</para>
<para>
<para>
The package is out of date on alpha in <literal>unstable</literal>, and will
not go to <literal>testing</literal>. Removing the package would not help at all, the
-package is still out of date on <literal>alpha</literal>, and will not
+package is still out of date on <literal>alpha</literal>, and will not
propagate to testing.
</para>
<para>
</informaltable>
<para>
In this case, the package is up to date on all release architectures in
-<literal>unstable</literal> (and the extra <literal>hurd-i386</literal>
+<literal>unstable</literal> (and the extra <literal>hurd-i386</literal>
doesn't matter, as it's not a release architecture).
</para>
<para>
<section id="t-p-u">
<title>Direct updates to testing</title>
<para>
-The <literal>testing</literal> distribution is fed with packages from
+The <literal>testing</literal> distribution is fed with packages from
<literal>unstable</literal> according to the rules explained above. However,
in some cases, it is necessary to upload packages built only for <literal>
testing</literal>. For that, you may want to upload to <literal>
<literal>unstable</literal> does not pull in any new dependencies.
</para>
<para>
-Version numbers are usually selected by adding the codename of the
-<literal>testing</literal> distribution and a running number, like
+Version numbers are usually selected by adding the codename of the
+<literal>testing</literal> distribution and a running number, like
<literal>1.2sarge1</literal> for the first upload through
-<literal>testing-proposed-updates</literal> of package version
+<literal>testing-proposed-updates</literal> of package version
<literal>1.2</literal>.
</para>
<para>
<para>
Such bugs are presumed to have an impact on the chances that the package will
be released with the <literal>stable</literal> release of Debian: in general,
-if a package has open release-critical bugs filed on it, it won't get into
+if a package has open release-critical bugs filed on it, it won't get into
<literal>testing</literal>, and consequently won't be released in <literal>
stable</literal>.
</para>
</para>
<para>
However, the old version may have provided a binary package with an old soname
-of a library, such as <literal>libacme-foo0</literal>. Removing the old
+of a library, such as <literal>libacme-foo0</literal>. Removing the old
<literal>acmefoo</literal> will remove <literal>libacme-foo0</literal>, which
will break any packages which depend on it.
</para>