SOLVED: Problem updating perl - transaction test fail

Howdy,

That's a bizarre problem that we've occasionally been seeing where the 32bit version of Perl ends up on a 64 bit system. While I can't begin to explain how that happens, I can assist in fixing it :-)

Try running this command on your system as root (which will remove the 32 bit version of Perl):

yum remove perl.i386

And then run this (which should install the correct one):

yum install perl

After that, can you run yum update?

-Eric

Any books you can recommend me?

Well, I enjoyed Atul Gawande's book "Better", both Freakonomics books, and most of the books by Tyler Cowen. But those aren't related to computers :-)

Moreso than any book, if you're interested in learning about using Linux and Virtualmin -- I'd suggest setting up a test server, perhaps within Virtualbox on your desktop. And then play around with your setup on your test server -- try things, break things, see how they work.

When something doesn't work, you can always just rebuild the test server.

If it does work, and you want to do it on your live server -- well, you know it works, so it should be safe to make that change on your production box!

-Eric

My problem has always been that after some days of work there's always "something that doesn't work" and in the end I grew tired of reinstalling and redoing all the work. But practice makes perfect :)

Well, that's a fine point!

One of the reasons I like VirtualBox is due to it's "snapshot" support.

So, you can perform an install of CentOS and Virtualmin on it. Once it's working at a basic level as you want it -- stop! Leave that VirtualBox guest, and create a snapshot of it.

Now, do all of your testing/work within that snapshot. You can mess it up all you want -- and once it's beyond repair, you can remove it, and create a new snapshot.

You'll never need to start from scratch -- you can always start over from where ever your original VirtualBox guest is at.

-Eric

Thanks for the book suggestions.

I did what Andy suggested in his first reply.

yum remove yum install and then yum update.

It removed i386 perl then during the install it put it back and also update x86_64.

Should both versions be running on the box simultaneously? Thanks guys

Nope, you should only have one version of Perl. It's a CentOS problem of some sort that it attempts to install both.

There's actually some additional details on that problem here in the question named "Why Is 32bit Perl installed on my 64bit CentOS System":

http://www.virtualmin.com/documentation/system/faq

Thanks Audrey, I was dealing with the same thing on my CentOS, solution worked great :)

I experience reversed error. My CentOS is 64 bit but Cloudmid try to install Perl i386. Any idea how to fix this error?

Below is the result of Cloudmin install scripts:

And yum remove perl.i386 result:

I had the same initial post problem. Same fix. Thanks.

Installed:
perl.i386 4:5.8.8-32.el5_6.3

Updated:
perl.x86_64 4:5.8.8-32.el5_7.6

Complete!

I ran the command yum remove perl.i386. But it removed all the other packages including the graphics. if we give like yum install perl.i386, will it install all dependency packages including the graphics?