Your message dated Mon, 04 Dec 2006 13:47:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332062: fixed in pdbv 2.0.11
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: pdbv

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: pdbv
Source-Version: 2.0.11

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

pdbv_2.0.11.dsc
  to pool/main/p/pdbv/pdbv_2.0.11.dsc
pdbv_2.0.11.tar.gz
  to pool/main/p/pdbv/pdbv_2.0.11.tar.gz
pdbv_2.0.11_all.deb
  to pool/main/p/pdbv/pdbv_2.0.11_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.
Mathieu Roy <[EMAIL PROTECTED]> (supplier of updated pdbv 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,  4 Dec 2006 13:52:59 +0100
Source: pdbv
Binary: pdbv
Architecture: source all
Version: 2.0.11
Distribution: unstable
Urgency: low
Maintainer: Mathieu Roy <[EMAIL PROTECTED]>
Changed-By: Mathieu Roy <[EMAIL PROTECTED]>
Description: 
 pdbv       - output an XHTML view of the dpkg database
Closes: 299278 316703 318793 332062 336801 391181 397634
Changes: 
 pdbv (2.0.11) unstable; urgency=low
 .
   * Merge all patches, NMUs improvements (thanks a lot to Christian Perrier
   and Alexis Sukrieh), with fixes made on the CVS
   (closes: #332062, #336801, #316703, #318793, #299278, #397634, #391181)
   * Bump Standards-Version to 3.7.2
   * Fix debconf templates according to Debian Developer's Reference 6.5.4.2
   * Add debhelper compatibily file
Files: 
 333d75d41b0118f0ac0b5f9e4d08d02a 553 admin optional pdbv_2.0.11.dsc
 e0663607bba4b997845f1e2cd9303c93 77816 admin optional pdbv_2.0.11.tar.gz
 a18e30b79f5765f552f2d9027403d3ad 71138 admin optional pdbv_2.0.11_all.deb

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

iD8DBQFFdCJj3JE9mF3wMWcRAt9oAKC2CJ7ErGTYxEKOGXWqSgJQtcBCJwCgqNPn
GVhf+/pVbaAsGFVss2TfWLg=
=VjZs
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to