Bug 1225227

Summary:	dnf appears to be incorrectly comparing package versions
Product:	[Fedora] Fedora	Reporter:	Bruno Wolff III <bruno>
Component:	dnf	Assignee:	Packaging Maintenance Team <packaging-team-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	bruno, jsilhan, jzeleny, mluscon, packaging-team-maint, pnemade, rholy, tim.lauridsen, vmukhame
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-05-27 07:50:39 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 Bruno Wolff III 2015-05-26 21:21:32 UTC

Description of problem:

While working on upgrading a system from f21 to f22 piecemeal to work around a router issue, I noticed that some packages were not being updated that should. wesnoth is a particular example. It looks like 1.12.2-1.fc22 is not considered to be an upgrade from 1.12.2-1.fc21.

This happened on two different systems.

When I use yum to try to do the update, it tries to update a lot of other packages as well, so perhaps what is really happening is that something is blocking the update when dnf does its depsolve, but that a misleading nothing to do response is used in place of something better describing the issue.

[root@wolff bruno]# dnf update wesnoth
Last metadata expiration check performed 14:33:23 ago on Tue May 26 01:31:36 2015.
Dependencies resolved.
Nothing to do.
Complete!
[root@wolff bruno]# rpm -q wesnoth
wesnoth-1.12.2-1.fc21.i686
[root@wolff bruno]# dnf list available wesnoth
Last metadata expiration check performed 14:33:56 ago on Tue May 26 01:31:36 2015.
Available Packages
wesnoth.i686                    1.12.2-1.fc22                    updates-testing

[root@wolff bruno]# rpm -q dnf
dnf-1.0.0-1.fc22.noarch

Comment 1 Jan Zeleny 2015-05-27 07:50:39 UTC

I think the actual problem is different and it's masked: when I try to install wesnoth on f21 system, there is no problem. However, when I try to do the same with --releasever=22, the following problem error message appears:

package wesnoth-1.12.2-1.fc22.x86_64 requires libboost_locale.so.1.57.0()(64bit), but none of the providers can be installed


Therefore it seems to be a dependency problem, rather than dnf problem. Closing as NOTABUG. To verify it's your case, you can try running dnf update wesnoth --best, it will likely show you the same error message. You can also try running dnf check-update if the update is listed there. Feel free to reopen if you find the problem is elsewhere.

Comment 2 Bruno Wolff III 2015-05-29 18:27:41 UTC

My real problem with this is that there was no error message, which could lead one to think there was no update available. I expect that when doing an update without --best, that you'd get some indication that there were updates available that couldn't be installed.
I could open a separate RFE bug for this?

Comment 3 Radek Holy 2015-06-01 07:48:09 UTC

bug 1210445

Comment 4 Bruno Wolff III 2015-06-01 19:50:50 UTC


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