[SOLVED] Slackware update destroyed my multilib.

wolfslacker · 03-03-2017, 12:11 PM

Destroyed is probably too strong a word. Anyway I'm running slackware 64 stable and I recently installed some updates. After rebooting, I couldn't run steam anymore. I instead got a message about needing to install "additional packages". The packages listed (curl, python-apt, xterm, etc..) have already been installed. I checked other apps and found Quicken via wine would also not start. So I'm thinking the updates may have overwritten some of my multilib files. I checked on Alien's website to see if there was a way to re-install multilib but could not find a solution. Any advice would be helpful. I didn't find any other problems with my other apps, only the 32-bit apps are affected.

BCarey · 03-03-2017, 12:41 PM

You reinstall multilib the same way you installed it originally. If you did it manually then repeat the process. A better option would be to install slackpkg+, then you only have to do "slackpkg reinstall multilib".

Out of curiosity how did you update your system?

Brian

wolfslacker · 03-03-2017, 01:26 PM

To update I did the following.
# slackpkg update
# slackpkg upgrade-all

phenixia2003 · 03-03-2017, 01:37 PM

Hello,

I guess that you've upgraded your system by running slackpkg upgrade-all, and thus, the multilib version of glibc/gcc have been overwritten by their pure 64-bit counterpart. To fix this, you need to upgrade your glibc/gcc to multilib version. To do that, you have two choices :

1. (re)download glibc/gcc from alienbob multilib repository, and upgrade them, by running the commands below (do not forget to replace the tag <VERSION> by the version of Slackware installed on your system) :

Code:

$ lftp -c 'open http://taper.alienbase.nl/mirrors/people/alien/multilib/ ; mirror -c -e -r <VERSION>'

cd <VERSION>
upgradepkg --reinstall *.t?z

When the multilib gcc/glibc packages have been installed, It is recommended to blacklist these packages to prevent them to be overwritten when you upgrade your Slackware with slackpkg :

Code:

$ slackpkg blacklist glibc gcc

2. As pointed out by BCarey, you can use slackpkg+ which is a slackpkg extension to support 3rd party repositories. For more about slackpkg+ and multilib, I strongly recommend you to read the multilib section in slackpkg+ README file :

Quote:

MULTILIB

If you want to use a multilib system, you can automatically configure the
multilib repository in slackpkgplus.conf and install multilib simply by running:
# /usr/doc/slackpkg+-*/setupmultilib.sh

To configure multilib manually (e.g. if you have installed multilib already),
uncomment the correct "MIRRORPLUS['multilib']=...",
and uncomment "PKGS_PRIORITY=( multilib )".
If you do not plan to build yourself 32bit packages on your 64bit machine, you may
avoid to install gcc:

PKGS_PRIORITY=( patches:gcc slackware64:gcc multilib )

To install multilib manually, launch:
# slackpkg update gpg
# slackpkg update
# slackpkg upgrade-all
# slackpkg install multilib

After that, you can keep multilib up-to-date by launching:
# slackpkg update
# slackpkg upgrade-all
periodically lauch
# slackpkg install multilib
to check for new multilib packages availability

To uninstall multilib, you must remove 'multilib' from PKGS_PRIORITY and from
REPOPLUS, but do NOT delete the related MIRRORPLUS line, then launch:
# slackpkg update
# slackpkg remove multilib
Note: this does NOT remove the core multilib packages, because they affect the
64bit system. You must remove these by launching:
# slackpkg upgrade-all
then delete or comment the related MIRRORPLUS line, and finally launch
# slackpkg update

or just re-run
# /usr/doc/slackpkg+-*/setupmultilib.sh

--
SeB

Cristiano Urban · 03-03-2017, 01:48 PM

If you use slackpkg+ to keep up to date your multilib packages, it is necessary to have the multilib repository set with the highest priority (see the PKGS_PRIORITY parameter in /etc/slackpkg/slackpkgplus.conf). This avoids the multilib packages are overwritten by the original ones.

bassmadrigal · 03-03-2017, 03:52 PM

Quote:

Originally Posted by phenixia2003

When the multilib gcc/glibc packages have been installed, It is recommended to blacklist these packages to prevent them to be overwritten when you upgrade your Slackware with slackpkg :

Code:

$ slackpkg blacklist glibc gcc

It might be easier to just blacklist all of Eric's packages. If you're not going to use slackpkg+, you can add the following to the blacklist:

Code:

[0-9]+alien
[0-9]+compat32

This will also prevent the compat32 packages as well as any of Eric's other packages from being removed if slackpkg clean-system is run (where if glibc and gcc are only added, all compat32 and Eric's other packages will be removed).

wolfslacker · 03-03-2017, 11:07 PM

Thank you all for your help. I was able to re-install multilib and my 32-bit apps are working again.