I did an update to slack 14.2 current today and it blew up with messages about GLIBC_2.25 not found. This is a multilib system. It seems that glib is at 2.23.

The system is not bootable as it hangs.

Any idea how to fix this?

I kernel ffmpeg alien and compat32 black listed in slackpkg/blacklist.

Maybe grab glib 2.25 and manually put the files and links in place then try to fix any problems?



Oh yeah I still have 14.1 bootable on the same box so I can get to the file system.

A "slack 14.2 current" does not exist.
You either run 14.2, or -current. You NEVER mix the two. If you have installed packages meant for -current on a Slackware 14.2 installation (or vice versa) you will most certainly end up with a broken system.

Let me rephrase that the system is current and always has been. Not sure what went wrong as I did the usual update, install-new, upgrade-all.

This was never a 14.2 system.

Anyway is there a way to fix this ?

Great, then you'll be able to fix this from the 14.1 installation.

You say the broken system was running -current, so I'll assume that's the case. Boot 14.1, and mount the filesystem on /mnt. Then download (at least) the main glibc package for -current for the appropriate $ARCH (x86_64 or i586).

Install/upgrade like this:

ROOT=/mnt upgradepkg --install-new --reinstall glibc-2.25-x86_64-2.txz

(or for 32-bit glibc-2.25-i586-2.txz)

After that you might want to make sure that slackpkg is pointed to the correct mirror for your system and run it through the paces in case anything else was missed.

3 members found this post helpful.

Thanks Pat that got the system to boot. I am not sure what went wrong I had the correct mirror. Not sure why it did not pick up the new GLIBC. I will have to be more careful in the future.

I checked this process on another box that is also running current. The thing is that glibc-2.25 does not show up in the list of things that will be upgraded. Needless to say this bothers me. The original box was only at glibc-2.23 the other box is at glibc-2.24. I would think that slackpgk would have the latest glibc if it was upgraded what am I doing wrong?

This makes me wonder if its slackpkg or me. I tried another mirror with the same results.

Here is a screenshot of the slackpkg upgrade-all no glibc-2.25 listed.

Attached Thumbnails

 

Check your blacklist. If you're running multilib, you probably blacklisted the multilib glibc packages, so they won't be presented in slackpkg. If you want to continue using multilib and slackpkg, I'd recommend you looking into slackpkg+ to keep multilib updated. However, I would keep an eye on both changelogs to make sure that the multilib packages are updated before you try and upgrade (I'm not sure how on top of it Eric tends to be since I don't typically follow -current on any machines).

1 members found this post helpful.

Thanks I am sure this has something to do with it. So far I just did as Pat said and everything still works but I have a felling it will cause a problem at some point.

Have a look at this section on getting slackpkg+ set up to manage your multilib.

OK a little checking and I see that you are 100% correct.

I need to actually check the change log for both as you said before doing an update.

I will probably forget knowing me, so I better keep an alternate way to fix things.

A live CD or USB stick should work in a pinch I would think.

Gaa! I _just_ did this. So this thread helped me out too!