Your message dated Sun, 18 Feb 2007 20:32:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#411340: fixed in apt-listchanges 2.72.3
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: apt-listchanges
Version: 2.72.2
Severity: minor
Tags: l10n patch

Hi,

Christian requested an translation update but seemed to ignore my mail.
This is not a problem for me, I know he has a lot to do, but I don't
want my changes lost ...

Christian, do you normally confirm such mails or could there be a problem
with your mail system?Maybe I'm blacklisted or something like this?

----- Forwarded message from Jens Seidel <[EMAIL PROTECTED]> -----

From: Jens Seidel <[EMAIL PROTECTED]>
Subject: Re: debconf PO translations for the package apt-listchanges
Date: Sun, 11 Feb 2007 19:14:56 +0100
To: Christian Perrier <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.13 (2006-08-11)

Hi Christian,

On Thu, Feb 08, 2007 at 04:17:15PM +0100, Christian Perrier wrote:
> Quoting Christian Perrier ([EMAIL PROTECTED]):
> > Dear Debian I18N people,
> > 
> > I would like to know if some of you would be interested in translating
> > apt-listchanges.

I attached patches against both de.po files from the latest package. It 
should apply fine.

Jens

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

I forgot to mention a really minor issue I found in po/*.po:                    
                                           
The space infront of "!" should be removed in "seems to be a directory !"    

Jens


--- End Message ---
--- Begin Message ---
Source: apt-listchanges
Source-Version: 2.72.3

We believe that the bug you reported is fixed in the latest version of
apt-listchanges, which is due to be installed in the Debian FTP archive:

apt-listchanges_2.72.3.dsc
  to pool/main/a/apt-listchanges/apt-listchanges_2.72.3.dsc
apt-listchanges_2.72.3.tar.gz
  to pool/main/a/apt-listchanges/apt-listchanges_2.72.3.tar.gz
apt-listchanges_2.72.3_all.deb
  to pool/main/a/apt-listchanges/apt-listchanges_2.72.3_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pierre Habouzit <[EMAIL PROTECTED]> (supplier of updated apt-listchanges 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 18 Feb 2007 21:18:02 +0100
Source: apt-listchanges
Binary: apt-listchanges
Architecture: source all
Version: 2.72.3
Distribution: unstable
Urgency: low
Maintainer: Pierre Habouzit <[EMAIL PROTECTED]>
Changed-By: Pierre Habouzit <[EMAIL PROTECTED]>
Description: 
 apt-listchanges - Display change history from .deb archives
Closes: 410544 411340
Changes: 
 apt-listchanges (2.72.3) unstable; urgency=low
 .
   * Big l10n upload, thanks to many contributors, especially Christian
     Perrier, Frans Pop and Jens Seidel. (Closes: 411340, 410544).
   * preinst: rm -f ... || true is useless.
Files: 
 bec9a6023d83f8483ce5ccbf2d6cd2aa 655 utils optional apt-listchanges_2.72.3.dsc
 0be29e0f14afe2905954e7d3f73c5856 84528 utils optional 
apt-listchanges_2.72.3.tar.gz
 6ef77b4ffb043724ca61900e41473f21 64880 utils optional 
apt-listchanges_2.72.3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF2LYXvGr7W6HudhwRAj8pAJ443f3Gjpoc4vz9yL63ls3XgQ5ZWwCggeGU
dgJlB4VjrtJ8dJszIiBSPAs=
=5Hg0
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to