Your message dated Wed, 12 Mar 2008 16:47:04 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#470395: fixed in libio-dirent-perl 0.04-2
has caused the Debian Bug report #470395,
regarding libio-dirent-perl: FTBFS with Perl 5.10 (the empty /usr/share/perl5 
is gone)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
470395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=470395
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libio-dirent-perl
Version: 0.04-1
Severity: important
User: [EMAIL PROTECTED]
Usertags: perl-5.10-transition

This package fails to build with Perl 5.10.0 (currently in experimental)
because of a bug in debian/rules that has been uncovered by a change
in ExtUtils::Install.

Until Perl 5.10.0, ExtUtils::Install had a bug that created an empty
/usr/lib/perl5 or /usr/share/perl5 directory when 'make install' was
run. This package fails to build because it relies on the presence of
this empty directory, usually by trying to remove it without checking
if it exists first.

The suggested fix for the usual 'unconditional rmdir' case is to use a
conditional like

[ ! -d $(TMP)/usr/share/perl5 ] || rmdir --ignore-fail-on-non-empty
--parents --verbose $(TMP)/usr/share/perl5

See the current dh-make-perl templates.

Please treat this bug as 'grave' already: Perl 5.10.0 was scheduled for
unstable about a week ago, and it will render this package uninstallable
and unbuildable when it actually enters sid.

Details about the ExtUtils::Install change can be found in #465783.
-- 
Niko Tyni   [EMAIL PROTECTED]



--- End Message ---
--- Begin Message ---
Source: libio-dirent-perl
Source-Version: 0.04-2

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

libio-dirent-perl_0.04-2.diff.gz
  to pool/main/libi/libio-dirent-perl/libio-dirent-perl_0.04-2.diff.gz
libio-dirent-perl_0.04-2.dsc
  to pool/main/libi/libio-dirent-perl/libio-dirent-perl_0.04-2.dsc
libio-dirent-perl_0.04-2_i386.deb
  to pool/main/libi/libio-dirent-perl/libio-dirent-perl_0.04-2_i386.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.
Ludovic Drolez <[EMAIL PROTECTED]> (supplier of updated libio-dirent-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: Wed, 12 Mar 2008 14:35:47 +0100
Source: libio-dirent-perl
Binary: libio-dirent-perl
Architecture: source i386
Version: 0.04-2
Distribution: unstable
Urgency: low
Maintainer: Ludovic Drolez <[EMAIL PROTECTED]>
Changed-By: Ludovic Drolez <[EMAIL PROTECTED]>
Description: 
 libio-dirent-perl - Perl module for accessing dirent structs returned by 
readdir
Closes: 470395
Changes: 
 libio-dirent-perl (0.04-2) unstable; urgency=low
 .
   * fixed a FTBFS with Perl 5.10. Closes: Bug#470395
Files: 
 7da8d474c76b4b9f774a05f04a80c827 622 perl optional libio-dirent-perl_0.04-2.dsc
 19b0fb81ffc643ab8a2bb10eec49cab9 2017 perl optional 
libio-dirent-perl_0.04-2.diff.gz
 fe59cac8a438e19ea9145230608fcd36 10812 perl optional 
libio-dirent-perl_0.04-2_i386.deb

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

iD8DBQFH1/6psRlQAP1GppgRAnPDAJ90qmx2FdvhupUVcoArJDsyB4X5GgCfcEk2
wwQ7hk5qQHIePXI3Jn1q1OY=
=eCDC
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to