> I updated today, and looked at the conflicts. One of them is for > python2-modulemd and python3-modulemd. They are obsolete, being > replaced by libmodulemd. But it isn't happening for some reason. > > package python2-dnf-2.7.5-8.fc28.noarch requires python2-modulemd, but > none of the providers can be installed > - package libmodulemd-1.0.4-2.fc28.x86_64 obsoletes python2-modulemd > < 1.3.4 provided by python2-modulemd-1.3.3-1.fc28.noarch > - cannot install the best update candidate for package > python3-modulemd-1.3.3-1.fc28.noarch > - cannot install the best update candidate for package > python2-dnf-2.7.5-8.fc28.noarch > > package python3-dnf-2.7.5-8.fc28.noarch requires python3-modulemd, but > none of the providers can be installed > - package libmodulemd-1.0.4-2.fc28.x86_64 obsoletes python3-modulemd > < 1.3.4 provided by python3-modulemd-1.3.3-1.fc28.noarch > - cannot install the best update candidate for package > python3-dnf-2.7.5-8.fc28.noarch > - cannot install the best update candidate for package > python2-modulemd-1.3.3-1.fc28.noarch > > When I try to remove them so I can install their replacement, > libmodulemd, dnf rejects the transaction because it would lead to > removing itself. > > Is the workaround to use rpm --force to remove python[23]-modulemd, and > then use rpm to install libmodulemd? > > Or, is there a fix in the works, and I should just wait? The modulemd package got retired in f28 and rawhide ahead of a new DNF that uses libmodulemd being available. As a result, DNF could not be installed at the time. Modulemd should only have been retired after the new DNF was available. As soon as I found this out this morning, I unretired modulemd and retagged the modulemd build in them. So modulemd should be back now, and sanity restored. _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
