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


  Search this Thread
Old 10-05-2006, 05:20 PM   #1
Andy Alt
Registered: Jun 2004
Location: Minnesota, USA
Distribution: Slackware32-stable, Debian32 stable, LFS 7.1
Posts: 390

Rep: Reputation: 50
upgrading aaa_elflibs, contradiction

I was wonder about the recommended procedure for upgrading aaa_elflibs. I haven't had any problems for over 18 months, but would like to get a final answer on this.

In the slack package description of aaa_elflibs:
aaa_elflibs: This package should be not upgraded or reinstalled (it could copy
aaa_elflibs: over newer library versions).
In UPGRADE.txt, no mention is made of aaa_elflibs. There are three packages that it says to upgrade before upgrading everything else.

So does this mean it is or isn't safe to simply use "upgradepkg" on aaa_elflibs?
Old 10-05-2006, 05:27 PM   #2
Andy Alt
Registered: Jun 2004
Location: Minnesota, USA
Distribution: Slackware32-stable, Debian32 stable, LFS 7.1
Posts: 390

Original Poster
Rep: Reputation: 50
Disregard. I found the answer.
Slackware aaa_elflibs and aaa_base packages

The aaa_elflibs contains a collection of basic libraries already present in other slackware packages (a few required a/ and l/ libraries). The idea is to save you in the case you select a non-full installation and omit some crucial libraries.

But precisely because of that, you shouldn't upgrade the package, since it contains libraries present in other packages, and would end up overwritting them (aaa_elflibs sometimes contains an older version of a few libs).

If you followed me, then you might realize that it *could* (I haven't tried it) be possible to upgrade aaa_elflibs, if it's done before everything else. But once again, it shouldn't be needed, ever.
Old 10-05-2006, 05:46 PM   #3
LQ Newbie
Registered: Sep 2006
Posts: 5

Rep: Reputation: 0
I believe during slackware-current I did have to upgrade aaa_elflibs because something had changed in one of the other packages. I believe a library that was part of apache was added to aaa_elflibs and when I upgraded apache the library was missing. I believe it was libmm. If i remember correctly there was some issue with the version of libmm which caused apache not to load and I had to actually upgrade aaa_elflibs in order to get apache working correctly again. You might want to look into changelog and search for libmm. I'm not sure if its an issue now but when upgrading regularly to slackware-current it was a brief issue for me.


documentation, upgrade, upgradepkg

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 aaa_elflibs and aaa_base packages rignes Slackware 3 08-06-2006 02:05 PM
Upgrading to Badger! Can't login anymore after upgrading? BellaSha87 Ubuntu 1 12-03-2005 12:09 PM
rpm Contradiction GlassEyeSlim Linux - Software 7 02-17-2005 12:40 PM
warning about latest current aaa_elflibs-10.1.0 xushi Slackware 2 01-25-2005 07:57 AM
Installing aaa_elflibs aikempshall Slackware 6 07-10-2004 07:47 AM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:03 AM.

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