Bug 1389273 - --releasever option is not working properly
Summary: --releasever option is not working properly
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 10:31 UTC by Zuzana Svetlikova
Modified: 2017-02-01 12:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-01 12:57:48 UTC
Type: Bug


Attachments (Terms of Use)

Description Zuzana Svetlikova 2016-10-27 10:31:25 UTC
Description of problem:
--releasever option doesn't work (properly)

Version-Release number of selected component (if applicable):
dnf-2.0.0-0-rc1.4.fc26
rpm-4.13.0-0-rc2.1.fc26

How reproducible:
always

Steps to Reproduce:
1. dnf info nodejs --releasever=24
2. # wrong output, repos not synced
3. dnf clean all
4. # repos sync, but output is still wrong

Actual results:
Repos don't sync, shows info for rawhide.
After dnf clean all repos sync, but dnf still shows info only for rawhide.

Expected results:
dnf syncs repos and shows correct info.

Additional info:

Comment 1 Michal Luscon 2016-11-22 15:51:39 UTC
Hi,

are you still able to reproduce this?

Comment 2 Zuzana Svetlikova 2017-02-01 12:55:23 UTC
Yes, this is still reproducible.

Comment 3 Igor Gnatenko 2017-02-01 12:57:48 UTC
$ dnf --releasever=24 --disablerepo=\* --enablerepo=fedora --enablerepo=updates info nodejs

DNF doesn't know differences between rawhide and released repos, it takes those which are enabled.


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