Processing of developers-reference_3.4.7_amd64.changes
developers-reference_3.4.7_amd64.changes uploaded successfully to localhost along with the files: developers-reference_3.4.7.dsc developers-reference_3.4.7.tar.bz2 developers-reference_3.4.7_all.deb developers-reference-de_3.4.7_all.deb developers-reference-fr_3.4.7_all.deb developers-reference-ja_3.4.7_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1rnydp-0001yz...@franck.debian.org
Bug#569219: marked as done (Document transitional and meta-packages)
Your message dated Thu, 19 Jan 2012 20:48:50 + with message-id e1rnyug-0008ij...@franck.debian.org and subject line Bug#569219: fixed in developers-reference 3.4.7 has caused the Debian Bug report #569219, regarding Document transitional and meta-packages 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.) -- 569219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: developers-reference Version: 3.4.3 Severity: wishlist Tags: patch We have several meta-packages and transitional packages in the archive, some of them do not document that anywhere in their description. Users should be given such an information, so they can decide to remove some to save disk space and to remove useless packages from the system. I propose to clearly state a package is a meta-package or a transitioanl package in the long description. This is a common practice already. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-486 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Index: best-pkging-practices.dbk === --- best-pkging-practices.dbk (revisione 7068) +++ best-pkging-practices.dbk (copia locale) @@ -343,6 +343,13 @@ this about this particular package, if you have information related to both). -- /itemizedlist +para +If the package is a meta-package (a package which depends on one or more +packages) or a transitional package (a package provided to ease upgrades to +packages with a different name), you should clearly state so identifying +what kind of package it belongs, that way users are given the chance to remove +potential useless packages without losing any functionality. +/para /section section id=bpp-upstream-info ---End Message--- ---BeginMessage--- 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 569...@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 *
Bug#629530: marked as done (developers-reference: PDF code example has wrong U+2019 for ')
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008ip...@franck.debian.org and subject line Bug#629530: fixed in developers-reference 3.4.7 has caused the Debian Bug report #629530, regarding developers-reference: PDF code example has wrong U+2019 for ' 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.) -- 629530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: developers-reference Version: 3.4.4 Severity: minor If I copy script example under 6.5. CONFIGURATION MANAGEMENT . . . from PDF: | 4. Modify all PO files by using sed. The use of that command is recommended over any text editor |to guarantee that the files encoding will not be broken by the edit action: |cd debian/po |for i in *.po; do sed -i ’s/tpyo/typo/g’ $i; done Here, ’ is non ASCII and not ASCII '. This makes copied script to fail. TeX backend (specifically pdflatex) used to create this PDF is the cause. If you move this build this with XeTeX (specifically xelatex), this problem goes away. Also, works fine. So changing example to use double quote may work around issue. Regards, Osamu PS: This is based on the same TeX conversion bug or singularity. I could not fix its ill effect for debiandoc-sgml. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash developers-reference depends on no packages. Versions of packages developers-reference recommends: ii debian-policy 3.9.2.0Debian Policy Manual and related d Versions of packages developers-reference suggests: ii doc-base 0.10.1 utilities to manage online documen -- no debconf information ---End Message--- ---BeginMessage--- 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 629...@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
Bug#643929: marked as done (Wrong link to common-licenses)
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008is...@franck.debian.org and subject line Bug#643929: fixed in developers-reference 3.4.7 has caused the Debian Bug report #643929, regarding Wrong link to common-licenses 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.) -- 643929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: developers-reference Version: 3.4.6 Severity: normal Tags: patch Page II says Developer's Reference is licensed under GPLv2, but link to common-licenses file is GPL, which points to GPLv3. Attached patch should solve this, by pointing to GPL-2 file. -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- Index: common.ent === --- common.ent (revisione 8928) +++ common.ent (copia locale) @@ -18,7 +18,7 @@ !-- standard information -- !ENTITY fsf-addr Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA -!ENTITY file-GPL filename/usr/share/common-licenses/GPL/filename +!ENTITY file-GPL filename/usr/share/common-licenses/GPL-2/filename !ENTITY debian-formal Debian GNU/Linux !-- signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- 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. *
Bug#643930: marked as done (Adjust link to Mentor's FAQ)
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008iv...@franck.debian.org and subject line Bug#643930: fixed in developers-reference 3.4.7 has caused the Debian Bug report #643930, regarding Adjust link to Mentor's FAQ 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.) -- 643930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643930 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: developers-reference Version: 3.4.6 Severity: normal Tags: patch Page 3 provides links to Mentor's FAQ, but that link currently redirects to a wiki page. I think it would make more sense to provide the pointed link instead. Attached patch should solve this, by pointing to wiki page directly. -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- Index: common.ent === --- common.ent (revisione 8928) +++ common.ent (copia locale) @@ -103,7 +103,7 @@ !-- deprecated -- -!ENTITY url-mentors http://people.debian.org/~mpalmer/debian-mentors_FAQ.html; +!ENTITY url-mentors http://wiki.debian.org/DebianMentorsFaq; !ENTITY url-rules-files http://arch.debian.org/arch/private/srivasta/; signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- 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
Bug#643931: marked as done (Refresh references for squeeze release)
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008iy...@franck.debian.org and subject line Bug#643931: fixed in developers-reference 3.4.7 has caused the Debian Bug report #643931, regarding Refresh references for squeeze release 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.) -- 643931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: developers-reference Version: 3.4.6 Severity: normal Tags: patch Several locations are not up-to-date with current release information. Attached patch should solve this, by refreshing some information related to releases, supported architectures, and number of packages. -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- Index: resources.dbk === --- resources.dbk (revisione 8928) +++ resources.dbk (copia locale) @@ -534,10 +534,9 @@ architectures. Debian 2.1 shipped for the literali386/literal, literalm68k/literal, literalalpha/literal, and literalsparc/literal architectures. Since then Debian has grown hugely. -Debian 5 supports a total of twelve architectures: literalalpha/literal, -literalamd64/literal, literalarm/literal, -literalarmel/literal, literalhppa/literal, -literali386/literal, literalia64/literal, literalmips/literal, +Debian 6 supports a total of nine architectures: literalamd64/literal, +literalarmel/literal, literali386/literal, +literalia64/literal, literalmips/literal, literalmipsel/literal, literalpowerpc/literal, literals390/literal, literalsparc/literal. /para @@ -669,8 +668,8 @@ filenameproposed-updates/filename directory. Those packages in filenameproposed-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-stableuploads to the literalstable/literal distribution/link for details. /para @@ -763,7 +762,7 @@ Debian 2.1, literalslink/literal; Debian 2.2, literalpotato/literal; Debian 3.0, literalwoody/literal; Debian 3.1, literalsarge/literal; Debian 4.0, literaletch/literal; Debian 5.0, literallenny/literal -and the next release will be called literalsqueeze/literal. +and the next release will be called literalwheezy/literal. There is also a ``pseudo-distribution'', called literalsid/literal, which is the current literalunstable/literal distribution; since packages are moved from literalunstable/literal to Index: common.ent === --- common.ent (revisione 8928) +++ common.ent (copia locale) @@ -10,10 +10,10 @@ !-- volatile information -- -!ENTITY number-of-pkgs 12000 +!ENTITY number-of-pkgs 15000 !ENTITY number-of-maintainers 1000 -!ENTITY number-of-arches 12 +!ENTITY number-of-arches 11 !-- standard information -- !ENTITY fsf-addr Free Software Foundation, Inc., signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- 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
Bug#643932: marked as done (FTP Team related changes)
Your message dated Thu, 19 Jan 2012 20:48:51 +
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
---BeginMessage---
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
-titleBest practices for filename.orig.tar.{gz,bz2,lzma}/filename files/title
+titleBest 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 @@
titlePristine 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.footnotepara 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-commandgzip/commands 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 replaceableupstream-version/replaceable and
replaceabledebian-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
emphasissignificant/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
Bug#643933: marked as done (GPG keysize must be greater than 1024 bits)
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008ie...@franck.debian.org and subject line Bug#643933: fixed in developers-reference 3.4.7 has caused the Debian Bug report #643933, regarding GPG keysize must be greater than 1024 bits 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.) -- 643933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: developers-reference Version: 3.4.6 Severity: normal Tags: patch Keyring maintainers explicitly asked to provide GPG keys greater than 1024 bits [0], while page 4 currently states key must be at least 1024. Attached patch should solve this, by rephrasing the sentence stating keys must be greater than 1024 bits. [0] 20090520092534.gg22...@earth.li -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- Index: new-maintainer.dbk === --- new-maintainer.dbk (revisione 8928) +++ new-maintainer.dbk (copia locale) @@ -155,7 +155,7 @@ /para para You need a version 4 key for use in Debian Development. Your key length must -be at least 1024 bits; there is no reason to use a smaller key, and doing so +be greater than 1024 bits; there is no reason to use a smaller key, and doing so would be much less secure.footnotepara Version 4 keys are keys conforming to the OpenPGP standard as defined in RFC 2440. Version 4 is the key type that has always been created when using GnuPG. PGP versions since 5.x also could signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- 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.
Bug#643934: marked as done (Guest access disabled to DSA request tracker system)
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008ih...@franck.debian.org and subject line Bug#643934: fixed in developers-reference 3.4.7 has caused the Debian Bug report #643934, regarding Guest access disabled to DSA request tracker system 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.) -- 643934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: developers-reference Version: 3.4.6 Severity: normal Tags: patch Page 13 says it's possible to login to DSA request tracker system using guest/readonly, but it has been disabled due to abuses [0]. Attached patch should solve this, by pointing to DD accessible-only credentials. [0] http://wiki.debian.org/rt.debian.org?action=diffrev1=19rev2=20 -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- Index: resources.dbk === --- resources.dbk (revisione 8928) +++ resources.dbk (copia locale) @@ -238,8 +238,9 @@ 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 +url=url-rt; / (you can login with user debian its password is available at +filenamemaster.debian.org:file-debian-rt-password;/filename. +) 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. /para para Index: common.ent === --- common.ent (revisione 8928) +++ common.ent (copia locale) @@ -166,6 +166,7 @@ !ENTITY file-lisp-controller filename/usr/share/doc/common-lisp-controller/README.packaging/filename !ENTITY file-debian-private-archive ~debian/archive/debian-private/ !ENTITY file-debian-private-key ~debian/misc/irc-password +!ENTITY file-debian-rt-password ~debian/misc/rt-password !ENTITY file-bpp-autotools filename/usr/share/doc/autotools-dev/README.Debian.gz/filename !ENTITY cron-bug-report '0 17 * * fri echo index maint replaceableaddress/replaceable | mail request@bugs-host;' signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- 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
Bug#643935: marked as done (Do not mention yada as package helper)
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008it...@franck.debian.org and subject line Bug#643935: fixed in developers-reference 3.4.7 has caused the Debian Bug report #643935, regarding Do not mention yada as package helper 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.) -- 643935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: developers-reference Version: 3.4.6 Severity: normal Tags: patch Yada seems unmaintained and has been recently orphaned, it shouldn't be suggested as package helper at all. Attached patch should solve this, by removing yada section. -- .''`. : :' : Luca Falavigna dktrkr...@debian.org `. `' `- Index: tools.dbk === --- tools.dbk (revisione 8928) +++ tools.dbk (copia locale) @@ -193,24 +193,6 @@ /para /section -section id=yada -titlesystemitem role=packageyada/systemitem/title -para -systemitem role=packageyada/systemitem is another packaging helper tool. -It uses a filenamedebian/packages/filename file to auto-generate -filenamedebian/rules/filename and other necessary files in the -filenamedebian//filename subdirectory. The -filenamedebian/packages/filename file contains instruction to build -packages and there is no need to create any filenameMakefile/filename -files. There is possibility to use macro engine similar to the one used in -SPECS files from RPM source packages. -/para -para -For more informations see ulink -url=http://yada.alioth.debian.org/;literalYADA/literal site/ulink. -/para -/section - section id=equivs titlesystemitem role=packageequivs/systemitem/title para signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- 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
Bug#655096: marked as done (developers-reference: Typo in chapter 5.11.2, NMUs and debian/changelog)
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008ix...@franck.debian.org and subject line Bug#655096: fixed in developers-reference 3.4.7 has caused the Debian Bug report #655096, regarding developers-reference: Typo in chapter 5.11.2, NMUs and debian/changelog 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.) -- 655096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: developers-reference Severity: minor Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, in section 5.11.2 is a minor typo, fixed by attached trivial patch: If the package is a not a native package [...] Cheers, Andreas - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-8-generic (SMP w/2 CPU cores) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJPCa/+AAoJEGHzRCZ03mYkCX0QAJlac+Toee3NP/axiL5QGK8j Rdz2KB7HGCO0QWCmgaObdNn7eW3T1Hsj+wEfnCTzf4/zoZ/k82i73TKaaN/mVhP6 NOHbirPt5981KDa0+77GtOj4inJ/BgvNctyG2w7XyaGjrOw92VqM0Dhz9vNZDn6X eqaFZQQhb9VjtE++IEJeQCQHxjG5MjlwD3CFe/LYO4+woQp+XPJe6OLQmPo1SYxm S8H/uLyH6/MnNOTDuqTtiwGeG+6csjH9DDAMyLGWUIXXHX4GaD3DmMyeDWXs83a4 dIPZzfxEW+mkOy5zgONTOzYGbOKSkW3zJ3EAOCXOSFTTRlZRs7Kfip0QviOx23mf hcPmurUvcZbubY8ttZDUQkv9weh6Nmfjbn0y02dZAoLVfOCilj4VhKoWphqiv8Wq 2cEWFQp8vCSYuVWlLKwcE6F1m3MYbrg1MqNNyKwK6krPs4ReO4C1O5nnJlhDJujg utGCF12MJgJfRZ4GpHBAzbo0Yco8voMAgG1khFNiJnEqdmZn7+oMuTOaTEcHXEF8 /aVu6C5vDJ3I9qxAweVYoP9Wsj6BB/5CZ3h93th21aukLmVBdxXbqnbOX55jMk8A Z0ML3hYvBDDK/gfgTJHGbodqPcFZEmyjhvEv0O7xAVx0ihIpUYaEmWucwmwe4v7x 2EnwWtAJiUSwyLQkZU1j =eu+T -END PGP SIGNATURE- Index: pkgs.dbk === --- pkgs.dbk (revision 9028) +++ pkgs.dbk (working copy) @@ -2061,7 +2061,7 @@ version literal1.5+nmu1/literal. /para para -If the package is a not a native package, you should add a minor version number +If the package is not a native package, you should add a minor version number to the Debian revision part of the version number (the portion after the last hyphen). This extra number must start at literal1/literal. For example, if the current version is literal1.5-2/literal, then an NMU would get ---End Message--- ---BeginMessage--- 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 655...@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
Bug#655153: marked as done (Trivial unfuzzy: please document the easy way)
Your message dated Thu, 19 Jan 2012 20:48:51 + with message-id e1rnyuh-0008j2...@franck.debian.org and subject line Bug#655153: fixed in developers-reference 3.4.7 has caused the Debian Bug report #655153, regarding Trivial unfuzzy: please document the easy way 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.) -- 655153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: developers-reference Version: 3.4.6 Severity: wishlist Tags: l10n patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, The developers reference currently documents two ways to unfuzzy translations [1]. msguntypot offers an easy way to do the job, please document it instead. The attached diff may be difficult to read, but you can have a look at the built document [2] if you prefer. 1: http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#s6.5.2.3 2: http://people.debian.org/~taffit/developers-reference/best-pkging-practices.html#s6.5.2.3 Regards David - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJPCf4OAAoJELgqIXr9/gnyUJgQAJC5cCA/j6XskVILGPSP7ery Shd+ibqjHCvh0hwhq2yIPooiJhrZB0lvxCVZB3wJ153fcATf5pzixWorRbUvseNw LsVGocmssdG3dEleUtOHbjfPz3SvkMDJtno4EIl0Pat8o9kzQ3t/SdKbUrqwuSee EagdwFZeIRoE7t12QRqFpXoqUzBh4djmcbgYWw27hOFBkm0RuNnWEF4N5XiUShUW wgJPjArSguRW5ediJNr0/6aCoHVCqcOJlkvpFyz9DRnhd0s8pV9Ty4fWz0UJpplP 9X40zYi75P8l3+aVaToVYIQr5J4HO+39FdNxpzBKdC+5+cFtQaphCbwqfubv2uPR Oza4wvdwJu0lUXklOlF8ZFYwezVxIjV92IRnIf7ExhXyLladwKRSmxmn85EAIPr7 fbjUFCDLs9FZvJ5G0LTTTEMWkWNfE9brh1X0EKPLx/UYX00MF/VIJ+kDmODvVtW0 CveRTVTIxZNF/w3MPcaAQOaAFZASHc00ki2uYshB3zFJ+/JWw9d6sazF8X+fv47o TXHob+f84pYbPk4gjdGG7Z3N80qyhjvqzAxznElnDu6podloH3wS+tHym2+Kanpe 8Nil5LMPTmyrJoqTyPi0zWs72iXCDRZrYs3u2crCr+zjDPK/QBZN8GoN5DWTpePu TFBP1MwqecxIgYIcSwfP =Q0YY -END PGP SIGNATURE- Index: best-pkging-practices.dbk === --- best-pkging-practices.dbk (révision 9028) +++ best-pkging-practices.dbk (copie de travail) @@ -830,129 +830,63 @@ translator will send you an update. /para para -To emphasisunfuzzy/emphasis translations, you can use two methods. The first -method does emphasispreventive/emphasis search and replace actions in the -PO files. The latter uses commandgettext/command utilities to emphasisunfuzzy/emphasis -strings. +To emphasisunfuzzy/emphasis translations, you can use +commandmsguntypot/command (part of the systemitem +role=packagepo4a/systemitem package). /para -para -emphasisPreventive unfuzzy/emphasis method: -/para orderedlist numeration=arabic listitem para -Try finding a complete translation file emphasis role=strongbefore/emphasis -the change: +Regenerate the POT and PO files. /para -programlistingfor i in debian/po/*po; do echo -n $i: ; msgfmt -o /dev/null --statistics $i; done/programlisting -para -The file only showing emphasistranslated/emphasis items will be used -as the reference file. If there is none (which should not happen if you take -care to properly interact with translators), you should use the file -with the most translated strings. -/para +programlistingdebconf-updatepo/programlisting /listitem listitem para -Identify the needed change. In this example, let's assume the change is about -fixing a typo in the word literaltypo/literal which was inadvertently -written as literaltpyo/literal. Therefore, the change is -commands/tpyo/typo/command. +Make a copy of the POT file. /para +programlistingcp templates.pot templates.pot.orig/programlisting /listitem listitem para -Check that this change is only applied to the place where you really intend -to make it and emphasis role=strongnot/emphasis in any other place -where the original string is appropriate. This specifically applies to -change in punctuation, for instance. +Make a copy of all the PO files. /para +programlistingmkdir po_fridge; cp *.po po_fridge/programlisting /listitem listitem para -Modify all PO files by using commandsed/command. The use of that command -is recommended over any text editor to guarantee that the files encoding will -not be broken by the edit action: +Change the debconf template files to fix the typos. /para
developers-reference_3.4.7_amd64.changes ACCEPTED into unstable
Accepted: 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 Override entries for your package: developers-reference-de_3.4.7_all.deb - optional doc developers-reference-fr_3.4.7_all.deb - optional doc developers-reference-ja_3.4.7_all.deb - optional doc developers-reference_3.4.7.dsc - source doc developers-reference_3.4.7_all.deb - optional doc Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 569219 629530 643929 643930 643931 643932 643933 643934 643935 655096 655153 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1rnyug-0008id...@franck.debian.org
Bug#656569: debian-policy: Mandorary Testsuite or Demo requirement for all Libraries.
Package: debian-policy Severity: normal Dear Maintainer What has lead up to this situation was the discovery of libogre 1.7.3-3 in the testing branch. I will be very simple it don't work at all even with the most basic OGRE test command line no graphical and it segfaulted out yet no simple application existed for it that a end user could be requested to install and run to find out if it was dud or not. This is not a suitable location for support end user ends up blaming the program not the library as they should. This is not the first time I have seen 100 percent non functional parts make it to testing. What I am requesting that its Mandatory requirement to provide a testsuite package or a demo package matching up with all libraries. This way something to test the functionality of the libraries even to the most basic level has to exist. --The Rules I am putting Forwards START-- If library has a upstream test-suite the test-suite be build and bundled as package-testsuite. If library has upstream demos/sample applications they will be packaged up package-demos.. If those packages happen to contain parts that are license incompatible with main repo but can be shipped in contrib or non-free without causing the maintainer any legal trouble. They should still be shipped. If the upstream testsuite or demos cannot be shipped for any reason in main, contrib or non-free repositories a package-testsuite-min must be made. If required the package-testsuite-min will contain the smallest functional program for the library will be provided where possible without requiring x11 packaged basically initing the basic structs of the library and shutting library down cleanly. Package-testsuite-min, package-testsuite and package-demos will all be built with the exact same complier and envorment used to make the library. It is mandatory that the Maintainer before sending package up stream to run in order of preference the upstream testsuite, upstream demos or the smallest functional program. If Maintainer will report in package description what test was run being one of testsuite,demo or testsuite-min along with any known failures. Integration of upstream testsuite with deb8 is preferred if possible. --The Rules I am putting Forwards END-- Libraries missing all 3 will be pretty simple to search for. I would be kind and say maintainers have 12 months to come into line with the new policy. This should allow end users making applications to work out if it complier or library failure. The idea that a library will be run some time in 10 days before it moves from unstable to testing is a flawed one. Only way to be 100 percent sure it run its make it mandatory for the maintainer todo so. Issue of maintainers being able to skip out on providing test-suites means they also get to skip out on running them. If they have had to build them anyhow they might as well run them. Maintainers praying that someone tries there library before the 10 days is up is not suitable to say the least. Even in 10 days a all users of the unstable branch might not use all functions of a library to the extent the libraries own testsuite will. So detectable faults are slipping threw that should be stopped. Issues of testsuites not existing removes means to for users to test against hardware particular errors. This will become more important as more items use opencl and other acceleration methods. Saying users can build from source is not going to cut it. In case of a complier error the source code build will not work of the test-suite but the binary build should work the same as everyone else with the binary build. Reverse is also true if the binary testsuite does not work yet everyone rebuilding the testsuite with a different complier it works you know you had a complier issue and the package need to be rebuilt. Really go to repo and search testsuite and the problem is straight up in your face. Less than 20 items return. End user cannot test there system unless they know how to code even then building the testsuite from source may give a false reading due to complier defect. That the library is bust when the complier is, List of people who should be able to check. Maintainer, Automated system about the maintainer reason for deb8 support recommendation and the end user. The issue causing me to request this is a segfault all kind of errors can be sneaking past due to testing not being done. There can be security issues sneaking past as well. Will everyone like this most likely not. I know it will mean more disk space. Of course one option might be extra branches in the repos test and test-non- free for containing the test-suites so all mirror sites don't have major storage requirement expand. There are reasons at times test suites cannot be allowed to be modified so they fall outside the normal permitted licenses by Debian even that they are perfectly allowed to be shipped as long as there source code is not
Bug#656569: debian-policy: Mandorary Testsuite or Demo requirement for all Libraries.
Hi, Off-topic, but in hope of chiseling away at the problem to make what remains a little simpler: oiaohm wrote: Yes libogre contains quite a decent testsuite that basically is not provided even in the source debs due to license issue blocking it from main. Do you know where I can read more about this? Is there a bug filed in Debian? Is there anyone working with upstream on fixing it, assuming they consider it worth addressing? Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120120072659.GA2779@burratino
Processed: block 597567 with 248809
Processing commands for cont...@bugs.debian.org: block 597567 with 248809 Bug #597567 [mumudvb] mumudvb: using a questionable username Was not blocked by any bugs. Added blocking bug(s) of 597567: 248809 and 429671 thanks Stopping processing here. Please contact me if you need assistance. -- 597567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132704482025129.transcr...@bugs.debian.org
