Exploring the possibility of an l10n upload of adduser to fix pending documentation l10n bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Debian maintainer,
(“oh no, not another one”…)
The adduser Debian package, which you are the maintainer of, has
pending bug reports which include translation updates or fixes
for documentation handled by po4a, namely bug number 670579 (and
maybe other similar bugs).
Please note that I've asked to join your Alioth project in order to
commit directly those l10n stuff (in order to avoid getting them
discarded like in the last MU), and would be happy to continue handling
them in the future.
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:
Thursday, April 26, 2012 : send this notice
Thursday, May 03, 2012 : post an NMU announcement to debian-i18n
with you (maintainer) CC'ed
Sunday, May 13, 2012 : deadline for receiving translation
updates
Monday, May 14, 2012 : build the package and upload it to
DELAYED/15-day, send the NMU patch to the BTS.
Tuesday, May 29, 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)
iQIcBAEBCAAGBQJPmbtDAAoJELgqIXr9/gny0noQAKpA5zzp8VrVDgfTzstl3ol2
N4bFUGGQvFyEnDdVarbKM5oJ/zieRBGh+utvuTXZaMcYeUxjVtHrYNTNvEp9rc13
QvPDYfZwwkh0Jd9qi/4NsGulhtmyr7adgI+jSfR+DWJv6CRTpcPGCjvqKp3d37SQ
idxukvffBRXNgEtNlU9dL13IqCIF4LyaEbDGPxespxW6+/7gQhKERzxrGoObjxys
ld1aWL2LV59rihtFTaxgaSUYTLYFldXwWEvrM4xktqnFIkbWw/d2d+Xh7jd1cCu9
AHUP+ttkyRrNNkruNTVIEP4pUUnrhDiQfoDGvlvTdbT/x21ohGnLQNAF5vitw0zf
Q10bHkSi+wrUr8C7/gg3iyKz2CM5m1zixlk+XQbbwpHG6QBx9j23hMK1om0vKWwi
lmRW5r95kTIuvdQFqSjXnyongEEUU0RwLjwrxw3yPV+xZQZHOyNwF3Gk4duUfK6Q
l2hCyPXilE0hG3mCFifo3Q7h8gxFBXqRjUdytl4eYLAwM0bywoiE+QSqt/kqPNvo
ZqAZL+tOHSfSL5AWPanNwJsLOBQ8dgXA2IBQoWs1yYyd+G5cUNIBFX+HE6a3BvRX
XxhEhTMVwZbJS3hHCbu+Ylv1jXyUl+OBtbYVMqdmk3g0dBldA7Ym0TpOCLGSfupD
u23eqBbw9/dWXXdyW1d2
=Hrxr
-----END PGP SIGNATURE-----
Reply to: