Opened 8 months ago

Closed 7 months ago

Last modified 7 months ago

#1018 closed System Defect (fixed)

pc-metapackagemanager don't perform pkg autoremove

Reported by: yurkis Owned by: kris
Priority: trivial Milestone:
Component: System Tool Version: 10.0-RELEASE
Keywords: Cc: trac-bugs@…

Description

After uninstalling some big meta package (like gnome 3, for example) most of packager related in this meta package is still in the system. Looks like meta package manager don't perform 'pkg autoremove' after meta package deinstalation.

Change History (4)

comment:1 Changed 7 months ago by yurkis

  • Owner set to kris

Kris, please take a look

comment:2 Changed 7 months ago by kris

Yep, I will be adding it shortly. We tried it back in earlier pkgng version and it caused some pretty bad issues, but with 1.2.x it looks to have stabilized.

comment:3 Changed 7 months ago by kris

  • Resolution set to fixed
  • Status changed from new to closed

Here you go!

https://github.com/pcbsd/pcbsd/commit/26c7c829fed3423dbf93b7ce1a740dc12d3ef2e4

I added this to pc-pkgmanager, not pc-metapkgmanager. Since this is just running the "pkg autoremove" command, it acts as a front-end to display list of potential removal items, then does it if the user OKs the list.

For now I don't want to add any "automatic" pruning, until we get more testing with 'pkg autoremove' and confirm it doesn't go horribly wrong somewhere.

comment:4 Changed 7 months ago by cabpa

Hi Kris,

When can autoremove fix be tested because when I uninstalled NVIDIA from the Basic View in the Package Manager, I can still instance of NVIDIA in Advanced view? I don't know if the packages in the Advanced View are the same/related packages in the Advanced View

Note: See TracTickets for help on using tickets.