Your message dated Sun, 04 Sep 2005 05:17:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326455: fixed in libsql-abstract-limit-perl 0.033-3
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 3 Sep 2005 12:08:58 +0000
>From [EMAIL PROTECTED] Sat Sep 03 05:08:58 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c173118.adsl.hansenet.de (localhost.localdomain) 
[213.39.173.118] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EBWpN-0003AU-00; Sat, 03 Sep 2005 05:08:58 -0700
Received: from aj by localhost.localdomain with local (Exim 4.52)
        id 1EBWpM-0005Eo-E5; Sat, 03 Sep 2005 14:08:56 +0200
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
From: Andreas Jochens <[EMAIL PROTECTED]>
Subject: libsql-abstract-limit-perl: FTBFS: Failed 1/6 test scripts
Message-Id: <[EMAIL PROTECTED]>
Date: Sat, 03 Sep 2005 14:08:56 +0200
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: libsql-abstract-limit-perl
Version: 0.033-1
Severity: serious

When building 'libsql-abstract-limit-perl' in a clean unstable chroot,
I get the following error:

t/02.syntax.......Base class package "Class::DBI" is empty.
    (Perhaps you need to 'use' the module which defines that package first.)
 at t/02.syntax.t line 48
BEGIN failed--compilation aborted at t/02.syntax.t line 48.
# Looks like your test died before it could output anything.
dubious
        Test returned status 255 (wstat 65280, 0xff00)
DIED. FAILED tests 1-7
        Failed 7/7 tests, 0.00% okay
t/03.subclass.....ok
t/pod-coverage....skipped
        all skipped: Test::Pod::Coverage 1.04 required for testing POD coverage
t/pod.............skipped
        all skipped: Test::Pod 1.14 required for testing POD
Failed Test   Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t/02.syntax.t  255 65280     7   14 200.00%  1-7
2 tests skipped.
Failed 1/6 test scripts, 83.33% okay. 7/33 subtests failed, 78.79% okay.
make: *** [install-stamp] Error 255

Regards
Andreas Jochens

---------------------------------------
Received: (at 326455-close) by bugs.debian.org; 4 Sep 2005 12:18:54 +0000
>From [EMAIL PROTECTED] Sun Sep 04 05:18:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EBtQn-0001xr-00; Sun, 04 Sep 2005 05:17:05 -0700
From: Krzysztof Krzyzaniak (eloy) <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#326455: fixed in libsql-abstract-limit-perl 0.033-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 04 Sep 2005 05:17:05 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: libsql-abstract-limit-perl
Source-Version: 0.033-3

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

libsql-abstract-limit-perl_0.033-3.diff.gz
  to 
pool/main/libs/libsql-abstract-limit-perl/libsql-abstract-limit-perl_0.033-3.diff.gz
libsql-abstract-limit-perl_0.033-3.dsc
  to 
pool/main/libs/libsql-abstract-limit-perl/libsql-abstract-limit-perl_0.033-3.dsc
libsql-abstract-limit-perl_0.033-3_all.deb
  to 
pool/main/libs/libsql-abstract-limit-perl/libsql-abstract-limit-perl_0.033-3_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.
Krzysztof Krzyzaniak (eloy) <[EMAIL PROTECTED]> (supplier of updated 
libsql-abstract-limit-perl 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,  4 Sep 2005 13:55:24 +0200
Source: libsql-abstract-limit-perl
Binary: libsql-abstract-limit-perl
Architecture: source all
Version: 0.033-3
Distribution: unstable
Urgency: low
Maintainer: Debian Catalyst Maintainers <[EMAIL PROTECTED]>
Changed-By: Krzysztof Krzyzaniak (eloy) <[EMAIL PROTECTED]>
Description: 
 libsql-abstract-limit-perl - portable LIMIT emulation
Closes: 326455
Changes: 
 libsql-abstract-limit-perl (0.033-3) unstable; urgency=low
 .
   * debian/control - libdbd-anydata-perl, libclass-dbi-perl added to
     Build-Depends-Indep (closes: #326455)
Files: 
 9be0d754ab6c04de5753d87dda6df13b 923 perl optional 
libsql-abstract-limit-perl_0.033-3.dsc
 fca7d23edd2187a906144bddc5eb0734 1657 perl optional 
libsql-abstract-limit-perl_0.033-3.diff.gz
 d260f420df481606683fb55f0dc5be0f 19398 perl optional 
libsql-abstract-limit-perl_0.033-3_all.deb

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

iD8DBQFDGuHH+NMfSd6w7DERAi2+AJ4lrCNOMhBDxmWAUAUxxkkPheYXqQCfWqRM
VB+Xlh4KUK8KJcTFLfiLq3M=
=Cth1
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to