yum problem glibc x86_64

[Neal Becker]

seth vidal wrote:

> On Wed, 2004-04-21 at 14:31, Neal D. Becker wrote:
>> I think I'm making some progress.  My guess about the problem is correct.
>> There are also issues with some other packages, including openldap, which
>> also has multiple versions.
>> 
>> I believe this is a serious problem for yum to deal with.  I suspect what
>> it needs to do is to treat these multiple versions as completely
>> independent packages, with independent dependencies.
>> 
>> So basically, an x86_64 machine wants x86_64 packages, but if there is an
>> i386 package, it should be treated as an independent upgrade when upgrade
>> is requested, and the logic for choosing i386/i686 should apply to that.
>> Does that make sense?
> 
> it does do this.
> 
> I need some more information to help you debug.
> 
> You should also make sure your repository that you're pulling from is
> consistent, if it is not then all bets are off.
> 

I'm trying to use:
http://mirror.linux.duke.edu/pub/fedora/linux/core/development

All others I tried kept crapping out in various ways.

After using rpm -e --justdb for glibc and for openvpn I'm getting closer (I
think).  I used this to get yum to stop being confused about the duplicated
packages for glibc and for openvpn (x86_64 version + i386/i686 version). 
Also I think xorg-x11-libs.

What I'm doing:

yum update

I have a brand new virgin FC2T2 system, with maybe a few updates.  When I
did the initial install, I selected "install everything".

I am NOT asking to just update x86_64 packages.  I said just "update".  I
think yum seems to be deciding to only update x86_64 packages, but I didn't
say it should.

Now yum gets as far trying the test install, here's what happens:
Errors reported doing trial run
package glibc-2.3.3-22 (which is newer than glibc-2.3.3-20) is already
installed
package glibc-common-2.3.3-22 (which is newer than glibc-common-2.3.3-20) is
already installed
file /etc/gconf/2/path from install of GConf2-2.6.0-4 conflicts with file
from package GConf2-2.5.90-1.1
file /etc/gconf/schemas/desktop_default_applications.schemas from install of
gnome-vfs2-2.6.0-5 conflicts with file from package gnome-vfs2-2.5.91-2
file /etc/gconf/schemas/desktop_gnome_url_handlers.schemas from install of
gnome-vfs2-2.6.0-5 conflicts with file from package gnome-vfs2-2.5.91-2
file /etc/gconf/schemas/system_http_proxy.schemas from install of
gnome-vfs2-2.6.0-5 conflicts with file from package gnome-vfs2-2.5.91-2
file /etc/gconf/schemas/system_smb.schemas from install of
gnome-vfs2-2.6.0-5 conflicts with file from package gnome-vfs2-2.5.91-2
file /usr/bin/catchsegv from install of glibc-common-2.3.3-20 conflicts with
file from package glibc-common-2.3.3-22
file /etc/fonts/fonts.conf from install of fontconfig-2.2.1-10 conflicts
with file from package fontconfig-2.2.1-8.1
file /etc/xinetd.d/sgi_fam from install of fam-2.6.10-9 conflicts with file
from package fam-2.6.10-7
file /usr/share/mimelnk/video/x-ms-asf.desktop from install of
kdelibs-3.2.2-3 conflicts with file from package
kaffeine-0.4.1-0.lvn.1.1.90
file /usr/share/mimelnk/video/x-ms-wmv.desktop from install of
kdelibs-3.2.2-3 conflicts with file from package
kaffeine-0.4.1-0.lvn.1.1.90
file /usr/share/services/mms.protocol from install of kdelibs-3.2.2-3
conflicts with file from package kaffeine-0.4.1-0.lvn.1.1.90

rpm -q yum
yum-2.0.6-1

rpm -q --qf "%{name}-%{version}-%{release}.%{arch}\n" glibc
glibc-2.3.3-22.x86_64

yum -c yum.conf list glibc
Gathering header information file(s) from server(s)
Server: Fedora Core 1.91 - x86_64 - Base
Server: development
Finding updated packages
Downloading needed headers
Looking in Available Packages:
Name                                Arch   Version                  Repo
--------------------------------------------------------------------------------
glibc                               i386   2.3.3-20                
development
glibc                               i686   2.3.3-20                
development

Looking in Installed Packages:
Name                                Arch   Version                  Repo
--------------------------------------------------------------------------------
glibc                               x86_64 2.3.3-22                 db

I have no idea how to determine if a mirror is "consistent".  Maybe if it's
not so loaded that it doesn't time out on me, it's because nobody's using
it because it isn't consistent? :)