Teamspeak broken

[Folling]

Is this a new report?

Yes

System Info

Void 6.18.12_1 x86_64 AuthenticAMD uptodate rrrrrmdF

Package(s) Affected

teamspeak3

Does a report exist for this bug with the project's home (upstream) and/or another distro?

MISSING: libglapi>=7.11_1
ERROR: Transaction aborted due to unresolved dependencies

Expected behaviour

teamspeak3 should be installable using xbps-src and xi

Actual behaviour

It's not because libglapi was recently removed (afaict because it's now provided by libgallium), but xbps-src still detects it as a dependency for teamspeak3. Newer teamspeak versions fix this.

Steps to reproduce

1. ./xbps-src pkg teamspeak3
2. xi teamspeak3

[classabbyamp]

does removing line 158 (the one with glapi on it) from common/shlibs fix it?

[Folling]

xbps-src errors:

   SONAME: libglapi.so.0 <-> UNKNOWN PKG PLEASE FIX!
   SONAME: libglib-2.0.so.0 <-> glib>=2.86.0_1
   SONAME: libgthread-2.0.so.0 <-> glib>=2.86.0_1
   SONAME: libm.so.6 <-> glibc>=2.41_1
   SONAME: libnspr4.so <-> nspr>=4.37_1
   SONAME: libnss3.so <-> nss>=3.116_1
   SONAME: libnssutil3.so <-> nss>=3.116_1
   SONAME: libpci.so.3 <-> pciutils>=3.7.0_1
   SONAME: libplc4.so <-> nspr>=4.37_1
   SONAME: libplds4.so <-> nspr>=4.37_1
   SONAME: libpthread.so.0 <-> glibc>=2.41_1
   SONAME: libpulse.so.0 <-> libpulseaudio>=15.0_1
   SONAME: libquazip.so <-> teamspeak3 (ignored)
   SONAME: libresolv.so.2 <-> glibc>=2.41_1
   SONAME: librt.so.1 <-> glibc>=2.41_1
   SONAME: libsmime3.so <-> nss>=3.116_1
   SONAME: libxcb-dri2.so.0 <-> libxcb>=1.2_1
   SONAME: libxcb-dri3.so.0 <-> libxcb>=1.10_1
   SONAME: libxcb-glx.so.0 <-> libxcb>=1.2_1
   SONAME: libxcb-present.so.0 <-> libxcb>=1.10_1
   SONAME: libxcb-sync.so.1 <-> libxcb>=1.10_1
   SONAME: libxcb.so.1 <-> libxcb>=1.2_1
   SONAME: libxkbcommon.so.0 <-> libxkbcommon>=0.2.0_1
   SONAME: libxml2.so.2 <-> libxml2>=2.7.0_1
   SONAME: libxshmfence.so.1 <-> libxshmfence>=1.1_1
   SONAME: libxslt.so.1 <-> libxslt>=1.1.24_1
   SONAME: libz.so.1 <-> zlib>=1.2.3_1
=> ERROR: teamspeak3-3.5.6_2: cannot guess required shlibs, aborting!

I was able to fix it by moving to a newer teamspeak version locally, but as far as I understand that ts version doesn't support 32 bit anymore, so I'm not sure if we can package it.

[classabbyamp]

which newer version? still 3.something or the 6.something beta? if it's not the beta we could update thr template.

because this is a precompiled binary, we can't do much if it requires old libraries void no longer has

[Folling]

I've updated to 3.6.2

[fanyx]

I can't replicate teamspeak requiring libglapi.so.0 on my system. It's not required at all during my build of 3.6.2.

Meanwhile i've found two other issues, one of them resolvable, the other isn't:

• resolvable: libGLdispatch.so.0 is provided by libglvnd, but has no entry in common/shlibs.
• unresolvable: teamspeak3 is requiring libwebp.so.6 on my build, but we've moved on to libwebp7 by now.

[Folling]

Yes 3.6.2 works flawlessly, it's the existing version 3.5.6 that breaks. Which is why I'm advocating for the upgrade to the template

[fanyx]

See my post above.
Build of 3.6.2 breaks, due to libwebp6 not available in void repos anymore.
We've upgraded to libwebp7 and deprecated webp6.

nihil:~ 
 ✔ $ xlocate libwebp.so.6
nihil:~ 
 ✗ $ 

=> teamspeak3-3.6.2_1: running pre-pkg hook: 04-generate-runtime-deps ...
[...]
   SONAME: libwebp.so.6 <-> UNKNOWN PKG PLEASE FIX!
[...]
=> ERROR: teamspeak3-3.6.2_1: cannot guess required shlibs, aborting!

[Folling]

I saw your post, but you claimed you cannot replicate it because "it's not required in your build of 3.6.2", but that's not replicating anything as I am reporting an issue for 3.5.6.

And yes, my upgrade to 3.6.2 worked around the libwebp issue by removing the webp.6 library in do_install: rm ./imageformats/libqwebp.so which works fine for my purposes. I had also added libglvnd in shlibs. Sorry for not mentioning that earlier.

[fanyx]

but that's not replicating anything as I am reporting an issue for 3.5.6.

Sorry, was investigating if your proposed "fix by upgrading" was feasible.
You're correct, that my analysis does not help with the current version 3.5.9 package.

[Folling]

probably just a misunderstanding, my side included :D