Dear maintainer,
During a test rebuild for CMake 4, rttr failed to rebuild.
Log Summary:
-------------------------------------------------------------------------------
[...]
MZA51tg/0IM1T6+0XqBpfpXvZjXG+Ko8RoTcfTnzbjB9KPUBUPV3ys1KDRG3MjKT
leyf5SS/IXu83N82eRsgbkkx+RwaC3gSAXCJgn8NBt63uiSDimA98hI9z4U/mRRV
+MYgBCTX4UNCB5Am/Y253GtR4kJE83FcBX4KreK5jg3X4JcfxNUvNedUKVzj6Pph
JAaaLswVx1iAq4kcM+2vMXcEwrfT2MGSTRRsb2G64bRQurWJCdncEzgovNdsqDGq
8rmrXVMj9Tdvyk2j+s68vNNNkP/5FoHBJMtEmBI9LpnwQqxJQQc=
=/Htc
-----END PGP SIGNATURE-----
dpkg-source: warning: cannot verify inline signature for ./rttr_0.9.6+dfsg1-6.1.dsc: no acceptable signature found
dpkg-source: info: extracting rttr in /build/reproducible-path/rttr-0.9.6+dfsg1
dpkg-source: info: unpacking rttr_0.9.6+dfsg1.orig.tar.gz
dpkg-source: info: unpacking rttr_0.9.6+dfsg1-6.1.debian.tar.xz
Check disk space
----------------
Sufficient free space for build
User Environment
----------------
APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=sbuild
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SHELL=/bin/sh
USER=sbuild
dpkg-buildpackage
-----------------
Command: dpkg-buildpackage --sanitize-env -us -uc -b
dpkg-buildpackage: info: source package rttr
dpkg-buildpackage: info: source version 0.9.6+dfsg1-6.1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Benjamin Drung <bdrung@debian.org>
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture arm64
debian/rules clean
dh clean
dh_clean
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/reproducible-path/rttr-0.9.6+dfsg1'
dh_auto_configure -- \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_BUILD_TYPE=Release -DBUILD_UNIT_TESTS=false -DUSE_PCH=false -DBUILD_BENCHMARKS=false -DBUILD_EXAMPLES=false \
-DCMAKE_CXX_FLAGS="-g -O2 -ffile-prefix-map=/build/reproducible-path/rttr-0.9.6+dfsg1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard"
cd obj-aarch64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb PKG_CONFIG=/usr/bin/pkg-config cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/aarch64-linux-gnu -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release -DBUILD_UNIT_TESTS=false -DUSE_PCH=false -DBUILD_BENCHMARKS=false -DBUILD_EXAMPLES=false "-DCMAKE_CXX_FLAGS=-g -O2 -ffile-prefix-map=/build/reproducible-path/rttr-0.9.6+dfsg1=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -mbranch-protection=standard" ..
CMake Error at CMakeLists.txt:34 (cmake_minimum_required):
Compatibility with CMake < 3.5 has been removed from CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.
-------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here (for the next 30 days):
https://debusine.debian.net/artifact/2410628/
The most likely cause of build failures is the removed backwards compatibility for
CMake versions earlier than 3.5. You can find additional information in my
debian-devel announcement:
https://lists.debian.org/debian-devel/2025/04/msg00310.html
About the archive rebuild: The build was made on debusine.debian.net,
using sbuild.
You can find the build task here:
https://debusine.debian.net/work-request/154789/
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks,
Timo