Slack: script to detect orphaned libraries, broken lib links, missing dependencies

Affromen · 03-09-2010, 03:34 AM

The first bit is from output that script generates into my terminal, the second is cat from file orphaned.log

GrapefruiTgirl · 03-09-2010, 03:42 AM

AHA!! There's no problem with your system!

Don't worry about what it says on the screen -- only the log file.

For some reason (like maybe you pressed ENTER a few times, or there's some other weird bug that I can't reproduce) you are getting a few lines on your terminal. I don't know why

but it is very late here so I will have to re-investigate this tomorrow.

(of course, maybe someone can figure this out during the night!)

Meanwhile, just go by what's in the log -- notice that orphaned libs are identified by the words:

Orphaned library:

so if that is not there, there is no problem.

You can comment out this line from the script:

Code:

         printf "$DIR/$LIB                                                  \r"

and this should go away.

Sasha

repo · 03-09-2010, 05:51 AM

Here the output on a slackware 13.0 32 bit

Quote:

root@cannabis Downloads]# orphans
## Count installed packages: 907
## Checking for missing libraries (via broken symlinks)...
Done.
## Searching for orphaned libraries (not belonging to an installed package)...
All done!
root@cannabis Downloads]#

dive · 03-09-2010, 07:15 AM

Nice script GrapefruitGirl, thanks

SavoTU · 03-09-2010, 01:24 PM

I get the below output as well but the log file says all ok. Will take a look into the massive 957 packages installed now.

bash-4.1$ sh orphans.sh
## Count installed packages: 957
## Checking for missing libraries (via broken symlinks)...
Done.
## Searching for orphaned libraries (not belonging to an installed package)...
/usr/i486-slackware-linux/lib/libstdc++-3-libc6.1-2-2.10.0.so /usr/i486-slackware-linux/lib/libstdc++-3-libc6.2-2-2.10.0.so /usr/i486-slackware-linux/lib/libstdc++.so.4.0.0 /usr/i486-slackware-linux/lib/libstdc++.so.5.0.7 All done!
bash-4.1$

sahko · 03-09-2010, 02:33 PM

I use the attached customized script from Arch's devtools which uses ldd to find broken library links.

GrapefruiTgirl · 03-09-2010, 03:02 PM

NOTICE: I am currently (among other things) correcting that erronious output to the console.

However, please keep in mind that unless the line begins with:

Orphaned library:

it is not reporting an orphan.

Updated version will be available later on, with that console output removed.

Sasha

GrapefruiTgirl · 03-09-2010, 03:02 PM

@ sahko -- I'll have a look at that too, maybe I can learn something from it

Sasha

piete · 03-09-2010, 03:20 PM

I'm sorry for the minor thread detour, but out of interest, what happened with your -current upgrade? Those orphaned libraries look like things that shouldn't be orphaned. I do miss the package browser for quick reference on what exists where!

- Piete.

GrapefruiTgirl · 03-09-2010, 04:01 PM

How do you mean "You miss the package browser" ? You mean pkgtool? It is still there.. Maybe you refer to a GUI tool like KPackage? Not sure if that still exists...

Anyhow, I am not certain what *exactly* happened to my upgrade -- I suspect it was my blatant disregard for changelog-reading while trying to do several things at once. Maybe I upgraded aaa_elflibs at the wrong time, or by the wrong means. After having finished downloading the upgrades, slackpkg began installing, and almost immediately things went to hell in a basket

so I think it was elf-libs package that screwed it up. But I'm not certain.

Sasha

Didier Spaier · 03-09-2010, 05:15 PM

Thanks Sasha for this script -- works well here.

And thanks also because looking at it I eventually founded a way of piping needed data in a "while read" construct, avoiding to write a file unnecessarily to feed it.

GrapefruiTgirl · 03-09-2010, 05:19 PM

thanks Didier, glad you got something useful from it.

On the topic of piping stuff into `while` : I have discovered that the method I used here:

Code:

cat somefile | while read ...

works in cases where THIS code below, does not:

Code:

while read blah; do
  blah blah
done < somefile

I haven't looked into why one works and the other does not, nor WHEN one works and the other does not, but if someone knows, that'd be handy to know.
I was banging my head for hours one day using the latter method, when finally I switched the code to the FORMER method and suddenly all worked correctly.

Cheers!
Sasha

EDIT: P.S. there will be an update to the script later this evening; nothing super-major, just some cleanups and slight adjustments.

EDIT: New version -- 19:55 hrs (GMT -04:00) Tue Mar 09 2010

Didier Spaier · 03-09-2010, 05:48 PM

I don't know if this is related to that but following your first post I ended up replacing this:

Code:

echo ${chemin_vers_client[$num_client]}/install.rdf >chemin_install.rdf
while read chemin; do
  version_client[$num_client]=$(cat $chemin|awk '/<em:version>/ {print $0; exit}'|tr -d '[:alpha:]<>:/[:space:]')
done <chemin_install.rdf

by that:

Code:

version_client[$num_client]=$(echo $chemin_install_rdf| \
  while read chemin; do
   cat $chemin|awk '/<em:version>/ {print $0; exit}'|tr -d '[:alpha:]<>:/[:space:]'
  done)

At first I tried that instead:

Code:

echo $chemin_install_rdf| \
  while read chemin; do
   version_client[$num_client]=$(cat $chemin|awk '/<em:version>/ {print $0; exit}'|tr -d '[:alpha:]<>:/[:space:]')
  done

which didn't work because version_client[$num_client] was not accessible outside the while loop: I should have read better the abs-guide in order to understand in which cases variables are local...

GrapefruiTgirl · 03-09-2010, 05:54 PM

At a glance, I'd say it's related, but honestly, I thought variables in the shell were only "local" to something if they were specifically defined as 'local' -- but the same thing is what was happening for me that time I spoke of: a variable was not being available inside the while loop by one means, but my the other means, it became available to the loop, but NOT available OUTSIDE the loop.

If I try to explain more about this, I may make matters worse because I don't have that particular code in front of me, and it was 'weird code' to start with. Maybe a new thread would be a good place to sort this out

piete · 03-10-2010, 07:10 AM

Quote:

Originally Posted by GrapefruiTgirl

How do you mean "You miss the package browser" ? You mean pkgtool? It is still there.. Maybe you refer to a GUI tool like KPackage? Not sure if that still exists...

Sorry, I meant http://packages.slackware.it/ . Like many other posters, I work from memory a lot without having a Slack box in front of me, so a completely OS agnostic search is very convenient