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.
ROOT# slackpkg upgrade-all
You need the GPG key of Slackware Linux Project <security@slackware.com>.
To download and install that key, run:
# slackpkg update gpg
You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.
ROOT# slackpkg update gpg
Downloading http://bear.alienbase.nl/mirrors/slackware/slackware-14.2/GPG-KEY...
--2017-04-10 17:28:27-- http://bear.alienbase.nl/mirrors/slackware/slackware-14.2/GPG-KEY
Resolving bear.alienbase.nl... 163.172.25.142
Connecting to bear.alienbase.nl|163.172.25.142|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1572 (1.5K)
Saving to: ‘/tmp/slackpkg.7lNcI1/gpgkey’
/tmp/slackpkg.7lNcI1/gpgkey 100%[=============================================================================>] 1.54K --.-KB/s in 0s
2017-04-10 17:28:27 (58.3 MB/s) - ‘/tmp/slackpkg.7lNcI1/gpgkey’ saved [1572/1572]
ROOT#
If i run slackpkg upgrade-all again, i get the same error.
thanks in advance.
I am using current, there doesn't seem to be osuosl mirror for it.
btw: slackpkg update gpg outputs it would save the file to ‘/tmp/slackpkg.BzU9yL/gpgkey’,
but there isn't a slackpkg.BzU9yL directory at all (hence no gpgkey either)
Are you running slackpkg update AFTER running slackpkg update gpg and BEFORE running slackpkg upgrade-all? I ask because I was having a similar problem recently, and it was simply because I neglected to do this...
(These are lines 301-304 in slackpkg.) It seems to me like something must be going wrong in these lines. Perhaps temporarily turning off the stdout and stderr redirection to /dev/null would shed some light on the issue. In other words, change those lines to:
ROOT# getfile ${SOURCE}GPG-KEY $TMPDIR/gpgkey
bash: getfile: command not found
ROOT# slackpkg search getfile
awk: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
Looking for getfile in package list. Please wait... DONE
No package name matches the pattern.
Pretty lost.
editing /usr/sbin/slackpkg gives.
Code:
ROOT# slackpkg update gpg
Downloading http://ftp.mirrorservice.org/sites/ftp.slackware.com/pub/slackware/slackware-current/GPG-KEY...
--2017-04-10 18:39:27-- http://ftp.mirrorservice.org/sites/ftp.slackware.com/pub/slackware/slackware-current/GPG-KEY
Resolving ftp.mirrorservice.org... 212.219.56.184, 2001:630:341:12::184
Connecting to ftp.mirrorservice.org|212.219.56.184|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1572 (1.5K)
Saving to: ‘/tmp/slackpkg.Ihaplm/gpgkey’
/tmp/slackpkg.Ihaplm/gpgkey 100%[=============================================================================>] 1.54K --.-KB/s in 0s
2017-04-10 18:39:27 (44.4 MB/s) - ‘/tmp/slackpkg.Ihaplm/gpgkey’ saved [1572/1572]
gpg: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
ROOT#
awk: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
That's not a good error. This says you're missing the readline and aaa_elflibs packages, as that file is containted in both of them.
Did you already run slackpkg upgrade-all, but maybe had the wrong mirror picked (32bit instead of 64bit or vice versa)? This could install the wrong version of packages and could break a lot of things in your install. This could easily lead to issues preventing the gpg key from being properly imported.
That's not a good error. This says you're missing the readline and aaa_elflibs packages, as that file is containted in both of them.
Did you already run slackpkg upgrade-all, but maybe had the wrong mirror picked (32bit instead of 64bit or vice versa)? This could install the wrong version of packages and could break a lot of things in your install. This could easily lead to issues preventing the gpg key from being properly imported.
I didn't change the mirrors before the error occured.
After that i changed them, but couldn't run "slackpkg upgrade-all" anymore, hence i can't have run it.
Well, it's hard to tell what exactly has happened to your system. Before scrapping it completely you could try reinstalling the aaa_elflibs and readline packages. I don't think slackpkg will work, but you can try that first. If that fails, try getting them from your installation media or a mirror (but make sure you are using the package for the correct architecture - 32 bit or 64 bit). Then use:
where you replace /path/to/txz/file with the actual path. I'm not sure if upgradepkg will work or not with your system in its current state, but it's also worth a try.
But I think it's quite possible that those are not the only things that are messed up with your system.
Last edited by montagdude; 04-10-2017 at 11:58 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.