Summary: | net-misc/networkmanager-1.46.0-r1: QA Notice: Unresolved soname dependency | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Neko-san <gentoo.qxrin> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | QA | CC: | bkohler, gnome, llvm, toolchain, zmedico |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Compressed Build Log |
Description
Neko-san
2024-04-07 09:26:54 UTC
Created attachment 889716 [details]
Compressed Build Log
(The full log's file size was too big to be attached uncompressed.)
networkmanager[tools] very clearly does depend on dev-libs/newt, which provides that library, so I'm not sure what's going on there. It reports it for me too. Reason is probably this: $ cat /var/db/pkg/dev-libs/newt-0.52.24/PROVIDES arm_64: _snack.so libnewt.so.0.52.24 while other packages that provide a *.so.X symlink (newt doesn't) record the correct SONAME of lib*.so.X in PROVIDES file, not the full path. Of course nmtui isn't linking to the very specific versioned file, but the one it can and portage's QA check gets confused because it got confused what to put in its own PROVIDES records. Given that, assigning to portage, not gnome@. CCing newt maintainer as well. There's some kind of toolchaing an/or split-usr interaction going on, since on my merge-usr system the soname dependency appears normal: # grep newt /var/tmp/portage/net-misc/networkmanager-1.46.0-r1/build-info/NEEDED.ELF.2 X86_64;/usr/bin/nmtui;;;libnm.so.0,libgio-2.0.so.0,libgobject-2.0.so.0,libglib-2.0.so.0,libgmodule-2.0.so.0,libnewt.so.0.52,libc.so.6,ld-linux-x86-64.so.2;x86_64 Also note that non-soname *.so symlinks have also appeared in bug 928400. It's noteworthy that this is happening with an llvm toolchain. |