Exploring the possibility of an l10n upload of debfoster to fix pending l10n bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Control: tag -1 patch
Dear Debian maintainer,
(“oh no, not another one”…)
The ddebfoster Debian package, which you are the maintainer of, has
pending bug reports which include translation updates or fixes
for translation handled by gettext, namely bug number 533502 (and
maybe other similar bugs, e.g. #672276).
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 a week) is roughly the following:
Sunday, July 29, 2012 : send this notice
Sunday, August 5, 2012 : post an NMU announcement to debian-i18n
with you (maintainer) CC'ed
Wednesday, August 15, 2012 : deadline for receiving translation
updates
Thursday, August 16, 2012 : build the package and upload it to
DELAYED/10-day, send the NMU patch to the BTS.
Sunday, August 26, 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)
iQIcBAEBCAAGBQJQFaHCAAoJELgqIXr9/gnyJkQP/3Pijs6qff6E58swy9NRey2y
jwbdYf4O+ucAPUCRNrXdFEKlyH+8wo4zirBxUavZ/I5IV2wqL2CEY+bWvnnvP9NU
15IwolqHy3lDZAAO2TsfiH4Bz43ibCe7rvO0G98Lbnb5+s0yupVBrHj63nRhhwXK
82+LkL9VLEe85xqN8467VhryR+WodOA1xXYkgmnpHwKVMG4OxvPZBtN/NapJmnf2
oT+/oxn9U6R/gIMhlsiojhN6XQg1WdkQokd7yLdB7EfYDEHuGM+cnoIJgILPqBJg
1+6V5NRnIwUMFCkcLN1VnqgOVJVCMNKmm8nnevc3mlfqcimFO9buXS10+QaB3ZKJ
ahi4/8kzw0xicX4ty7hTbezqVVAtdlmlDKHM2F5Gs0uHGA9s2m60BWImVI7lu9Mk
x7R7WlenFdJc5w9jojS62htyjLszsW1glRxiXNKUM8kPWRhTGtFnUXvixUKV9gYG
55X3Ox3t+xmOvR2Mt9EYMNprm9FiQxCEaXTm6mZ4UAGE06oUJGIix1BUQgFg1z9c
el6KNNhPn31OMrUu5Rp9tUa/vx7vpdBwoOobCM4TgmhNSTHhubaeUOtcF28SQepX
cSQUYB5NQ726OcN3ejWT4jg7i7EbcjzGJn4lGVxL8rBJahEqHdtL5Z5jvoZG401l
v8Fyy4wPd1/LepVd1r+6
=T3LL
-----END PGP SIGNATURE-----
Reply to: