61105 2026-10-16 20:56:58 +0300 lomiri-app-launch, qtmir: FTBFS with libuserspace-rcu 0.15.7-alt2 (-std=gnu99), NMU in tasks #437309, #437310 2026-10-16 20:56:58 +0300 1 1 4 Development Sisyphus lomiri-app-launch unstable all Linux NEW P5 normal --- 1 lav snk snk qa-sisyphus oldest_to_newest 302674 0 lav 2026-10-16 20:56:58 +0300 Since libuserspace-rcu 0.15.7-alt2 (built with --enable-compiler-atomic-builtins, bug #60896) the urcu headers require C11: /usr/include/urcu/compiler.h:62: #error "URCU was configured to use atomic builtins, but this toolchain does not support them." lttng-ust tracepoint headers include urcu, so C code with lttng tracepoints built with -std=gnu99 fails (beehive FTBFS since 2026-10-10/11): - lomiri-app-launch: lomiri-app-launch-trace.c (CMakeLists.txt sets -std=gnu99) - qtmir: src/platforms/mirserver/tracepoints.c (CMakeLists.txt sets -std=gnu99) NMU: - task #437309 lomiri-app-launch 0.2.0-alt1.1: -std=gnu99 -> -std=gnu11 (the same as ROSA 2004-std-workaround.patch; upstream main still has gnu99) - task #437310 qtmir 0.8.0_git20260226.fb30a11-alt1.1: C part of upstream commit 929ad8c6 (CMAKE_C_STANDARD 17 instead of -std=gnu99)