Red Hat Bugzilla – Bug 1267886
STOP rename python-dnf to python2-dnf and back all the time
Last modified: 2015-10-13 09:37:02 EDT
first it was "python-dnf", then it was "python2-dnf", now it's "python-dnf" and you maintainers obviously never heard about Obsoletes/Provides in SPEC files to avoid spit early testers in their face by for them to deal with "rpm --nodpes"
Package python-dnf-plugins-core-0.1.12-2.fc22.noarch has missing requires of python2-dnf >= ('0', '1.1.2', None)
Package python-dnf-plugins-core-0.1.12-2.fc22.noarch has missing requires of python2-dnf < ('0', '2.0', None)
I really think f22 branch updates of dnf* packages should be updated separately, I see always merge happens from master and then struggle for having successful f22 koji build due to python-dnf/python2-dnf package names.
it would be enough *one* time make a decision how it is named and the just use Provides/Obsoletes and just rebuild one the plugins to keep it in sync, not break upgrades and don't force users to deal with --noeps
to be honest it scares me terrible that a group maintaining a package manager don't use Provides/Obsoletes in a sane way
1.1.2-2 was completly broken in F22 and did not show any updates
1.1.2-4 works at least for basic operations
python-dnf-plugins-core with 1.1.2-4 has a broken dep
It has been released for Fedora 22 by a mistake and package was removed from repository. Sorry for it.