LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-06-2017, 02:31 PM   #1
TarFile
Member
 
Registered: Mar 2003
Posts: 282

Rep: Reputation: 23
Updated 14.2 current GLIBC_2.25 not found


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.

Last edited by TarFile; 06-06-2017 at 02:32 PM.
 
Old 06-06-2017, 02:37 PM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 6,571

Rep: Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818
Quote:
Originally Posted by TarFile View Post
I did an update to slack 14.2 current today
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.
 
Old 06-06-2017, 02:43 PM   #3
TarFile
Member
 
Registered: Mar 2003
Posts: 282

Original Poster
Rep: Reputation: 23
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 ?
 
Old 06-06-2017, 02:50 PM   #4
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,224

Rep: Reputation: 3299Reputation: 3299Reputation: 3299Reputation: 3299Reputation: 3299Reputation: 3299Reputation: 3299Reputation: 3299Reputation: 3299Reputation: 3299Reputation: 3299
Quote:
Originally Posted by TarFile View Post
Oh yeah I still have 14.1 bootable on the same box so I can get to the file system.
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.
Old 06-06-2017, 03:02 PM   #5
TarFile
Member
 
Registered: Mar 2003
Posts: 282

Original Poster
Rep: Reputation: 23
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.
 
Old 06-06-2017, 03:28 PM   #6
TarFile
Member
 
Registered: Mar 2003
Posts: 282

Original Poster
Rep: Reputation: 23
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.
 
Old 06-06-2017, 03:46 PM   #7
TarFile
Member
 
Registered: Mar 2003
Posts: 282

Original Poster
Rep: Reputation: 23
Here is a screenshot of the slackpkg upgrade-all no glibc-2.25 listed.
Attached Thumbnails
Click image for larger version

Name:	slackpkg_upgrade.png
Views:	28
Size:	77.9 KB
ID:	25196  
 
Old 06-06-2017, 05:00 PM   #8
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,040

Rep: Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031
Quote:
Originally Posted by TarFile View Post
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.
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.
Old 06-06-2017, 08:13 PM   #9
TarFile
Member
 
Registered: Mar 2003
Posts: 282

Original Poster
Rep: Reputation: 23
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.
 
Old 06-06-2017, 08:24 PM   #10
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,040

Rep: Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031
Have a look at this section on getting slackpkg+ set up to manage your multilib.
 
Old 06-06-2017, 08:26 PM   #11
TarFile
Member
 
Registered: Mar 2003
Posts: 282

Original Poster
Rep: Reputation: 23
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.
 
Old 06-30-2017, 09:49 PM   #12
codeguy
Member
 
Registered: Jan 2004
Distribution: Slackware
Posts: 130

Rep: Reputation: 16
Gaa! I _just_ did this. So this thread helped me out too!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] slackware current issue on kernel upgrade....`GLIBC_2.22' nitecrawler Slackware 16 09-11-2015 01:58 AM
GLIBC_2.14 not found during Houdini installation MarXindia Linux - Newbie 7 06-04-2014 05:36 PM
glibc_2.4 not found?? can't install software!!! gvp87 Linux - Software 0 08-05-2007 11:31 AM
[For Help] 'GLIBC_2.3' not found eNsEmpire Linux - Software 0 03-13-2007 09:39 PM
version 'GLIBC_2.3' not found BadGuy Linux - Software 2 02-24-2003 07:50 AM


All times are GMT -5. The time now is 04:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration