Bug 23223 - During upgrade of mga5/kde4 system to mga6, many conflicts occur due to selection of obsolete kde-l10n package
Summary: During upgrade of mga5/kde4 system to mga6, many conflicts occur due to selec...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks: 21340
  Show dependency treegraph
 
Reported: 2018-06-24 22:40 CEST by Martin Whitaker
Modified: 2018-06-25 14:02 CEST (History)
0 users

See Also:
Source RPM: perl-URPM
CVE:
Status comment:


Attachments
Suggested fix (1.31 KB, text/plain)
2018-06-24 23:08 CEST, Martin Whitaker
Details

Description Martin Whitaker 2018-06-24 22:40:44 CEST
[split out from bug 23202]
I still occasionally see the major failure reported in bug 23037 comment 67. The root cause of the failure is

chosen attica-5.42.0-1.mga6.x86_64 for attica[== 5.42.0-1.mga6]
selecting attica-5.42.0-1.mga6.x86_64
installed package kde-l10n-en_GB-4.14.3-1.mga5.noarch is conflicting with attica-5.42.0-1.mga6.x86_64 (Conflicts: kde-l10n[< 15.04.0])
promoting kde-l10n-en_GB-16.12.3-2.mga6.noarch|kde-l10n-en_GB-16.12.3-2.mga6.noarch because of conflict above
chosen kde-l10n-en_GB-16.12.3-2.mga6.noarch for kde-l10n-en_GB|kde-l10n-en_GB
selecting kde-l10n-en_GB-16.12.3-2.mga6.noarch

Once the obsolete kde-l10n-en_GB-16.12.3-2.mga6.noarch has been selected, it has a cascade effect, leading to what's seen in attachment 10246 [details].
Comment 1 Martin Whitaker 2018-06-24 23:08:51 CEST
Created attachment 10251 [details]
Suggested fix
Comment 2 Martin Whitaker 2018-06-24 23:13:03 CEST
The attached patch fixes the problem. It causes no failures in the urpmi test suite (when tested on a mga6 system).

Keywords: (none) => PATCH
Assignee: bugsquad => thierry.vignaud

Comment 3 Thierry Vignaud 2018-06-25 14:02:56 CEST
ACK, local test is OK, push in progress

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.