Bug 1611664

Summary:	DNF sees "best" candidate from modular repo and is complaining
Product:	[Fedora] Fedora	Reporter:	Igor Raits <igor.raits>
Component:	dnf	Assignee:	rpm-software-management
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	29	CC:	dmach, jmracek, marko.haverinen, mblaha, mhatina, nphilipp, packaging-team-maint, rpm-software-management, vmukhame
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-27 13:38:05 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:

Description Igor Raits 2018-08-02 15:07:31 UTC

Description of problem:
[brain@igor-t480s ~]$ sudo dnf update
Repository 'koji-rawhide' is missing name in configuration, using id.
Last metadata expiration check: 0:04:56 ago on Thu 02 Aug 2018 04:59:56 PM CEST.
Dependencies resolved.

 Problem: cannot install the best update candidate for package ripgrep-0.8.1-10.fc29.x86_64
  - package ripgrep-0.8.1-10.module_1963+f854a682.x86_64 is disabled
Nothing to do.
Complete!

Version-Release number of selected component (if applicable):
dnf-3.0.4-1.fc29.noarch
libdnf-0.16.1-2.fc29.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Have a rawhide system
2. Install ripgrep from rawhide repo
3. Try to run dnf update

Actual results:
Complaining that it can't install best candidate for ripgrep.

Expected results:
DNF doesn't complain.

Additional info:
ripgrep exists both in modular repo and in rawhide. Modular doesn't have a default so it should not be enabled.

Comment 1 Jan Kurik 2018-08-14 08:39:22 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 2 Nils Philippsen 2018-09-14 15:42:47 UTC

Confirming that this still happens:

--- 8< ---
root@rawhide:~> dnf update --best
Last metadata expiration check: 1:23:31 ago on Fri 14 Sep 2018 15:44:40 CEST.
Error:
 Problem 1: cannot install the best update candidate for package gimp-2:2.10.6-2
.fc30.x86_64
  - package gimp-2:2.10.6-2.module_2129+0d46cbd3.x86_64 is disabled
 Problem 2: cannot install the best update candidate for package gimp-libs-2:2.1
0.6-2.fc30.x86_64
  - package gimp-libs-2:2.10.6-2.module_2129+0d46cbd3.x86_64 is disabled
--- >8 ---

Comment 3 Marko Haverinen 2018-09-27 13:28:12 UTC

I think I have the same issue. I'm on F29 beta, upgraded to it yesterday.

sudo dnf upgrade
Last metadata expiration check: 0:05:32 ago on to 27. syyskuuta 2018 16.07.16.
Dependencies resolved.

 Problem 1: cannot install the best update candidate for package gimp-2:2.10.6-2.fc29.x86_64
  - package gimp-2:2.10.6-2.module_2129+8576126a.x86_64 is disabled
 Problem 2: cannot install the best update candidate for package gimp-libs-2:2.10.6-2.fc29.x86_64
  - package gimp-libs-2:2.10.6-2.module_2129+8576126a.x86_64 is disabled
 Problem 3: cannot install the best update candidate for package libnghttp2-1.33.0-1.fc29.x86_64
  - package libnghttp2-1.33.0-1.module_2177+2526c218.x86_64 is disabled
 Problem 4: cannot install the best update candidate for package libuv-1:1.23.0-1.fc29.x86_64
  - package libuv-1:1.23.0-1.module_2177+2526c218.x86_64 is disabled
 Problem 5: cannot install the best update candidate for package nodejs-1:10.11.0-1.fc29.x86_64
  - package nodejs-1:10.11.0-1.module_2200+adbac02b.x86_64 is disabled
 Problem 6: cannot install the best update candidate for package npm-1:6.4.1-1.10.11.0.1.fc29.x86_64
  - package npm-1:6.4.1-1.10.11.0.1.module_2200+adbac02b.x86_64 is disabled
 Problem 7: cannot install the best update candidate for package perl-HTTP-Tiny-0.076-1.fc29.noarch
  - package perl-HTTP-Tiny-0.076-1.module_2073+eebc5b71.noarch is disabled
Nothing to do.
Complete!

Comment 4 Jaroslav Mracek 2018-09-27 13:38:05 UTC


*** This bug has been marked as a duplicate of bug 1616118 ***