Your message dated Sun, 26 Aug 2007 20:47:08 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332105: fixed in ssmtp 2.61-12.1
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: ssmtp

This package depends/pre-depends on debconf without allowing the dependency
to be satisfied with an alternate of debconf-2.0. That is to say, its
dependency should read: debconf | debconf-2.0

Until this is fixed, it is impossible to use this package with cdebconf,
and very hard to impossible to install cdebconf at all.

debconf-2.0 was added to policy as a virtual package in 2002 and has been
provided by debconf since 2003. In early 2004, dh_installdebconf began
automatically adding it as an alternate to debconf in dependencies it
generates for packages using debhelper. So if you're using a current
version of debhelper you should only need to rebuild your package and
review it. If you are not using debhelper, make sure the dependency is
modified to allow debconf-2.0 to satisfy it.

This bug report was filed by semiautomated means after a trio of posts to
the debian-devel mailing list, and you have probably also received a bcced
mail about the issue before. If your package's dependencies are correct and
it really has some valid reason to depend on debconf alone, please reassign
this bug report to cdebconf with an explanation of what debconf feature
your package depends on, so it can be reimplemented in cdebconf.


--- End Message ---
--- Begin Message ---
Source: ssmtp
Source-Version: 2.61-12.1

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

ssmtp_2.61-12.1.diff.gz
  to pool/main/s/ssmtp/ssmtp_2.61-12.1.diff.gz
ssmtp_2.61-12.1.dsc
  to pool/main/s/ssmtp/ssmtp_2.61-12.1.dsc
ssmtp_2.61-12.1_i386.deb
  to pool/main/s/ssmtp/ssmtp_2.61-12.1_i386.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.
Amaya Rodrigo Sastre <[EMAIL PROTECTED]> (supplier of updated ssmtp 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, 20 Aug 2007 21:08:14 +0200
Source: ssmtp
Binary: ssmtp
Architecture: source i386
Version: 2.61-12.1
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Amaya Rodrigo Sastre <[EMAIL PROTECTED]>
Description: 
 ssmtp      - extremely simple MTA to get mail off the system to a mail hub
Closes: 332105 427737
Changes: 
 ssmtp (2.61-12.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Fix typo in logcheck regex (Closes: #427737).
   * cdebconf transition: allow the dependency on debconf to be satisfied with
     an alternate of debconf-2.0 (Closes: #332105).
Files: 
 ca611795d905a2c2a6f6b91530e851e8 635 mail extra ssmtp_2.61-12.1.dsc
 957e6fff08625fe34f4fc33d0925bbc9 53341 mail extra ssmtp_2.61.orig.tar.gz
 ff1b2e93b610a0e50365561c6b2eabbc 34502 mail extra ssmtp_2.61-12.1.diff.gz
 e2dd6f8f0fd81dc0fa87ee127375202e 45780 mail extra ssmtp_2.61-12.1_i386.deb

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

iEYEARECAAYFAkbJ6GgACgkQNFDtUT/MKpDuHgCg+NvYQL6OH5uZ8u7bhX8Z+9c9
U5AAoIUlmwjZc/0npijF+FKgZcuEPwHP
=zjwB
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to