Your message dated Sun, 02 Apr 2006 14:32:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332041: fixed in mush 7.2.5unoff2-25
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: mush

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: mush
Source-Version: 7.2.5unoff2-25

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

mush-src_7.2.5unoff2-25_all.deb
  to pool/non-free/m/mush/mush-src_7.2.5unoff2-25_all.deb
mush_7.2.5unoff2-25.diff.gz
  to pool/non-free/m/mush/mush_7.2.5unoff2-25.diff.gz
mush_7.2.5unoff2-25.dsc
  to pool/non-free/m/mush/mush_7.2.5unoff2-25.dsc



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.
Pawel Wiecek <[EMAIL PROTECTED]> (supplier of updated mush 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,  2 Apr 2006 19:54:10 +0200
Source: mush
Binary: mush-src
Architecture: source all
Version: 7.2.5unoff2-25
Distribution: unstable
Urgency: low
Maintainer: Pawel Wiecek <[EMAIL PROTECTED]>
Changed-By: Pawel Wiecek <[EMAIL PROTECTED]>
Description: 
 mush-src   - The mail user shell -- source only package
Closes: 330434 332041 350304
Changes: 
 mush (7.2.5unoff2-25) unstable; urgency=low
 .
   * Updated debconf dependency to include debconf-2.0 alternative
     (closes: #332041)
   * Added swedish translation of debconf templates from Daniel Nylander
     <[EMAIL PROTECTED]> (closes: #330434)
   * Updated russian translation of debconf templates from Yuri Kozlov
     <[EMAIL PROTECTED]> (closes: #350304)
Files: 
 516d42605c2de006bd71d5554d126b03 688 non-free/mail extra 
mush_7.2.5unoff2-25.dsc
 ea376c218e9cab7d093927eeda624d3f 139741 non-free/mail extra 
mush_7.2.5unoff2-25.diff.gz
 8ac5c605cc221b4d792c3d218bc8a015 508992 non-free/mail extra 
mush-src_7.2.5unoff2-25_all.deb

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

iD8DBQFEMBFbBOdjEO/Bh3ARAnpKAJ9OHF0KWVXuetw6bLHnMMcWbER3owCggu+Y
Zetx2pjaw/I8SsqPN0UWwfc=
=uIQQ
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to