[Slackbuilds-users] tracking down SBo "dependencies"

Arnaud arnaud.garcia-fernandez at laposte.net
Thu Feb 29 19:30:49 UTC 2024


Well, you've still got sbbdep then, in reverse mode it could help you.
It does calculate a full dependency tree, binary only, so for like python packages it won't work, but in your case it should.
I never used it like that though, so it's kind of a guess.

 - Yth

Le 29 février 2024 19:22:49 UTC, Jim <zsd+slackbuilds at jdvb.ca> a écrit :
>Hi Arnaud,
>
>On Thu, Feb 29, 2024 at 16:53 (+0000), Arnaud via SlackBuilds-users wrote:
>
>> Tracking the breakage might require launching the app,
>
>Trying *every* program after upgrading a library seems like a bit of a
>non-starter.
>
>> or checking with ldd.
>
>After seeing a complaint appear in my terminal window I ran ldd on a lot of
>things (such as the vlc binary and the libraries of libheif) and it didn't
>show up.  However, what I didn't look at immediately, which I now know was
>the place to look, is /usr/X11/lib64/vlc/plugins/codec/libdav1d_plugin.so,
>which is (presumably) the thing that whined after I upgrades dav1d.
>
>Similarly /usr/X11/lib64/libheif/libheif-dav1d.so has a reference to
>libdav1d.so.7.
>
>> However, tracking potential breakages could be done using hoorex.
>
>Not in this case...
>
>> # hoorex -i dav1d This'll list all installed packages requiring directly
>> dav1d.
>
>And there's the problem... Neither vlc nor libheif (nor maybe others I
>haven't found yet) *directly* require dav1d, so hoorex doesn't list them.
>
>Cheers.
>                                Jim
>
>> Le 29 février 2024 16:12:14 UTC, Jim <zsd+slackbuilds at jdvb.ca> a écrit :
>>>I recently upgraded the SBo dav1d, which upgraded the library from
>>>libdav1d.so.6 to libdav1d.so.7.
>
>>>Unfortunately, a couple of other SBo packages (libheif and vlc) had
>>>references to (specifically) libdav1d.so.6, which caused them to whine a
>>>bit.
>
>>>It was easy enough to recompile libheif and vlc after I found the problem,
>>>but this got me wondering...
>
>>>Does anyone have an easy way of tracking down this sort of "breakage" which
>>>might happen when upgrading an SBo package?
>
>>>Thanks.
>>> Jim
>>>_______________________________________________
>>>SlackBuilds-users mailing list
>>>SlackBuilds-users at slackbuilds.org
>>>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>>FAQ - https://slackbuilds.org/faq/
>
>
>> -- 
>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>
>
>_______________________________________________
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/
>

-- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240229/75439d9b/attachment.htm>


More information about the SlackBuilds-users mailing list