>From: Ed Wilts <[EMAIL PROTECTED]> >Subject: Re: Failures on rpm -Fv updates > >It sounds like you grabbed the i386 update directory when you don't have >an i386 package installed. That's a good way to shoot yourself in the >foot. You can search the list archives or bugzilla on how to undo your >change. Then you should go back and grab the right architecture- >specific version.
Hmmm... I *am* running an Athlon, but the mirror only had athlon specific packages for the kernel, not for glibc. Witness: ncftp ...updates/9/en/os/athlon > dir -rw-rw-r-- 13846677 Jun 2 08:34 kernel-2.4.20-18.9.athlon.rpm -rw-rw-r-- 14330407 Jun 2 08:34 kernel-smp-2.4.20-18.9.athlon.rpm ncftp ...x/updates/9/en/os/i686 > dir -rw-rw-r-- 4878094 Apr 9 09:13 glibc-2.3.2-27.9.i686.rpm -rw-rw-r-- 13989825 Jun 2 08:34 kernel-2.4.20-18.9.i686.rpm -rw-rw-r-- 14574141 Jun 2 08:34 kernel-bigmem-2.4.20-18.9.i686.rpm -rw-rw-r-- 14569238 Jun 2 08:34 kernel-smp-2.4.20-18.9.i686.rpm -rw-rw-r-- 828650 Apr 9 09:14 nptl-devel-2.3.2-27.9.i686.rpm -rw-rw-r-- 1122284 Mar 28 16:30 openssl-0.9.7a-5.i686.rpm So I assumed I had the i386 of glibc... >Note that had you used up2date, this would not have happened. Can't - I've already used my one allotment. I paid for the RHN service last year, but this year cash's quite a bit tighter. ~gb -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
