X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=developers-reference.sgml;h=a00cabd3ace8f97d7fcf6ee63b1a026c12149ca0;hb=0705951199dd03a594900f56aa58225d68314ba6;hp=e83d7fe963b0f1e3247dc961720ae6e65c59bf2e;hpb=a088baf8d9dafdd548f7549e449684b868312382;p=developers-reference.git
diff --git a/developers-reference.sgml b/developers-reference.sgml
index e83d7fe..a00cabd 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -7,7 +7,7 @@
%dynamicdata;
-
+
@@ -264,7 +264,7 @@ Also note that your key must be self-signed (i.e. it has to sign
all its own user IDs; this prevents user ID tampering). All
modern OpenPGP software does that automatically, but if you
have an older key you may have to manually add those signatures.
-
+
If your public key isn't on public key servers such as &pgp-keyserv;,
please read the documentation available locally in &file-keyservs;.
@@ -463,7 +463,7 @@ the following steps:
-
Orphan all your packages, as described in
[.
]-
-Send an email about why you are leaving the project to
+Send an gpg-signed email about why you are leaving the project to
&email-debian-private;.
-
Notify the Debian key ring maintainers that you are leaving by
@@ -1047,8 +1047,8 @@ distribution.
These are the lines for
experimental:
-deb http://ftp.xy.debian.org/debian/ ../project/experimental main
-deb-src http://ftp.xy.debian.org/debian/ ../project/experimental main
+deb http://ftp.xy.debian.org/debian/ experimental main
+deb-src http://ftp.xy.debian.org/debian/ experimental main
If there is a chance that the software could do grave damage to a system,
@@ -1357,12 +1357,17 @@ maintainer has set up forwarding commit notifications to the PTS.
-
Translations of descriptions or debconf templates
submitted to the Debian Description Translation Project.
+
+ derivatives
+
-
+Information about changes made to the package in derivative distributions
+(for example Ubuntu).
The PTS email interface
You can control your subscription(s) to the PTS by sending
-various commands to pts@qa.debian.org.
+various commands to pts@qa.debian.org.
@@ -1380,6 +1385,11 @@ various commands to pts@qa.debian.org.
using the specified email address or the sender address if the second
argument is left out.
+unsubscribeall [<email>]
+-
+ Removes all subscriptions of the specified email address or the sender
+ address if the second argument is left out.
+
which [<email>]
-
Lists all subscriptions for the sender or the email address optionally
@@ -1396,6 +1406,7 @@ various commands to pts@qa.debian.org.
- summary: automatic summary mails about the state of a package
- cvs: notification of CVS commits
- ddtp: translations of descriptions and debconf templates
+
- derivatives: changes made on the package by derivative distributions
- upload-source: announce of a new source upload that
has been accepted
- upload-binary: announce of a new binary-only upload (porting)
@@ -1412,7 +1423,14 @@ various commands to pts@qa.debian.org.
keyword [<email>] {+|-|=} <list of keywords>
-
Accept (+) or refuse (-) mails classified under the given keyword(s).
- Define the list (=) of accepted keywords.
+ Define the list (=) of accepted keywords. This changes the default set
+ of keywords accepted by a user.
+
+keywordall [<email>] {+|-|=} <list of keywords>
+
-
+ Accept (+) or refuse (-) mails classified under the given keyword(s).
+ Define the list (=) of accepted keywords. This changes the set of
+ accepted keywords of all the currently active subscriptions of a user.
keyword <sourcepackage> [<email>] {+|-|=} <list of keywords>
-
@@ -1425,6 +1443,12 @@ various commands to pts@qa.debian.org.
the bot.
+
+The pts-subscribe command-line utility (from the
+devscripts package) can be handy to temporarily
+subscribe to some packages, for example after having made an
+non-maintainer upload.
+
Filtering PTS mails
Once you are subscribed to a package, you will get the mails sent to
@@ -1705,6 +1729,11 @@ Downgrade the package to the previous version (if one exists) — this
tests the postrm and prerm scripts.
-
Remove the package, then reinstall it.
+
-
+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.
@@ -1747,6 +1776,10 @@ If no original source is included in the upload, the original
source tar-file used by dpkg-source when constructing the
.dsc file and diff to be uploaded must be
byte-for-byte identical with the one already in the archive.
+
+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.
Picking a distribution
@@ -2431,7 +2464,7 @@ 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
-ftp://security.debian.org/pub/SecurityUploadQueue/ .
+ftp://security-master.debian.org/pub/SecurityUploadQueue/ .
Once an upload to the security queue has been accepted, the package
@@ -2756,12 +2789,22 @@ new Debian version, there is no corresponding source update. If you
get this wrong, the archive maintainers will reject your upload (due
to lack of corresponding source code).
-The ``magic'' for a recompilation-only NMU is triggered by using the
-third-level number on the Debian part of the version. For instance,
-if the latest version you are recompiling against was version
-``2.9-3'', your NMU should carry a version of ``2.9-3.0.1''. If the
-latest version was ``3.4-2.1'', your NMU should have a version number
-of ``3.4-2.1.1''.
+The ``magic'' for a recompilation-only NMU is triggered by using a
+suffix appended to the package version number,
+following the form b<number>.
+For instance, if the latest version you are
+recompiling against was version ``2.9-3'', your NMU should carry a
+version of ``2.9-3+b1''. If the latest version was ``3.4+b1'' (i.e, a
+native package with a previous recompilation NMU), your NMU should have
+a version number of ``3.4+b2''.
+
+
+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 the
+same package, and has therefore been abandoned in favor of this new
+syntax.
Similar to initial porter uploads, the correct way of invoking
dpkg-buildpackage is dpkg-buildpackage -B to only
@@ -2910,7 +2953,7 @@ In order to prevent autobuilders from needlessly trying to build your
package, it must be included in packages-arch-specific, a
list used by the wanna-build script.
The current version is available as
-;
+;
please see the top of the file for whom to contact for changes.
@@ -3307,7 +3350,7 @@ urgency uploaded since the previous testing transition is taken into account.
Those delays may be doubled during a freeze, or testing transitions may be
switched off altogether;
-
-It must have fewer release-critical bugs than the version currently available
+It must have the same number or fewer release-critical bugs than the version currently available
in testing;
-
It must be available on all architectures on which it has previously
@@ -3791,10 +3834,11 @@ package related to other packages in some way that is not handled by
the package manager (e.g., "this is the client for the foo server")?
Be careful to avoid spelling and grammar mistakes. Ensure that you
-spell-check it. ispell has a special -g option
-for debian/control files:
+spell-check it. Both ispell and aspell
+have special modes for checking debian/control files:
ispell -d american -g debian/control
+aspell -d en -D -c debian/control
Users usually expect these questions to be answered in the package
description:
@@ -3851,7 +3895,7 @@ Note that we expect this field will eventually be replaced by a proper
home page from the description to this field, you should probably wait
until that is available.
Please make sure that this line matches the regular expression
- /^ Homepage: [^ ]*$/,
+ /^ Homepage: [^ ]*$/,
as this allows packages.debian.org to parse it correctly.
@@ -3923,15 +3967,9 @@ id="bug-answering"> for more information on how to use the bug
tracking system.
It is an old tradition to acknowledge bugs fixed in non-maintainer
-uploads in the first changelog entry of the proper maintainer upload,
-for instance, in a changelog entry like this:
-
- * Maintainer upload, closes: #42345, #44484, #42444.
-
-This will close the NMU bugs tagged "fixed" when the package makes
-it into the archive. The bug for the fact that an NMU was done can be
-closed the same way. Of course, it's also perfectly acceptable to
-close NMU-fixed bugs by other means; see [.
+uploads in the first changelog entry of the proper maintainer upload.
+Please use the option -v to dpkg-buildpackage
+to close the relevant bug report.
]
@@ -4737,7 +4775,7 @@ to your short description. If you are looking for examples, just run:
There are two kinds of original source tarballs: Pristine source
and repackaged upstream source.
-
+
Pristine source
The defining characteristic of a pristine source tarball is that the
@@ -4796,7 +4834,7 @@ case, dpkg-source renames the temporary directory
-
+
Repackaged upstream source
You should upload packages with a pristine source
@@ -5588,8 +5626,9 @@ sort of automated functions that one finds in
debhelper.
The consensus is that debmake is now deprecated in
-favor of debhelper. However, it's not a bug to use
-debmake.
+favor of debhelper. It is a bug to use
+debmake in new packages. New packages using
+debmake will be rejected from the archive.