-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue,  7 Feb 2006 23:36:33 -0600
Source: liblog-log4perl-perl
Binary: liblog-log4perl-perl
Architecture: source all
Version: 1.03-1
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava <[EMAIL PROTECTED]>
Changed-By: Manoj Srivastava <[EMAIL PROTECTED]>
Description: 
 liblog-log4perl-perl - A Perl port of the widely popular log4j logging package.
Changes: 
 liblog-log4perl-perl (1.03-1) unstable; urgency=low
 .
   * New upstream release
     * (ms) Some perl-5.6.1 installations have a buggy Carp.pm. Skipping
            4 test cases for these. Reported by Andy Ford and Matisse Enzer.
     * (ms) The DBI appender now reconnects on stale DB connections.
     * (ms) Fixed Win32 test bug as reported in
            http://rt.cpan.org/Ticket/Display.html?id=17436 by barbie.
            Instead of deleting a file still in use by an appender (which
            Windows doesn't like), the file gets now truncated.
Files: 
 1cda9aa5c691eff111079461fbb37b7a 672 perl optional 
liblog-log4perl-perl_1.03-1.dsc
 2b471ec7e844a2b603239c3808155b56 211260 perl optional 
liblog-log4perl-perl_1.03.orig.tar.gz
 a2be4728d3376ecc5274e9db90b29f91 36711 perl optional 
liblog-log4perl-perl_1.03-1.diff.gz
 82b734ef2a7021397caebbeecafeb68c 344770 perl optional 
liblog-log4perl-perl_1.03-1_all.deb

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

iD8DBQFD6YTeIbrau78kQkwRApfBAKDW9K7vF6cVvxBtj4YibbDMcfBSEwCfSLCe
VigyWP5YFPkpny8Wg0MK700=
=rNHH
-----END PGP SIGNATURE-----


Accepted:
liblog-log4perl-perl_1.03-1.diff.gz
  to pool/main/libl/liblog-log4perl-perl/liblog-log4perl-perl_1.03-1.diff.gz
liblog-log4perl-perl_1.03-1.dsc
  to pool/main/libl/liblog-log4perl-perl/liblog-log4perl-perl_1.03-1.dsc
liblog-log4perl-perl_1.03-1_all.deb
  to pool/main/libl/liblog-log4perl-perl/liblog-log4perl-perl_1.03-1_all.deb
liblog-log4perl-perl_1.03.orig.tar.gz
  to pool/main/libl/liblog-log4perl-perl/liblog-log4perl-perl_1.03.orig.tar.gz


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

Reply via email to