Running yum update on CentOS 4.8 32 bit I keep getting this:
--> Running transaction check --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.024 for package: perl-IO-Compress --> Finished Dependency Resolution Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed by package perl-IO-Compress
I try to uninstall perl-IO-Compress but something like 91 packages depend on it. Any ideas?
Matt wrote:
Running yum update on CentOS 4.8 32 bit I keep getting this:
--> Running transaction check --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.024 for package: perl-IO-Compress --> Finished Dependency Resolution Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed by package perl-IO-Compress
I try to uninstall perl-IO-Compress but something like 91 packages depend on it. Any ideas?
You might start out by
yum clean all
and retrying.
mark
On Mon, Jan 3, 2011 at 2:39 PM, Matt lm7812@gmail.com wrote:
Running yum update on CentOS 4.8 32 bit I keep getting this:
--> Running transaction check --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.024 for package: perl-IO-Compress --> Finished Dependency Resolution Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed by package perl-IO-Compress
I try to uninstall perl-IO-Compress but something like 91 packages depend on it. Any ideas?
Do you have 3rd party repositories enabled? Did you enable them with care and use yum-plugin-priorities or yum-plugin-protectbase?
You may have to untangle installed packages from mixed repositories before you can go any further.
-- Jeff
Running yum update on CentOS 4.8 32 bit I keep getting this:
--> Running transaction check --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.024 for package: perl-IO-Compress --> Finished Dependency Resolution Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed by package perl-IO-Compress
I try to uninstall perl-IO-Compress but something like 91 packages depend on it. Any ideas?
Do you have 3rd party repositories enabled? Did you enable them with care and use yum-plugin-priorities or yum-plugin-protectbase?
You may have to untangle installed packages from mixed repositories before you can go any further.
Thats likely it. Have rpmforge-release-0.5.1-1.el4.rf installed.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Matt said the following on 03/01/11 21:39:
Running yum update on CentOS 4.8 32 bit I keep getting this:
--> Running transaction check --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.024 for package: perl-IO-Compress --> Finished Dependency Resolution Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed by package perl-IO-Compress
I try to uninstall perl-IO-Compress but something like 91 packages depend on it. Any ideas?
Conflict with rpmforge, happened to several installation since mid December.
Solved removing perl RPM packages and using CPAN.
Ciao, luigi
- -- / +--[Luigi Rosa]-- \
UFOs are for real: Air Force doesn't exist.
on 1-3-2011 9:00 PM Luigi Rosa spake the following:
Matt said the following on 03/01/11 21:39:
Running yum update on CentOS 4.8 32 bit I keep getting this:
--> Running transaction check --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.024 for package: perl-IO-Compress --> Finished Dependency Resolution Error: Missing Dependency: perl(Compress::Raw::Zlib) = 2.024 is needed by package perl-IO-Compress
I try to uninstall perl-IO-Compress but something like 91 packages depend on it. Any ideas?
Conflict with rpmforge, happened to several installation since mid December.
Solved removing perl RPM packages and using CPAN.
CPAN will just hide the problems, since RPM will NOT know about any CPAN packages and will happily overwrite them.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Scott Silva said the following on 04/01/11 20:06:
CPAN will just hide the problems, since RPM will NOT know about any CPAN packages and will happily overwrite them.
I am not a Perl expert, but in my experience the packages installed with CPAN and with RPM does not overwrite each other. CPAN stores the libraries in a different directory in which Perl looks for libraries before than looking for the libraries downloaded with RPM.
This is according my experience, but some Perl installation expert will be able to clarify this issue.
Ciao, luigi
- -- / +--[Luigi Rosa]-- \
Critics are like eunuchs in a harem: they know how it's done, they've seen it done every day, but they're unable to do it themselves. --Brendan Behan
On 01/04/2011 11:48 AM, Luigi Rosa wrote:
-- I am not a Perl expert, but in my experience the packages installed with CPAN and with RPM does not overwrite each other. CPAN stores the libraries in a different directory in which Perl looks for libraries before than looking for the libraries downloaded with RPM.
This is according my experience, but some Perl installation expert will be able to clarify this issue.
Right up until an update for Perl itself is pushed - and then you will find all your packages gone. If you need to tweek, use cpan2rpm to generate rpms. I've generally found the issues are tied to man files - so if you suppress the man file generation in the spec and stick with perldoc for a module's documentation you can generally work around the conflicts.
On Tue, Jan 4, 2011 at 3:42 PM, Benjamin Franz jfranz@freerun.com wrote:
On 01/04/2011 11:48 AM, Luigi Rosa wrote:
-- I am not a Perl expert, but in my experience the packages installed with CPAN and with RPM does not overwrite each other. CPAN stores the libraries in a different directory in which Perl looks for libraries before than looking for the libraries downloaded with RPM.
This is according my experience, but some Perl installation expert will be able to clarify this issue.
Right up until an update for Perl itself is pushed - and then you will find all your packages gone. If you need to tweek, use cpan2rpm to generate rpms. I've generally found the issues are tied to man files - so if you suppress the man file generation in the spec and stick with perldoc for a module's documentation you can generally work around the conflicts.
This is why http://perl.arix.com/cpan2rpm/ exists. It's very handy for precisely this sort of situation.
It doesn't protect against advanced modules that are now part of the base Perl deployment, or that used to be part of it, but it was critical to my development of the first complete Bugzilla RPM's, and invaluable for submitting .spec files to RPMforge or EPEL.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Benjamin Franz said the following on 04/01/11 21:42:
Right up until an update for Perl itself is pushed - and then you will find all your packages gone. If you need to tweek, use cpan2rpm to generate rpms. I've generally found the issues are tied to man files - so if you suppress the man file generation in the spec and stick with perldoc for a module's documentation you can generally work around the conflicts.
You are right about the problem about update. That's why I put every Perl library I install on a server in a script that invokes either yum or CPAN to install/update/document the installed libraries.
I will give cpan2rpm a try, thank you
Ciao, luigi
- -- / +--[Luigi Rosa]-- \
Good day for a change of scene. Repaper the bedroom wall.
-
Benjamin Franz -
Jeff -
Luigi Rosa -
m.roth＠5-cent.us -
Matt -
Nico Kadel-Garcia -
Scott Silva