SCIENTIFIC-LINUX-USERS Archives

September 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Garrett Holmstrom <[log in to unmask]>
Reply To:
Garrett Holmstrom <[log in to unmask]>
Date:
Fri, 23 Sep 2011 21:34:33 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
On 2011-09-23 17:14, Christopher Tooley wrote:
> I may have solved this:
> I removed /etc/rpm/platform:
> 	rm /etc/rpm/platform
>
> confirmed that rpm recognized that I had x86_64 arch:
> 	rpm -E '%{_arch}'
> 	x86_64
>
> and then reinstalled python:
> 	yum install python.x86_64
>
> After doing a couple more installs of the x86_64 bit versions of some pam and nss modules I was able to get back to working order.  There are probably some other things that may need to be fixed, but yum update isn't showing a whole bunch of i386 packages anymore :)
>
> For the record, I did an upgrade with a CD from i386 SL 5.4 to SL 5.7 x86_64.  Upon rebooting, yum would insist I had 386 arch, and the authentication method I had was failing (it was looking for 64 bit versions of the pam modules and nss modules).

For the record, note that migrating a system from one arch to another is 
completely unsupported and is likely to cause it to behave unpredictably 
in the future.  That said, congrats for making it work on your system.  ;)

-- 
Garrett Holmstrom

ATOM RSS1 RSS2