Bug 21606 - kdelibs4 needs to be updated in mga6 to ease upgrade and avoid conflicts
Summary: kdelibs4 needs to be updated in mga6 to ease upgrade and avoid conflicts
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: High critical
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: advisory MGA6-64-OK MGA6-32-OK
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2017-08-25 00:34 CEST by David Walser
Modified: 2017-09-01 23:11 CEST (History)
5 users (show)

See Also:
Source RPM: kdelibs4-4.14.30-2.mga6.src.rpm
CVE:
Status comment:


Attachments
Mga5 -> mga6 upgrade log (251.04 KB, application/x-zip-compressed)
2017-08-31 12:12 CEST, Patrick G
Details

Description David Walser 2017-08-25 00:34:51 CEST
In http://advisories.mageia.org/MGAA-2017-0066.html, kdelibs4 in mga5 was updated to 4.14.35.  We need to update it to match that in mga6 so as to not break upgrades.
Comment 1 Nicolas Lécureuil 2017-08-25 09:40:21 CEST
pushed in updates_testing

src.rpm:
        kdelibs4-4.14.35-1.mga6

CC: (none) => mageia
Assignee: kde => qa-bugs

Nicolas Lécureuil 2017-08-25 10:03:13 CEST

Summary: kdelibs4 needs to be updated in mga6 to match mga5 => kdelibs4 needs to be updated in mga6 to ease upgrade and avoid conflicts

Comment 2 David Walser 2017-08-25 12:02:36 CEST
Advisory:
----------------------------------------

The kdelibs4 package has been updated to version 4.14.35, containing the
latest bug fixes from upstream.  It had also been updated for Mageia 5 in
MGAA-2017-0066 and therefore needed to be upgraded in Mageia 6 to match.

References:
http://advisories.mageia.org/MGAA-2017-0066.html
----------------------------------------

Updated packages in core/updates_testing:
----------------------------------------
libkde3support4-4.14.35-1.mga6
libkdecore5-4.14.35-1.mga6
libkdefakes5-4.14.35-1.mga6
libkdesu5-4.14.35-1.mga6
libkdeui5-4.14.35-1.mga6
libkdnssd4-4.14.35-1.mga6
libkfile4-4.14.35-1.mga6
libkhtml5-4.14.35-1.mga6
libkimproxy4-4.14.35-1.mga6
libkio5-4.14.35-1.mga6
libkjsembed4-4.14.35-1.mga6
libkjs4-4.14.35-1.mga6
libkmediaplayer4-4.14.35-1.mga6
libknewstuff2_4-4.14.35-1.mga6
libknotifyconfig4-4.14.35-1.mga6
libkntlm4-4.14.35-1.mga6
libkdeclarative5-4.14.35-1.mga6
libkparts4-4.14.35-1.mga6
libkrosscore4-4.14.35-1.mga6
libkrossui4-4.14.35-1.mga6
libktexteditor4-4.14.35-1.mga6
libkunittest4-4.14.35-1.mga6
libkutils4-4.14.35-1.mga6
libsolid4-4.14.35-1.mga6
libthreadweaver4-4.14.35-1.mga6
libkpty4-4.14.35-1.mga6
libkjsapi4-4.14.35-1.mga6
libplasma3-4.14.35-1.mga6
libkunitconversion4-4.14.35-1.mga6
libkdewebkit5-4.14.35-1.mga6
libknewstuff3_4-4.14.35-1.mga6
libkcmutils4-4.14.35-1.mga6
libkprintutils4-4.14.35-1.mga6
libkidletime4-4.14.35-1.mga6
libkemoticons4-4.14.35-1.mga6
kdelibs4-core-4.14.35-1.mga6
kdelibs4-handbooks-4.14.35-1.mga6
kdelibs4-devel-4.14.35-1.mga6

from kdelibs4-4.14.35-1.mga6.src.rpm
Comment 3 Lewis Smith 2017-08-30 08:22:50 CEST
Testing MGA6/64

Updated what packages I had already installed from Classic ISO:
 kdelibs4-core-4.14.35-1.mga6
 lib64kdecore5-4.14.35-1.mga6
 lib64kdeui5-4.14.35-1.mga6
 lib64kdnssd4-4.14.35-1.mga6
 lib64kemoticons4-4.14.35-1.mga6
 lib64kfile4-4.14.35-1.mga6
 lib64khtml5-4.14.35-1.mga6
 lib64kio5-4.14.35-1.mga6
 lib64kjs4-4.14.35-1.mga6
 lib64kjsembed4-4.14.35-1.mga6
 lib64kntlm4-4.14.35-1.mga6
 lib64kparts4-4.14.35-1.mga6
 lib64krosscore4-4.14.35-1.mga6
 lib64ktexteditor4-4.14.35-1.mga6
 lib64solid4-4.14.35-1.mga6
and reverted to SDDM display manager -> Plasma desktop.
After a diverse session, no visible problems (beyond wrestling with Plasma itself...).
For me this is OK, but I prefer a note from a habitual SDDM/Plasma user.

CC: (none) => lewyssmith

Lewis Smith 2017-08-30 08:59:51 CEST

Whiteboard: (none) => advisory

Comment 4 Patrick G 2017-08-31 12:08:03 CEST
If upgrade from mga5 to mga6 is done via the CLI command :
  urpmi --replacefiles --auto-update --auto --download-all
as indicated in the release notes, the upgrade fails.

I used --download-all (with --retry, --resume) as a consequence of a bad internet link

Only the first transaction concerning priority packages is successful.
The second one (all other packages) failed.

There are also conflicts between kdepimlibs4-core-4.14.10-14.mga6.x86_64 (and other kde mga6 packages) and task-obsolete-6-125.mga6.noarch, but it's probably a consequence of kdelibs4 not being up to date in mga6.
I attach the upgrade log.

This drives to a system where gcc, glibc, dbus, binutils, x11 and others (a total of 163 packages) are upgraded but where the kernel, the nonfree nvidia driver and 2215 other packages are not.

My prod machine is in this case : I got mga5 kdelib update on 2017/08/25 and kdepim update on 2017/08/29 then, no luck,I try to upgrade to mga6 the day after.

KDE is the only DE I installed. I'm not sure I can reboot successfully due to the partial upgrade. So I don't know what to do except waiting for this mga6 update.

I push the priority to High as upgrade attempts could fail as long as the correction is not transferred to "Core update"

Priority: Normal => High
CC: (none) => patrick.g.mga

Comment 5 Patrick G 2017-08-31 12:12:24 CEST
Created attachment 9651 [details]
Mga5 -> mga6 upgrade log

failed mga upgrade after mga5 kdelib update
Comment 6 James Kerr 2017-08-31 13:03:34 CEST
(In reply to Lewis Smith from comment #3)
> Testing MGA6/64
> 
> For me this is OK, but I prefer a note from a habitual SDDM/Plasma user.

I've had all of 37 of these packages installed on mga6-64 since yesterday morning and have seen no regressions in normal use, although I only use a limited number of KDE applications.

CC: (none) => jim

Comment 7 James Kerr 2017-08-31 13:43:51 CEST
I also checked that the packages all installed cleanly on mga6-32 (in a vbox VM) but have done very little testing of that installation.
Comment 8 Lewis Smith 2017-08-31 20:13:27 CEST
@ Patrick G
Alas, this bug is not in itself about doing upgrades, but specifically that the kdelibs4 packages concerned update cleanly, and show no reversion (= continue to work) in their uprated version. The idea being that KDE4->Plasma upgrades stand a better chance of succeeding. Have you followed the advice in the Mageia 6 ERRATA, which documents an albeit complicated way of wining through? That was devised by someone with over 4000 pkgs.

@ James
Thank you for your tests. I am OKiing both architectures, and pushing this update.

Whiteboard: advisory => advisory MGA6-64-OK MGA6-32-OK
Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 9 Patrick G 2017-08-31 22:29:42 CEST
(In reply to Lewis Smith from comment #8)

Thanks for your answer.

> @ Patrick G
> Alas, this bug is not in itself about doing upgrades, but specifically that
> the kdelibs4 packages concerned update cleanly, and show no reversion (=
> continue to work) in their uprated version. 

Yes, as software engineer I understand that perfectly. Actually, in my real life job, I"m in the process of doing non-regression tests for a new version of one of our software :).

> Have you followed the advice
> in the Mageia 6 ERRATA, which documents an albeit complicated way of wining
> through? That was devised by someone with over 4000 pkgs.

I haven't read this part of the errata before you mentionned it but yes I tried that. But the cases are different. 
On my system, all rpm are already download, thanks to the --download-all option. URPMI already install all the 2215 (actually 2215 in mga5 becomes 2378 in mga6) packages in one transaction, without the need of the --split-length option. The problem is that the conflicting packages (with lower version) ARE on the mga6 media (and then in /var/cache/urpmi/rpms). So URPMI keeps more recent kdelib mga5 packages which conducts the install to fail.

> The idea being that KDE4->Plasma
> upgrades stand a better chance of succeeding. 
I just want to underline that systems with kde can't be upgraded to mga6 until this bug is solved. Furthermore for some cases like mine, the system is left in an inoperative state. That's why I raise the priority: if it happens to me it could happen to others.

Note for the future: don't update package in distib #n-1 if not updated in distrib #n, especially in upgrade period :).

kdelibs4 is also not updated in Cauldron (kdelibs4-core-4.14.30-2.mga6.x86_64.rpm).
Comment 10 Nicolas Lécureuil 2017-09-01 00:06:22 CEST
kdelibs in cauldron is planned to die in a near future
Comment 11 Mageia Robot 2017-09-01 23:11:20 CEST
An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2017-0072.html

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


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