yum update failure glibc.i686 on Fedora 7 Test 2 x64 yum 3.1.4-1.fc7

[John Hall]

Since at least yesterday afternoon yum updates have failed.
Could it be an incorrect version string in one of the package dependencies?
Config error on my part?
Below is the end /error message from
yum -y --skip-broken upgrade The rest of the output of the command is
attached.

Checking deps for glibc.x86_64 0-2.5.90-19 - u
--> Processing Dependency: glibc-common = 2.5.90-19 for package: glibc
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
Checking deps for glibc-common.x86_64 0-2.5.90-19 - u
Checking deps for glibc-common.x86_64 0-2.5.90-17 - None
Checking deps for glibc.x86_64 0-2.5.90-19 - u
--> Processing Dependency: glibc-common = 2.5.90-17 for package: glibc
Error: No Package Matching glibc.i686

[Michal Jaegermann]

On Thu, Mar 22, 2007 at 12:45:05PM -0400, John Hall wrote:
>  Since at least yesterday afternoon yum updates have failed.
>  Could it be an incorrect version string in one of the package dependencies?
>  Config error on my part?
>  Below is the end /error message from
>  yum -y --skip-broken upgrade The rest of the output of the command is attached.
>  
>  Checking deps for glibc.x86_64 0-2.5.90-19 - u
>  --> Processing Dependency: glibc-common = 2.5.90-19 for package: glibc
>  --> Restarting Dependency Resolution with new changes.
>  --> Running transaction check
>  Checking deps for glibc-common.x86_64 0-2.5.90-19 - u
>  Checking deps for glibc-common.x86_64 0-2.5.90-17 - None
>  Checking deps for glibc.x86_64 0-2.5.90-19 - u
>  --> Processing Dependency: glibc-common = 2.5.90-17 for package: glibc
>  Error: No Package Matching glibc.i686 
Why do you have in this picture 0-2.5.90-19, 0-2.5.90-17 and
glibc.i686?   Do you have indeed the later installed?  Maybe
the problem is in 'skip-broken' plugin which has troubles in
a multilib situation?

I did not notice anything like the above so far but on my test
rig I do not have any x86 packages installed.

   Michal

[John Hall]

Hi Michal, I have installed 0-2.5.90-17 and would be upgrading to 19
It seems to be trying to create a situation where both would be installed.

The problem is not with --skip-broken

Yum runs in cycles without end with out --skip-broken

I ran
yum -y upgrade glibc and got a file conflict.
between -17 and -19 versions
I am currently trying to erase and add in the packages one at a time.
I may erase alot of packages and then ad them back to correct the problem.
John
On 3/22/07, Michal Jaegermann <michal(a)harddata.com&gt; wrote:
>  On Thu, Mar 22, 2007 at 12:45:05PM -0400, John Hall wrote:
>  > Since at least yesterday afternoon yum updates have failed.
>  > Could it be an incorrect version string in one of the package
>  dependencies?
>  > Config error on my part?
>  > Below is the end /error message from
>  > yum -y --skip-broken upgrade The rest of the output of the command is
>  attached.
>  >
>  > Checking deps for glibc.x86_64 0-2.5.90-19 - u
>  > --> Processing Dependency: glibc-common = 2.5.90-19 for package: glibc
>  > --> Restarting Dependency Resolution with new changes.
>  > --> Running transaction check
>  > Checking deps for glibc-common.x86_64 0-2.5.90-19 - u
>  > Checking deps for glibc-common.x86_64 0-2.5.90-17 - None
>  > Checking deps for glibc.x86_64 0-2.5.90-19 - u
>  > --> Processing Dependency: glibc-common = 2.5.90-17 for package: glibc
>  > Error: No Package Matching glibc.i686
>
>  Why do you have in this picture 0-2.5.90-19, 0-2.5.90-17 and
>  glibc.i686?   Do you have indeed the later installed?  Maybe
>  the problem is in 'skip-broken' plugin which has troubles in
>  a multilib situation?
>
>  I did not notice anything like the above so far but on my test
>  rig I do not have any x86 packages installed.
>
>     Michal
>
>  --
>  fedora-test-list mailing list
>  fedora-test-list(a)redhat.com
>  To unsubscribe:
>  https://www.redhat.com/mailman/listinfo/fedora-test-list
>

[Michal Jaegermann]

On Fri, Mar 23, 2007 at 02:47:20AM -0400, John Hall wrote:
>  
>  I ran
>  yum -y upgrade glibc and got a file conflict.
>  between -17 and -19 versions 
That usually means that you have both x86 and x86_64 variants
installed and that a mirror from which you are trying to run
updates has/had different versions for both.  Packages for different
architectures have to be updated "in a lockstep" or you will see
such conflicts.

Metadata should have expired in the meantime anyway but in a case
you got a mess there, due to not entirely healthy mirror you were
trying to get that stuff from, try if 'yum clean metadata' will
straighten things out.

In case you need a glibc update only for x86_64 then running

     yum -y upgrade glibc.x86_64

gives a helpful hand to yum. Also when you know that something
is not entirely healthy then running 'yum -y...' is not so great
idea.

   Michal