Bug 23131 - M5->6 upgrade fails with many errors especially kde-l10n (& other) conflicts, and failed dependencies
Summary: M5->6 upgrade fails with many errors especially kde-l10n (& other) conflicts,...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 21340
  Show dependency treegraph
 
Reported: 2018-06-07 20:11 CEST by Lewis Smith
Modified: 2018-07-08 15:09 CEST (History)
2 users (show)

See Also:
Source RPM: mgaapplet
CVE:
Status comment:


Attachments
Log file of successful upgrade as per previous comment (115.56 KB, application/x-bzip)
2018-07-08 15:08 CEST, Lewis Smith
Details

Description Lewis Smith 2018-06-07 20:11:05 CEST
Description of problem:
I created a special upgrade test M5 system from the 5.1 Classic ISO, 6 desktops hence including KDE; updated it (668 pkgs); added a large number of additional packages, often KDE-oriented, -> 3300 in total. Using LXDE, screensaver disabled,
 # urpmi --auto-update
 $ killall mgaapplet
 $ mgaapplet --testing
Eventually this shows the 'upgrade' systray icon, clicking which leads to a few dialogues.
Trying to upgrade has been painful in that it often seems to start OK, then simply stops - forever. After many attempts, it started in earnest. I did NOT ask for 'download all in one', which may have a bearing. It warned of 8.3Gb downloads (say 10h); the disk space is there.
It does very long bursts of downloads, then often pops a dialogue about conflicts (majority kde-l10n) & failed dependencies, OKing which continues. I have the impression it re-downloaded many things. After several such enormous cycles over 24h, it eventually failed. I hesitate to attach the log because it is, uncompressed, >6Mb. For the moment, I retain it in the hope that someone will ask for specific aspects. I have tried in vain manual editing...
Looking at it I wonder whether many of the failed dependencies were due to not doing the upgrade in one go. Should I try that?
The pop-up failure dialogues are much smaller; should I perhaps save just those? - they seem to have the essential. I should have thought of this sooner...
I think that if the omnipresent kde-l10n-en_GB-16.12.3-2.mga6.noarch conflicts could be sorted, the rest could be looked at.
I await feedback about how to progress this major issue, happy to furnish info from the upgrade log.
Comment 1 Marja Van Waes 2018-06-08 21:53:23 CEST
(In reply to Lewis Smith from comment #0)

> I think that if the omnipresent kde-l10n-en_GB-16.12.3-2.mga6.noarch
> conflicts could be sorted, the rest could be looked at.
> I await feedback about how to progress this major issue, happy to furnish
> info from the upgrade log.

Thanks for the test, Lewis!

I think KDE team will need the upgrade logs.

For the non-KDE conflicts & failed dependencies, we need separate bug reports.

Assignee: bugsquad => kde
CC: (none) => marja11

Marja Van Waes 2018-06-08 21:54:32 CEST

Blocks: (none) => 21340

Comment 2 Lewis Smith 2018-06-10 09:21:54 CEST
@Marja : thanks for your comments, and the pointer to the tracker bug.

Following some very enlightening discussion with Martin, it is clear that it is futile attempting any KDE upgrade until 23037 kde-l10n-en_GB mass conflicts is sorted. So I am holding off until then. And hope is near for that one.

Then it should be easier to identify other (if any) problems, and posting upgrade logs should become sensible.
Comment 3 Martin Whitaker 2018-07-02 23:45:33 CEST
The bugs causing the widespread kde conflicts should now be fixed.

CC: (none) => mageia

Comment 4 Lewis Smith 2018-07-08 15:05:43 CEST
(In reply to Martin Whitaker from comment #3)
> The bugs causing the widespread kde conflicts should now be fixed.
Thanks for the prompt! An e-mail would have been OK.
----------------------------------------------------
At last I have re-run my test M5->6 upgrade, with considerable success: essentially, NO conflicts or other other errors en route. Great work.
START
6-desktop M5 system with many added applications, including everything KDE I could find. The system brought up-to date. 3303 pkgs.

Running under XFCE from LightDM, no screensaver or locker.
 # urpmi --auto-update --auto   [to be sure]
 $ killall mgaapplet
 $ rpm -qa | wc -l
 3303               [currently installed pkgs]
 # journalctl -f    [to capture initial O/P incl log file name; then ^C]
 # journalctl -f    [another terminal, to monitor all subsequent O/P to end]
 $ LC_ALL=C mgaapplet --testing
This eventually shows the 'upgrade' arrow in Systray. Click that!

This launched the upgrade process. I default answered the few initial dialogues (downloading in batches). Then there were *no more* all the way to the end!
8.3 Gb downloads, 3634 pkgs to upgrade. At 450Kb/s, over 5 1/2h.

NO error dialogues all the way, the only iffies were some red system journal msgs about some PAM-using pkgs, which passed without incident.
It ended with a 'successful upgrade' dialogue. Foolishly clicked the 'reboot' option which luckily did not work, so I could then copy out the log file & close terminal sessions.
 $ rpm -qa | wc -l
 4176          [post-upgrade pkgs]
 $ rpm -qa | grep .mga5 | wc -l
 317           [Mageia 5 packages not upgraded]

AFTER
Re-booting the upgraded system ended with the "good luck - press any key to continue" console. I changed the display manager with drakdm to SDDM to see whether that would make a difference (a waste of time), & re-booted. Worse: it stopped at the Grub prompt.
Re-booted to a different installed system, chrooted to the upgraded one:
 # update-grub
Re-booted to the upgraded system, that now worked: SDDM showing Plasma - which worked. As did XFCE from SDDM. Curiosity: using drakdm to revert to LightDM, this was shown already selected. Re-starting X or re-booting stayed with SDDM. Trivial.

So it looks as if only 'update-grub' was missing somewhere. This was a massive test, and vindicates that M5->6 upgrade *is* viable. If you have to fiddle with the end result, so be it.
Need to find the upgrade tracker bug to comment that OK.

Will attach the compressed log file for the record.
Comment 5 Lewis Smith 2018-07-08 15:08:12 CEST
Created attachment 10273 [details]
Log file of successful upgrade as per previous comment

Compressed log file of successful 5->6 upgrade as per previous comment.
Comment 6 Lewis Smith 2018-07-08 15:09:15 CEST
Good as far as I am concerned.

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


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