Bug 1257417 - Can't disable @System repo in dnf
Can't disable @System repo in dnf
Product: Fedora
Classification: Fedora
Component: dnf (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-27 01:06 EDT by Sitsofe Wheeler
Modified: 2015-09-01 12:01 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-09-01 12:01:23 EDT
Type: Bug
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 Sitsofe Wheeler 2015-08-27 01:06:36 EDT
Description of problem:
When doing yum operations it's not possible to exclude the @System virtual repository.

Version-Release number of selected component (if applicable):

How reproducible:
Reproducible every time.

Steps to Reproduce:
1. Do a dnf info on a package that is installed e.g.
dnf info dnf
2. Note that multiple packages are returned.
3. Retry the search with all repositories disabled:
dnf --disablerepo='*' info dnf

Actual results:
Installed Packages
Name        : dnf
Arch        : noarch
Epoch       : 0
Version     : 1.0.1
Release     : 2.fc22
Size        : 714 k
Repo        : @System
From repo   : updates
Summary     : Package manager forked from Yum, using libsolv as a dependency resolver
URL         : https://github.com/rpm-software-management/dnf
License     : GPLv2+ and GPLv2 and GPL
Description : Package manager forked from Yum, using libsolv as a dependency resolver.

Expected results:
No information to be returned.

Additional info:
Trying to do
dnf --disablerepo='@System' info dnf
results in
Error: Unknown repo: '@System'
Comment 1 Honza Silhan 2015-09-01 12:01:23 EDT
DNF always adds installed packages and --(disable/enable)repo control just available repositories. You should rather use `dnf repoquery --available/--installed --info ...`. We don't plan to make a regression.

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