[SOLVED] Empty "/KEEP" directory created by several multilib packages on -current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Huh, I have this, as well with Mako on slackware-current. I don't remember having it on 14.2, though. I figured I screwed up somewhere installing something, but haven't deleted it, because I didn't know if something were actually using it.
--- convertpkg-compat32.orig 2019-07-20 21:39:15.707079303 -0700
+++ convertpkg-compat32 2019-07-20 21:40:09.557619807 -0700
@@ -349,8 +349,8 @@
if [ $(find KEEP/ | wc -l) -gt 1 ];
then
rsync -a KEEP/ ./
- rm -rf KEEP
fi
+rm -rf KEEP
# Keep documentation we might be required to keep, or is just polite:
if [ -d usr/doc ]; then
I fixed it and uploaded a completely fresh set of 'compat32' packages.
The best you can do is download all the packages below https://slackware.nl/people/alien/mu...re64-compat32/ and run "upgradepkg --reinstall --install-new" on them so that you can be certain you have all of them installed at the correct release.
If you still have it, it must still be part of one of the installed packages.
Check /var/log/packages to find out which package installed it, and re-download that from a multilib repository, or re-generate it using the latest compat32-tools.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.