Bug 22841 - Dependences mistake with plasma-desktop and kwallet
Summary: Dependences mistake with plasma-desktop and kwallet
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-31 13:37 CEST by Jybz
Modified: 2018-03-31 15:25 CEST (History)
1 user (show)

See Also:
Source RPM: plasma-desktop plasma-desktop-handbook kwalletmanager kwalletmanager-handbook
CVE:
Status comment:


Attachments

Description Jybz 2018-03-31 13:37:06 CEST
Hi !

Related to this bug https://bugs.mageia.org/show_bug.cgi?id=22840 I uninstalled kwalletmanager, I didn't saw, but it also removed plasma-desktop and maybe plasma-desktop-handbook.

When I reinstalled kwallet, it didn't reinstalled kwalletmanager, kwalletmanager-handbook, plasma-desktop, plasma-desktop-handbook.

When I reboot, I had no plasma anymore, and manage with "konsole". With drakconf, I saw that :

kwalletmanager depends ONLY on
  kwalletmanager-handbook

kwalletmanager-handbook depends ONLY on
  kwalletmanager

plasma-desktop depends on
  kwalletmanager
  or kwalletmanager-handbook
  or both

plasma-desktop-handbook depends on
  nothing previously mentionned.

Maybe other dependencies that is already installed. But on my opinion, it should be the opposite, all must depend on plasma-desktop.

I put this bug as major, because it is really hard to find what was removed (because no removed-packages-log) and when it removes plasma-desktop only for a "simple" software should not happend. Feel free to put the severity lower.
Nicolas Lécureuil 2018-03-31 15:11:56 CEST

Severity: major => normal
CC: (none) => mageia

Comment 1 Nicolas Lécureuil 2018-03-31 15:25:44 CEST
i won't remove kwallet* from requires on plasma-desktop.

They are needed for a better user experience.

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


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