Bug 22685

Summary:	libksieve conflict in updates testing
Product:	Mageia	Reporter:	Thomas Andrews <andrewsfarm>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins, mageia, marja11
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Bug Depends on:	22660
Bug Blocks:

Description Thomas Andrews 2018-03-02 23:59:06 CET

Description of problem
After activating all updates testing repositories and going to Mageia Update, I am seeing the following message:

"The following package has to be removed for others to be upgraded:
lib64kf5ksieveui_5-16.12.3-1.mga6.x86_64
 (due to unsatisfied libksieve == 2:16.12.3)"

This is in a vbox VM, 64-bit Plasma install from the Classical iso. This is a basic install, with no additional apps installed. The install is fully updated from the US kernel.org mirror, with tainted versions replacing non-tainted packages. 64 and 32 bit repositories are active. All "Debug" and "Backport" repositories have been removed, leaving only various "Release," "Updates," and "Updates Testing" repositories remaining. When I see this message, all  repositories are active.

If I say "no" to removing the package, Mageia Update opens, with no packages selected, and I can continue with other updates.

I do not see this on another 64-bit Plasma install on real hardware. That is my production install, and has several additional apps installed, some tainted, including the 32-bit version of Google Earth. It uses the same mirror, and the same repositories. Instead, I see a message about the tainted version of transcode being unable to be selected, due to a missing package - but I assume that is something for yet another bug report.

Comment 1 Marja Van Waes 2018-03-03 20:07:41 CET

bug 22660 hasn't been assigned to QA team, yet.

I suppose the Kde Application Stack isn't ready to be tested, yet.

Please try again when bug 22660 is assigned to QA team.

Depends on: (none) => 22660
CC: (none) => marja11
Assignee: bugsquad => kde

Comment 2 Nicolas Lécureuil 2018-03-04 09:51:44 CET

KDE Stack is ready for QA ( even if we need to this this one ).

CC: (none) => mageia

Comment 3 Thomas Andrews 2018-03-04 17:22:35 CET

Last night I performed the Plasma 5 update in a vbox guest in one operation. At first, I approved the removal of the package, but when I deselected all packages and tried only selecting those I was updating, after each selection I was again asked if I approved the removal of the package, even though I had not yet selected the packages that triggered the approval.

As you can probably understand, this was extremely annoying. In a situation where the user is going to install all updates in one operation, it probably isn't a serious problem. But, even in this minimal Plasma install, over 400 packages were updated. In a situation where the user must do the updates in stages, this would be intolerable.

Comment 4 Nicolas Lécureuil 2018-03-04 19:57:01 CET

(In reply to Thomas Andrews from comment #3)
> Last night I performed the Plasma 5 update in a vbox guest in one operation.
> At first, I approved the removal of the package, but when I deselected all
> packages and tried only selecting those I was updating, after each selection
> I was again asked if I approved the removal of the package, even though I
> had not yet selected the packages that triggered the approval.
> 
> As you can probably understand, this was extremely annoying. In a situation
> where the user is going to install all updates in one operation, it probably
> isn't a serious problem. But, even in this minimal Plasma install, over 400
> packages were updated. In a situation where the user must do the updates in
> stages, this would be intolerable.

of course this will be fixed.

Comment 5 Dave Hodgins 2018-03-04 22:21:11 CET

If necessary, we could first process an update for
lib64kf5ksieveui_5-16.12.3-1.mga6.x86_64 that removes the requires for
libksieve == 2:16.12.3.

CC: (none) => davidwhodgins

Comment 6 Thomas Andrews 2018-03-04 23:08:10 CET

I like that idea. From my view on the outside, it sounds like the simplest solution.

Comment 7 Nicolas Lécureuil 2018-03-04 23:25:32 CET

no, we need to clean this better.

Comment 8 Nicolas Lécureuil 2018-03-05 09:55:06 CET

please test again, new packages available.

Comment 9 Thomas Andrews 2018-03-05 20:05:56 CET

I'm still seeing the "needs to be removed" message in vbox. At first I thought the new packages hadn't filtered through yet, so I waited a few more hours. The second time, I looked further, and the new "sieve" packages had indeed been added. They all carried a new version number and the new date in the changelog.

Others in the rather long list of new dependencies for libksieve had not been changed to new versions. Could one or all of those be part of the problem?

Comment 10 Thomas Andrews 2018-03-05 23:26:33 CET

FWIW, I'm seeing the same message in a 32-bit vbox guest, using 32-bit package names, of course.

Comment 11 Nicolas Lécureuil 2018-03-06 00:38:25 CET

Please test new lbksieve to see if the message is still there.

libksieve-17.12.2-5.mga6

Comment 12 Thomas Andrews 2018-03-06 05:31:24 CET

Looks good here now, in both 64-bit and 32-bit vbox guests.

I would mark the bug resolved, but I don't know if you need confirmation from someone else first. Your call, I suppose.

Comment 13 Nicolas Lécureuil 2018-03-06 08:15:04 CET

enough for me :) ( as  i tested too )

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