When trying to test an update of a package of mine, I realized that it was impossible to install it with dnf, while yum had no issue installing it. DNF: $ sudo dnf install -y crypto-policies-20140905-2.git4649b7d.fc21.noarch.rpm [sudo] password for nmav: Package crypto-policies-20140905-1.git4649b7d.fc21.noarch is already installed, skipping. Error: Nothing to do. YUM: $ sudo yum install -y crypto-policies-20140905-2.git4649b7d.fc21.noarch.rpm Loaded plugins: auto-update-debuginfo, langpacks Examining crypto-policies-20140905-2.git4649b7d.fc21.noarch.rpm: crypto-policies-20140905-2.git4649b7d.fc21.noarch Marking crypto-policies-20140905-2.git4649b7d.fc21.noarch.rpm as an update to crypto-policies-20140905-1.git4649b7d.fc21.noarch Resolving Dependencies --> Running transaction check ---> Package crypto-policies.noarch 0:20140905-1.git4649b7d.fc21 will be updated ---> Package crypto-policies.noarch 0:20140905-2.git4649b7d.fc21 will be an update while rpmdev-vercmp reports: crypto-policies-20140905-2.git4649b7d.fc21 > crypto-policies-20140905-1.git4649b7d.fc21
well, it seems that dnf update does the expected thing, even though that behavior is unclear from the man page.
To be precise, this is a duplicate of bug 1138700. Anyway, we need to reconsider the behaviour of the "install" command. And Nikos, feel free to open a bug if the man page does not describe something that it should. *** This bug has been marked as a duplicate of bug 1138700 ***
*** This bug has been marked as a duplicate of bug 1160950 ***