Bug 1158551 - RFE: please implement equivalent of yum-config-manager
Summary: RFE: please implement equivalent of yum-config-manager
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf-plugins-core
Version: 21
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1156511
TreeView+ depends on / blocked
 
Reported: 2014-10-29 15:47 UTC by Miroslav Suchý
Modified: 2015-03-26 09:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-26 09:06:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miroslav Suchý 2014-10-29 15:47:06 UTC
Description of problem:
Please implement equivalent of yum-config-manager

There is no replacement for yum-config-manager, which is very helpful

Comment 1 Jan Zeleny 2014-10-30 08:15:54 UTC
I'm not sure this should block the adoption of dnf in F22. The dnf team has never claimed 100% functionality and this is where I would draw the line - it might be a nice enhancement for the future but it's not something that would be absolutely crucial. Dnf's configuration is way more simple than that of yum.

Comment 2 Miroslav Suchý 2014-10-30 15:02:51 UTC
This BZ blocks bug 1156511. But bug 1156511 does not block adoption of dnf in F22. :) It is low priority bug.

Anyway - what I'm using is:
  yum-config-manager --disable fedora updates updates-testing
  yum-config-manager --enable rawhide

While this can be replaced by bunch of sed, it would be nice to preserve this little tool.

Comment 3 Michael Mráka 2015-01-29 14:29:29 UTC
Upstream pull request for dnf config-manager:

https://github.com/rpm-software-management/dnf-plugins-core/pull/65

Comment 4 Jan Zeleny 2015-01-30 08:01:39 UTC
Have you considered having this in extras plugins? What's the reason for having this in core?

Comment 5 Miroslav Suchý 2015-01-30 09:00:03 UTC
When you have this in core then DNF can behave identical to yum and in case of unavailable repo suggest to user:

 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable %(repoid)s

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=%(repoid)s.skip_if_unavailable=true


Or:


    msg = _('There are no enabled repos.\n'
            ' Run "yum repolist all" to see the repos you have.\n'
            ' You can enable repos with yum-config-manager --enable <repo>')


See:
  /usr/share/yum-cli/yumcommands.py
  /usr/share/yum-cli/yummain.py

If you move that to extras then most users will not have this command available and giving such suggestions would not be correct and as result in case those events you will leave users clueless and desperate.

Comment 6 Honza Silhan 2015-03-26 09:06:43 UTC
config-manager is in dnf-plugins-core [1]

[1] http://dnf-plugins-core.readthedocs.org/en/latest/config_manager.html


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