Exploring the possibility of an l10n upload of gnarwl to fix pending po-debconf l10n bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Debian maintainer,
(“oh no, not another one”…)
The gnarwl Debian package, which you are the maintainer of, has pending
bug reports which include translation updates or fixes for po-debconf,
namely bug number 659777 (and maybe other similar bugs).
The i18n team is now hunting the very last bits of missing localization
and your package went on our radar. You may have uploaded recently but,
unfortunately for you, you then got *another* l10n bug report. We
really should prevent translators from translating...:-)
So, sorry for this, but the radar beeped at your package and here am I
with an NMU intent...:-)
In case you can't update your package, I hereby propose, as part of
a more general action of the Debian i18n Task Force to build and
possibly upload a non-maintainer upload for this package in order to
fix this as well as all pending translations for the documentation
and debconf templates.
Of course, an upload made by you would even be better...:-)
Such changes are always harmless, which explains why I safely consider
building NMU's for such issues even though they're obviously non critical.
The schedule for the NMU (in case it happens, that is if you agree with
it or if I don't receive any answer in 3 days) is roughly the following:
Saturday, August 18, 2012 : send this notice
Tuesday, August 21, 2012 : post an NMU announcement to debian-i18n
with you (maintainer) CC'ed
Sunday, August 26, 2012 : deadline for receiving translation
updates
Monday, August 27, 2012 : build the package and upload it to
DELAYED/4-day, send the NMU patch to the BTS.
Wednesday, August 31, 2012 : NMU reaches incoming
If you intent to upload yourself, please discuss with me. I propose
handling a translation update round and I can handle it myself for you.
That will just require a few days.
In case I upload an NMU, I will subscribe to the Package Tracking System
for this package and follow its life for 60 days after my NMU in order
to fix any issue potentially introduced by my upload.
Let me know, as soon as possible, if you have any kind of objection to
this process.
If you'd rather do the fix yourself, I will of course leave the package
alone. Same if you have reasons not to do the update now.
Regards
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJQL+NuAAoJELgqIXr9/gnyqKgQAIuYEjKJyWlon/a8I+zLfGzl
aSJunEmomwX9S7hm40+uiTO7PtHVLk2Pgyp2ph3MLYSg4DtZHLjlc/Ywc1eEq4B6
q2uwFVyu27PWU7BRe6gNlEtXjPRkyW6aJJnc1X+EDU8tHu/nzgJuLtrao6aEZIkH
8a/fBkclNcxHcutnrY1woI1qj8d0cJMq2TtuJuSr1uWatUPizRIcp1tubry3A1Ca
/8VIuxaUPCKEnP0iI7PoNIY4fJtHwAcg5vec8gGrKcjA8z4uDJloVsDjyx5E9De8
wwo89/I0qCxp0W7saZ2ni5TEXr3tuBuu1v2i559kOVT+6PC1c+Xg3j7k5cZIERhW
VsbZjAu9KUTVVxnOoPnNiMBymL7mFec2zeQu26X7ipFSGuSHM/lGyRwQOEikTAiO
0u/HJa3bJwLtJI0T0EET7nIg5Tqas0YTvqm0kCftsYN4golnetxswP1CUBPNyu4m
L5nu4aFeuZsZ3Nx3MkaJ5Xx6SM3ezJgF3lry3X0cRa+ssEykz0lHbbtol4WvVDAq
1htkX225KrGF3CfAYpm62j0+YeGgTVcC05QYqwSjufGkcWqm88wfaJG6fAluoRNg
fpAAezg0H/pz3sJOsXQJmYacZnB1cuGe7RPtG4IZA9FoaKWPd0V91vywuc3Ktses
nnxnJ5JCB3dp+gsV5B9M
=VUO7
-----END PGP SIGNATURE-----
Reply to: