Bug 452494 - XML::LibXML::Reader broken
Summary: XML::LibXML::Reader broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-XML-LibXML
Version: 9
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Stepan Kasal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-23 12:52 UTC by Ralf Kleineisel
Modified: 2008-07-30 20:04 UTC (History)
2 users (show)

Fixed In Version: 1.66-1.fc9
Clone Of:
Environment:
Last Closed: 2008-07-30 20:04:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ralf Kleineisel 2008-06-23 12:52:18 UTC
Description of problem:
XML::LibXML::Reader doesn't compile:
$perl -e "use XML::LibXML::Reader;"
v-string in use/require non-portable at
/usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi/XML/LibXML/Reader.pm
line 11.

Version-Release number of selected component (if applicable):
perl-XML-LibXML-1.65-5.fc9.i386

How reproducible:
Every time

Steps to Reproduce:
1. Start a perl script which contains "use XML::LibXML::Reader;"
2.
3.
  
Actual results:
Error message:
v-string in use/require non-portable at
/usr/lib/perl5/vendor_perl/5.10.0/i386-linux-thread-multi/XML/LibXML/Reader.pm
line 11.

Expected results:


Additional info:

Comment 1 Stepan Kasal 2008-06-23 16:18:17 UTC
Thank you for your bug report.  I reproduced the same problem in rawhide, and it
disappeared when I updated to perl-XML-LibXML-1.66-1.fc10.  (I guess that a
rebuild of the current module would also suffice.)
Consequently, package perl-XML-LibXML-1.66-1.fc9, which is about to appear in
Fedora 9 Updates Testing later today, shall fix the problem.

Comment 2 Fedora Update System 2008-06-23 16:32:56 UTC
perl-XML-LibXML-1.66-1.fc9 has been submitted as an update for Fedora 9

Comment 3 Fedora Update System 2008-07-30 20:04:54 UTC
perl-XML-LibXML-1.66-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.