Sorry for using the list for that, but jfs@computer.org which is the
address quite widely used by Javier definitely seems to have serious
problems.
Javier, I was trying to warn you about the possible NMU of one of your
packages.
----- Forwarded message from Mail Delivery System <MAILER-DAEMON@puccini.debian.org> -----
Date: Tue, 21 Nov 2006 22:23:42 +0000 (UTC)
From: Mail Delivery System <MAILER-DAEMON@puccini.debian.org>
Subject: Undelivered Mail Returned to Sender
To: bubulle@kheops.frmug.org
X-CRM114-Status: UNSURE (1.7900) This message is 'unsure'; please train it!
Content-Description: Notification
This is the Postfix program at host puccini.debian.org.
I'm sorry to have to inform you that your message could not be
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to <postmaster>
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The Postfix program
<jfs@computer.org> (expanded from <checksecurity@packages.debian.org>):
delivery temporarily suspended: connect to lemroh.ieee.org[140.98.193.30]:
Connection refused
Content-Description: Delivery report
Reporting-MTA: dns; puccini.debian.org
X-Postfix-Queue-ID: 48862800210
X-Postfix-Sender: rfc822; bubulle@kheops.frmug.org
Arrival-Date: Thu, 16 Nov 2006 21:17:49 +0000 (UTC)
Final-Recipient: rfc822; jfs@computer.org
Original-Recipient: rfc822; checksecurity@packages.debian.org
Action: failed
Status: 4.0.0
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to
lemroh.ieee.org[140.98.193.30]: Connection refused
Content-Description: Undelivered Message
Date: Thu, 16 Nov 2006 20:21:03 +0100
From: Christian Perrier <bubulle@debian.org>
To: checksecurity@packages.qa.debian.org, checksecurity@packages.debian.org
Subject: Intent to NMU checksecurity to fix pending po-debconf l10n bugs
Dear Debian maintainer,
The checksecurity 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 331305 (it is pretty likely that several other translation
bug reports are pending).
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
apologies.
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 checksecurity in order to fix this as well as all pending translations
for the debconf templates.
The coordination page of this action can be seen at
http://people.debian.org/~lwall/i18n/
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:
16 nov 2006 : send this notice
23 nov 2006 : post a NMU announcement to debian-i18n with you
(maintainer) CC'ed
30 nov 2006 : deadline for receiving translation updates
02 déc 2006 : build the package and upload it to DELAYED/2-day
send the NMU patch to the BTS
04 déc 2006 : NMU uploaded to incoming
05 déc 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 checksecurity 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.
--
----- End forwarded message -----
--
Attachment:
signature.asc
Description: Digital signature