Bug 333673 - Cannot uninstall a package when other packages depend on it
Summary: Cannot uninstall a package when other packages depend on it
Status: RESOLVED DUPLICATE of bug 331730
Alias: None
Product: muon
Classification: Applications
Component: muon (show other bugs)
Version: 2.2.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jonathan Thomas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-21 06:58 UTC by Victor Varvaryuk
Modified: 2015-01-15 15:44 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
The package could not be marked for installation or upgrade: (187.75 KB, image/png)
2014-04-21 06:58 UTC, Victor Varvaryuk 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Varvaryuk 2014-04-21 06:58:24 UTC 
Several months ago when I marked for uninstallation a package which other packages depend on, those packages were marked for removal too.

At some point something happened to Muon, and I can uninstall only a package if there are no other packages depending on it. i am getting this kind of message:

> The "linux-image-extra-3.11.0-12-generic" package could not be marked for installation or upgrade:

Reproducible: Always
Comment 1 Victor Varvaryuk 2014-04-21 06:58:44 UTC 
Created attachment 86195 [details]
The package could not be marked for installation or upgrade:
Comment 2 Martin Zbořil 2014-04-22 04:57:55 UTC 
I have the same issue.

I am trying to get rid of most gnome based stuff i have installed together with ubuntu/kubuntu, and while doing so i get this message.

the way around is to use apt, but muon would be my preferred way to do it as it is very well designed for such tasks, keep up good work!
Comment 3 Fabio Correa 2014-06-15 19:24:39 UTC 
This bug was previously reported at https://bugs.kde.org/show_bug.cgi?id=331730
Comment 4 Aleix Pol 2015-01-15 15:44:42 UTC 
Can you please provide input in the other bug report? Maybe we can fully understant the issue then.

*** This bug has been marked as a duplicate of bug 331730 ***