From 6f5535e521e72fdc605aac4238a199c8f378b1c9 Mon Sep 17 00:00:00 2001 From: aba Date: Tue, 4 Apr 2006 21:41:26 +0000 Subject: [PATCH] more fixes git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@3714 313b444b-1b9f-4f58-a734-7bb04f332e8d --- debian/changelog | 11 +++++++ developers-reference.sgml | 64 ++++++++++++++++++++++++--------------- 2 files changed, 50 insertions(+), 25 deletions(-) diff --git a/debian/changelog b/debian/changelog index 361c2af..97e3102 100644 --- a/debian/changelog +++ b/debian/changelog @@ -29,6 +29,17 @@ developers-reference (3.3.7) unstable; urgency=low - document severity of RoM-request bugs. Closes: #305947 - update FSF address. Closes: #334820 - fix P-a-s link. Closes: #341195 + - reflect binNMU changes. Closes: #349493 + - new security upload queue. Closes: #352749 + - fix experimental's sources.list entry. Closes: #347229 + - remove deprecated "Closes:..." to ACK NMU bug fixes. Closes: #353447 + - when resigning, gpg-sign your mail. Closes: #348160 + - make pristine source and repackaged origtargz anchors work. + Closes: #351255 + - same number of RC bugs is ok. Closes: #351944 + - dpkg-source doesn't keep permissions. Thanks, Enrico Zini. + Closes: #306120 + - also mention aspell. Closes: #320981 -- Andreas Barth Sat, 25 Jun 2005 06:04:20 -0600 diff --git a/developers-reference.sgml b/developers-reference.sgml index 455239a..3a52e9f 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -7,7 +7,7 @@ %dynamicdata; - + @@ -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, @@ -1705,6 +1705,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 +1752,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 +2440,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 +2765,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 @@ -3307,7 +3326,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 +3810,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: @@ -3923,15 +3943,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 +4751,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 +4810,7 @@ case, dpkg-source renames the temporary directory

- + Repackaged upstream source

You should upload packages with a pristine source -- 2.30.2