Bug 223488

Summary: yum-skip-broken makes weird decisions, and fails to skip the correct packages
Product: [Fedora] Fedora Reporter: Ralf Ertzinger <redhat-bugzilla>
Component: yum-utilsAssignee: Tim Lauridsen <tim.lauridsen>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-12 16:14:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Console output of the above commands none

Description Ralf Ertzinger 2007-01-19 17:57:05 UTC 
Description of problem:
Please see the attached console log for details.
I tried to update to current rawhide today, which had a missing dependency. The
current (not updated) package state is listed in the file, too.

yum --obsoletes upgrade
fails (missing dep)

yum --obsoletes upgrade --ignore-broken
fails quite strangely, with a missing glibc dep (huh?)

The correct solution would be to skip the directfb update, as shown by
yum --obsoletes upgrade --exclude directfb


Version-Release number of selected component (if applicable):
yum-skip-broken-1.0.1-1.fc7

How reproducible:
Always (in this particular configuration)

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Ralf Ertzinger 2007-01-19 17:57:05 UTC 
Created attachment 146012 [details]
Console output of the above commands
Comment 2 Tim Lauridsen 2007-01-26 14:00:56 UTC 
it dont looks like a problem with in the plugin, the 
Error: No Package Matching glibc.i686
message is caused by a exception in the yum packageSack(returnNewestByNameArch).

The exception occours when depsolver tries to solve dependencies for 
glibc-common.i386 0:2.5.90-15

the following command should should give the samme error, without skip-broken i
s running.
 
yum --obsoletes upgrade glibc-common

it look like that glibc.i686 cant be found in the packageSack, this is very
strange .

The depcheck for glibc.i686 0:2.5.90-15, has been done for already
so i should be in packageSack.

--> Populating transaction set with selected packages. Please wait.
---> Package glibc.i686 0:2.5.90-15 set to be updated
--> Running transaction check
--> Processing Dependency: glibc-common = 2.5.90-15 for package: glibc
--> Processing Dependency: glibc = 2.5.90-14 for package: glibc-headers
--> Processing Dependency: glibc = 2.5.90-14 for package: glibc-devel
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Package glibc-common.i386 0:2.5.90-15 set to be updated
---> Package glibc-devel.i386 0:2.5.90-15 set to be updated
---> Package glibc-headers.i386 0:2.5.90-15 set to be updated
--> Running transaction check

Dont know what can be done to solve the issue, maybe there is bug in the
dependency section for the glibc-common spec.

There is also some issues in the yum code, the traceback should be catched by
the depsolver and reported as a normal dep error.
Comment 3 Tim Lauridsen 2007-02-07 11:56:31 UTC 
Look like the depsolving of glibc.i686 not only is giving problems when running
skip-broken.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227603

https://www.redhat.com/archives/fedora-test-list/2007-February/msg00317.html
Comment 4 Tim Lauridsen 2008-03-12 16:14:03 UTC 
yum >= 3.2.10 in current rawhide have much improved '--skip-broken' buildin, so
please try 

yum remove yum-skip-broken
yum install pygpgme
yum install --enablerepo=development update yum

to check it out.