RPM Problem - "corrupt" RPM (perl-XML-LibXML and -SAX)
I rebuilt one of my systems last night, and started with apt4rpm. I downloaded the stuff from the ftp.gwdg.de site (apt, apt-server, apt-libs, perl-XML-*, etc) and installed with 'rpm -Uvh [insert list of needed rpm files here]'. It ran through OK, but ended up with: 8:perl-XML-LibXML ################################## [ 89%] Can't locate XML/SAX.pm in @INC (@INC contains: /usr/lib/perl5/5.8.3/i586-linux-thread-multi /usr/lib/perl5.8.3 ..... [extra paths removed for brevity] ). BEGIN failed--compilation aborted. (above message repeats twice) error: %post(perl-XML-LibXML-1.56-rb1) scriptlet failed, edit status 2 apt4rpm goes ahead and finishes installing fine. My first thought was to rpm -e perl-XML-LibXML perl-XML-SAX apt4rpm, but it will NOT remove it (gives me the same error above, about not being able to find XML/SAX.pm. I've tried reinstalling perl-XML-LibXML off the SuSE DVD, which installs fine, but then rpm -qa shows that I have BOTH versions of perl-XML-LibXML installed. (So, I removed the "new" one...) I >think< the perl-SAX module is actually the culprit here. I've tried re-downloading it from ftp.gwdg.de's apt4rpm directory, as well as off of rpm.pbone.net (slightly newer version), but it still craps out with the same error. Anyone able to help before I pull the remaining hair on my head out? (Oh, I've tried doing an rpm --rebuilddb too - didn't help)
On Friday 15 October 2004 15:35, Steve Kratz wrote:
I rebuilt one of my systems last night, and started with apt4rpm. I downloaded the stuff from the ftp.gwdg.de site (apt, apt-server, apt-libs, perl-XML-*, etc) and installed with 'rpm -Uvh [insert list of needed rpm files here]'.
It ran through OK, but ended up with:
8:perl-XML-LibXML ################################## [ 89%] Can't locate XML/SAX.pm in @INC (@INC contains: /usr/lib/perl5/5.8.3/i586-linux-thread-multi /usr/lib/perl5.8.3 ..... [extra paths removed for brevity] ).
BEGIN failed--compilation aborted.
(above message repeats twice)
error: %post(perl-XML-LibXML-1.56-rb1) scriptlet failed, edit status 2
apt4rpm goes ahead and finishes installing fine.
My first thought was to rpm -e perl-XML-LibXML perl-XML-SAX apt4rpm, but it will NOT remove it (gives me the same error above, about not being able to find XML/SAX.pm. I've tried reinstalling perl-XML-LibXML off the SuSE DVD, which installs fine, but then rpm -qa shows that I have BOTH versions of perl-XML-LibXML installed. (So, I removed the "new" one...)
I >think< the perl-SAX module is actually the culprit here. I've tried re-downloading it from ftp.gwdg.de's apt4rpm directory, as well as off of rpm.pbone.net (slightly newer version), but it still craps out with the same error.
Anyone able to help before I pull the remaining hair on my head out?
I had the same problem only an hour ago! ;) I installed perl-XML-LibXML-Common perl-XML-SAX from the funktronics repository. Cheers, Leen
I had the same problem only an hour ago! ;) I installed
perl-XML-LibXML-Common perl-XML-SAX
from the funktronics repository.
I'll try that -- I .did. get things uninstalled. I ended up using YaST to nuke anything having to do with perl. I haven't tried reinstalling apt yet (going to see if I can get it somewhere other than the gwdg.de site -- signed RPMs that have an obvious install problem leave a bad taste in my mouth :)
On Friday 15 October 2004 16:34, Steve Kratz wrote:
I had the same problem only an hour ago! ;) I installed
perl-XML-LibXML-Common perl-XML-SAX
from the funktronics repository.
I'll try that -- I .did. get things uninstalled. I ended up using YaST to nuke anything having to do with perl. I haven't tried reinstalling apt yet (going to see if I can get it somewhere other than the gwdg.de site -- signed RPMs that have an obvious install problem leave a bad taste in my mouth :)
Chances are those will be just copies of the ones on ftp.gwdg.de. Odd: my perl-XML-LibXML comes strait from SuSE, while it seems to need perl-XML-LibXML-Common and perl-XML-SAX to function properly. Cheers, Leen
Op vrijdag 15 oktober 2004 15:35, schreef Steve Kratz:
I rebuilt one of my systems last night, and started with apt4rpm. I downloaded the stuff from the ftp.gwdg.de site (apt, apt-server, apt-libs, perl-XML-*, etc) and installed with 'rpm -Uvh [insert list of needed rpm files here]'.
Steve, are you sure that you need the perl-XML* rpms? From http://linux01.gwdg.de/apt4rpm, I quote: "Make sure that the apt server application "apt4rpm" is not listed (in this case the command 'rpm -q apt4rpm' should tell you that the rpm is not installed), unless you want to provide an apt repository.... ". The only packages needed to get a functional apt client are apt and apt-libs. -- Richard Bos Without a home the journey is endless
Steve, are you sure that you need the perl-XML* rpms? From http://linux01.gwdg.de/apt4rpm, I quote: "Make sure that the apt server application "apt4rpm" is not listed (in this case the command 'rpm -q apt4rpm' should tell you that the rpm is not installed), unless you want to provide an apt repository.... ".
The only packages needed to get a functional apt client are apt and apt-libs.
Hrmmm, I >know< something I was installing last night was requesting that... Does the apt-server require the perl stuff by chance?
The only packages needed to get a functional apt client are apt and apt-libs.
I just went into YaST, tried removing perl-XML-LibXML, and it definately complains that apt4rpm has a dependency on it... Maybe they assume the perl modules will be there on any system?!? *shrug*
Op vrijdag 15 oktober 2004 21:11, schreef Steve Kratz:
I just went into YaST, tried removing perl-XML-LibXML, and it definately complains that apt4rpm has a dependency on it...
apt4rpm is needed to create your own local apt repository. Is that what you want? If you don't want to create your own apt repository/server, just have apt4rpm (including apt-server) removed. The apt client is obtained by installing apt-libs and apt, that's it. -- Richard Bos Without a home the journey is endless
apt4rpm is needed to create your own local apt repository. Is that what you want? If you don't want to create your own apt repository/server, just have apt4rpm (including apt-server) removed. The apt client is obtained by installing apt-libs and apt, that's it.
Ah, gotcha... I didn't know that (I assumed apt-server did that, didn't know apt4rpm was for rolling your own as well :) Thanks!
participants (3)
-
Leendert Meyer -
Richard Bos -
Steve Kratz