Your message dated Sun, 29 Jul 2012 15:02:17 +0000
with message-id <[email protected]>
and subject line Bug#679295: fixed in keystone 2012.1.1-2
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-2
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: Thu, 19 Jul 2012 06:21:30 +0000
Source: keystone
Binary: python-keystone keystone keystone-doc
Architecture: source all
Version: 2012.1.1-2
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 680082 680847 681003 681249 682784
Changes:
keystone (2012.1.1-2) unstable; urgency=low
.
* Debconf templates and debian/control reviewed by the debian-l10n-
english team as part of the Smith review project. Closes: #679295
* [Debconf translation updates]
* Recycle translations from nova for several languages. Additionnally:
* Danish (Joe Hansen). Closes: #680082
* Swedish (Martin Bagge / brother). Closes: #680847
* Spanish; (SM Baby Siabef). Closes: #681003
* Italian (Beatrice Torracca). Closes: #681249
* Slovak (Ivan Masár). Closes: #682784
* Fixed the get-vcs-source target in debian/rules.
Checksums-Sha1:
8d0e205da0ef92cc5fa84c1429a776f4cbcb611c 1898 keystone_2012.1.1-2.dsc
5d3767972d97ee892ec33eac67981d6d0eeb6e5c 17524
keystone_2012.1.1-2.debian.tar.gz
91af51a03b8f06d1cf51311c749cce3e0b975018 91288
python-keystone_2012.1.1-2_all.deb
89c513f9944dc0cbc5d193144a2856586d7a6a68 13812 keystone_2012.1.1-2_all.deb
d036759763ea2e1f2ffdbce6123ea69fc4551cff 237516 keystone-doc_2012.1.1-2_all.deb
Checksums-Sha256:
0ad28369e90d4cbe83925b7b5e37d3fb38feb79e719b72e351469b4759f3947d 1898
keystone_2012.1.1-2.dsc
ad25403be26d0739d4c2f75d434c863339b40b4601276c67d8dbb77eef82c0d0 17524
keystone_2012.1.1-2.debian.tar.gz
32607e1c2ef7a868df765fcd25ef3ea1343f52e68abc6b03a59048891762ee0e 91288
python-keystone_2012.1.1-2_all.deb
07a90c15f6ce18d060bcbc0e045f74bcc644f5b3cce879d96595be3e220762af 13812
keystone_2012.1.1-2_all.deb
8a6a50bd3c1dbf6deb4d2438741dbc99e8c071748c0087133531af8e5f4e28ac 237516
keystone-doc_2012.1.1-2_all.deb
Files:
a1cf58a8f2b2b0262aaabd426422174f 1898 net extra keystone_2012.1.1-2.dsc
67c23cebe34d9c7bd8d7ba3cb72782d0 17524 net extra
keystone_2012.1.1-2.debian.tar.gz
c8d9e8ff9d614a6417e5b418df45e86a 91288 python extra
python-keystone_2012.1.1-2_all.deb
ecc00ab0bd4dd056d6fe4601f083aeed 13812 python extra keystone_2012.1.1-2_all.deb
b6985fbb897ff4781d7a912ee70dd994 237516 doc extra
keystone-doc_2012.1.1-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlAVUF4ACgkQl4M9yZjvmknSlACbBWf3DFjDQDUk1PegXINWa4BV
8LAAoMMMs/oSOg7gUPWzbPB+73f+AZ1J
=ncMx
-----END PGP SIGNATURE-----
--- End Message ---
