Rpm install not clearing old package metadata
See original GitHub issueWhen upgrading via the rpm it looks like the beer-garden packages aren’t getting fully removed.
When upgrading from an older version I can see some extra directories in the lib/python3.6/site-packages
directory:
- brewtils-2.4.1-py3.6.egg-info
- brewtils-2.4.4.dist-info
- brew_view-2.4.4-py3.6.egg-info
- brew_view-2.4.7.dist-info
It’s also happening with non-beergarden packages:
- six-1.11.0.dist-info
- six-1.12.0.dist-info
The old directories are all empty, so this may not actually be a problem.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
during upgrade, how does rpm know which files to delete?
Install the files that the RPM provides. Run the %post section of the RPM. Run the %preun of the old package. Delete any...
Read more >dnf clean all does not clean package metadata for local repos
Workaround is to run 'clean metadata' instead. Can you confirm whether it's fixed in dnf-1.0.
Read more >How to install/remove/query/update RPM packages in Linux ...
1. Make sure there are no RPM processes left running on your system. · 2. Delete the lock files that RPM uses: ·...
Read more >AIX: Old Open Source RPM Packages Clean-Up then use Yum
The problem makes adding new RPM packages impossible. The problem is probably due to using RPM packages from difference source over a number...
Read more >yum + how to remove unused rpm/patch on linux redhat
The old package is not installed any longer, just the new one. ... a "yum clean all" will remove them, along with the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, I think we should generate logging configs if they don’t exist.
Also, the upgrade currently errors if the init script is missing (since it can’t stop the service). We should probably be better about handling that.