Hi, I have given a try to dnf to my current cauldron, which used to be synced with urpmi --auto-update. I did: dnf check-update which worked fine and listed the packages to be upgraded. Then dnf distro-sync which failed with the messages in attachments, namely some conflicting packages but only under i586 (I am running x86_64) Therefore, I did a urpmi --auto-update, which succeeded without finding any conflicts. So either urpmi hides the conflicts, or dnf finds conflicts that do not exist!? Cheers, chris.
Created attachment 8673 [details] the error log of dnf
This might be a duplicate of bug 18343 (which needs a better summary than it has), I cannot tell from the attachment which version of those libraries was installed. See the note here: https://wiki.mageia.org/en/Using_DNF : > When dnf searches for dependencies, it'll stop looking when it finds a hit. > That means that dnf can want to install a 32bit library, even if you're on a 64 > bit system and installing the 64bit version of the same library is preferred. > You can add --exclude *.i586 to your command to avoid pulling in 32bit packages
CC: (none) => mageiatools, marja11Assignee: bugsquad => ngompa13
This is happening because your urpmi repository configuration includes 32-bit repositories, and you've installed 32-bit library packages. You need to enable the corresponding 32-bit repositories in DNF. It's a variant of bug 19480. The reason this happens is that mageia-repos (the package shipping the default repository configuration) has the 32-bit repositories disabled by default. It's mentioned in https://wiki.mageia.org/en/Using_DNF: > 32-bit repositories are turned off by default on 64-bit x86. Try enabling the correct repositories.
It also mentions you have tainted enabled, which means you need to also enable that through dnf config-manager.
Err, tainted and nonfree repositories enabled, I mean.
ah, very good, thanks for the clarifications. Then I close the bug as invalid! Thanks!
Status: NEW => RESOLVEDResolution: (none) => INVALID