Re: [gentoo-user] "Broken soname dependencies found" after portage upgrade

2021-12-12 Thread tastytea
On 2021-12-12 18:11+0200 Nikos Chantziaras  wrote:

> After upgrading from portage 3.0.28 to 3.0.30, I get this when doing 
> emerge --depclean:
> 
> Calculating dependencies... done!
>   * Broken soname dependencies found:
>   *
>   *   x86_64: libexpat.so required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>   *   x86_64: libgdbm_compat.so.3 required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>   *   x86_64: liblttng-ust.so.0 required by:
>   * dev-dotnet/dotnet-sdk-bin-6.0.100
>   *
>   *   x86_64: libreadline.so.6 required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>   *   x86_64: libgdbm.so.3 required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>   *   x86_64: libbz2.so.1.0 required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>  >>> No packages selected for removal by depclean  
> 
> What does it even mean?

It means the binary wants to load some libraries (like libexpat.so)
portage can't find.

> (And before anyone asks, the software works just fine, and neither 
> revdep-rebuild nor revdep-rebuild.sh find anything wrong.)

But vmware (or rather, the linker) seems to find them. Maybe they are in
the same directory as the binary and portage doesn't search there? You
can check which libraries exactly the binary wants to load with ldd.

-- 
Get my PGP key with `gpg --locate-keys tasty...@tastytea.de` or at
.


pgpcpA4f0qLHX.pgp
Description: Digitale Signatur von OpenPGP


Re: [gentoo-user] "Broken soname dependencies found" after portage upgrade

2021-12-12 Thread Neil Bothwick
On Sun, 12 Dec 2021 18:11:53 +0200, Nikos Chantziaras wrote:

> After upgrading from portage 3.0.28 to 3.0.30, I get this when doing 
> emerge --depclean:
> 
> Calculating dependencies... done!
>   * Broken soname dependencies found:
>   *
>   *   x86_64: libexpat.so required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>   *   x86_64: libgdbm_compat.so.3 required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>   *   x86_64: liblttng-ust.so.0 required by:
>   * dev-dotnet/dotnet-sdk-bin-6.0.100
>   *
>   *   x86_64: libreadline.so.6 required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>   *   x86_64: libgdbm.so.3 required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>   *   x86_64: libbz2.so.1.0 required by:
>   * app-emulation/vmware-workstation-16.2.1.18811642-r1
>   *
>  >>> No packages selected for removal by depclean  
> 
> What does it even mean?
> 
> (And before anyone asks, the software works just fine, and neither 
> revdep-rebuild nor revdep-rebuild.sh find anything wrong.)

Revdep-rebuild won't work because vmware-workstation is a binary package.
You may need to add a file to /etc/revdep-rebuild that adds the vmware
path (somewhere in /opt?) to SEARCH_DIRS_MASK.


-- 
Neil Bothwick

We are upping our standards - so up yours.


pgpFLmgxvpv04.pgp
Description: OpenPGP digital signature


[gentoo-user] "Broken soname dependencies found" after portage upgrade

2021-12-12 Thread Nikos Chantziaras
After upgrading from portage 3.0.28 to 3.0.30, I get this when doing 
emerge --depclean:


Calculating dependencies... done!
 * Broken soname dependencies found:
 *
 *   x86_64: libexpat.so required by:
 * app-emulation/vmware-workstation-16.2.1.18811642-r1
 *
 *   x86_64: libgdbm_compat.so.3 required by:
 * app-emulation/vmware-workstation-16.2.1.18811642-r1
 *
 *   x86_64: liblttng-ust.so.0 required by:
 * dev-dotnet/dotnet-sdk-bin-6.0.100
 *
 *   x86_64: libreadline.so.6 required by:
 * app-emulation/vmware-workstation-16.2.1.18811642-r1
 *
 *   x86_64: libgdbm.so.3 required by:
 * app-emulation/vmware-workstation-16.2.1.18811642-r1
 *
 *   x86_64: libbz2.so.1.0 required by:
 * app-emulation/vmware-workstation-16.2.1.18811642-r1
 *
>>> No packages selected for removal by depclean

What does it even mean?

(And before anyone asks, the software works just fine, and neither 
revdep-rebuild nor revdep-rebuild.sh find anything wrong.)