Michael,

Did you look at the src.rpm to verify that this line was missing. If it is indeed missing then I think it should be bugzilla'ed .

-connie sieh

On Sun, 21 Jun 2009, Michael Mansour wrote:

Hi,

After installing perl-LDAP, the other dependency packages were installed:

Jun 20 23:42:32 Installed: perl-XML-NamespaceSupport-1.09-1.2.1.noarch
Jun 20 23:42:32 Installed: perl-XML-SAX-0.14-5.noarch
Jun 20 23:42:33 Installed: 1:perl-LDAP-0.33-3.fc6.noarch

Since then, one of my perl packages is doing strange things, and
generating an error when run with:

could not find ParserDetails.ini in /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX

Checking the package:

# rpm -ql perl-XML-SAX |grep ParserDetails
/usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserDetails.ini

but the file doesn't actually exist on the filesystem:

# ll /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserDetails.ini
ls: /usr/lib/perl5/vendor_perl/5.8.8/XML/SAX/ParserDetails.ini: No
such file or directory

I've un-installed and re-installed, same problem. The RPM DB says
it's there when in fatc it's not.

I found this:

http://perl-xml.sourceforge.net/faq/

which in this section:

3.18.   "could not find ParserDetails.ini"

Explains the following:

"
If you are packaging XML::SAX in an alternative distribution format (such as
RPM), your post-install script should check if ParserDetails.ini exists and if
it doesn't, run this command:

perl -MXML::SAX -e "XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()"


Don't unconditionally run this command, or users who re-install XML::SAX may
find that any fast SAX parser they have installed will be replaced as the
default by the pure-Perl parser.
"

So this tells us that the post-install script in the RPM doesn't actually work
right?

I ran that perl command above and the ParserDetail.ini file was then created
and the problem went away.

Should the issue with this RPM package be raised in bugzilla?

Regards,

Michael.

I'm using:

Scientific Linux SL release 5.3 (Boron)

Regards,

Michael.
------- End of Original Message -------

Reply via email to