Your message dated Sat, 21 Nov 2015 06:19:14 +0000
with message-id <[email protected]>
and subject line Bug#796234: fixed in xringd 1.20-27
has caused the Debian Bug report #796234,
regarding xringd: [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.)
--
796234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796234
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xringd
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: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: xringd
Source-Version: 1.20-27
We believe that the bug you reported is fixed in the latest version of
xringd, 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.
Steve Kowalik <[email protected]> (supplier of updated xringd 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: SHA256
Format: 1.8
Date: Sat, 21 Nov 2015 17:08:38 +1100
Source: xringd
Binary: xringd
Architecture: amd64 source
Version: 1.20-27
Distribution: unstable
Urgency: low
Maintainer: Steve Kowalik <[email protected]>
Changed-By: Steve Kowalik <[email protected]>
Closes: 796234 798378 800395 800461 801187 801243 801387 801393 801450 801454
801635 801639
Description:
xringd - extended ring daemon - monitor phone rings and take action
Changes:
xringd (1.20-27) unstable; urgency=low
.
* Remove /etc/xringd.conf.bak on purge. (Closes: #798378)
* Debconf templates and debian/control reviewed by the debian-l10n-
english team as part of the Smith review project. Closes: #796234
* [Debconf translation updates]
- Danish (Joe Hansen). Closes: #800395
- Russian (Yuri Kozlov). Closes: #800461
- Brazilian Portuguese (Adriano Rafael Gomes). Closes: #801187
- German (Mario Blättermann). Closes: #801243
- Dutch; (Frans Spiesschaert). Closes: #801387
- Spanish; (Camaleón). Closes: #801393
- Italian (Beatrice Torracca). Closes: #801450
- Czech (Miroslav Kure). Closes: #801454
- Portuguese (Miguel Figueiredo). Closes: #801635
- French (Jean-Pierre Giraud). Closes: #801639
Checksums-Sha1:
2ff618846501513ce89f8b525c57e33c3e1a0d17 1610 xringd_1.20-27.dsc
17bf542d86bff74611d8226f490bf0083af46ec2 12581 xringd_1.20-27.diff.gz
dc1a2cdbd9c162ac38bb730faf36d8457743e96c 23338 xringd_1.20-27_amd64.deb
Checksums-Sha256:
5d052bd5971e67da87561d7c474b18f17fb3d65b072804ab1d2b5a5ada52083e 1610
xringd_1.20-27.dsc
e3ea5208e1372e96992aa32563217a0cf2c39f3d439e295b3208e391f3fb48dc 12581
xringd_1.20-27.diff.gz
f35130b2491673c87ebea3b66bc37db1cd2779fb47a6b018545cf985ca005071 23338
xringd_1.20-27_amd64.deb
Files:
4190966207464c77ac187460acba7a61 1610 comm extra xringd_1.20-27.dsc
f7db0025caa47aa56b516dcda5428f96 12581 comm extra xringd_1.20-27.diff.gz
c8f9251d8936be3ad1bbcd6a4d049634 23338 comm extra xringd_1.20-27_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWUAvjAAoJEP3WO69YilU/lcAP/38pGZq7tBg0dXsOzBB/1uwb
leNBFvua0GQPSjt+FOL5iJC2z/Z6+9NLxzmCZbLZwBjZWwNjIbY5fTEBdm61kXfp
l5/YwQjHvCBfwUXLT9Aq8Qy2UIqeXfpjm/iO7p5jyVW3FyVrrOjICPACKdRrwv80
0hgewShZFKhoard+u0RLFgHsSNsdnUwR8UHkQc/ZRnvgD+TZGXt3w7X/pKr7asos
QFSbh9PgZbDYhTWh5jP31AMgiaP0/GLNXIykS0A4LBABVxzPbFxmvRhi7GZZfAXT
1SWJrUru/Xu/P+m3UvCe/w0ghe5vz1evjjzH1PcPHHIyueDgirIPfcTROBDF4KOZ
H1Zswc/cePy5sbNoZma95GUhX9AjPP9lSJOAVLDKEgdObpz/3NpCwh/wVp0p76of
6eKhQH6hW+OL/lYStxTqwT+fv8RONznDb0X7XJhUVCalaC9hSgzt0EvUjq3z1Nfn
5Un41/jrCrBqYn/4LepR7mjMMW0hSA0qJuwP8wDKrY4CNNFztpKdX8U2Y5TJsXim
iLjuqemm/FpqpRU9wc6EslTQ7+yIC4Hh8d92MlHit3GjRozNmToUg/12MDyxVT9h
dPMejfZkf76GmfcmTeC7/hxyioPGijTJeZbjwYmlboPjcdrFrba6JZF/uC4iKULp
4F2c5jBSvp4EI1jelCTt
=rNni
-----END PGP SIGNATURE-----
--- End Message ---
