Bug 1081550

Summary: [PATCH] yum shell doesn't accept skip_broken as a valid config option
Product: [Fedora] Fedora Reporter: Xavier Bachelot <xavier>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: admiller, james.antill, packaging-team-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:44:31 UTC Type: Bug
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
Enable skip_broken option (untested patch)
none
Fix a typo in the man page
none
Add more options to yum shell
none
Add more options to yum shell none

Description Xavier Bachelot 2014-03-27 14:41:41 UTC
Description of problem:
I'm trying to activate the skip packages with broken deps feature from within the yum shell.
After reading the man page, I came up with :
config skip_broken 1
but this is not recognized as a valid config option.

Version-Release number of selected component (if applicable):
yum-3.4.3-137.fc20.noarch

How reproducible:
Always

Steps to Reproduce:
1. enter yum shell 
2. type 'config skip_broken 1'
3.

Actual results:
> config skip_broken 1

    config arg [value]
      args: debuglevel, errorlevel, obsoletes, gpgcheck, assumeyes, exclude
        If no value is given it prints the current value.
        If value is given it sets that value.

Expected results:
Broken deps skipping is enable.


Additional info:
A number of other configuration options are likely not accepted from the yum shell, but are equally valid options.

Comment 1 Xavier Bachelot 2014-03-27 14:43:46 UTC
Created attachment 879517 [details]
Enable skip_broken option (untested patch)

Comment 2 Xavier Bachelot 2014-03-27 16:20:26 UTC
Created attachment 879534 [details]
Fix a typo in the man page

Comment 3 Xavier Bachelot 2014-03-27 16:21:24 UTC
Created attachment 879535 [details]
Add more options to yum shell

Comment 4 Xavier Bachelot 2014-03-27 17:21:55 UTC
Created attachment 879546 [details]
Add more options to yum shell

Comment 5 Fedora End Of Life 2015-05-29 11:23:08 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-06-29 19:44:31 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.