Bug 231523 - yum-skip-broken option should default to True
yum-skip-broken option should default to True
Product: Fedora
Classification: Fedora
Component: yum-utils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-03-08 15:35 EST by Christopher Stone
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 1.1.2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-18 04:42:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Christopher Stone 2007-03-08 15:35:36 EST
I see no reason why someone should have to type --skip-broken every time they
use yum after installing the yum-skip-broken rpm.  Why would someone install the
plug-in and not want it on by default?

If someone would actually want to install the plug-in and not use it, they can
disable it in the skip-broken.conf file.
Comment 1 Tim Lauridsen 2007-03-09 05:15:57 EST
Because you don't want to run the skip broken test everytime, because it take
much longer time to complete the depsolving.
So installing the plugin is adding some extra funtionality to yum, but it is not
the same as you want to use it every time.
Most of the time you will just run 'yum update' and if you get an error you will
run 'yum --skip-broken update'.

Maybe adding a 'check_always' option to conf file, could be an idea, if you want
to always make the skip-broken check. 
Comment 2 Christopher Stone 2007-03-10 17:46:51 EST
Adding check_always to the conf would be fine by me, as long as there is some
way to default the --skip-broken option to true without modifying skip-broken.py
Comment 3 Tim Lauridsen 2007-03-13 07:55:03 EDT
I have added a 'check_always' option in upstream CVS.
It will be available in next yum-utils release.

Note You need to log in before you can comment on or make changes to this bug.