Exploring the possibility of an l10n upload of libpam-rsa to fix pending po-debconf l10n bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Debian maintainer,
(“oh no, not another one”…)
The libpam-rsa Debian package, which you are the maintainer of, has
pending bug reports which include translation updates or fixes for
po-debconf, namely bug number 685428 (and maybe other similar bugs like
####).
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:
Monday, August 20, 2012 : send this notice
Thursday, August 23, 2012 : post an NMU announcement to debian-i18n
with you (maintainer) CC'ed
Tuesday, August 28, 2012 : deadline for receiving translation
updates
Wednesday, August 29, 2012 : build the package and upload it to
DELAYED/2-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)
iQIcBAEBCAAGBQJQMpraAAoJELgqIXr9/gnyZ4IP/2D9vMgAL7onYjeEuf/iCDAT
+Kduxo/TdZW+FRbc/NFwFwrUVkg1D7YhOKk3gim6pRVnVoZr7n/fRk87HLIELNxj
HxQUhNu9nKX+QgOn1QanOyRIJMpPgc7olRu0TDwLk045wFC2EYSIEgYOBB3Ua2Rg
8/nmOiDGBMDrkNM7P6iHX7JGreL2vbjmN/pdcmgAZ83MLt5Kt5gRoGVBXTeruEe7
KLeRjjEpCgctLCCanZiApFE3WGRYDVqQ4LfUlDPx1AL20yqKNrLawcuPxlV5dst/
6RhPpM9yvPKB2glJzXSxetu9o++o/Av/2mDjpllfErtSqcKkXqD7KmV0cnRYdUta
Zjlwpnlpa8mVyD7gBUH+VAEqxsXW6GO+5atulPJ/AQ/vl2Kbt+LX2rjV6cX1JhrS
3Qcmm6gRhrsFBV1SgKC6crv0bICX/Ub9xzG+OFfggiJQN7NSRIMMZfbj/5LawAEv
o+FgZLMycFmePMeySIaZc+qtMLYD26bjMYq/rTxj6jb3BINsTZVE99ucgs1/TkbO
KEgKfXFB/i/hdlXbpssPC9oRRZNmm8OSkEm5De29DxcP8B10aA5gDbT6TP7Dp2GS
qSRc0CNfbH85NqOGU3vx3UJcbb0SjJYv+LeLfzsYjER7+UvkuF9a8m/juK/cGTEO
OJx3fagPGirdROBQ9/Rb
=u0WL
-----END PGP SIGNATURE-----
Reply to: