** Description changed: [impact] bpftrace 0.20.2-1ubuntu4.2 is broken with the version of llvm-toolchain-18 in noble-updates: Regression from https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2081848 root@nsnx2:~# bpftrace bpftrace: error while loading shared libraries: libLLVM-18.so.18.1: cannot open shared object file: No such file or directory [test plan] bpftrace runs tests during build which verifies _something_ but also we should install bpftrace on a system that has no other packages from proposed and check it at least starts. + + [regression potential] + It is still possible that rebuilding bpftrace is not safe because of some other change in the archive since release. The tests should catch most of these, but if there is some other regression caused by building against a version in proposed and running against a version in release or updates it would not be caught (and sadly neither would the autopkgtests, they just build and run the tests). It's not clear what to do about this (other than improve the autopkgtests).
** Description changed: [impact] bpftrace 0.20.2-1ubuntu4.2 is broken with the version of llvm-toolchain-18 in noble-updates: Regression from https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2081848 root@nsnx2:~# bpftrace bpftrace: error while loading shared libraries: libLLVM-18.so.18.1: cannot open shared object file: No such file or directory [test plan] - bpftrace runs tests during build which verifies _something_ but also we should install bpftrace on a system that has no other packages from proposed and check it at least starts. + bpftrace runs tests during build which verifies _something_ but also we should install bpftrace on a system that has no other packages from proposed run a simple command such as "sudo bpftrace -e 'kprobe:do_nanosleep { printf("%d sleeping\n", pid); }'". [regression potential] - It is still possible that rebuilding bpftrace is not safe because of some other change in the archive since release. The tests should catch most of these, but if there is some other regression caused by building against a version in proposed and running against a version in release or updates it would not be caught (and sadly neither would the autopkgtests, they just build and run the tests). It's not clear what to do about this (other than improve the autopkgtests). + It is still possible that rebuilding bpftrace is not safe because of some other change in the archive since release. The tests should catch most of these, but if there is some other regression caused by building against a version in proposed and running against a version in release or updates it might not be caught (and sadly neither would the autopkgtests, they just build and run the tests). It's not clear what to do about this (other than improve the autopkgtests). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2097317 Title: bpftrace: error while loading shared libraries: libLLVM-18.so.18.1: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/2097317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
