user [email protected]
usertags 1133435 python3.15
thanks
Hi!
While rebuilding the python related packages against the Python 3.15rc2
version I ran into this issue [1].
This can be fixed with the upstream commit 06dcced:
libbpf-tools/opensnoop: hint on unused variable [2].
On top of this, as this package doesn't match the python module name, in
order to pass the autodep8 autopkgtest, the import_name needs to be set
to 'bcc'.
I've applied the fix in the sandbox [3] to verify that it builds
successfully, please consider applying the patch to get the package back
to building successfully.
Happy hacking,
[1]: https://debusine.debian.net/debian/r-python-python3.15/artifact/4603275/
[2]:
https://github.com/iovisor/bcc/commit/06dccedd74bc34f5a06cd523e731d7b6655b5d08
[3]: https://debusine.debian.net/debian/r-python-python3.15/
--
"Can you imagine what I would do if I could do all I can?" -- Sun Tzu
Saludos /\/\ /\ >< `/
commit 06dccedd74bc34f5a06cd523e731d7b6655b5d08
Author: Athos Ribeiro <[email protected]>
Date: Thu Apr 23 11:31:00 2026 -0300
Origin: https://github.com/iovisor/bcc/commit/06dccedd74bc34f5a06cd523e731d7b6655b5d08
Forwarded: not-needed
libbpf-tools/opensnoop: hint on unused variable
GCC-16 changed the default of the unused-but-set-variable warnings,
which now throws an error when -Wall or -Wextra is enabled.
sps_cnt is only used when USE_BLAZESYM is defined. This patch does a
void cast to hint the compiler to ignore sps_cnt being unused in those
cases.
* https://gcc.gnu.org/gcc-16/porting_to.html#changes-to-wunused
--- a/libbpf-tools/opensnoop.c
+++ b/libbpf-tools/opensnoop.c
@@ -286,6 +286,8 @@
blazesym_result_free(result);
#endif
+ /* avoid compiler warnings on sps_cnt not being used */
+ (void) sps_cnt;
}
void handle_lost_events(void *ctx, int cpu, __u64 lost_cnt)
import_name = bcc
