Hello! Here’s a summary of my first +1 maintenance shift (please don’t judge too strictly).
FTBFS fixes
gdb-mingw-w64 (MP #501291)
gdb-mingw-w64-target cross-compiles for Windows PE targets but was picking up the -Wl,--package-metadata flag (now included in dpkg-buildflags by default), which is only meaningful for ELF binaries. Fixed by switching from DEB_LDFLAGS_MAINT_APPEND to DEB_LDFLAGS_MAINT_SET so that ELF-specific linker flags are not inherited. Thanks to @bdrung for the sponsorship.
unity (MP #501513)
Reviewed an existing fix proposal (MP #500983 by Lexi Ewald) and then prepared an improved version addressing all build failures. I’ve upgraded C++ standard from C++11 to C++14, added missing <algorithm> and <cstdint> includes, replaced deprecated boost::prior with std::prev, added a systemd user unit directory fallback for when pkg-config data is unavailable, and bumped debhelper compat to 13. Thanks to @ginggs for the sponsorship.
meson (LP #2143267)
Meson’s Boost dependency resolver was silently selecting libboost_python313.so on systems running Python 3.14, producing a Python 3.14 ABI extension module linked against a 3.13 library, which segfaulted at import time. Fixed by deriving the exact Boost Python module name from the detected Python version (e.g., boost_python314) and marking the dependency as non-required so tests skip gracefully when no matching library is found. Thanks to @r41k0u for the sponsorship.
rust-rav1e (LP #2133869, comment #7) | version in Ubuntu
rust-ravif was broken after librust-rav1e-dev was dropped (it had been vendored as a MIR requirement, but the MIR was closed as the package could stay in universe). Attempted to revert the vendoring, but hit a cargo toml ^0.8 vs Ubuntu’s rust-toml 0.9.8 version conflict. Debian 0.8.1-7 already bumps the constraint to ^0.9, and that’s the only change, no new upstream release or new features. I’ve verified in a PPA the build passes in resolute-proposed and requested a sync. Thanks to @jbicha for the sponsorship.
WIP
libnbd (LP #2143548)
Investigating an FTBFS where the test suite crashes with SIGPIPE (exit code 141) when running parallel tests with verbose output on amd64, arm64, and ppc64el. The failure doesn’t look straightforward, so I’m continuing to work on this beyond the shift.