Your message dated Tue, 27 Jul 2021 16:01:45 +0200 with message-id <f7b47467-aba0-b081-9b3f-438fe890c8fc@debian.org> and subject line Re: Bug#991535: unblock: developers-reference/11.0.21 has caused the Debian Bug report #991535, regarding unblock: developers-reference/11.0.21 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 owner@bugs.debian.org immediately.) -- 991535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991535 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: unblock: developers-reference/11.0.21
- From: Holger Levsen <holger@debian.org>
- Date: Tue, 27 Jul 2021 03:17:33 +0200
- Message-id: <[🔎] 20210727011733.GA26612@layer-acht.org>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: unblock Please unblock package developers-reference 11.0.21, which is a documentation and translation only update: developers-reference (11.0.21) unstable; urgency=medium * best-pkging-practices: replace 'atter' with 'other', with thanks to Jeremy Bicha. Closes: #991291 * pkgs: update releases used in examples for the time when bullseye is stable. * resources: update 'dak ls evince' example output. * Update all .po files for changed strings in the English original. -- Holger Levsen <holger@debian.org> Tue, 20 Jul 2021 15:20:35 +0200 debdiff developers-reference_11.0.20.dsc developers-reference_11.0.21.dsc |diffstat debian/changelog | 17 ++++- source/best-pkging-practices.rst | 2 source/locales/de/LC_MESSAGES/best-pkging-practices.po | 5 - source/locales/de/LC_MESSAGES/pkgs.po | 14 ++-- source/locales/fr/LC_MESSAGES/best-pkging-practices.po | 57 ++++++++--------- source/locales/fr/LC_MESSAGES/pkgs.po | 14 ++-- source/locales/it/LC_MESSAGES/best-pkging-practices.po | 15 +++- source/locales/it/LC_MESSAGES/pkgs.po | 34 ++++++++-- source/locales/ja/LC_MESSAGES/best-pkging-practices.po | 15 +++- source/locales/ja/LC_MESSAGES/pkgs.po | 34 ++++++++-- source/locales/ru/LC_MESSAGES/best-pkging-practices.po | 15 +++- source/locales/ru/LC_MESSAGES/pkgs.po | 34 ++++++++-- source/pkgs.rst | 4 - source/resources.rst | 16 ++-- 14 files changed, 198 insertions(+), 78 deletions(-) The full debdiff is attached. unblock developers-reference/11.0.21 Thanks for your work on bullseye! -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Bottled water companies don't produce water, they produce plastic bottles.diff -Nru developers-reference-11.0.20/debian/changelog developers-reference-11.0.21/debian/changelog --- developers-reference-11.0.20/debian/changelog 2021-06-18 23:50:52.000000000 +0200 +++ developers-reference-11.0.21/debian/changelog 2021-07-20 15:20:35.000000000 +0200 @@ -1,12 +1,23 @@ +developers-reference (11.0.21) unstable; urgency=medium + + * best-pkging-practices: replace 'atter' with 'other', with thanks to + Jeremy Bicha. Closes: #991291 + * pkgs: update releases used in examples for the time when bullseye is + stable. + * resources: update 'dak ls evince' example output. + * Update all .po files for changed strings in the English original. + + -- Holger Levsen <holger@debian.org> Tue, 20 Jul 2021 15:20:35 +0200 + developers-reference (11.0.20) unstable; urgency=medium [ Judit Foglszinger ] - * removing freenode and moving reference to cloaks to Debian wiki. - Closes: 990054. + * ressources: Remove freenode and move reference to cloaks to Debian wiki. + Closes: #990054. [ Holger Levsen ] * Update all .po files for changed strings in the English original. - * fix typo in previous d/changelog entry + * Fix typo in previous d/changelog entry. -- Holger Levsen <holger@debian.org> Fri, 18 Jun 2021 23:50:52 +0200 diff -Nru developers-reference-11.0.20/source/best-pkging-practices.rst developers-reference-11.0.21/source/best-pkging-practices.rst --- developers-reference-11.0.20/source/best-pkging-practices.rst 2021-01-17 22:22:11.000000000 +0100 +++ developers-reference-11.0.21/source/best-pkging-practices.rst 2021-07-20 14:58:54.000000000 +0200 @@ -1466,7 +1466,7 @@ point). 4. **may** use *packagename*\ ``-``\ *upstream-version*\ ``+dfsg`` - (or any atter suffix which is added to the tarball name) as + (or any other suffix which is added to the tarball name) as the name of the top-level directory in its tarball. This makes it possible to distinguish pristine tarballs from repackaged ones. diff -Nru developers-reference-11.0.20/source/locales/de/LC_MESSAGES/best-pkging-practices.po developers-reference-11.0.21/source/locales/de/LC_MESSAGES/best-pkging-practices.po --- developers-reference-11.0.20/source/locales/de/LC_MESSAGES/best-pkging-practices.po 2021-01-17 23:28:02.000000000 +0100 +++ developers-reference-11.0.21/source/locales/de/LC_MESSAGES/best-pkging-practices.po 2021-07-20 15:01:41.000000000 +0200 @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: developers-reference\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-01-17 22:27+0000\n" +"POT-Creation-Date: 2021-07-20 13:01+0000\n" "PO-Revision-Date: 2020-03-02 19:51+0100\n" "Last-Translator: Carsten Schoenert <c.schoenert@t-online.de>\n" "Language: de\n" @@ -2760,9 +2760,10 @@ "Originaldistribution zu suchen)." #: ../best-pkging-practices.rst:1468 +#, fuzzy msgid "" "**may** use *packagename*\\ ``-``\\ *upstream-version*\\ ``+dfsg`` (or " -"any atter suffix which is added to the tarball name) as the name of the " +"any other suffix which is added to the tarball name) as the name of the " "top-level directory in its tarball. This makes it possible to distinguish" " pristine tarballs from repackaged ones." msgstr "" diff -Nru developers-reference-11.0.20/source/locales/de/LC_MESSAGES/pkgs.po developers-reference-11.0.21/source/locales/de/LC_MESSAGES/pkgs.po --- developers-reference-11.0.20/source/locales/de/LC_MESSAGES/pkgs.po 2021-05-05 19:55:08.000000000 +0200 +++ developers-reference-11.0.21/source/locales/de/LC_MESSAGES/pkgs.po 2021-07-20 15:17:39.000000000 +0200 @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: developers-reference\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-05-05 17:55+0000\n" +"POT-Creation-Date: 2021-07-20 13:17+0000\n" "PO-Revision-Date: 2020-03-02 19:50+0100\n" "Last-Translator: Carsten Schoenert <c.schoenert@t-online.de>\n" "Language: de\n" @@ -537,12 +537,13 @@ "Veröffentlichungszeitpunkt in ``Stable`` eingefügt." #: ../pkgs.rst:237 +#, fuzzy msgid "" "Uploads to a supported ``stable`` release should target their suite name " -"in the changelog, i.e. ``buster`` or ``stretch``. You should normally use" -" ``reportbug`` and the ``release.debian.org`` pseudo-package to send a " -"*source* ``debdiff``, rationale and associated bug numbers to the stable " -"release managers, and await a request to upload or further information." +"in the changelog, i.e. ``bullseye`` or ``buster``. You should normally " +"use ``reportbug`` and the ``release.debian.org`` pseudo-package to send a" +" *source* ``debdiff``, rationale and associated bug numbers to the stable" +" release managers, and await a request to upload or further information." msgstr "" "Uploads in eine unterstützte ``Stable`` Version sollten den Suite-Namen " "im Änderungslog enthalten, d. H. ``buster`` oder ``stretch``. " @@ -623,9 +624,10 @@ "unter $URL gefunden werden\")." #: ../pkgs.rst:264 +#, fuzzy msgid "" "The proposed package must have a correct version number (e.g. " -"``...+deb10u1`` for ``buster`` or ``+deb9u1`` for ``stretch``) and you " +"``...+deb11u1`` for ``bullseye`` or ``+deb10u1`` for ``buster``) and you " "should be able to explain what testing it has had." msgstr "" "Das vorgeschlagene Paket muss eine korrekte Versionsnummer haben (z. B. " diff -Nru developers-reference-11.0.20/source/locales/fr/LC_MESSAGES/best-pkging-practices.po developers-reference-11.0.21/source/locales/fr/LC_MESSAGES/best-pkging-practices.po --- developers-reference-11.0.20/source/locales/fr/LC_MESSAGES/best-pkging-practices.po 2021-05-03 18:13:51.000000000 +0200 +++ developers-reference-11.0.21/source/locales/fr/LC_MESSAGES/best-pkging-practices.po 2021-07-20 15:01:42.000000000 +0200 @@ -1,6 +1,8 @@ # French po4a translation of developers-reference: resources -# Copyright (C) 1999-2006, 2010,2021 Debian French l10n team <debian-l10n-french@lists.debian.org> -# This file is distributed under the same license as the developers-reference package. +# Copyright (C) 1999-2006, 2010,2021 Debian French l10n team +# <debian-l10n-french@lists.debian.org> +# This file is distributed under the same license as the +# developers-reference package. # # Antoine Hulin <antoine@origan.fdn.fr>, 1999-2002. # Frédéric Bothamy <frederic.bothamy@free.fr>, 2003-2006. @@ -10,17 +12,16 @@ msgstr "" "Project-Id-Version: developers-reference \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-01-17 22:27+0000\n" +"POT-Creation-Date: 2021-07-20 13:01+0000\n" "PO-Revision-Date: 2021-01-30 01:01+0100\n" "Last-Translator: Jean-Pierre Giraud <jean-pierregiraud@neuf.fr>\n" +"Language: fr_FR\n" "Language-Team: French <debian-l10n-french@lists.debian.org>\n" +"Plural-Forms: nplurals=2; plural=(n > 1)\n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" +"Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.8.0\n" -"Language: fr_FR\n" -"Plural-Forms: nplurals=2; plural=(n > 1);\n" -"X-Generator: Lokalize 2.0\n" #: ../best-pkging-practices.rst:4 msgid "Best Packaging Practices" @@ -523,8 +524,8 @@ "Les descriptions longues de paquets associés, par exemple construits à " "partir du même paquet source, peuvent partager des paragraphes afin " "d'améliorer la cohérence et de réduire la charge de travail pour les " -"traducteurs, mais il faut qu'il y ait au moins un paragraphe distinct " -"qui décrive le rôle spécifique du paquet." +"traducteurs, mais il faut qu'il y ait au moins un paragraphe distinct qui" +" décrive le rôle spécifique du paquet." #: ../best-pkging-practices.rst:249 msgid "" @@ -722,8 +723,8 @@ "``Homepage`` fields described above is also shown." msgstr "" "L'exemple qui suit montre une instance de ce champ pour un dépôt Git du " -"paquet ``vim``. Veuillez noter que l'URL a la forme ``https://`` (au " -"lieu de ``ssh://``). Une utilisation des champs ``Vcs-Browser`` et " +"paquet ``vim``. Veuillez noter que l'URL a la forme ``https://`` (au lieu" +" de ``ssh://``). Une utilisation des champs ``Vcs-Browser`` et " "``Homepage``, décrits précédemment, est aussi indiquée." #: ../best-pkging-practices.rst:362 @@ -996,8 +997,7 @@ #: ../best-pkging-practices.rst:507 msgid "Supplementing changelogs with ``NEWS.Debian`` files" -msgstr "" -"Complément des journaux de modifications dans les fichiers ``NEWS.Debian``" +msgstr "Complément des journaux de modifications dans les fichiers ``NEWS.Debian``" #: ../best-pkging-practices.rst:509 msgid "" @@ -1585,8 +1585,8 @@ "Pour se conformer à notre engagement de `diversité et équité " "<https://www.debian.org/intro/diversity>`__, veuillez utiliser des " "constructions de genre neutre dans votre écriture. Cela signifie éviter " -"les pronoms tels que il ou elle lors d’une référence à un rôle (tel " -"que « responsable ») dont le genre est inconnu. À la place, vous devriez " +"les pronoms tels que il ou elle lors d’une référence à un rôle (tel que «" +" responsable ») dont le genre est inconnu. À la place, vous devriez " "utiliser une forme plurielle (`They singulier " "<https://en.wikipedia.org/wiki/Singular_they>`__)." @@ -2229,13 +2229,13 @@ "traductions doivent être modifiées. Il est recommandé que la " "documentation traduite contienne l'indication du système de suivi des " "versions source qui est utilisé. Un système pratique est fourni par `doc-" -"check <https://salsa.debian.org/installer-team/installation-guide/blob" -"/master/scripts/doc-check>`__ du paquet ``debian-installer``, qui permet " -"un survol de l'état de la traduction pour toute langue, par l'utilisation" -" de commentaires structurés dans la version du fichier à traduire et, " -"pour le fichier traduit, la version du fichier sur laquelle est basée la " -"traduction. Il est possible d'adapter ce système dans votre propre dépôt " -"de gestion de versions." +"check <https://salsa.debian.org/installer-team/installation-" +"guide/blob/master/scripts/doc-check>`__ du paquet ``debian-installer``, " +"qui permet un survol de l'état de la traduction pour toute langue, par " +"l'utilisation de commentaires structurés dans la version du fichier à " +"traduire et, pour le fichier traduit, la version du fichier sur laquelle " +"est basée la traduction. Il est possible d'adapter ce système dans votre " +"propre dépôt de gestion de versions." #: ../best-pkging-practices.rst:1186 msgid "" @@ -2573,8 +2573,8 @@ "packages, which have other purposes." msgstr "" "Par exemple, avec l'option ``--guess-dummy``, ``deborphan`` essaye de " -"trouver tous les paquets de transition qu'il était nécessaire de mettre " -"à niveau, mais qui peuvent maintenant être supprimés. Pour ce faire, " +"trouver tous les paquets de transition qu'il était nécessaire de mettre à" +" niveau, mais qui peuvent maintenant être supprimés. Pour ce faire, " "``deborphan`` recherche les chaînes ``dummy`` ou ``transitional`` dans " "leur description courte, bien que ce serait mieux de rechercher les deux," " dans la mesure où il y a des paquets ``dummy`` ou ``transitional`` qui " @@ -2797,9 +2797,10 @@ "miroirs Debian plutôt que d'essayer de trouver le dépôt officiel amont) ;" #: ../best-pkging-practices.rst:1468 +#, fuzzy msgid "" "**may** use *packagename*\\ ``-``\\ *upstream-version*\\ ``+dfsg`` (or " -"any atter suffix which is added to the tarball name) as the name of the " +"any other suffix which is added to the tarball name) as the name of the " "top-level directory in its tarball. This makes it possible to distinguish" " pristine tarballs from repackaged ones." msgstr "" @@ -2995,9 +2996,9 @@ msgstr "" "Les symboles de débogage peuvent être extraits d'un fichier objet à " "l'aide de ``objcopy --only-keep-debug``. Ensuite les informations de " -"débogage peuvent être supprimées du fichier objet et ``objcopy --add-" -"gnu-debuglink`` peut être utilisé pour préciser le chemin vers le fichier" -" contenant les symboles de débogage. objcopy 1 explique en détail le " +"débogage peuvent être supprimées du fichier objet et ``objcopy --add-gnu-" +"debuglink`` peut être utilisé pour préciser le chemin vers le fichier " +"contenant les symboles de débogage. objcopy 1 explique en détail le " "fonctionnement." #: ../best-pkging-practices.rst:1564 diff -Nru developers-reference-11.0.20/source/locales/fr/LC_MESSAGES/pkgs.po developers-reference-11.0.21/source/locales/fr/LC_MESSAGES/pkgs.po --- developers-reference-11.0.20/source/locales/fr/LC_MESSAGES/pkgs.po 2021-05-05 19:55:10.000000000 +0200 +++ developers-reference-11.0.21/source/locales/fr/LC_MESSAGES/pkgs.po 2021-07-20 15:17:40.000000000 +0200 @@ -12,7 +12,7 @@ msgstr "" "Project-Id-Version: developers-reference \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-05-05 17:55+0000\n" +"POT-Creation-Date: 2021-07-20 13:17+0000\n" "PO-Revision-Date: 2021-02-02 19:30+0100\n" "Last-Translator: Jean-Pierre Giraud <jean-pierregiraud@neuf.fr>\n" "Language: fr_FR\n" @@ -538,12 +538,13 @@ "prochaine mise à jour de la distribution." #: ../pkgs.rst:237 +#, fuzzy msgid "" "Uploads to a supported ``stable`` release should target their suite name " -"in the changelog, i.e. ``buster`` or ``stretch``. You should normally use" -" ``reportbug`` and the ``release.debian.org`` pseudo-package to send a " -"*source* ``debdiff``, rationale and associated bug numbers to the stable " -"release managers, and await a request to upload or further information." +"in the changelog, i.e. ``bullseye`` or ``buster``. You should normally " +"use ``reportbug`` and the ``release.debian.org`` pseudo-package to send a" +" *source* ``debdiff``, rationale and associated bug numbers to the stable" +" release managers, and await a request to upload or further information." msgstr "" "Les envois vers une version ``stable`` prise en charge devraient cibler " "leur nom de publication dans le journal de modification, c'est-à-dire " @@ -618,9 +619,10 @@ "debdiff can be found at $URL`` »)." #: ../pkgs.rst:264 +#, fuzzy msgid "" "The proposed package must have a correct version number (e.g. " -"``...+deb10u1`` for ``buster`` or ``+deb9u1`` for ``stretch``) and you " +"``...+deb11u1`` for ``bullseye`` or ``+deb10u1`` for ``buster``) and you " "should be able to explain what testing it has had." msgstr "" "Le paquet projeté doit avoir un numéro de version correct (par exemple, " diff -Nru developers-reference-11.0.20/source/locales/it/LC_MESSAGES/best-pkging-practices.po developers-reference-11.0.21/source/locales/it/LC_MESSAGES/best-pkging-practices.po --- developers-reference-11.0.20/source/locales/it/LC_MESSAGES/best-pkging-practices.po 2021-01-17 23:28:04.000000000 +0100 +++ developers-reference-11.0.21/source/locales/it/LC_MESSAGES/best-pkging-practices.po 2021-07-20 15:01:43.000000000 +0200 @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: developers-reference \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-01-17 22:27+0000\n" +"POT-Creation-Date: 2021-07-20 13:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -2488,7 +2488,7 @@ #: ../best-pkging-practices.rst:1468 msgid "" "**may** use *packagename*\\ ``-``\\ *upstream-version*\\ ``+dfsg`` (or " -"any atter suffix which is added to the tarball name) as the name of the " +"any other suffix which is added to the tarball name) as the name of the " "top-level directory in its tarball. This makes it possible to distinguish" " pristine tarballs from repackaged ones." msgstr "" @@ -2788,3 +2788,14 @@ #~ " user by email." #~ msgstr "" +#~ msgid "" +#~ "**may** use *packagename*\\ ``-``\\ " +#~ "*upstream-version*\\ ``+dfsg`` (or any " +#~ "atter suffix which is added to the" +#~ " tarball name) as the name of " +#~ "the top-level directory in its " +#~ "tarball. This makes it possible to " +#~ "distinguish pristine tarballs from repackaged" +#~ " ones." +#~ msgstr "" + diff -Nru developers-reference-11.0.20/source/locales/it/LC_MESSAGES/pkgs.po developers-reference-11.0.21/source/locales/it/LC_MESSAGES/pkgs.po --- developers-reference-11.0.20/source/locales/it/LC_MESSAGES/pkgs.po 2021-05-05 19:55:12.000000000 +0200 +++ developers-reference-11.0.21/source/locales/it/LC_MESSAGES/pkgs.po 2021-07-20 15:17:42.000000000 +0200 @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: developers-reference \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-05-05 17:55+0000\n" +"POT-Creation-Date: 2021-07-20 13:17+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -507,10 +507,10 @@ #: ../pkgs.rst:237 msgid "" "Uploads to a supported ``stable`` release should target their suite name " -"in the changelog, i.e. ``buster`` or ``stretch``. You should normally use" -" ``reportbug`` and the ``release.debian.org`` pseudo-package to send a " -"*source* ``debdiff``, rationale and associated bug numbers to the stable " -"release managers, and await a request to upload or further information." +"in the changelog, i.e. ``bullseye`` or ``buster``. You should normally " +"use ``reportbug`` and the ``release.debian.org`` pseudo-package to send a" +" *source* ``debdiff``, rationale and associated bug numbers to the stable" +" release managers, and await a request to upload or further information." msgstr "" #: ../pkgs.rst:243 @@ -559,7 +559,7 @@ #: ../pkgs.rst:264 msgid "" "The proposed package must have a correct version number (e.g. " -"``...+deb10u1`` for ``buster`` or ``+deb9u1`` for ``stretch``) and you " +"``...+deb11u1`` for ``bullseye`` or ``+deb10u1`` for ``buster``) and you " "should be able to explain what testing it has had." msgstr "" @@ -5096,3 +5096,25 @@ #~ "the ``ftp.debian.org`` pseudo-package." #~ msgstr "" +#~ msgid "" +#~ "Uploads to a supported ``stable`` " +#~ "release should target their suite name" +#~ " in the changelog, i.e. ``buster`` or" +#~ " ``stretch``. You should normally use " +#~ "``reportbug`` and the ``release.debian.org`` " +#~ "pseudo-package to send a *source* " +#~ "``debdiff``, rationale and associated bug " +#~ "numbers to the stable release managers," +#~ " and await a request to upload " +#~ "or further information." +#~ msgstr "" + +#~ msgid "" +#~ "The proposed package must have a " +#~ "correct version number (e.g. ``...+deb10u1``" +#~ " for ``buster`` or ``+deb9u1`` for " +#~ "``stretch``) and you should be able " +#~ "to explain what testing it has " +#~ "had." +#~ msgstr "" + diff -Nru developers-reference-11.0.20/source/locales/ja/LC_MESSAGES/best-pkging-practices.po developers-reference-11.0.21/source/locales/ja/LC_MESSAGES/best-pkging-practices.po --- developers-reference-11.0.20/source/locales/ja/LC_MESSAGES/best-pkging-practices.po 2021-01-17 23:28:05.000000000 +0100 +++ developers-reference-11.0.21/source/locales/ja/LC_MESSAGES/best-pkging-practices.po 2021-07-20 15:01:44.000000000 +0200 @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: developers-reference \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-01-17 22:27+0000\n" +"POT-Creation-Date: 2021-07-20 13:01+0000\n" "PO-Revision-Date: 2020-03-24 13:38+0900\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -2168,7 +2168,7 @@ #: ../best-pkging-practices.rst:1468 msgid "" "**may** use *packagename*\\ ``-``\\ *upstream-version*\\ ``+dfsg`` (or " -"any atter suffix which is added to the tarball name) as the name of the " +"any other suffix which is added to the tarball name) as the name of the " "top-level directory in its tarball. This makes it possible to distinguish" " pristine tarballs from repackaged ones." msgstr "" @@ -2443,3 +2443,14 @@ #~ " user by email." #~ msgstr "" +#~ msgid "" +#~ "**may** use *packagename*\\ ``-``\\ " +#~ "*upstream-version*\\ ``+dfsg`` (or any " +#~ "atter suffix which is added to the" +#~ " tarball name) as the name of " +#~ "the top-level directory in its " +#~ "tarball. This makes it possible to " +#~ "distinguish pristine tarballs from repackaged" +#~ " ones." +#~ msgstr "" + diff -Nru developers-reference-11.0.20/source/locales/ja/LC_MESSAGES/pkgs.po developers-reference-11.0.21/source/locales/ja/LC_MESSAGES/pkgs.po --- developers-reference-11.0.20/source/locales/ja/LC_MESSAGES/pkgs.po 2021-05-05 19:55:14.000000000 +0200 +++ developers-reference-11.0.21/source/locales/ja/LC_MESSAGES/pkgs.po 2021-07-20 15:17:43.000000000 +0200 @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: developers-reference \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-05-05 17:55+0000\n" +"POT-Creation-Date: 2021-07-20 13:17+0000\n" "PO-Revision-Date: 2020-03-20 12:21+0900\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -451,10 +451,10 @@ #: ../pkgs.rst:237 msgid "" "Uploads to a supported ``stable`` release should target their suite name " -"in the changelog, i.e. ``buster`` or ``stretch``. You should normally use" -" ``reportbug`` and the ``release.debian.org`` pseudo-package to send a " -"*source* ``debdiff``, rationale and associated bug numbers to the stable " -"release managers, and await a request to upload or further information." +"in the changelog, i.e. ``bullseye`` or ``buster``. You should normally " +"use ``reportbug`` and the ``release.debian.org`` pseudo-package to send a" +" *source* ``debdiff``, rationale and associated bug numbers to the stable" +" release managers, and await a request to upload or further information." msgstr "" #: ../pkgs.rst:243 @@ -503,7 +503,7 @@ #: ../pkgs.rst:264 msgid "" "The proposed package must have a correct version number (e.g. " -"``...+deb10u1`` for ``buster`` or ``+deb9u1`` for ``stretch``) and you " +"``...+deb11u1`` for ``bullseye`` or ``+deb10u1`` for ``buster``) and you " "should be able to explain what testing it has had." msgstr "" @@ -4446,3 +4446,25 @@ #~ "the ``ftp.debian.org`` pseudo-package." #~ msgstr "" +#~ msgid "" +#~ "Uploads to a supported ``stable`` " +#~ "release should target their suite name" +#~ " in the changelog, i.e. ``buster`` or" +#~ " ``stretch``. You should normally use " +#~ "``reportbug`` and the ``release.debian.org`` " +#~ "pseudo-package to send a *source* " +#~ "``debdiff``, rationale and associated bug " +#~ "numbers to the stable release managers," +#~ " and await a request to upload " +#~ "or further information." +#~ msgstr "" + +#~ msgid "" +#~ "The proposed package must have a " +#~ "correct version number (e.g. ``...+deb10u1``" +#~ " for ``buster`` or ``+deb9u1`` for " +#~ "``stretch``) and you should be able " +#~ "to explain what testing it has " +#~ "had." +#~ msgstr "" + diff -Nru developers-reference-11.0.20/source/locales/ru/LC_MESSAGES/best-pkging-practices.po developers-reference-11.0.21/source/locales/ru/LC_MESSAGES/best-pkging-practices.po --- developers-reference-11.0.20/source/locales/ru/LC_MESSAGES/best-pkging-practices.po 2021-01-17 23:28:06.000000000 +0100 +++ developers-reference-11.0.21/source/locales/ru/LC_MESSAGES/best-pkging-practices.po 2021-07-20 15:01:45.000000000 +0200 @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: developers-reference \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-01-17 22:27+0000\n" +"POT-Creation-Date: 2021-07-20 13:01+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -2495,7 +2495,7 @@ #: ../best-pkging-practices.rst:1468 msgid "" "**may** use *packagename*\\ ``-``\\ *upstream-version*\\ ``+dfsg`` (or " -"any atter suffix which is added to the tarball name) as the name of the " +"any other suffix which is added to the tarball name) as the name of the " "top-level directory in its tarball. This makes it possible to distinguish" " pristine tarballs from repackaged ones." msgstr "" @@ -2793,3 +2793,14 @@ #~ " user by email." #~ msgstr "" +#~ msgid "" +#~ "**may** use *packagename*\\ ``-``\\ " +#~ "*upstream-version*\\ ``+dfsg`` (or any " +#~ "atter suffix which is added to the" +#~ " tarball name) as the name of " +#~ "the top-level directory in its " +#~ "tarball. This makes it possible to " +#~ "distinguish pristine tarballs from repackaged" +#~ " ones." +#~ msgstr "" + diff -Nru developers-reference-11.0.20/source/locales/ru/LC_MESSAGES/pkgs.po developers-reference-11.0.21/source/locales/ru/LC_MESSAGES/pkgs.po --- developers-reference-11.0.20/source/locales/ru/LC_MESSAGES/pkgs.po 2021-05-05 19:55:15.000000000 +0200 +++ developers-reference-11.0.21/source/locales/ru/LC_MESSAGES/pkgs.po 2021-07-20 15:17:44.000000000 +0200 @@ -3,7 +3,7 @@ msgstr "" "Project-Id-Version: developers-reference \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2021-05-05 17:55+0000\n" +"POT-Creation-Date: 2021-07-20 13:17+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -520,10 +520,10 @@ #: ../pkgs.rst:237 msgid "" "Uploads to a supported ``stable`` release should target their suite name " -"in the changelog, i.e. ``buster`` or ``stretch``. You should normally use" -" ``reportbug`` and the ``release.debian.org`` pseudo-package to send a " -"*source* ``debdiff``, rationale and associated bug numbers to the stable " -"release managers, and await a request to upload or further information." +"in the changelog, i.e. ``bullseye`` or ``buster``. You should normally " +"use ``reportbug`` and the ``release.debian.org`` pseudo-package to send a" +" *source* ``debdiff``, rationale and associated bug numbers to the stable" +" release managers, and await a request to upload or further information." msgstr "" #: ../pkgs.rst:243 @@ -572,7 +572,7 @@ #: ../pkgs.rst:264 msgid "" "The proposed package must have a correct version number (e.g. " -"``...+deb10u1`` for ``buster`` or ``+deb9u1`` for ``stretch``) and you " +"``...+deb11u1`` for ``bullseye`` or ``+deb10u1`` for ``buster``) and you " "should be able to explain what testing it has had." msgstr "" @@ -5159,3 +5159,25 @@ #~ "the ``ftp.debian.org`` pseudo-package." #~ msgstr "" +#~ msgid "" +#~ "Uploads to a supported ``stable`` " +#~ "release should target their suite name" +#~ " in the changelog, i.e. ``buster`` or" +#~ " ``stretch``. You should normally use " +#~ "``reportbug`` and the ``release.debian.org`` " +#~ "pseudo-package to send a *source* " +#~ "``debdiff``, rationale and associated bug " +#~ "numbers to the stable release managers," +#~ " and await a request to upload " +#~ "or further information." +#~ msgstr "" + +#~ msgid "" +#~ "The proposed package must have a " +#~ "correct version number (e.g. ``...+deb10u1``" +#~ " for ``buster`` or ``+deb9u1`` for " +#~ "``stretch``) and you should be able " +#~ "to explain what testing it has " +#~ "had." +#~ msgstr "" + diff -Nru developers-reference-11.0.20/source/pkgs.rst developers-reference-11.0.21/source/pkgs.rst --- developers-reference-11.0.20/source/pkgs.rst 2021-05-05 19:49:47.000000000 +0200 +++ developers-reference-11.0.21/source/pkgs.rst 2021-07-20 15:10:28.000000000 +0200 @@ -235,7 +235,7 @@ it will be included in ``stable`` with the next point release. Uploads to a supported ``stable`` release should target their suite name in -the changelog, i.e. ``buster`` or ``stretch``. You should normally use +the changelog, i.e. ``bullseye`` or ``buster``. You should normally use ``reportbug`` and the ``release.debian.org`` pseudo-package to send a *source* ``debdiff``, rationale and associated bug numbers to the stable release managers, and await a request to upload or further information. @@ -262,7 +262,7 @@ in your request (not just the raw patches or "a debdiff can be found at $URL"). - The proposed package must have a correct version number - (e.g. ``...+deb10u1`` for ``buster`` or ``+deb9u1`` for ``stretch``) + (e.g. ``...+deb11u1`` for ``bullseye`` or ``+deb10u1`` for ``buster``) and you should be able to explain what testing it has had. - The update must be built in an ``stable`` environment or chroot (or ``oldstable`` if you target that). diff -Nru developers-reference-11.0.20/source/resources.rst developers-reference-11.0.21/source/resources.rst --- developers-reference-11.0.20/source/resources.rst 2021-06-18 23:43:25.000000000 +0200 +++ developers-reference-11.0.21/source/resources.rst 2021-07-20 15:16:28.000000000 +0200 @@ -853,12 +853,16 @@ :: $ dak ls evince - evince | 0.1.5-2sarge1 | oldstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc - evince | 0.4.0-5 | etch-m68k | source, m68k - evince | 0.4.0-5 | stable | source, alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc - evince | 2.20.2-1 | testing | source - evince | 2.20.2-1+b1 | testing | alpha, amd64, arm, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc - evince | 2.22.2-1 | unstable | source, alpha, amd64, arm, armel, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc + evince | 3.22.1-3+deb9u2 | oldstable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x + evince | 3.22.1-3+deb9u2 | oldstable-debug | source + evince | 3.30.2-3+deb10u1 | stable | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x + evince | 3.30.2-3+deb10u1 | stable-debug | source + evince | 3.38.2-1 | testing | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x + evince | 3.38.2-1 | unstable | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x + evince | 3.38.2-1 | unstable-debug | source + evince | 40.4-1 | buildd-experimental | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x + evince | 40.4-1 | experimental | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x + evince | 40.4-1 | experimental-debug | source In this example, you can see that the version in ``unstable`` differs from the version in ``testing`` and that there has been a binary-onlyAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: Holger Levsen <holger@debian.org>, 991535-done@bugs.debian.org
- Subject: Re: Bug#991535: unblock: developers-reference/11.0.21
- From: Paul Gevers <elbrus@debian.org>
- Date: Tue, 27 Jul 2021 16:01:45 +0200
- Message-id: <f7b47467-aba0-b081-9b3f-438fe890c8fc@debian.org>
- In-reply-to: <[🔎] 20210727011733.GA26612@layer-acht.org>
- References: <[🔎] 20210727011733.GA26612@layer-acht.org>
Hi Holger, On 27-07-2021 03:17, Holger Levsen wrote: > Please unblock package developers-reference 11.0.21, which is a documentation > and translation only update: Unblocked. However, next time I'd love to see less strings becoming fuzzy for only a buster -> bullseye, stretch -> buster update. It's not going to be time well spent for translators to only find such renames. Also, it will mean some untranslated (because fuzzy) strings that are not really needed in my opinion (IIUC). Paul, who sometimes refrains from making minor improvements in release-notes (at this stage) unless he can fix it in the translations too.Attachment: OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---