Bug#1072146: libexplain: kill(pid = 42 "sh", sig = SIGTERM) failed, Operation not permitted (EPERM)

Source: libexplain Version: 1.4.D001-13 Severity: normal Tags: patch Hi, libexplain fails to build in sbuild+unshare now used on some of the buildd: PATH=`pwd`/bin:$PATH /bin/sh test/04/t0462a.sh 1c1 < kill(pid = 42, sig = SIGTERM) failed, Operation not permitted (EPERM) --- > kill(pid = 42 "sh"

Bug#1070014: libwibble: FTBFS on arm{64,el}: (7/36) Fs: ../wibble/sys/fs.test.h: 72: assertion `i.ischr()' failed;

Hi, * Sebastian Ramacher [2024-04-28 17:11]: https://buildd.debian.org/status/fetch.php?pkg=libwibble&arch=arm64&ver=1.1-3%2Bb1&stamp=1714230781&raw=0 make[5]: Entering directory '/<>/debian/build' cd /<>/debian/build/wibble && sh -c "LD_LIBRARY_PATH=/<>/debian/build/wibble /<>/debian/build

Bug#1021121: not installable due to new python3-matrix-nio

Package: python3-pantalaimon Version: 0.10.4-2 Severity: grave Tags: fixed-upstream Hi, I've uploaded python3-matrix-nio 0.20.0 to unstable to close a security issue. Sadly python3-pantalaimon has a versioned dependency making it now uninstallable: python3-matrix-nio (<< 0.20). There is a new ups

Bug#1104498: libquazip: add qtdeclarative5-dev as a build dependency to make the package reproducible (future FTBFS)

Source: libquazip Version: 0.9.1-4 Severity: normal Tags: ftbfs User: debian...@lists.debian.org Usertags: apt-cache Hi, libquazip uses d-shlibs that uses apt-cache and the apt cache during the build to get information about packages not installed in the build chroot. That makes the package FTBFS

Bug#1098859: ipsvd: please revert changes to 1.0.0-8 (#1090184), bug fixed in sbuild

Source: ipsvd Version: 1.0.0-11 Severity: wishlist X-Debbugs-Cc: Andreas Beckmann , Niels Thykier Hi, thanks for your uploads to work around #1090184. From my testing this was actually a bug in sbuild: https://salsa.debian.org/debian/sbuild/-/commit/39120d9263656b31d7bc98d87ccc415955d11851 th

Bug#1108416: zbarcam: Invalid argument in zbar_processor_init()

Control: severity -1 important * Kim Alvefur [2025-07-03 14:56]: On Mon, Jun 30, 2025 at 08:13:31PM +0200, Jochen Sprickerhof wrote: I tried to reproduce your bug but for me zbarcam works without problem. Can you give some more information about the camera you used? It's one of the

Bug#1108416: zbarcam: Invalid argument in zbar_processor_init()

* Kim Alvefur [2025-07-03 17:30]: I imagine this could also be something in the kernel rather than in zbar-tools but I haven't looked into that yet. you can try: mpv av://v4l2:/dev/video0 to test. mpv manages to show video from the even-numbered devices but the fps is *very* low Given t

Bug#1108416: zbarcam: Invalid argument in zbar_processor_init()

Hi Kim, I tried to reproduce your bug but for me zbarcam works without problem. Can you give some more information about the camera you used? Also: * Kim Alvefur [2025-06-27 23:49]: Output of `strace -o zbar.trace zbarcam` below. This does not include threads, can you you run it again wit