Description of problem: Trying to upgrade a Mageia 5 installation to Cauldron results in some errors about conflicting packages. See urpmi messages below. # urpmi --auto-update --auto --test (snip) Installation failed: kmailtransport = 16.08.0 is needed by kio5-smtp-16.08.0-3.mga6.x86_64 While some packages may have been installed, there were failures. A requested package cannot be installed: kmailtransport-16.08.0-3.mga6.x86_64 (due to conflicts with kdepimlibs4-core-4.14.10-8.mga6.x86_64) (snip) How reproducible: Always. At lest in the current state of the repositories. Steps to Reproduce: 1. Start with a fully up-to-date Mageia 5 installation that has kontact installed. Note that kontact is not actually necessary but is sufficient because it depends on the conflicting packages. 2. Remove all repositories with "urpmi.removemedia -a". 3. Add a set of Cauldron repositories with ""urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.x86_64.list'" 4. Do a test update with "urpmi --auto-update --auto --test" 5. See error messages about conflicting packages.
Assignee: bugsquad => kde
>A requested package cannot be installed: >kmailtransport-16.08.0-3.mga6.x86_64 (due to conflicts with kdepimlibs4-core-4.14.10-8.mga6.x86_64) This come from this file that both packages provide the same: /usr/share/config.kcfg/mailtransport.kcfg
CC: (none) => geiger.david68210
Should be fixed with kdepimlibs4-core-4.14.10-9.mga6
closing
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED
I'm still seeing the same package conflict error message with the newer kdepimlibs4-core-4.14.10-9.mga6. # LANGUAGE=C urpmi --auto-select --test --noclean (snip) Installation failed: kmailtransport = 16.08.0 is needed by kio5-smtp-16.08.0-3.mga6.x86_64 While some packages may have been installed, there were failures. A requested package cannot be installed: kmailtransport-16.08.0-3.mga6.x86_64 (due to conflicts with kdepimlibs4-core-4.14.10-9.mga6.x86_64) (snip)
will be fixed with KDE Apps 16.08.1 ( later today ).
I'm still seeing the same package conflict error message. I'll remove kontact and update the system to test for other bugs.