Your message dated Thu, 19 Jan 2012 20:48:51 +0000 with message-id <e1rnyuh-0008ib...@franck.debian.org> and subject line Bug#643932: fixed in developers-reference 3.4.7 has caused the Debian Bug report #643932, regarding FTP Team related changes to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 643932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: developers-reference Version: 3.4.6 Severity: normal Tags: patch There are several inaccuracies related to FTP Team tasks (supported compressions, scripts name, directory names, etc...) Attached patch should solve this, by refreshing FTP Team information. -- .''`. : :' : Luca Falavigna <dktrkr...@debian.org> `. `' `-Index: best-pkging-practices.dbk =================================================================== --- best-pkging-practices.dbk (revisione 8928) +++ best-pkging-practices.dbk (copia locale) @@ -1680,7 +1680,7 @@ </section> <section id="bpp-origtargz"> -<title>Best practices for <filename>.orig.tar.{gz,bz2,lzma}</filename> files</title> +<title>Best practices for <filename>.orig.tar.{gz,bz2,xz}</filename> files</title> <para> There are two kinds of original source tarballs: Pristine source and repackaged upstream source. @@ -1689,7 +1689,7 @@ <title>Pristine source</title> <para> The defining characteristic of a pristine source tarball is that the -<filename>.orig.tar.{gz,bz2,lzma}</filename> file is byte-for-byte identical to a tarball officially +<filename>.orig.tar.{gz,bz2,xz}</filename> file is byte-for-byte identical to a tarball officially distributed by the upstream author.<footnote><para> We cannot prevent upstream authors from changing the tarball they distribute without also incrementing the version number, so there can be no guarantee that a pristine @@ -1699,7 +1699,7 @@ If a difference arises later (say, if upstream notices that he wasn't using maximal compression in his original distribution and then re-<command>gzip</command>s it), that's just too bad. Since there is no good -way to upload a new <filename>.orig.tar.{gz,bz2,lzma}</filename> for the same version, there is not even any +way to upload a new <filename>.orig.tar.{gz,bz2,xz}</filename> for the same version, there is not even any point in treating this situation as a bug. </para> </footnote> This makes it possible to use checksums to easily verify that all changes between Debian's version and upstream's are contained in the Debian diff. Also, if the original @@ -1753,17 +1753,17 @@ that you must remove before uploading. </para> <para> -In these cases the developer must construct a suitable <filename>.orig.tar.{gz,bz2,lzma}</filename> +In these cases the developer must construct a suitable <filename>.orig.tar.{gz,bz2,xz}</filename> file himself. We refer to such a tarball as a repackaged upstream source. Note that a repackaged upstream source is different from a Debian-native package. A repackaged source still comes with Debian-specific -changes in a separate <filename>.diff.gz</filename> or <filename>.debian.tar.{gz,bz2,lzma}</filename> +changes in a separate <filename>.diff.gz</filename> or <filename>.debian.tar.{gz,bz2,xz}</filename> and still has a version number composed of <replaceable>upstream-version</replaceable> and <replaceable>debian-version</replaceable>. </para> <para> There may be cases where it is desirable to repackage the source even though -upstream distributes a <filename>.tar.{gz,bz2,lzma}</filename> that could in principle be +upstream distributes a <filename>.tar.{gz,bz2,xz}</filename> that could in principle be used in its pristine form. The most obvious is if <emphasis>significant</emphasis> space savings can be achieved by recompressing the tar archive or by removing genuinely useless cruft from the upstream @@ -1771,7 +1771,7 @@ if you repackage source that could have been pristine. </para> <para> -A repackaged <filename>.orig.tar.{gz,bz2,lzma}</filename> +A repackaged <filename>.orig.tar.{gz,bz2,xz}</filename> </para> <orderedlist numeration="arabic"> <listitem> Index: pkgs.dbk =================================================================== --- pkgs.dbk (revisione 8928) +++ pkgs.dbk (copia locale) @@ -231,11 +231,11 @@ <para> For the native packages, the source package includes a Debian source control file (<filename>.dsc</filename>) and the source tarball -(<filename>.tar.{gz,bz2,lzma}</filename>). A source package of a non-native package +(<filename>.tar.{gz,bz2,xz}</filename>). A source package of a non-native package includes a Debian source control file, the original source tarball -(<filename>.orig.tar.{gz,bz2,lzma}</filename>) and the Debian changes +(<filename>.orig.tar.{gz,bz2,xz}</filename>) and the Debian changes (<filename>.diff.gz</filename> for the source format â1.0â or -<filename>.debian.tar.{gz,bz2,lzma}</filename> for the source format â3.0 (quilt)â). +<filename>.debian.tar.{gz,bz2,xz}</filename> for the source format â3.0 (quilt)â). </para> <para> With source format â1.0â, whether a package is native or not was determined @@ -268,7 +268,7 @@ </para> <para> Please notice that, in non-native packages, permissions on files that are not -present in the <filename>*.orig.tar.{gz,bz2,lzma}</filename> will not be preserved, as diff does not store file +present in the <filename>*.orig.tar.{gz,bz2,xz}</filename> 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. @@ -470,11 +470,11 @@ <para> The Debian archive maintainers are responsible for handling package uploads. 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 -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 +archive maintenance tools, <command>dak process-upload</command>. Specifically, +updates to existing packages to the <literal>unstable</literal> distribution are +handled 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 some times to occur. Please be patient. </para> <para> @@ -1171,7 +1171,7 @@ <listitem> <para> Be sure to use the <emphasis role="strong">exact same -<filename>*.orig.tar.{gz,bz2,lzma}</filename></emphasis> as used in the +<filename>*.orig.tar.{gz,bz2,xz}</filename></emphasis> as used in the normal archive, otherwise it is not possible to move the security fix into the main archives later. </para> @@ -1257,7 +1257,7 @@ 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,bz2,lzma}</filename> in your upload (even if you are not uploading +<filename>.orig.tar.{gz,bz2,xz}</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 @@ -1311,11 +1311,11 @@ </para> <para> There is one exception when an explicit removal request is not necessary: If a -(source or binary) package is an orphan, it will be removed semi-automatically. -For a binary-package, this means if there is no longer any source package -producing this binary package; if the binary package is just no longer produced -on some architectures, a removal request is still necessary. For a -source-package, this means that all binary packages it refers to have been +(source or binary) package is no longer built from source, it will be removed +semi-automatically. For a binary-package, this means if there is no longer any +source package producing this binary package; if the binary package is just no +longer produced on some architectures, a removal request is still necessary. For +a source-package, this means that all binary packages it refers to have been taken over by another source package. </para> <para> @@ -1972,7 +1972,7 @@ While preparing the patch, you should better be aware of any package-specific practices that the maintainer might be using. Taking them into account reduces the burden of getting your changes integrated back in the normal package -workflow and thus increases the possibilities that that will happen. A good +workflow and thus increases the possibilities that will happen. A good place where to look for for possible package-specific practices is <ulink url="&url-debian-policy;ch-source.html#s-readmesource"><filename>debian/README.source</filename></ulink>. </para> Index: resources.dbk =================================================================== --- resources.dbk (revisione 8928) +++ resources.dbk (copia locale) @@ -562,26 +562,26 @@ 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> @@ -738,7 +738,7 @@ 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> @@ -848,10 +848,10 @@ 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 @@ -1027,7 +1027,7 @@ <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> @@ -1036,7 +1036,7 @@ <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>signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Source: developers-reference Source-Version: 3.4.7 We believe that the bug you reported is fixed in the latest version of developers-reference, which is due to be installed in the Debian FTP archive: developers-reference-de_3.4.7_all.deb to main/d/developers-reference/developers-reference-de_3.4.7_all.deb developers-reference-fr_3.4.7_all.deb to main/d/developers-reference/developers-reference-fr_3.4.7_all.deb developers-reference-ja_3.4.7_all.deb to main/d/developers-reference/developers-reference-ja_3.4.7_all.deb developers-reference_3.4.7.dsc to main/d/developers-reference/developers-reference_3.4.7.dsc developers-reference_3.4.7.tar.bz2 to main/d/developers-reference/developers-reference_3.4.7.tar.bz2 developers-reference_3.4.7_all.deb to main/d/developers-reference/developers-reference_3.4.7_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 643...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot <taf...@debian.org> (supplier of updated developers-reference package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 17 Jan 2012 16:36:12 -0400 Source: developers-reference Binary: developers-reference developers-reference-de developers-reference-fr developers-reference-ja Architecture: source all Version: 3.4.7 Distribution: unstable Urgency: low Maintainer: Developers Reference Maintainers <debian-policy@lists.debian.org> Changed-By: David Prévot <taf...@debian.org> Description: developers-reference - guidelines and information for Debian developers developers-reference-de - guidelines and information for Debian developers, in German developers-reference-fr - guidelines and information for Debian developers, in French developers-reference-ja - guidelines and information for Debian developers, in Japanese Closes: 569219 629530 643929 643930 643931 643932 643933 643934 643935 655096 655153 Changes: developers-reference (3.4.7) unstable; urgency=low . * Team upload. . [ Raphaël Hertzog ] * Document some best practices for meta-packages. Extend those for transitional packages. Based on a patch by Luca Falavigna <dktrkr...@debian.org> (thanks!). Closes: #569219 * Update license pointer to correctly point to GPL-2. Closes: #643929 Thanks to Luca Falavigna. * Update URL of Debian Mentors FAQ. Closes: #643930 Thanks to Luca Falavigna for the patch. * Refresh some release-specific information. Closes: #643931 Based on a patch by Luca Falavigna. * Refresh some ftpmaster-related information. Closes: #643932 Thanks to Luca Falavigna for the patch. * Update minimal GPG key length to match current requirements. Closes: #643933 Thanks to Luca Falavigna for the patch. * Update login information for rt.debian.org. Closes: #643934 Thanks to Luca Falavigna for the patch. * Drop section about yada. Its usage is highly discouraged. Closes: #643935 Thanks to Luca Falavigna for the patch. * Update best practice about unfuzzying PO file translations to recommend msguntypot. Thanks to David Prévot for the patch. Acked-by Christian Perrier. Closes: #655153 . [ David Prévot ] * Add doc-base file for the German translation. * Typo fix, thanks to Andreas Moog. Closes: #655096 * Use XeTeX backend, that fix quotes in examples. Closes: #629530 * Build the Japanese PDF, thanks to Osamu Aoki and the maint-guide build process. . * Translation updates (all completed) - Japanese by Hideki Yamane. - German by Chris Leick. - French by David Prévot. Checksums-Sha1: 07d537e5047d07c0a4a63a0a634f9e5ea28c7d28 2236 developers-reference_3.4.7.dsc 335a6bc01eb768235d756f90d1153e5902cf8bff 653774 developers-reference_3.4.7.tar.bz2 23ed2d29b0d93a39ac7a9a9200950090f6982341 694234 developers-reference_3.4.7_all.deb 591951e359219c137c9f9ca16dfc8d28ad94ceb6 772434 developers-reference-de_3.4.7_all.deb 87fe948293456c0a0bad44b22225adf4c594d6b0 751928 developers-reference-fr_3.4.7_all.deb 30193d3c19a35623f531d2f95e1b93c394430041 1193226 developers-reference-ja_3.4.7_all.deb Checksums-Sha256: f7b2d4b33610cfe10d5745032eb54877854235ae29dbed9689297b301309d3ee 2236 developers-reference_3.4.7.dsc cbe0e52b61d041bd54a48f7d4000decdeb227397a0a22072a5c99778cff82dae 653774 developers-reference_3.4.7.tar.bz2 63a188fa918d0cfe2e80b3406b534268951ac69c22963dad11191b6abe2b53ff 694234 developers-reference_3.4.7_all.deb b0fae103033e27d1d836369847d355485ca2fd1b5d0e617cfb1caf52de017018 772434 developers-reference-de_3.4.7_all.deb d55e2606462e66f43c5fd388b91cbd82a7c1e53669764ce7cb06dbbefab8085f 751928 developers-reference-fr_3.4.7_all.deb 0e5b2a9a747350a70c9e434b2dc0500572dd719e2816afb4a3749f41e7ce167e 1193226 developers-reference-ja_3.4.7_all.deb Files: 21e6ba5a10c2107b2fa47af60d5dd7c7 2236 doc optional developers-reference_3.4.7.dsc ee399c35ad753abfe1a8d43ed2411216 653774 doc optional developers-reference_3.4.7.tar.bz2 9b0c02ed87d50455c62094b649ff03f7 694234 doc optional developers-reference_3.4.7_all.deb 4c6b522f83e951c4212e359e20f24ff8 772434 doc optional developers-reference-de_3.4.7_all.deb 50b4150d8b4380d715cc861b29f88c91 751928 doc optional developers-reference-fr_3.4.7_all.deb d749b22d72eba528bb5a54a8295688f0 1193226 doc optional developers-reference-ja_3.4.7_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJPFeE1AAoJELgqIXr9/gny97sQAJSsCnWuKmV0GrQbi9mvNYhj m1nvVq9NwQ90Lyu42YqbbfJQZOChN46Me2ArdSi9RjmsskdX+UM/CyuCkWNCKiKM cEGeaZXbMAH+cxWdw3PCCJaW/iXc++GA20g6WMVudTSUd3VO2wS6l5u/pqOY6Zyd haMNfFQlrg3zu42mxtgiAHuNVkqaEUDTfVoFvf8kZJZKVRpv54W7YickyZAwL2G0 sZ6xXfvjl7B5xBKkrsT+fnz3ToZyvgU51GfyAA2clAMiLi/Iz8EfWSHR7Wh30V9Y +F3INoy1ugVPC28gs9VKtT8xvHlXBofkwxWFMX6g7jICo9NMMd+x29oUmArzohtu EjviRU4wMa98ag2wj4/ktCAktcy+E5G+DAy+txXXzaBFRp019O9tu62tR4DlDhyk JjMZSmNCsEFOX5KACbRerwZazQvLOIx7kJHwYkBzD/TkIJuakZw/d3i+J5dIoNBu lsoPBxsYE09/zLDysOnPo6qV9B7rEnIO6prvUHQYmzvMZ0Ir3n1hh4eV4rdPT3DG ORy2Ra3e9dakHLLAYQd/YXe8vsL6G4g14KK4FECSyiWTQUKUk7H9hAgG4g7UbSvy 18p3g0FacbOUk8CR/X3gIZIOLMf1dsb+FE1T9XIBFquUUG2SWIXR28kbNzhTu9yF sH+zpuw5cJW4O0Bt//PH =IRnS -----END PGP SIGNATURE-----
--- End Message ---