LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 03-13-2009, 04:22 AM   #1
phys
Member
 
Registered: Jun 2006
Location: Istanbul, Turkey
Distribution: Slackware
Posts: 90

Rep: Reputation: 23
Upgrading to "slackware-current"


Quote:
*** upgradepkg glibc-solibs before other ***
*** packages. Take care not to miss new ***
*** packages that were split from old ***
*** ones: upgradepkg --install-new is ***
*** (as always) the safest approach. ***
Hi;

Patrick says that upgrade glibc-solibs package before other packages. I did not notice this warning and upgraded all packages to current, then installed new packages including "kde-compat" packages and cleaned old ones. Now it seems to be everything OK with KDE 4.2.1 and other programs.

Does anyone know that why Patrick pointed out to install glibc-solibs package first? What problems can I experince?
 
Old 03-13-2009, 06:39 AM   #2
XGizzmo
Member
 
Registered: Mar 2007
Distribution: Slackware
Posts: 264

Rep: Reputation: 68
Almost every program in Slackware is linked to glibc. If you don't upgrade glibc-solibs first there is a better
than average chance you will render your system completely unusable. And you will need to do something like the
steps listed here. http://rlworkman.net/howtos/glibc-recovery
 
Old 03-13-2009, 07:48 AM   #3
phys
Member
 
Registered: Jun 2006
Location: Istanbul, Turkey
Distribution: Slackware
Posts: 90

Original Poster
Rep: Reputation: 23
Quote:
Almost every program in Slackware is linked to glibc.
This means "pkgtool" also uses this package. While installing new packages for current, does pkgtool need upgraded glibc-solibs?
I have upgraded my slack box (v12.2) to current using slackpkg from binary packages not source. For my method does it matter whether upgrading glibc-solibs first or not?
 
Old 03-13-2009, 08:05 AM   #4
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by phys View Post
This means "pkgtool" also uses this package. While installing new packages for current, does pkgtool need upgraded glibc-solibs?
I have upgraded my slack box (v12.2) to current using slackpkg from binary packages not source. For my method does it matter whether upgrading glibc-solibs first or not?
Running programs will not be replaced by remove / copy operations. See unlink(2).
 
Old 03-13-2009, 09:50 AM   #5
GazL
Senior Member
 
Registered: May 2008
Posts: 3,425

Rep: Reputation: 937Reputation: 937Reputation: 937Reputation: 937Reputation: 937Reputation: 937Reputation: 937Reputation: 937
Quote:
Originally Posted by guanx View Post
Running programs will not be replaced by remove / copy operations. See unlink(2).
except that upgradepkg etc. are just shell scripts and it's the utilities it will try and run later (which won't be loaded) that will hit problems with library incompatibility.

This incompatibility could happen either way around, though library developers try and keep things backwards compatible wherever possible.

Because of this, it's much more likely for a library to be backward compatible than for a program linked against the old library to be forward compatible with the new library which is why I believe Pat recommends to update the libs first.

Having said that, if you did it in the wrong order, but got away with it, then I don't think you'll need to take any remedial action. You just got lucky.


Personally, I always use the ROOT= and install into a fresh parallel filesystem to avoid these sort of issues when doing these mass updates, which also has the advantage of leaving you with a nice easy backout plan. It means you have to reapply any of your customisations to the new enviroment, but there are ways to make that fairly painless.
 
Old 03-14-2009, 07:57 PM   #6
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Rep: Reputation: 70
phys,

check out the upgrade HowTos in my signature. While they are not specifically for this -current, the HowTos show how to do a proper upgrade using slackpkg along with the official Slackware documentation.
 
  


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
slackware 12.1 blank screen after clicking "end current session" nick_slack Slackware 7 05-25-2008 09:01 PM
KDE problem using Slackware "12.1" -->current version phodopus Slackware 1 02-07-2008 03:25 AM
slackware "current" problems after install on vmware jimp180 Slackware - Installation 2 07-17-2007 01:35 PM
firefox 2.0 "save as box" problem on Slackware Current davimint Slackware 5 05-25-2007 06:28 PM
Checkinstall faults after upgrading to "current" Waldi Slackware 0 01-16-2004 02:55 AM


All times are GMT -5. The time now is 02:54 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration