For a while now I've been seeing skipped-package notices, which I don't really understand. I know it's a version mis-match, but all my attempts to sort it out have failed, so I need help, please. The current state is
Skipping filters plugin, no data --> Running transaction check ---> Package perl-Compress-Zlib.x86_64 0:2.020-119.el6 will be obsoleted ---> Package perl-IO-Compress.noarch 0:2.037-1.el6.rfx will be obsoleting --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.037 for package: perl-IO-Compress-2.037-1.el6.rfx.noarch ---> Package perl-IO-Compress-Base.x86_64 0:2.020-119.el6 will be obsoleted ---> Package perl-IO-Compress-Zlib.x86_64 0:2.020-119.el6 will be obsoleted --> Finished Dependency Resolution
Packages skipped because of dependency problems: perl-IO-Compress-2.037-1.el6.rfx.noarch from rpmforge-extras
Can someone please tell me what needs erasing/installing/updating to get this cleaned up?
Thanks
Anne
On 12/12/11 18:47, Anne Wilson wrote:
For a while now I've been seeing skipped-package notices, which I don't really understand. I know it's a version mis-match, but all my attempts to sort it out have failed, so I need help, please. The current state is
Skipping filters plugin, no data --> Running transaction check ---> Package perl-Compress-Zlib.x86_64 0:2.020-119.el6 will be obsoleted ---> Package perl-IO-Compress.noarch 0:2.037-1.el6.rfx will be obsoleting --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.037 for package: perl-IO-Compress-2.037-1.el6.rfx.noarch ---> Package perl-IO-Compress-Base.x86_64 0:2.020-119.el6 will be obsoleted ---> Package perl-IO-Compress-Zlib.x86_64 0:2.020-119.el6 will be obsoleted --> Finished Dependency Resolution
Packages skipped because of dependency problems: perl-IO-Compress-2.037-1.el6.rfx.noarch from rpmforge-extras
Can someone please tell me what needs erasing/installing/updating to get this cleaned up?
Thanks
Anne
It might be helpful to show the output from 'rpm -qa perl* | sort'.
As to the reason for the above error... it looks like you have the protect or priority plugins stopping rpmforge-extras packages from updating base components?
Try:
yum --disablerepo=* --enablerepo=rpmforge-extras update perl-IO-Compress
which should remove the following if installed:
perl-Compress-Zlib perl-IO-Compress-Base perl-IO-Compress-Bzip2 perl-IO-Compress-Zlib
and install/update the following:
perl-IO-Compress perl-Compress-Raw-Bzip2 perl-Compress-Raw-Zlib
HTHs
On 12/12/2011 07:44 PM, Ned Slider wrote:
On 12/12/11 18:47, Anne Wilson wrote:
For a while now I've been seeing skipped-package notices, which I don't really understand. I know it's a version mis-match, but all my attempts to sort it out have failed, so I need help, please. The current state is
Skipping filters plugin, no data --> Running transaction check ---> Package perl-Compress-Zlib.x86_64 0:2.020-119.el6 will be obsoleted ---> Package perl-IO-Compress.noarch 0:2.037-1.el6.rfx will be obsoleting --> Processing Dependency: perl(Compress::Raw::Zlib) = 2.037 for package: perl-IO-Compress-2.037-1.el6.rfx.noarch ---> Package perl-IO-Compress-Base.x86_64 0:2.020-119.el6 will be obsoleted ---> Package perl-IO-Compress-Zlib.x86_64 0:2.020-119.el6 will be obsoleted --> Finished Dependency Resolution
Packages skipped because of dependency problems: perl-IO-Compress-2.037-1.el6.rfx.noarch from rpmforge-extras
Can someone please tell me what needs erasing/installing/updating to get this cleaned up?
Thanks
Anne
It might be helpful to show the output from 'rpm -qa perl* | sort'.
Output after "repair" recommended by you:
rpm -qa perl* | sort perl-5.10.1-119.el6.x86_64 perl-Archive-Tar-1.58-119.el6.x86_64 perl-Bit-Vector-7.1-2.el6.x86_64 perl-Cairo-1.062-1.el6.x86_64 perl-Carp-Clan-6.03-2.el6.noarch perl-CGI-3.51-119.el6.x86_64 perl-Compress-Raw-Bzip2-2.037-1.el6.rf.x86_64 perl-Compress-Raw-Zlib-2.037-1.el6.rfx.x86_64 perl-Crypt-OpenSSL-Bignum-0.04-8.1.el6.x86_64 perl-Crypt-OpenSSL-Random-0.04-9.1.el6.x86_64 perl-Crypt-OpenSSL-RSA-0.25-10.1.el6.x86_64 perl-Date-Calc-6.3-2.el6.noarch perl-Date-Manip-5.54-4.el6.noarch perl-DBD-MySQL-4.013-3.el6.x86_64 perl-DBI-1.609-4.el6.x86_64 perl-devel-5.10.1-119.el6.x86_64 perl-Digest-HMAC-1.01-22.el6.noarch perl-Digest-SHA1-2.12-2.el6.x86_64 perl-Digest-SHA-5.47-119.el6.x86_64 perl-Encode-Detect-1.01-2.el6.x86_64 perl-Error-0.17015-4.el6.noarch perl-ExtUtils-MakeMaker-6.55-119.el6.x86_64 perl-ExtUtils-ParseXS-2.2003.0-119.el6.x86_64 perl-File-Find-Rule-0.30-9.el6.noarch perl-gettext-1.05-16.el6.x86_64 perl-Git-1.7.1-2.el6_0.1.noarch perl-Glib-1.223-1.el6.x86_64 perl-Gtk2-1.223-2.el6.x86_64 perl-HTML-Parser-3.64-2.el6.x86_64 perl-HTML-Tagset-3.20-4.el6.noarch perl-IO-Compress-2.037-1.el6.rfx.noarch perl-IO-Socket-INET6-2.56-4.el6.noarch perl-IO-Socket-SSL-1.31-2.el6.noarch perl-IO-Zlib-1.09-119.el6.x86_64 perl-libs-5.10.1-119.el6.x86_64 perl-libwww-perl-5.833-2.el6.noarch perl-Mail-DKIM-0.37-2.el6.noarch perl-MailTools-2.04-4.el6.noarch perl-Module-Pluggable-3.90-119.el6.x86_64 perl-NetAddr-IP-4.027-3.el6.x86_64 perl-Net-DNS-0.65-2.el6.x86_64 perl-Net-LibIDN-0.12-3.el6.x86_64 perl-Net-SSLeay-1.35-9.el6.x86_64 perl-Net-Whois-1.9-1.2.el6.rf.noarch perl-Net-Whois-IP-1.04-1.el6.rf.noarch perl-Net-XWhois-0.90-1.2.el6.rf.noarch perl-Number-Compare-0.01-13.el6.noarch perl-Package-Constants-0.02-119.el6.x86_64 perl-Pango-1.221-2.el6.x86_64 perl-Pod-Escapes-1.04-119.el6.x86_64 perl-Pod-Simple-3.13-119.el6.x86_64 perl-Socket6-0.23-3.el6.x86_64 perl-Test-Harness-3.17-119.el6.x86_64 perl-Test-Simple-0.92-119.el6.x86_64 perl-Text-Glob-0.08-7.el6.noarch perl-TimeDate-1.16-11.1.el6.noarch perl-Time-HiRes-1.9721-119.el6.x86_64 perl-URI-1.40-2.el6.noarch perl-version-0.77-119.el6.x86_64
As to the reason for the above error... it looks like you have the protect or priority plugins stopping rpmforge-extras packages from updating base components?
Try:
yum --disablerepo=* --enablerepo=rpmforge-extras update perl-IO-Compress
which should remove the following if installed:
perl-Compress-Zlib perl-IO-Compress-Base perl-IO-Compress-Bzip2 perl-IO-Compress-Zlib
and install/update the following:
perl-IO-Compress perl-Compress-Raw-Bzip2 perl-Compress-Raw-Zlib
Yes, it completed, thanks.
I have the following repos:
adobe-linux-i386.repo _local.repo CentOS-Base.repo mirrors-rpmforge CentOS-CR.repo mirrors-rpmforge-extras CentOS-Debuginfo.repo mirrors-rpmforge-testing CentOS-Media.repo rpmforge.repo epel.repo rpmfusion-free-updates.repo epel-testing.repo rpmfusion-free-updates-testing.repo google-chrome.repo rpmfusion-nonfree-updates.repo rpmfusion-nonfree-updates-testing.repo
To avoid similar problems in the future, can you give me some guidelines for priority settings? It seems I got it wrong somewhere :-) Thanks
Anne
Vreme: 12/13/2011 06:47 PM, Anne Wilson piše:
To avoid similar problems in the future, can you give me some guidelines for priority settings? It seems I got it wrong somewhere:-) Thanks
It is not wise to have third-party repositories overwriting base packages. This should only be used by hand per package basis.
I have created local repository where I copy packages I wish to replace and only that "third-party" repository has same priority as official repositories.
RPMForge (now RepoForge) has "non-violent", or safe repository that *should not* contain packages that overwrite base packages, and "violent" repository named "extras" that is meant to overwrite base packages.
On 12/13/2011 07:53 PM, Ljubomir Ljubojevic wrote:
Vreme: 12/13/2011 06:47 PM, Anne Wilson piše:
To avoid similar problems in the future, can you give me some guidelines for priority settings? It seems I got it wrong somewhere:-) Thanks
It is not wise to have third-party repositories overwriting base packages. This should only be used by hand per package basis.
I have created local repository where I copy packages I wish to replace and only that "third-party" repository has same priority as official repositories.
RPMForge (now RepoForge) has "non-violent", or safe repository that *should not* contain packages that overwrite base packages, and "violent" repository named "extras" that is meant to overwrite base packages.
Thanks. I think that makes it clear - it seems that if I see this sort of problem again I have to look at repositories that are not normally enabled, and consider whether to temporarily enable them. Is it safe to leave rpmfusion-free-updates.repo and rpmfusion-nonree-updates.repo without a specific priority setting? The various testing repos are not enabled.
Anne
Vreme: 12/15/2011 12:37 PM, Anne Wilson piše:
On 12/13/2011 07:53 PM, Ljubomir Ljubojevic wrote:
Vreme: 12/13/2011 06:47 PM, Anne Wilson piše:
To avoid similar problems in the future, can you give me some guidelines for priority settings? It seems I got it wrong somewhere:-) Thanks
It is not wise to have third-party repositories overwriting base packages. This should only be used by hand per package basis.
I have created local repository where I copy packages I wish to replace and only that "third-party" repository has same priority as official repositories.
RPMForge (now RepoForge) has "non-violent", or safe repository that *should not* contain packages that overwrite base packages, and "violent" repository named "extras" that is meant to overwrite base packages.
Thanks. I think that makes it clear - it seems that if I see this sort of problem again I have to look at repositories that are not normally enabled, and consider whether to temporarily enable them. Is it safe to leave rpmfusion-free-updates.repo and rpmfusion-nonree-updates.repo without a specific priority setting? The various testing repos are not enabled.
You can keep all desired repositories enabled as long as you have yum-plugin-priorities installed and keep third-party repositories with lesser priority (larger number). Like base=1, epel=2, repoforge=3, rpmfusion-* =3, etc.
Here is how I decided to setup third party repositories: http://rpms.plnet.rs/CentDOS.repo There are few changes needed like "torakat" repo with now centosplus kernels.
On 12/15/2011 04:24 PM, Ljubomir Ljubojevic wrote:
You can keep all desired repositories enabled as long as you have yum-plugin-priorities installed and keep third-party repositories with lesser priority (larger number). Like base=1, epel=2, repoforge=3, rpmfusion-* =3, etc.
Here is how I decided to setup third party repositories: http://rpms.plnet.rs/CentDOS.repo There are few changes needed like "torakat" repo with now centosplus kernels.
Thanks. That's really helpful. I'll go through mine now and check that they all have the right priorities.
Thanks again
Anne
On Thu, Dec 15, 2011 at 10:24 AM, Ljubomir Ljubojevic office@plnet.rs wrote:
You can keep all desired repositories enabled as long as you have yum-plugin-priorities installed and keep third-party repositories with lesser priority (larger number). Like base=1, epel=2, repoforge=3, rpmfusion-* =3, etc.
Does this always do what you want when things appear in different repos? Like something you have installed from extras being added later to EPEL, etc.?
On 12/15/2011 01:27 PM, Les Mikesell wrote:
On Thu, Dec 15, 2011 at 10:24 AM, Ljubomir Ljubojevic office@plnet.rs wrote:
You can keep all desired repositories enabled as long as you have yum-plugin-priorities installed and keep third-party repositories with lesser priority (larger number). Like base=1, epel=2, repoforge=3, rpmfusion-* =3, etc.
Does this always do what you want when things appear in different repos? Like something you have installed from extras being added later to EPEL, etc.?
Obviously not ...
If you actually want something from a lower rated repo, you must add an:
exclude=<package_name>
in the higher rated repo. That in effect no longer looks for the package in the higher rated repo and gets it from the next one down the list.
Since all repos do not test the others for interactivity, and since every user might have different repos than everyone else (including local ones, etc.) ... there is no one size fits all solution for adding more than just the base repos.
Vreme: 12/15/2011 08:27 PM, Les Mikesell piše:
On Thu, Dec 15, 2011 at 10:24 AM, Ljubomir Ljubojevicoffice@plnet.rs wrote:
You can keep all desired repositories enabled as long as you have yum-plugin-priorities installed and keep third-party repositories with lesser priority (larger number). Like base=1, epel=2, repoforge=3, rpmfusion-* =3, etc.
Does this always do what you want when things appear in different repos? Like something you have installed from extras being added later to EPEL, etc.?
Plugin "Priorities" hides packages with the same name, leaving only package from the repo with top most priority (lower number). This prevents visibility and installability of packages in repo's with lower priority (higher number). You can still see them if you add "--showduplicates --disableplugin=priorities".
EPEL is base-repo friendly, so there should be no problems with EPEL. Trick comes with RepoForge (ex-RPMForge), aTrpms, and other third party repo's. Policy of the RepoForge for example is that they will not recompile their own packages if package they depend on is bumped in EPEL and overrides RepoForge's package with same name. I do understand them, they have limited time and infrastructure to always keep up with EPEL.
But only real problems are with Audio/Video packages: players, codecs (decoders, encoders), and supporting libraries. In order to be sure that those packages will work without interruptions, players are compiled with hard-coded dependencies on particular version of libraries, codec packages, etc.
We can narrow it down even further to decoders/encoders with licensing issues like MP3. Upstream, CentOS consequently, and EPEL compile for example gstreamer package without license infringing codecs, but all others do. What people do is to install gstreamer from third party repo with gstreamer-bad (or was it -ugly) additional packages. So when upstream or EPEL publishes another version of gstreamer, hard-coded gstreamer-bad dependancy conflicts with new package. So third-party repo would have to rebuild their entire audio/video "package group" to avoid conflicts. Solution would be that there is communication between EPEL(/upstream) maintainer and third party repos.
So there will always be complications, but they are limited to audio/video packages (mostly).
On 12/15/2011 04:24 PM, Ljubomir Ljubojevic wrote:
Here is how I decided to setup third party repositories: http://rpms.plnet.rs/CentDOS.repo There are few changes needed like "torakat" repo with now centosplus kernels.
Can you explain, please, about those "exclude=*releases" statements? What exactly are they excluding?
Anne
Vreme: 12/15/2011 08:32 PM, Anne Wilson piše:
On 12/15/2011 04:24 PM, Ljubomir Ljubojevic wrote:
Here is how I decided to setup third party repositories: http://rpms.plnet.rs/CentDOS.repo There are few changes needed like "torakat" repo with now centosplus kernels.
Can you explain, please, about those "exclude=*releases" statements? What exactly are they excluding?
I use "exclude=*releases" so I no repository release package (like "centos-release", or "epel-release") will update/install *.repo files in /etc/yum/repos.d/ and in doing so add repository entries not controled by me.
But there is an error I just saw, it should be "exclude=*release", without the trailing "s". I will have to fix this as soon as possible.
Explanation:
When I install CentOS systems, I move original *.repo files to backup subdirectory because they do not contain "Enabled=" and "Priorities=" lines, and leave only my own .repo file. If there is no "exclude=*release" line, then next update of xxx-release would see that their .repo files are missing and would reinstall them. "New" .repo files would then circumvent priorities plugin and all my work was for nothing.
-
Anne Wilson -
Johnny Hughes -
Les Mikesell -
Ljubomir Ljubojevic -
Ned Slider