Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The removed_scripts and removed_packages directories can use a lot of disk space #33

Open
piterpunk opened this issue Apr 18, 2023 · 3 comments · May be fixed by #34
Open

The removed_scripts and removed_packages directories can use a lot of disk space #33

piterpunk opened this issue Apr 18, 2023 · 3 comments · May be fixed by #34
Labels
enhancement

Comments

@piterpunk
Copy link
Collaborator

When a package is upgraded, its old installation scripts and list of files are kept under /var/lib/pkgtools. After a while, a long running system can have a lot of stale files under these directories. As you can see with the following output:

punk@number5:/usr/libexec/slackpkg$ du -skx /var/lib/pkgtools/removed_scripts/
58244   /var/log/removed_scripts/
punk@number5:/usr/libexec/slackpkg$ du -skx /var/lib/pkgtools/removed_packages/
382968  /var/log/removed_packages/

Slackpkg is the tool that is usually used to upgrades Slackware systems, so it seems to be the best place to implement some routine to do a janitorial job of these directories.
@piterpunk piterpunk linked a pull request Apr 18, 2023 that will close this issue
Open
@opty77
Copy link

opty77 commented Apr 21, 2023 •
edited
Loading

On an more than 18 years old system:

opty@zeryk:~$ du -skx /var/lib/pkgtools/removed_scripts/ /var/lib/pkgtools/removed_packages/
24732   /var/lib/pkgtools/removed_scripts/
97800   /var/lib/pkgtools/removed_packages/

Please keep this disabled by default like now forever and add confirmation for sure.

Edit: Doubt about the second part here instead of PR so I'm better duplicating there.

@piterpunk
Copy link
Collaborator Author

Please keep this disabled by default like now forever and add confirmation for sure.

Edit: Doubt about the second part here instead of PR so I'm better duplicating there.

Answered at PR

@opty77
Copy link

opty77 commented May 26, 2023

Five weeks ago I was also thinking about whether slackpkg should even do this as it (slackpkg) doesn't manage packages directly but using pkgtools.

On the other hand it might never see the production so whatever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Keep N last package metadata piterpunk/slackpkg
2 participants
@piterpunk @opty77