(forw) Intent to NMU lvm2 to fix pending po-debconf l10n bugs

Christian Perrier bubulle at debian.org
Tue Oct 10 05:44:15 UTC 2006

Sorry for the double mail.

After a deeper analysis, it turns out that the debconf note you're
using is meant to be used in a very identified case. Moreover, you use
"critical" priority but take care to display the note only when
desperately needed.

Therefore, it is not to be removed, imho, BUT turned into an "error"
template (which debconf will *always* take care to display contrary to
note templates.

My NMU proposal still stands, but for fixing the pending l10n updates.

Without answer, I intend to do it tomorrow.

----- Forwarded message from Christian Perrier <bubulle at debian.org> -----

Date: Wed, 4 Oct 2006 22:35:04 +0200
From: Christian Perrier <bubulle at debian.org>
To: lvm2 at packages.debian.org
Subject: Intent to NMU lvm2 to fix pending po-debconf l10n bugs

Dear Debian maintainer,

The lvm2 Debian package, which you are the maintainer of, has
longstanding bug report(s) which include translation updates or fixes
for po-debconf.  At least one of these is older than 100 days, namely
bug number 312626.

Often, but not always, this means that the package is not very actively
maintained. I'm sending you this mail in order to check the situation and
determine the next necessary steps. If there is any reason for which you
haven't fixed the bug yet, or there's anything else you might want to tell
me, I will be very happy about any feedback. If so, please accept my

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 lvm2 in order to fix this as well as all pending translations
for the debconf templates.

Such changes are always harmless, which explains why I safely consider
building NMU's for such issues even though they're obviously non critical.

However, letting l10n-related 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.

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 7 days) is roughly the following:

 04 oct 2006   : send this notice
 11 oct 2006   : post a NMU announcement to debian-i18n with you
                 (maintainer) CC'ed
 18 oct 2006   : deadline for receiving translation updates
 20 oct 2006   : build the package and upload it to DELAYED/2-day
                 send the NMU patch to the BTS
 22 oct 2006   : NMU uploaded to incoming
 23 oct 2006   : NMU enters unstable

The patch for the NMU will then be sent to the oldest bug report with
a pending po-debconf translation.

I will then subscribe to the Package Tracking System for lvm2 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.


----- End forwarded message -----


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20061010/f2601d98/attachment.pgp

More information about the pkg-lvm-maintainers mailing list