Bug 216742

Summary: Feature request: Automatically exclude packages when dependencies cannot be met
Product: [Fedora] Fedora Reporter: Karl Lattimer <karl>
Component: yumAssignee: Jeremy Katz <katzj>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
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: 2006-11-27 22:29:49 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:

Description Karl Lattimer 2006-11-21 19:44:23 UTC 
Just running pup now and I noticed something that was sort of missing in a way. 

When yum is unable to find files to resolve dependencies it could exclude them
and continue to attempt to find a dependency solution. There have been many
times in the past that I have had packages on certain repositories conflicting
or not updating in line with core and extras and the upshot is that they break
the update process. It seems logical to me that there should be a way to exclude
packages where dependency resolution cannot be met during the update and
continue possibly stating that those packages won't be updated because a
dependency is failing. 

Eventually those packages should get updated as the repositories come back into
alignment. 

For instance, in my most recent update openoffice and wine required an
older/newer version of libxslt than my system or was available had going back to
the update selection and excluding openoffice and wine from the update process
then allowed me to proceed. Surely there must be a way of doing this automatically.
Comment 1 Jeremy Katz 2006-11-27 22:29:49 UTC 
There's a plugin to provide this functionality.  In general, the right behavior
is that the repository shouldn't be broken.