Exploring the possibility of an l10n upload of python-apt to fix pending l10n bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Debian maintainer,
(“oh no, not another one”…)
The python-apt 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 567765 (and
maybe other similar bugs like 652335).
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, June 3, 2012 : send this notice
Sunday, June 10, 2012 : post an NMU announcement to debian-i18n
with you (maintainer) CC'ed
Wednesday, June 20, 2012 : deadline for receiving translation
updates
Thursday, June 21, 2012 : build the package and upload it to
DELAYED/15-day, send the NMU patch to the BTS.
Friday, July 6, 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)
iQIcBAEBCAAGBQJPzAclAAoJELgqIXr9/gnyCEwP/2dGjo8H4ygtqZCLOZmx5RZm
gvwLqCMtilPXj3v3ljI+U0t5uW7XnrKKwvA9P3gwr+OHTOgB0adeDOtqW6SSL7uS
Ure0VF8Qx4vOR83lg/O9vWZsBek4yca1NCuLaOXNVCAZA121pU+4NExGbwDdQdvs
HoZsiQcAAEmgsDmF/CP4xdeh7JhJgF4IEEKzueevc4iKyL2ujbb15EA8ny3DS3S+
vsz7oXHmCX+nByAy+GCczIYqcCU6Jdh07L1u5ViQEMerkWJY1GAr9MbLtUfGj7cj
x/1mLG/KiKu8Mz4oJjZiKhFCTnHlkI/GFgLItTqLQ6Jmz9tk3r6ECBNfk+VI5exf
7ELgIbGwI0ld816z2f46TePGee4aqwd/6TyRW+hd00+lKB2KYGwl6L3m7l4yJ5+I
92kqSq/tcQSIw7S4W3dQRk4UpRwNwnBR11PmWU+7oH+q3PJmeRPQz2uAlsKCT9yu
UHGqNk5YCb9UMMWa77DFTRJn37g/hZcd5/TTbQDw6O2NlvUO182qwP5h9mzF1dPy
ITuikMw5MKIfGC4xbVuaMsyd9tmSWA9edmH5SR2sU/v7E0fDr/UEvadEAz3vrlBb
V6XnP4IeBE+vYcRvdXzyJVgu0DhLxXcQKl7kQz3nNtd13N6TDCYMESNuwFLXlCLr
dr8RDudQDBc3CP2xirnM
=VtzW
-----END PGP SIGNATURE-----
Reply to: