Description of problem: When installing a package that has been obsoleted by another one, DNF does not process those obsoletes to actually use the newer package for that name. Instead, it installs the original package. However, doing a "dnf update" afterwards will properly trigger the obsoletes and replace the package. This issue is observable when trying to install dnf-system-upgrade plugin by doing "dnf install fedup". You get the old fedup instead of the new plugin. Running "dnf update" will trigger the replacement of the package. Version-Release number of selected component (if applicable): 1.1.3-1.fc22 How reproducible: Always Steps to Reproduce: 1. sudo dnf install fedup Actual results: Installs fedup-0.9.2-1.fc22 Expected results: Installs dnf-system-upgrade (which obsoletes and provides fedup)
Everyone has the right to install the obsoleted package. DNF can print the warning that the package is obsoleted another package. Agree? The reason why system-upgrade plugin is replacing fedup during the upgrade is that it provides higher version of fedup than fedup package version.
I suppose so, but if system-upgrade plugin obsoletes AND provides fedup (as opposed to just obsoleting), then I would normally expect it to install the system-upgrade plugin if I run "dnf install fedup" because system-upgrade is a provider of fedup, right?
*** This bug has been marked as a duplicate of bug 1096506 ***