Exploring the possibility of an l10n upload of sn to fix pending po-debconf l10n bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Debian maintainer,
(“oh no, not another one”…)
The sn Debian package, which you are the maintainer of, has pending bug
reports which include translation updates or fixes for po-debconf,
namely bug number 656735 (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:
Sunday, August 19, 2012 : send this notice
Wedesday, August 22, 2012 : post an NMU announcement to debian-i18n
with you (maintainer) CC'ed
Monday, August 27, 2012 : deadline for receiving translation
updates
Tuesday, August 28, 2012 : build the package and upload it to
DELAYED/3-day, send the NMU patch to the BTS.
Thursday, 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)
iQIcBAEBCAAGBQJQMPyDAAoJELgqIXr9/gnywIcQAI1uR89Cn9AmyN1YN8OQAjep
18TTd51tiPa8HyHcGjq2obgc1OPPXKRStWbvvTCPQj9kkoupH3g3wE2O5ODPeIKG
y0axMW9UvE9I510Mg3lKQCgJu38ZsjAL/w6YEiI8tCK0tRlbEqS0eLtI5q5VNhi9
NejSoWU0ze3JO0+facJNWNk2kJVCu7K/giD9Mch4f5C3sjBqpU2rhl9N4Fehn5n7
GdK6RVfPf8P8kGtCFKnnqqALbcSh53M+OISyXSdbAk72FIcf4Sd+Kd45QgMOZtTz
I48pVH+VVEIiP0+Vdklt0WFlEk1E0cJ/DyJb5sQHeR/pcaZRJokrDxykj1oeBhC5
XCyNQbzF01WCqDtcJ0XDZKPbFUYbli5zMLvaoMEzlVGNu1gKDy4XWWs0eDZzKV4y
moNP2I+FiGzdPsN2+kpK7+pe1s2kk3CX6/Vfh8XZgsmZuAmpjvhVbUkh5tayDP7b
1AZv5WYcveaFGXl/w0qF0Mh2Tc+lCicvI/Oxk1YR9o9PHnopteSXtgxPfknc9+Sy
KKeSLQDzjbgvmDUb2TSRKWepclZJ/rK+zVGOA8rsUNOqclp8OOmIKf0p9WPfvkro
zgZZG7UNvDIz46O7jT4Go++S3oPFnHka6GsMhodBE70cI2z7qY7RxkN+qxeXpva0
gknOfUwam5pBGHVuY1yl
=aGb1
-----END PGP SIGNATURE-----
Reply to: