Bug 94750

Summary: Auto-remove installed dependencies when uninstalling package (Fedora/dnf)
Product: PackageKit Reporter: freedesktop
Component: backend-yumAssignee: Richard Hughes <richard>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: medium CC: jhasse, mail
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description freedesktop 2016-03-29 22:05:44 UTC 
On Fedora 23 (PackageKit 1.0.11), when a package is installed through any of dnf, pkcon or GNOME Software, the installed dependencies are recorded (presumably by DNF). dnf remove [package] will then remove the package and all the dependencies that were installed at its installation, unless they're otherwise needed.

However, uninstalling via GNOME Software or pkcon remove [package] doesn't remove the package.

This results in the accumulation of unneeded dependencies when uninstalling using a PackageKit frontend.

Example on my system:

# 1. Install sound-juicer using GNOME Software or either command below
#    -> Installs sound-juicer and libdiscid
pkcon install sound-juicer
# or
dnf install sound-juicer

# 2a. Remove sound-juicer with dnf (regardless of installation method)
#     -> Removes sound-juicer and libdiscid

# 2b. Remove sound-juicer with GNOME Software or the below pkcon command
#     -> Only removes sound-juicer
pkcon remove sound-juicer
Comment 1 AsciiWolf 2018-02-05 12:26:19 UTC 
Same issue on Ubuntu (backend-apt). Also being discussed here: https://github.com/hughsie/PackageKit/issues/201
Comment 2 AsciiWolf 2018-02-05 12:34:45 UTC 
Related GNOME Software bugreport: https://bugzilla.gnome.org/show_bug.cgi?id=776640
Comment 3 Richard Hughes 2018-08-21 15:52:41 UTC 
We moved the upstream bugtracker to GitHub a long time ago. If this issue still affects you please re-create the issue here: https://github.com/hughsie/PackageKit/issues
 
Sorry for the impersonal message, and fingers crossed your issue no longer happens. Thanks.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.