Bug 974461 - RFE: add 'debuginfo-remove' as cleanup counterpart to existing 'debuginfo-install'
RFE: add 'debuginfo-remove' as cleanup counterpart to existing 'debuginfo-ins...
Status: NEW
Product: Fedora
Classification: Fedora
Component: yum-utils (Show other bugs)
Unspecified Linux
unspecified Severity low
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-06-14 04:39 EDT by collura
Modified: 2014-02-02 17:33 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description collura 2013-06-14 04:39:55 EDT
Description of problem:

There exists 'debuginfo-install' to conveniently install debuginfo on demand for some argument package.  

There doesnt seem to be (?) a corresponding command to conveniently remove the debuginfo on demand when disk space is tight or no longer need the package. 

(though if i remember there is an automatic periodic uninstall when accumulated debuginfo reaches 4GB ?) 
(at one point i think there was a 'clean the trash' button in the package manager gui but i dont see it anymore ?)

There should be a 'debuginfo-remove' command to simplify the removal of debuginfo of a certain package (or all) on demand for whatever reason.  
It would basically go into '/var/cache/abrt-di' and remove the dustbunnies.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. install debuginfo for a package to triage a crash
2. package gets all fixed, ya
3. debuginfo still resides on system taking up space

Actual results:

 dustbunnies accumulate.

Expected results:

 should be easy way to sweep the dustbunnies.

Additional info:
Comment 1 collura 2013-06-14 05:17:00 EDT
old, related


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