Summary: | x11-misc/colord-1.4.7-r1 installs shared libraries that lack a SONAME | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | floppym, leio, sam, williamh |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://github.com/mesonbuild/meson/pull/8996 https://github.com/mesonbuild/meson/pull/9629 https://bugs.gentoo.org/show_bug.cgi?id=828562 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Agostino Sarubbo
2021-12-19 22:04:57 UTC
Created attachment 759824 [details]
build.log
build log and emerge --info
$ readelf -d /usr/lib64/libcolordcompat.so |grep SONAME 0x000000000000000e (SONAME) Library soname: [libcolordcompat.so] ci has reproduced this issue with version 1.4.5-r3 - Updating summary. This appears to be a regression with meson-0.60, as it works fine for me on 0.59, but not with 0.60 for sam (and SONAME is set when he downgraded to 0.59 too). Though it might be some bug in colord meson.build's too that gets triggered now, or is meant to actually be without a SONAME but not in /usr/lib64 or something. Can't look further today myself As of meson-0.60, shared_module targets do not get an SONAME. This could probably be fixed by changing 'colordcompat' to a shared_library target in lib/compat/meson.build. Alternatively, the module could be moved out of LIBDIR to avoid the QA check. ci has reproduced this issue with version 1.4.6 - Updating summary. ci has reproduced this issue with version 1.4.6-r1 - Updating summary. tinderbox_musl has reproduced this issue with version 1.4.6-r2 - Updating summary. ci has reproduced this issue with version 1.4.7 - Updating summary. ci has reproduced this issue with version 1.4.7-r1 - Updating summary. |