LinuxQuestions.org - Massive Updates!

LinuxQuestions.org (/questions/)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Massive Updates! (https://www.linuxquestions.org/questions/slackware-14/massive-updates-4175557522/)

Massive Updates!

-current just got a good shot in the arm! Hopefully smooth sailing for those tracking -current?

Quote:

Originally Posted by zbreaker (Post 5442130)

-current just got a good shot in the arm! Hopefully smooth sailing for those tracking -current?

Very smooth sailing indeed. This evening I upgraded 3 desktops, my Lenovo laptop, and my Acer netbook. All is well. :)

Installing them now.

Does this mean a new version is around the corner?

So far, so good. No hiccups.
:)

only need to recompile some third party packages coming from SBo but that is normal so i won't be calling it an issue

Massive Updates!

Is any of you running Alien Bob's ktown kde5?

I'm somehow hesitating to give it a try as I don't have much time these days and my laptop is my everyday machine...

i suggest to wait until AlienBOB tested his KDE 5 on the latest current update
i'm pretty sure it would make some functionality to break due to many library soname bump in this batch.

Quote:

Originally Posted by willysr (Post 5442197)

only need to recompile some third party packages coming from SBo but that is normal so i won't be calling it an issue

It would be nice to have an easy option to track which of the installed SBO/3rd-party packages needs to be recompiled, or just
have an option Recompile in sbopkg:->Packages in addition to "List/uninstall installed"
At the moment I'm using the following script to do this.

hi igor29768,

I'm afraid that's not possible in a comfortable way, because (first thing that comes to mind) sbopkg has no idea which optional dependencies have you built, for example, ffmpeg against.
there's no automatic dependency resolution for stuff you built from SBo as they are not carved in stone, one can choose what to build what against (apart from the mandatory deps).

what I can tell you is that here, to avoid pain during these updates, I usually rebuild everything third-party I got on my current systems (I maintain a personal sbopkg queue for that).

*service message for SBo-git current repo users*: as here there's a huge comic convention in these days which I have to attend (lot of friends there) and the fact that this time I will have also to issue some updates to follow the gnome platform update (and more) will delay a little updates of my personal repo, I hope you will understand.

Quote:

Originally Posted by igor29768 (Post 5442250)

you can utilise sbbdep
https://bitbucket.org/a4z/sbbdep/wiki/Home
just check to SBo packages and if a library is missing you will be notified

Ah, I forgot about sbbdep. I made a little script to check for broken libs: http://pastebin.com/fXh20kuH
Some packages however use libraries which cannot be found in the default paths and will appear broken, e.g. firefox.

Usage (e.g):

Quote:

./checkpkg /var/log/packages/*_SBo

Potentially broken packages will printed out.

Quote:

Originally Posted by ponce (Post 5442256)

I agree with you, and the sbbdep mentioned below would not list all of the possible dependencies/conflicts.

> I usually rebuild everything third-party
I do more or less the same, except that I'm looking for a way to better organize my personal sbopkg queue.
BTW, I am not advocating the complete automatic dependency-resolving upgrade workflow.
I was thinking about an addition to the the sbopkg dialog interface, something like the attached sketch.

>*service message for SBo-git current repo users*:
Have fun at the comic con and thanks for the Slackware-current SBo git!

Quote:

Originally Posted by igor29768 (Post 5442250)

This little script will give you a rough idea:

Code:

#!/bin/bash

#

# depcheck.sh

#

# This script is a very basic dependency checker for Slackware Linux. It scans

# all the binaries in the PATH and reports any missing libraries.



for DIRECTORY in $(echo $PATH | sed 's/:/ /g'); do

  for FILE in $DIRECTORY/*; do

    if [ $(file -b $FILE | cut -d' ' -f1) == 'ELF' ]; then

      if ldd $FILE | grep -q 'not found'; then

        echo "$FILE"

        ldd $FILE | grep 'not found' | awk '{print "Not found:", $1}'

      fi

    fi

  done

done

You can download it here or grab it from my Github repo:

$ git clone https://github.com/kikinovak/microlinux

Take a peek in the tools/ directory.

Cheers,

Niki

Quote:

Originally Posted by eldercitizen (Post 5442266)

Thanks for the script! I'm going to look on how to modify it for my use, and perhaps by replacing 'ldd' with 'objdump -x | grep NEEDED' or sbbdep.