[SOLVED] how to slackpkg update gpg ?

bassmadrigal · 04-10-2017, 12:19 PM

What version of Slackware do you have installed?

If it is the 64bit version, please provide the output of the following command:

Code:

ls -la /var/log/packages/*i?86*

If it is the 32bit version, please provide the output of the following command:

Code:

ls -la /var/log/packages/*x86_64*

The commands are used to find if you have any packages installed that are the wrong ARCH. It probably also wouldn't hurt to find what versions of aaa_elflibs and readline you have installed.

Code:

ls -la /var/log/packages/{aaa_elflibs,readline}*

audriusk · 04-10-2017, 12:31 PM

You also say that you run -current, but the output in your first post says:

Code:

Downloading http://bear.alienbase.nl/mirrors/slackware/slackware-14.2/GPG-KEY...

nodir · 04-10-2017, 12:38 PM

https://paste.debian.net/926898/

Code:

user$ ls -la /var/log/packages/{aaa_elflibs,readline}*
-rw-r--r-- 1 root root 2525 Apr  8 18:10 /var/log/packages/aaa_elflibs-14.2-i586-23
-rw-r--r-- 1 root root 1550 Apr  8 18:10 /var/log/packages/readline-6.3-i586-2
user$

audriusk · 04-10-2017, 12:55 PM

Quote:

Originally Posted by nodir

https://paste.debian.net/926898/

Code:

user$ ls -la /var/log/packages/{aaa_elflibs,readline}*
-rw-r--r-- 1 root root 2525 Apr  8 18:10 /var/log/packages/aaa_elflibs-14.2-i586-23
-rw-r--r-- 1 root root 1550 Apr  8 18:10 /var/log/packages/readline-6.3-i586-2
user$

This seems to be 32 bit version of Slackware, but it is partially 14.2 (stable) and partially -current. That is, some packages are from 14.2 and some from -current.

If you were running -current, as you claimed in this thread, you have accidentally downgraded some packages to 14.2.

bassmadrigal · 04-10-2017, 12:57 PM

If you are running -current, then you downgraded your aaa_elflibs and readline packages (and probably others). For -current, they should be aaa_elflibs-14.2-i586-28 and readline-7.0-i586-1

EDIT: audriusk beat me to it

nodir · 04-10-2017, 01:02 PM

well: accidently.
I sure got no idea how this could happen.

audriusk · 04-10-2017, 01:04 PM

Actually, only a few packages were downgraded:

Code:

$ # pkgs.txt contains your list of packages, the newest ones seem to have been changed on April 8th.
$ grep 'Apr  8' pkgs.txt | grep -v _SBo
-rw-r--r-- 1 root root   2525 Apr  8 18:10 /var/log/packages/aaa_elflibs-14.2-i586-23
-rw-r--r-- 1 root root   7929 Apr  8 18:10 /var/log/packages/glibc-solibs-2.23-i586-1
-rw-r--r-- 1 root root   1550 Apr  8 18:10 /var/log/packages/readline-6.3-i586-2

You could try upgrading them to versions from -current, hopefully this will be enough to fix your system.

audriusk · 04-10-2017, 01:11 PM

Quote:

Originally Posted by nodir

well: accidently.
I sure got no idea how this could happen.

Selected the wrong mirror URL? slackware-14.2 instead of slackware-current. From the output in your first post, it looks like that's what happened.

montagdude · 04-10-2017, 01:12 PM

EDIT: looks like some others beat me to it. Anyway, the still-relevant part:

Fix those packages by downloading them from a Slackware-current mirror and running upgradepkg on them. Then, once slackpkg is working again, first be sure to set your mirror to a -current mirror instead of 14.2. Then do `slackpkg update gpg` and `slackpkg upgrade-all` to make sure there are no remaining packages from 14.2.

nodir · 04-11-2017, 06:00 AM

thanks.
The bad news: I don't know how to fix those packages. I run into error messages about libreadline, whatever i try

Code:

ROOT# slackpkg upgrade  readline

Checking local integrity... awk: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
DONE
awk: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
Looking for readline in package list. Please wait... DONE

No packages match the pattern for upgrade. Try:

	/usr/sbin/slackpkg install|reinstall 


ROOT# slackpkg reinstall  readline

awk: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
Looking for readline in package list. Please wait... DONE

No packages match the pattern for reinstall. Try:

	/usr/sbin/slackpkg install|upgrade 


ROOT# slackpkg install  readline

awk: error while loading shared libraries: libreadline.so.7: cannot open shared object file: No such file or directory
Looking for readline in package list. Please wait... DONE

No packages match the pattern for install. Try:

	/usr/sbin/slackpkg reinstall|upgrade 


ROOT#

Code:

ROOT# grep -v '^#'  /etc/slackpkg/mirrors 
http://spout.ussg.indiana.edu/linux/slackware/slackware-current/
ROOT#

--------
Edit:
I downloaded the packages via webbrowser from here:
https://spout.ussg.indiana.edu/linux...ent/slackware/
and installed them with

Code:

upgradepkg --reinstall --install-new readline-7.0-i586-1.txz

Then ran "slackpkg update gpg" and "slackpkg update" and "slackpkg upggrade-all"
Magic !

Thanks to all who helped, and a bunch.

Alien Bob · 04-11-2017, 06:25 AM

Apparently you have not upgraded the aaa_elflibs package which contains "libreadline.so.7". Is it still blacklisted in your /etc/slackpkg/blacklist file? If so, remove the blacklist. This is slackware-current, the aaa_elflibs needs to be upgraded always.

Op top of that, you could also download and 'upgradepkg' the readline package (which also contains libreadline.so.7) manually. Get it from: http://spout.ussg.indiana.edu/linux/...7.0-i586-1.txz.

nodir · 04-11-2017, 06:31 AM

Nothing blacklisted in the blacklist file.

to me it looks as if the second part of my previous post did the trick. didn't it?

Code:

ROOT# locate libreadline.so
/usr/lib/libreadline.so.7.0
/usr/lib/libreadline.so
/usr/lib/libreadline.so.7
/usr/lib/libreadline.so.5.2
/usr/lib/libreadline.so.5
/usr/lib/libreadline.so.6
/usr/lib/libreadline.so.6.3
ROOT#

Alien Bob · 04-11-2017, 06:52 AM

Quote:

Originally Posted by nodir

Nothing blacklisted in the blacklist file.

to me it looks as if the second part of my previous post did the trick. didn't it?

You added that second part while I was writing my response apparently.