Your message dated Fri, 24 Aug 2012 06:02:39 +0000
with message-id <[email protected]>
and subject line Bug#679295: fixed in keystone 2012.1.1-4
has caused the Debian Bug report #679295,
regarding keystone: [debconf_rewrite] Debconf templates and debian/control
review proposal
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 [email protected]
immediately.)
--
679295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679295
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: keystone
Version: N/A
Severity: normal
Dear Debian maintainer,
Hello,
I just noticed new or modified debconf templates appearing for this
package.
I would like to suggest you to consider calling for debconf templates
review AND translation updates when you introduce new debconf
templates or modify the existing templates in a package or, if you
prefer, to send a call for translations after uploading the first
version that introduces new templates or templates changes.
If you're interested in suggestions for doing this, you can find some
at the end of this bug report.
The debian-l10n-english team will now start a review, on our own
initiative. It will be conducted through this bug report.
Suggestions for future debconf templates review
------------------------------------------------
1) Getting debconf templates reviewed
--------------------------------------
The Debian i18n contributors have developed a set of suggestions for
the writing style of debconf templates, to give them an overall
consistency all around Debian. These writing style suggestions are
explained in the Developers Reference. Lintian also warns about common
writing style concerns.
Maintainers are welcome when they ask for a review of debconf templates
and/or packages descriptions on [email protected].
It is of course not needed to wait for someone (such as me right me)
proposing you such a review.
In such situations (whether the review is requested by the maintainer
or proposed by someone else), someone from the debian-l10n-english
team will pick up the review to do, handle it, and finally send you a
bug report with the suggested templates. If you want, you can ask for
being CC'ed to the various discussions when the templates are
reviewed.
2) Call for new translations
----------------------------
As soon as the templates have been reviewed, you can ask Debian
translators for new translations:
Just go to your package's build tree and use:
$ podebconf-report-po --call
This will propose you a generic mail which is to be sent to
[email protected] and call for new translations.
This utility will mention existing translations to avoid duplicate
work.
It will also attach the needed material to this mail.
Please also think about giving a deadline to translators. We like
deadlines..:-)
3) Always call for translation updates before uploading
-------------------------------------------------------
(of course only when you change the debconf templates!)
If your package already includes debconf translations (ie *.po files
in debian/po), please consider calling for translation updates if you
happen to change something in the templates...or just in case when you
release a new version.
This is done with the following command:
$ podebconf-report-po
This will build private mails to translators (ie people listed in
"Last-Translator" in the PO files) for translations that are
incomplete. These mails will included the needed PO file for each
translator.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: keystone
Source-Version: 2012.1.1-4
We believe that the bug you reported is fixed in the latest version of
keystone, which is due to be installed in the Debian FTP archive.
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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand <[email protected]> (supplier of updated keystone 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 21 Aug 2012 08:06:07 +0000
Source: keystone
Binary: python-keystone keystone keystone-doc
Architecture: source all
Version: 2012.1.1-4
Distribution: unstable
Urgency: low
Maintainer: PKG OpenStack <[email protected]>
Changed-By: Thomas Goirand <[email protected]>
Description:
keystone - OpenStack identity service
keystone-doc - OpenStack identity service - documentation
python-keystone - OpenStack identity service - library
Closes: 679295 682438 683414 684565 684590 684606 684877 684942 685325 685405
685431 685434 685435 685623 685671
Changes:
keystone (2012.1.1-4) unstable; urgency=low
.
* Updated debian/keystone.templates, debian/control after review from
the internationalization team (Closes: #683414, #679295).
* Updated debconf translations with thanks to:
- de: Pfannenstein Erik <[email protected]> (Closes: #684877)
- cs: Michal Šimůnek <[email protected]> (Closes: #685434)
- pl: Michał Kułach <[email protected]> (Closes: #685431)
- fr: David Prévot <[email protected]> (Closes: #685325)
- sv: Martin Bagge <[email protected]> (Closes: #684942)
- sk: helix84 <[email protected]> (Closes: #684606)
- ru: Yuri Kozlov <[email protected]> (Closes: #684590)
- da: Joe Dalton <[email protected]> (Closes: #684565)
- pt: Pedro Ribeiro <[email protected]> (Closes: #682438)
- es: SM Baby Siabef <[email protected]> (Closes: #685435)
- it: Beatrice Torracca <[email protected]> (Closes: #685623)
* Added debconf translations with thanks to:
- pt_BR: Adriano Rafael Gomes <[email protected]> (Closes: #685405)
- nl: Jeroen Schot <[email protected]> (Closes: #685671)
Checksums-Sha1:
268b7cbdaa7f7b93047d6cbf0332526964ed0e4e 1898 keystone_2012.1.1-4.dsc
24a418465b98e4b0fa4bbc3d6e33914f76ca4ad6 18862
keystone_2012.1.1-4.debian.tar.gz
792b1b9564bea43bb33b0b8c3d1dce20aa6dda2f 91856
python-keystone_2012.1.1-4_all.deb
fb8a1c7f8c7908994c1987881eff8834e1dc67ac 15542 keystone_2012.1.1-4_all.deb
23c8c69e2945fe54646a8bbccb7965c84226af9a 238134 keystone-doc_2012.1.1-4_all.deb
Checksums-Sha256:
7804a6d343202932a203b101b7876f45fe0ddb5384edca44859dd42817b06d38 1898
keystone_2012.1.1-4.dsc
dd9c6c03989d5cb5f0f19c2f73d25427450cc091b3cbd0dacd0a373caac33e40 18862
keystone_2012.1.1-4.debian.tar.gz
669d8d58f18641bb40537bd5317e22b069a50fe58422aea833627dd83dd6e86b 91856
python-keystone_2012.1.1-4_all.deb
7c36c74b2b8881c67ce08073d7483e510579f94e562fe5bdc0b686d598deef05 15542
keystone_2012.1.1-4_all.deb
b8d5c4a8f03d9d7fc0de81a7efb18527f494e6b5682464e6ecdbdb326d335759 238134
keystone-doc_2012.1.1-4_all.deb
Files:
8b368d184823cdb851407b0193cd9140 1898 net extra keystone_2012.1.1-4.dsc
a7d32132511b35e0a357b70a922a0e33 18862 net extra
keystone_2012.1.1-4.debian.tar.gz
4133d817cad475cb14209b2566ee338f 91856 python extra
python-keystone_2012.1.1-4_all.deb
368c4cc5453cb9af0f6efdfb064666e5 15542 python extra keystone_2012.1.1-4_all.deb
0fd2546606ee6a49e1d3223591e3f3d2 238134 doc extra
keystone-doc_2012.1.1-4_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlA3GEUACgkQl4M9yZjvmkkFbACcCNhalyXErBZYKEz6xxWYotTL
abEAoNZUqzAiAFrX6D6v8C1Fm0VXcHJG
=jEpv
-----END PGP SIGNATURE-----
--- End Message ---
