[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Intent to NMU openssl to fix pending po-debconf l10n bugs

Dear Debian maintainer,

The openssl Debian package, which you are the maintainer of, has
pending bug report(s) which include translation updates or fixes
for po-debconf, namely bug number 461597 (and maybe other similar bugs).

Even if we're still far from the release of the next Debian version,
letting such bugs sleep in the BTS  is simply lowering
the chances that your package interaction with its users may be done
in something else than the English language. It is also not
encouraging for translators.

I have the intention, as part of a more general action of the Debian
i18n Task Force to build and possibly upload a non-maintainer upload
for openssl in order to fix this as well as all pending translations
for the 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 14 days) is roughly the following:

 Wednesday, May 07, 2008   : send this notice
 Wednesday, May 21, 2008       : post a NMU announcement to debian-i18n with you
                 (maintainer) CC'ed
 Saturday, May 31, 2008       : deadline for receiving translation updates
 Sunday, June 01, 2008       : build the package and upload it to DELAYED/2-day
                 send the NMU patch to the BTS
 Tuesday, June 03, 2008       : NMU reaches incoming

If you intent to upload yourself, please notify me so that I interrupt
the process on my side.

In case I upload an NMU, I will subscribe to the Package Tracking System for
openssl 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

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.


Attachment: signature.asc
Description: Digital signature

Reply to: