Submitted by lueung on Sun, 06/13/2010 - 08:12
While updating i get this: perl-5.8.8-32.el5_5.1.x86_64 conflicts with file from package perl-5.8.8-27.el5.i386
I only want the 64 package.
Status:
Active
While updating i get this: perl-5.8.8-32.el5_5.1.x86_64 conflicts with file from package perl-5.8.8-27.el5.i386
I only want the 64 package.
Comments
Submitted by JamieCameron on Sun, 06/13/2010 - 11:29 Comment #1
Looks like you have both the 32 and 64-bit versions of perl installed! Is that intentional?
You can verify with a command like :
rpm -q perl
Submitted by lueung on Sun, 06/13/2010 - 12:20 Comment #2
Nope not intentional. Prior to a migration I used rpm -ivh http://software.virtualmin.com/bleed/centos/5/i386/virtualmin-bleed-rele... which is 32. I think that is what caused it. Is there a 64 version?
How do I fix the current 32 conflict so it does not recur in future updates?
after rpm -q perl it displays
perl-5.8.8-27.el5 perl-5.8.8-27.el5
Submitted by JamieCameron on Sun, 06/13/2010 - 12:39 Comment #3
Is your system 32 or 64-bit? Normally I would recommend removing the perl package for the architecture that your system doesn't use, with a command like :
rpm -e perl-5.8.8-27.el5.i386
Prior to a migration I used rpm -ivh http://software.virtualmin.com/bleed/centos/5/i386/virtualmin-bleed-rele... which is 32. I think that is what caused it. Is there a 64 version?
This is unrelated. There is no perl in our bleeding edge repos.
The release package is architecture independent (noarch). Doesn't matter whether you installed it from the i386 path or the x86_64 path; it creates the same .repo file (which uses variables for the architecture rather than hardcoded paths).
Submitted by lueung on Sun, 06/13/2010 - 17:52 Comment #5
Thanks Jamie and Joe for the repo clarification. That did it the the trick. Always learn something new from you guys :)