Exploring the possibility of an l10n upload of mercurial-server to fix pending po-debconf l10n bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Debian maintainer,
(“oh no, not another one”…)
The mercurial-server Debian package, which you are the maintainer of,
has pending bug reports which include translation updates or fixes for
po-debconf, namely bug number 658943 (and maybe other similar bugs like
#675317).
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:
Friday, August 17, 2012 : send this notice
Monday, August 20, 2012 : post an NMU announcement to debian-i18n
with you (maintainer) CC'ed
Saturday, August 25, 2012 : deadline for receiving translation
updates
Sunday, August 26, 2012 : build the package and upload it to
DELAYED/4-day, send the NMU patch to the BTS.
Thursday, August 30, 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)
iQIcBAEBCAAGBQJQLn2VAAoJELgqIXr9/gnyMCkQAJiOdh+itAygKVm1ubp4u8SD
ZuSFcUjLI5mgSLZlszjwIcrFkLufU33TVr6up0bFh3RzEU0JrA05Z2PuhNaPVQMY
qMxa6Bsz5cwXQqRPHpfwWnGLSl/HPp/BnZqbMPBsfn6GVEfZ18j8bX0oQiHI66oT
SXvvCspGwdTobFveV6B2ClXp+8M5VmLMsItgfDdsLN8b9w9cf4BPVN8j0RtR9J+w
tYrL6u91Gret2qemMMXHgzOeNMdWdbNjQfkLyjpzMwVT6AReyyjys526lynRd/HY
66cFdmXc0+/fN+LwI/DDAEgbOLeUpSDC8fR2bX8LncnG4QjApk0IWFz3WFTwCPxp
HFZlWi81rnE1dlPFn/4vpDojdHyfcFNRkMjliwAsIcZrDs5o8SI5SVYCQJI54AgX
PKwWEz7JTfoRzqLdObSF+Cf81aljoPySUnHKUfBVIAwJZikxQVxeayySJ86kffv8
cSSpVKeQbqxzJWg4B8inpGrq3lXePORfiVQ3uaIm7CU1hW7hbzCmFo5ALfecBHv5
Pa12EWWxKWd/JnidRIVxKjGXfrhPeZzDLFYHDr+W9srJwKm002hWkkhihJCkRKRe
g+ufMCFgnEf1aHsmXboy5sBNhVC41kw0OWntG29aWBTs1bYrdd77503omJEbadAJ
mv7Nrn/v1WxPDUSCJrK/
=B37E
-----END PGP SIGNATURE-----
Reply to: