Exploring the possibility of an l10n upload of xfsdump to fix pending l10n bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Debian maintainer,
(“oh no, not another one”…)
The xfsdump 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 576257 (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 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)
iQIcBAEBCAAGBQJQFaEBAAoJELgqIXr9/gnyrzUQAIArdROkfYXvbDbnF5FzGkFG
atq30R7zZbX2saQD1wH6+GWa6DxIqPU5sIdLBQoObbu+HFvlP/h3LKmDNFomaF0R
6k3kILN4QlxmuloFMpsRpvDUT4lbN5hz3/tvVWCPDbeC4CWYtVM4MJ6hVNLW78DI
BU9ha2McgTlltQQ6+TKlWfLRp/jMsaswslCPYZQcZS7Lj9idkdqbnhkgvcy7eNLl
6T8qEfJh8+ktFAQ7kNGAfRbCJmo7yHWosQlO1h/ppR6ijeSlWU1gLpiBJJg5UD5B
Hb1NytKcSui3C06HYThVQVA4Z3LCxdXSIq44MhuojhWM3CqBjb5M6gvUrY/cX6SD
XtemI37U6xGZ/uX8UeF+o69XSpd/A1PubDQh+qGgYmp0i20ZdwxVIh3G+OP5Nyyp
ZCbrVP+qzugqUV0QiVzUHibKmK8leWXEkZY5M9fvQLlDdRomaD0rOLgxdLLbXmaK
1ZmfSzlMKeS+SUt3g6aphLOMqJ8FGrlyeixJum6JOuSnCFZccG6WFGTGjgIh4r37
HlQH3mHl/7yJYDrFmXI0W/oBxawKnq7g0gyi9ZBWtIKJo4TJSgxXj0LGqpo8vk5S
27GY3M79rvs36/W9hcBKHkwoRVRiTI/Bb5xgV6cGZIGvN/G3HOzrHrSV/YLhRSyI
efxQRIEXUx7TAhjFhblB
=Ev2E
-----END PGP SIGNATURE-----
Reply to: