Bug 19683 - kwalletmanager >= 16.08.2-1.mga6 is needed by kwalletmanager-handbook-16.08.2-1.mga6.noarch
Summary: kwalletmanager >= 16.08.2-1.mga6 is needed by kwalletmanager-handbook-16.08.2...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-30 09:39 CET by Marja Van Waes
Modified: 2016-10-30 11:44 CET (History)
3 users (show)

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

Attachments
journalctl ouput (3.77 KB, text/plain)
2016-10-30 10:41 CET, Marja Van Waes 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Marja Van Waes 2016-10-30 09:39:39 CET 
When upgrading from Mageia 5 to cauldron (with urpmi --auto-update, after editing /etc/urpmi/urpmi.cfg), one of the errors that keeps occurring, even after running urpmi --auto-update 10 times or so, is:

     kwalletmanager >= 16.08.2-1.mga6 is needed by kwalletmanager-handbook-16.08.2-1.mga6.noarch


Manually upgrading with "urpmi kwalletmanager kwalletmanager-handbook" worked fine.
Comment 1 Nicolas Lécureuil 2016-10-30 10:23:09 CET 
i think you have a local issue because all work fine here.

CC: (none) => mageia

Comment 2 Marja Van Waes 2016-10-30 10:41:42 CET 
Created attachment 8610 [details]
journalctl ouput

I think the problem is that kwalletmanager and kwalletmanager-handbook aren't done in the same transaction while upgrading.

Transaction 3610 is from the 10th 5=> cauldron upgrade with urpmi attempt, when the kwalletmanager error appeared.

Transaction 3743 is from manually upgrading with 
 "urpmi kwalletmanager kwalletmanager-handbook"

Is there a way to force interdepending packages to be upgraded in the same transaction, or is it only when upgrading with "urpmi --auto-update" that that doesn't happen?
Comment 3 Marja Van Waes 2016-10-30 10:49:24 CET 
@ Thierry

Is using "urpmi --auto-update" after adjusting urpmi.cfg the _wrong_ way to detect upgrade issues that might appear when using a "normal" upgrade method, like with upgrading with the iso or via mageia-applet-upgrade helper?

In other words, are interdependant packages put into the same transaction handled better when using a normal upgrade method, even if they are not when using urpmi --auto-update?

CC: (none) => thierry.vignaud

Comment 4 David GEIGER 2016-10-30 10:59:04 CET 
In a big update like you did, I uses "urpmi --auto-update --test" so it download first all packages and says if upgrade is possible or not and then I run "urpmi --auto-select" to install all packages.

CC: (none) => geiger.david68210

Comment 5 Marja Van Waes 2016-10-30 11:20:39 CET 
(In reply to David GEIGER from comment #4)
> In a big update like you did, I uses "urpmi --auto-update --test" so it
> download first all packages and says if upgrade is possible or not and then
> I run "urpmi --auto-select" to install all packages.

Thanks :-)

If that means this bug and bug 19682 are invalid, then please close them as invalid
Comment 6 Marja Van Waes 2016-10-30 11:44:05 CET 
2016:10:30:11:15 < marja> neoclust: david_david: can I close my kwalletmanager and kigo bugs as invalid?
2016:10:30:11:16 < marja> (or wait for tv to reply?)
2016:10:30:11:30 < david_david> marja: I think you can close them :)

Closing :-)

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.