Your message dated Thu, 8 Oct 2026 17:10:39 +0200 with message-id <aseyb-3S3ff8E7EO@nuc> and subject line Re: Bug#1148713: libatomic-queue: New upstream version available has caused the Debian Bug report #1148713, regarding libatomic-queue: New upstream version available to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1148713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1148713 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:libatomic-queue Version: 1.7.2-1 Severity: wishlist Hello. The author tells me in a github issue that version 1.9.4 is much better. This is what I found while trying to upgrade: - The package itself would build ok on unstable. - Apparently there is only one package using libatomic-queue-dev in their build-depends, namely "libmmmulti". I've checked and it builds fine when libatomic-queue-dev is at version 1.9.4. - Unfortunately, the autopkgtests would fail with this error: ninja: Entering directory `/tmp/autopkgtest-lxc.tt2yp8hv/downtmp/autopkgtest_tmp/build' [1/2] Compiling C++ object atomic_queue_tests.p/tests.cc.o FAILED: [code=1] atomic_queue_tests.p/tests.cc.o c++ -Iatomic_queue_tests.p -I. -I.. -I/usr/include -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O0 -g -DBOOST_ALL_NO_LIB -pthread -MD -MQ atomic_queue_tests.p/tests.cc.o -MF atomic_queue_tests.p/tests.cc.o.d -o atomic_queue_tests.p/tests.cc.o -c ../tests.cc ../tests.cc:10:10: fatal error: benchmarks.h: No such file or directory 10 | #include "benchmarks.h" | ^~~~~~~~~~~~~~ compilation terminated. ninja: build stopped: subcommand failed. Because the fix for that was not obvious to me I decided to upload 1.7.2-2 without upgrading to the new version yet. If it helps I could put version 1.9.4 in salsa without uploading anything yet. (I usually do my experiments in private forks). Thanks.
--- End Message ---
--- Begin Message ---Version: 1.9.4-1
--- End Message ---
