libraries and packages

Alien Bob · 08-14-2013, 08:14 AM

Quote:

Originally Posted by yakoub

given an error about missing library, how do i figure out which package contains it ?
for example : libatk-bridge-2.0.so.0
is there a special tool for that ?

Try searching in slakfinder.org

Eric

tronayne · 08-14-2013, 08:49 AM

Easy way:

Code:

locate libatk
/usr/lib64/libatk-1.0.so.0
/usr/lib64/libatk-1.0.so.0.20409.1
/usr/lib64/libatk-1.0.la
/usr/lib64/libatkmm-1.6.so.1.1.0
/usr/lib64/libatk-1.0.so
/usr/lib64/libatkmm-1.6.so.1
/usr/lib64/libatkmm-1.6.so
/usr/lib64/libatkmm-1.6.la

It's there, now, what package is it in?

Code:

fgrep libatk /var/log/packages/*
/var/log/packages/atk-2.4.0-x86_64-1:usr/lib64/libatk-1.0.la
/var/log/packages/atk-2.4.0-x86_64-1:usr/lib64/libatk-1.0.so.0.20409.1
/var/log/packages/atkmm-2.22.6-x86_64-1_SBo:usr/lib64/libatkmm-1.6.so.1.1.0
/var/log/packages/atkmm-2.22.6-x86_64-1_SBo:usr/lib64/libatkmm-1.6.la

The first two are standard equipment, the last two are SlackBuilds.org.

'Course you need to build the slocate data base (with slocate -u) first...

Hope this helps some.

Petri Kaukasoina · 08-14-2013, 10:00 AM

Quote:

Originally Posted by yakoub

found : at-spi2-atk-2.8.1-i486-1.txz
but slackpkg doesn't find it .
the reason i need it is audacious :
audacious: error while loading shared libraries: libatk-bridge-2.0.so.0: cannot open shared object file: No such file or directory

My crystal ball says that you have Slackware 14.0 but you try to run audacious for Slackware-current. You shouldn't mix binaries like that. When Patrick compiled audacious for Slackware 14.0, the at-spi2-atk packages was not yet part of Slackware, so audacious did not link against it. But at-spi2-atk was added to Slackware-current, so when audacious was compiled for it, it was linked against the new library.

yakoub · 08-15-2013, 12:43 AM

Quote:

Originally Posted by Petri Kaukasoina

My crystal ball says that you have Slackware 14.0 but you try to run audacious for Slackware-current. You shouldn't mix binaries like that. When Patrick compiled audacious for Slackware 14.0, the at-spi2-atk packages was not yet part of Slackware, so audacious did not link against it. But at-spi2-atk was added to Slackware-current, so when audacious was compiled for it, it was linked against the new library.

thanks a lot, your crystal ball is wonderful .
and all you others who assumed i have partial slackware install or trying to compile audacious manually then you drew very wrong conclusions .

what i did do was partial slackpkg upgrade from 14 to current .

the reason slackpkg couldn't find the new package that i switched mirrors and chose 14 instead of current by mistake .

ponce · 08-15-2013, 12:57 AM

Quote:

Originally Posted by yakoub

thanks a lot, your crystal ball is wonderful .
and all you others who assumed i have partial slackware install or trying to compile audacious manually then you drew very wrong conclusions .

what i did do was partial slackpkg upgrade from 14 to current .

the reason slackpkg couldn't find the new package that i switched mirrors and chose 14 instead of current by mistake .

maybe if you have described us the situation in your help request our guesses could have been more precise: we're not magicians

just to clarify: if you upgraded from slackware-14.0 to -current with

Code:

slackpkg upgrade-all

and you haven't run

Code:

slackpkg install-new

(as explained in the man page) you are running a partial install

yakoub · 08-15-2013, 01:06 AM

Quote:

Originally Posted by yakoub

thanks a lot, your crystal ball is wonderful .
and all you others who assumed i have partial slackware install or trying to compile audacious manually then you drew very wrong conclusions .

what i did do was partial slackpkg upgrade from 14 to current .

the reason slackpkg couldn't find the new package that i switched mirrors and chose 14 instead of current by mistake .

well actually i didn't do upgrade to current, my intention was to remain in 14 all the time .
so i guess this is a bug in slackware because "slackpkg upgrade" introduced packages that was built against slackware-current and not 14 as i intended .
and strangely i never upgraded audacious specifically to begin with, but only "upgrade l" .

ponce · 08-15-2013, 01:16 AM

you cannot upgrade only a part of the packages, as they are built against other packages/libraries and on a completely different toolchain so things most probably break: upgrading only the l serie you upgraded gtk+2 (used by audacious) that, beside other things, on -current is built against at-spi2-atk, that has been added as a new package, so you don't have it in your installation if you run just "slackpkg upgrade" from -14.0.
be advised, if you aren't already, that -current is not intended for unexperienced users: it's not a rolling release but something for developing and testing.
that said, if you want to use the new stuff safely, the only way for you is to follow what's described in the slackpkg's man page and switch completely to -current, following the procedure for upgrading from one release of the distribution to the next with slackpkg: change the mirror in /etc/slackpkg/mirrors to a -current one and

Code:

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system

with the last step be sure not to remove stuff you need (assuming it still works after the procedure, maybe it will need to be rebuilt).

yakoub · 08-15-2013, 04:23 AM

Quote:

Originally Posted by ponce

you cannot upgrade only a part of the packages, as they are built against other packages/libraries and on a completely different toolchain so things most probably break: upgrading only the l serie you upgraded gtk+2 (used by audacious) that, beside other things, on -current is built against at-spi2-atk, that has been added as a new package, so you don't have it in your installation if you run just "slackpkg upgrade" from -14.0.
be advised, if you aren't already, that -current is not intended for unexperienced users: it's not a rolling release but something for developing and testing.
that said, if you want to use the new stuff safely, the only way for you is to follow what's described in the slackpkg's man page and switch completely to -current, following the procedure for upgrading from one release of the distribution to the next with slackpkg: change the mirror in /etc/slackpkg/mirrors to a -current one and

Code:

# slackpkg update
# slackpkg install-new
# slackpkg upgrade-all
# slackpkg clean-system

with the last step be sure not to remove stuff you need (assuming it still works after the procedure, maybe it will need to be rebuilt).

ya i know, but i still try to be smart about it and did the following :

Code:

upgrade xfce
upgrade x 
upgrade l

and that is it, no need to upgrade all .
and whenever i notice things breaking then i look-up that particular package and upgrade it .

ponce · 08-15-2013, 04:38 AM

if you prefer it this way, go for it, you are the owner of your installation and are entitled to break it as you like.

but, please, IMHO, you shouldn't come here asking why things don't work or any kind of help (read: "you're on your own") if you're mixing stuff from stable and current as that setup is completely unsupported.

yakoub · 08-15-2013, 02:33 PM

Quote:

Originally Posted by ponce

if you prefer it this way, go for it, you are the owner of your installation and are entitled to break it as you like.

but, please, IMHO, you shouldn't come here asking why things don't work or any kind of help (read: "you're on your own") if you're mixing stuff from stable and current as that setup is completely unsupported.

man you are totally wrong, i didn't ask for help about my installation .
i asked a specific question and i think it is stupid that i should search for a library using a web service instead of having a command that i can run from the shell .
slackpkg file-search is the best answer .

ponce · 08-15-2013, 02:44 PM

yes, but as you have experienced yourself, it can and cannot work if you switch repositories back and forth from stable to current: I was referring above mainly to the fact that you said for you it wasn't working (then you found out that was because of the switching -we cannot know about that).

Didier Spaier · 08-15-2013, 02:50 PM

Quote:

Originally Posted by yakoub

man you are totally wrong, i didn't ask for help about my installation .

That was not that clear from your first post, IMO. Else you could have simply asked "How do i find which package contains "some" (not "a missing") library.

Quote:

Originally Posted by yakoub

i asked a specific question and i think it is stupid that i should search for a library using a web service instead of having a command that i can run from the shell.

It's not always stupid. A web service can be useful in case you are looking for a library that is not included in Slackware, as I don't know a shell command able to do that, working with all third-party repositories.

Alien Bob · 08-15-2013, 05:12 PM

Let us all refrain from further comments here, since the OP considers himself "smart" and those who try to answer his smart questions "stupid". Obviously he does not need us.

Eric