Hello,
since today I could not update my CentOS 5.3 system with yum cause of the following error message.
# yum update [...] Resolving Dependencies --> Running transaction check ---> Package exiv2.i386 0:0.18.2-1.el5.rf set to be updated ---> Package perl-Params-Util.i386 0:1.00-1.el5.rf set to be updated ---> Package perl-Moose.noarch 0:0.86-1.el5.rf set to be updated --> Processing Dependency: perl(Class::MOP) >= 0.89 for package: perl-Moose ---> Package perl-MRO-Compat.noarch 0:0.11-1.el5.rf set to be updated ---> Package exiv2-devel.i386 0:0.18.2-1.el5.rf set to be updated --> Finished Dependency Resolution perl-Moose-0.86-1.el5.rf.noarch from rpmforge has depsolving problems --> Missing Dependency: perl(Class::MOP) >= 0.89 is needed by package perl-Moose-0.86-1.el5.rf.noarch (rpmforge) Error: Missing Dependency: perl(Class::MOP) >= 0.89 is needed by package perl-Moose-0.86-1.el5.rf.noarch (rpmforge)
I have asked about the missing perl(Class::MOP) >= 0.89 package on the rpmforge mailing list without getting any answer. So maybe could this be a problem of CentOS or Epel repo?
Thank you very much for your help!
regards Olaf
Olaf Mueller wrote:
I have asked about the missing perl(Class::MOP) >= 0.89 package on the rpmforge mailing list without getting any answer. So maybe could this be a problem of CentOS or Epel repo?
a) rpmforge and epel don't mix well b) rpmforge perl packages get a mass rebuild at the moment, so ask again there.
Cheers,
Ralph
Ralph Angenendt wrote:
a) rpmforge and epel don't mix well
more specifically, EPEL doesn't mix well with -any- other repository as they insist on not using a repository tag
I for one leave EPEL disabled, and only enable it manually when I absolutely need something from it thats not available elsewhere.
On Tue, Jul 7, 2009 at 5:38 PM, John R Piercepierce@hogranch.com wrote:
Ralph Angenendt wrote:
a) rpmforge and epel don't mix well
more specifically, EPEL doesn't mix well with -any- other repository as they insist on not using a repository tag
I for one leave EPEL disabled, and only enable it manually when I absolutely need something from it thats not available elsewhere.
IMHO, on my CentOS 5.3 (32 bit) Desktop, RPMForge works very well. I have given it a much higher Priority than EPEL. When I added the EPEL Repository, the number of excluded packages went from approximately 400 to 1705. My belief is that if EPEL had a high priority, it would replace a *LOT* of packages I do not want replaced.
Olaf Mueller wrote:
I have asked about the missing perl(Class::MOP) >= 0.89 package on the rpmforge mailing list without getting any answer. So maybe could this be a problem of CentOS or Epel repo?
Ok, found it on the rpmforge list and the error is caused by rpmforge. It was not an answer to my problem but an answer to an other perl dependency error.
----- Dag Wieers wrote:
On Tue, 7 Jul 2009, Joe Ogulin wrote:
[...]
Feel free to jump in and help us with the perl packages. The only way to make this work is having people to actually commit to the work.
The reason why it now breaks is because Christoph is updating all the perl packages and inter-dependencies are not taken care of right now.
-----
So I have a repo where "inter-dependencies are not taken care of right now". Do I something missunderstood here, or behaved rpmforge like a testing repo without saying that this is testing only and not stable?
Either way, to keep thinks running I have to disable rpmforge repo.
regards Olaf
Hi,
On Tue, Jul 7, 2009 at 15:07, Olaf Muellerdaily-planet@istari.de wrote:
since today I could not update my CentOS 5.3 system with yum cause of the following error message.
As pointed out in the rpmforge mailing list, if you are complaining about dependency issues not because you need the specific packages with problems, but because you want to run "yum update" and be able to get the security updates from the other repositories not affected by the issue, and if you are on CentOS 5, you may use the "--skip-broken" option of yum (not available in CentOS 4!) to skip updating packages for which the dependencies are not met.
This is the command you should run in this case: # yum --skip-broken update
HTH, Filipe
-
Filipe Brandenburger -
John R Pierce -
Lanny Marcus -
Olaf Mueller -
Ralph Angenendt