Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#71264 - [sysdig] needs rebuilt for grpc 1.38
Attached to Project:
Community Packages
Opened by Jérôme Tamba (sprsd) - Tuesday, 15 June 2021, 12:37 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Tuesday, 15 June 2021, 13:54 GMT
Opened by Jérôme Tamba (sprsd) - Tuesday, 15 June 2021, 12:37 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Tuesday, 15 June 2021, 13:54 GMT
|
DetailsDescription:
Package grpc in versions 1.38.0-1 and above has some sonames that do not follow conventions, having two period-separated integers in place of one, for example: > ll /usr/lib/libgrpc++_unsecure.so* lrwxrwxrwx 1 root root 26 Jun 2 22:55 /usr/lib/libgrpc++_unsecure.so -> libgrpc++_unsecure.so.1.38 lrwxrwxrwx 1 root root 28 Jun 2 22:55 /usr/lib/libgrpc++_unsecure.so.1.38 -> libgrpc++_unsecure.so.1.38.0 -rwxr-xr-x 1 root root 482K Jun 2 22:55 /usr/lib/libgrpc++_unsecure.so.1.38.0 > objdump -p /usr/lib/libgrpc++_unsecure.so | grep SONAME SONAME libgrpc++_unsecure.so.1.38 Some others soname of the package, on the other hands, have the usual format: > ll /usr/lib/libgrpc.so* lrwxrwxrwx 1 root root 13 Jun 2 22:55 /usr/lib/libgrpc.so -> libgrpc.so.16 lrwxrwxrwx 1 root root 17 Jun 2 22:55 /usr/lib/libgrpc.so.16 -> libgrpc.so.16.0.0 -rwxr-xr-x 1 root root 3.8M Jun 2 22:55 /usr/lib/libgrpc.so.16.0.0 > objdump -p /usr/lib/libgrpc.so | grep SONAME SONAME libgrpc.so.16 Upgrading the package has thus broken the sysdig and csysdig binaries of the sysdig package: > ldd /bin/sysdig linux-vdso.so.1 (0x00007fff04b96000) libelf.so.1 => /usr/lib/libelf.so.1 (0x00007f45f4540000) libz.so.1 => /usr/lib/libz.so.1 (0x00007f45f4526000) libcurl.so.4 => /usr/lib/libcurl.so.4 (0x00007f45f4489000) libjsoncpp.so.24 => /usr/lib/libjsoncpp.so.24 (0x00007f45f4451000) libtbb.so.2 => /usr/lib/libtbb.so.2 (0x00007f45f440b000) libcares.so.2 => /usr/lib/libcares.so.2 (0x00007f45f43f2000) libgrpc++_unsecure.so.1 => not found ... This has been caused by a change upstream: https://github.com/grpc/grpc/commit/df73c74f99183cd7674149aadc693b12d121c9d9 As a side note, one of the issues this commit was resolving contains this comment suggesting that grpc++ abi compatibility is unsupported and recommending against packaging it: https://github.com/grpc/grpc/issues/23205#issuecomment-790806982 I hope reporting this as a grpc bug (and not sysdig one) was the correct choice, sorry if I got it wrong. Steps to reproduce: - Up to date system, install sysdig which pulls grpc - $ sysdig sysdig: error while loading shared libraries: libgrpc++_unsecure.so.1: cannot open shared object file: No such file or directory |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Tuesday, 15 June 2021, 13:54 GMT
Reason for closing: Fixed
Additional comments about closing: sysdig-0.27.1-5
Tuesday, 15 June 2021, 13:54 GMT
Reason for closing: Fixed
Additional comments about closing: sysdig-0.27.1-5