Your message dated Mon, 04 Dec 2006 13:47:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#391181: 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
Version: 2.0.10.1
Severity: serious

Hi,

I just received a mail from cron that it couldn't find /usr/bin/pdbv.

Which is expected, since it's no longer installed. However, the cron.d
script does not check that.

I'd recommend adding at least a "[ -x /usr/bin/pdbv ] && " in front of
whatever you're running.

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

Versions of packages pdbv depends on:
ii  coreutils [fileutils]         5.97-5     The GNU core utilities
ii  debconf                       1.5.5      Debian configuration management sy
ii  liblocale-gettext-perl        1.05-1     Using libc functions for internati
pn  libtie-ixhash-perl            <none>     (no description available)
ii  perl-base                     5.8.8-6.1  The Pathologically Eclectic Rubbis
ii  perl-modules                  5.8.8-6.1  Core Perl modules

Versions of packages pdbv recommends:
ii  popularity-contest            1.34       Vote for your favourite packages a
ii  procps                        1:3.2.7-3  /proc file system utilities


--- 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