Your message dated Wed, 10 Jul 2013 15:33:44 +0000
with message-id <[email protected]>
and subject line Bug#708660: fixed in keystone 2013.1.2-3
has caused the Debian Bug report #708660,
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.)
--
708660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708660
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: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.8-1-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: 2013.1.2-3
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: Wed, 10 Jul 2013 23:10:57 +0800
Source: keystone
Binary: python-keystone keystone keystone-doc
Architecture: source all
Version: 2013.1.2-3
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: 708660
Changes:
keystone (2013.1.2-3) unstable; urgency=low
.
* Updated keystone templates after the debian-l10n-english. A big thanks to
them for their huge work (Closes: #708660).
Checksums-Sha1:
bc4705c02f1f811029dc567c0f974c77b3811ece 2304 keystone_2013.1.2-3.dsc
22f479d33eda4bc9ce000f18d15636c45cadd152 244275
keystone_2013.1.2-3.debian.tar.gz
18eed4ef410ab4cc31cdd47cd59c60f950724c98 337418
python-keystone_2013.1.2-3_all.deb
437a4a79f031f7aac96e3ad545f5f64cbe8ee755 242480 keystone_2013.1.2-3_all.deb
997ecbf543989970c9d54c95900bbc02769762db 522824 keystone-doc_2013.1.2-3_all.deb
Checksums-Sha256:
6684b284535c236e78cd0b889061825f1e8eca74af410b7dff47da68c7a5767d 2304
keystone_2013.1.2-3.dsc
dcc317c515851454bea14a335afed59617b6598d861eed89b4fc0a9fa9b4c147 244275
keystone_2013.1.2-3.debian.tar.gz
1d92eb3095f7df7a51fe74aef296c5af91031016aa5b88d899687102ecc6a9b0 337418
python-keystone_2013.1.2-3_all.deb
04f256a996a0e46cc53160a5fc57f1e0e5435fb5ebd353366a4292fadef8e272 242480
keystone_2013.1.2-3_all.deb
d89c7e84f1018a1af4b87878d836155688b3136c198c08daba4cd075f8be97f9 522824
keystone-doc_2013.1.2-3_all.deb
Files:
9715ea47ec0368f356726e9715ed2dc3 2304 net extra keystone_2013.1.2-3.dsc
6565ece1e16464d743fd51016f0b4766 244275 net extra
keystone_2013.1.2-3.debian.tar.gz
4ec125b867a0951bcd30bdfd4d7df752 337418 python extra
python-keystone_2013.1.2-3_all.deb
ba9008394236c4d350376d4406c4e82e 242480 python extra
keystone_2013.1.2-3_all.deb
35983d5beaa9af8640110f19d85801c1 522824 doc extra
keystone-doc_2013.1.2-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlHdfUYACgkQl4M9yZjvmkm0FACffRzTD8v+vru1I9TEvDX+e+XD
rekAoJSRFwA+ToQjmmSiH7WdbK+NES8A
=vLas
-----END PGP SIGNATURE-----
--- End Message ---
