Your message dated Mon, 21 Aug 2006 06:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#383159: fixed in mail-notification 3.0.dfsg.1-4
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: mail-notification
Severity: important


 Hello,

 Recently gmime2.2 pakage has been uploaded. It includes some upstream bug 
 fixes and packaging fixes to comply with Debian policy. Your package 
 depends on now old and deperecated gmime2.1, which has to be removed
 from the archive.
 Please, make a new upload of your package with libgmime-2.0-2-dev as
 the Build Dependency instead of libgmime2.1-dev

 Thanks

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8)


--- End Message ---
--- Begin Message ---
Source: mail-notification
Source-Version: 3.0.dfsg.1-4

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

mail-notification-evolution_3.0.dfsg.1-4_amd64.deb
  to 
pool/main/m/mail-notification/mail-notification-evolution_3.0.dfsg.1-4_amd64.deb
mail-notification_3.0.dfsg.1-4.diff.gz
  to pool/main/m/mail-notification/mail-notification_3.0.dfsg.1-4.diff.gz
mail-notification_3.0.dfsg.1-4.dsc
  to pool/main/m/mail-notification/mail-notification_3.0.dfsg.1-4.dsc
mail-notification_3.0.dfsg.1-4_amd64.deb
  to pool/main/m/mail-notification/mail-notification_3.0.dfsg.1-4_amd64.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.
Pascal Giard <[EMAIL PROTECTED]> (supplier of updated mail-notification 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: Mon, 21 Aug 2006 08:31:21 -0400
Source: mail-notification
Binary: mail-notification mail-notification-evolution
Architecture: source amd64
Version: 3.0.dfsg.1-4
Distribution: unstable
Urgency: low
Maintainer: Pascal Giard <[EMAIL PROTECTED]>
Changed-By: Pascal Giard <[EMAIL PROTECTED]>
Description: 
 mail-notification - mail notification in system tray
 mail-notification-evolution - evolution support for mail notification
Closes: 383159
Changes: 
 mail-notification (3.0.dfsg.1-4) unstable; urgency=low
 .
   * [debian/control]:
     - Added mail-notification-evolution to Suggests.
     - Build-Depends on libgmime-2.0-2-dev (>=2.2.3) instead of 2.1
       (closes: #383159).
     - Removed duplicate Depends on evolution.
Files: 
 23cc6e8f05d10c05e8280f5ecb7063f8 917 gnome optional 
mail-notification_3.0.dfsg.1-4.dsc
 02edb437ef3da5fbcf02419aa3ca6272 7819 gnome optional 
mail-notification_3.0.dfsg.1-4.diff.gz
 878ab12bb3d479b8b92f02773bdffd72 347004 gnome optional 
mail-notification_3.0.dfsg.1-4_amd64.deb
 b57d129680deefdd84154e56cc3b4ed1 25314 gnome optional 
mail-notification-evolution_3.0.dfsg.1-4_amd64.deb

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

iD8DBQFE6avl1Lfd97FsypURAlHjAKCVJ3aBWcZRPpDBP5IkFH4uuA5F7QCgsu6n
cq1MN9Dw6hOlrSnVrIpkdDY=
=Jie3
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to