Description of problem: Upgrading Mageia 5 to 6, by using "urpmi.removemedia -a ; urpmi.addmedia --distrib MAGEIA_6_REP_URL", results in file conflicts between packages lib64pq5.7-9.4.15-1.mga6.x86_64 and lib64pq5-9.4.15-1.mga5.x86_64 . "urpmi --auto-update" messages follow. Installation failed: file /usr/lib64/libpq.so.5.7 from install of lib64pq5.7-9.4.15-1.mga6.x86_64 conflicts with file from package lib64pq5-9.4.15-1.mga5.x86_64 Version-Release number of selected component (if applicable): $ # On Mageia 5 (before upgrade) $ urpmf -f -m --name lib64pq5-9.4.15-1.mga5.x86_64 Core Updates:lib64pq5-9.4.15-1.mga5.x86_64 $ # On Mageia 6 (after partial upgrade) $ urpmf -f -m --name lib64pq5.7-9.4.15-1.mga6.x86_64 Core Updates:lib64pq5.7-9.4.15-1.mga6.x86_64 How reproducible: Always. Steps to Reproduce: 1. Start with a Mageia 5 system with package lib64pq5-9.4.15-1.mga5.x86_64 installed. 2. Remove all current Mageia 5 repositories with the command "urpmi.removemedia -a" 3. Add Mageia 6 repositories with the command "urpmi.addmedia --distrib MAGEIA_6_REP_URL" 4. Upgrade the system with the command "urpmi --auto-update" 5. Check for "Installation failed" and "conflicts with file from package" messages.
Sometimes file conflicts or failed installations are caused by some interdependent updates not ending up in the same transaction. With the "--split-length=0" option of urpmi all updates should end up in one big transaction. Please try whether that helps. If it doesn't, then please attach the journalctl (as root) output from the upgrade attempt CC'ing our registered postgresql9.4 maintainer.
CC: (none) => cjw, marja11Keywords: (none) => NEEDINFO
A month later and no reply. So there are no logs or whatever to investigate, therefore closing this report as OLD
Status: NEW => RESOLVEDResolution: (none) => OLD
(In reply to Marja van Waes from comment #2) > A month later and no reply. Sorry! Somehow, I missed your comment. I will try "--split-length=0" the next time I see a similar issue.