#1113403 phat: FTBFS with CMake 4

#1113403#5
Date:
2025-08-31 23:02:43 UTC
From:
To:
Dear maintainer,

During a test rebuild for CMake 4, phat failed to rebuild.

Log Summary:
-------------------------------------------------------------------------------
[...]
 bf73b29b5fa6f2e1f5fe07592be4fd8d4671f33b17fd174f0e62c6d6e8c0064e 4744 phat_1.7-1.debian.tar.xz
Files:
 ed9ebbae228e06edf8916e3eab3fc56e 4762145 phat_1.7.orig.tar.gz
 8dd94ecd87298e3e5ff73d6cb91b5307 4744 phat_1.7-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEz8XvhRCFHnNVtV6AnRFYKv1UjPoFAmZXPRsSHGdzcHJAbm9u
ZW1wdHkub3JnAAoJEJ0RWCr9VIz69scP/iDy+12g6lnFbEE/PpNHbUhw8Zinubrf
vYgSiFs7lVO/cNr/QSf6fwonZlFKQVKMiix0fx4kbUCgOwBrmTRRT/AazTof8i4W
Jgtgyf7DEVDjfrqypsCpCl7vjiA6nKsjWGc3FYExdZz/xDQY6HKMRCBqgeRNI+kz
dpDy3TfpU4ZuL6eLmpo6FskaTgdd5AM4pfpEKgM2l/C4QoQKpEA1A9isDKbMofhC
wKkKfh18bMFWqCDWGWVVVPyjqZmCQ+K3CCJPIfW5m5YyERtH7S+5Di8Rm7UEgWTi
IvjMcedrRBGcF969z3UfVC5nRaoWMOVlDc2HE3OBxdaGyfnfSGpjL3haLhw1ew/f
BnfQo4uXEBgCQ6Mpen22mscwrot2I3bbbp8AN/Acuq7AXhxWxLI9490WHz2BgOdb
YXXxsWxIC7oLMJAo0yRIaL6f4KpbQPX63avG6Rr+hd9oV/fEmQWHLj5Ihb4MZeQa
hHhE3Co5dbWc6rib1raTMI0B+SSM0nXbcSXbRHvpozOERUeWExlEncqAisRWSvY2
9a/czajsj8I7jJ7/u6wz/y+YPpxsXNh2tKIdy/FcdDOmGiIeV5+jjLoJ0TRDzwvY
Tv57p2v5VtQExuditEeW3TiZFP4JDP7Tx9jp6X+aeUz6Y9jBAAx1aEVX1f86A1EW
KmfIDC/X6KyK
=jbSh
-----END PGP SIGNATURE-----

dpkg-source: warning: cannot verify inline signature for ./phat_1.7-1.dsc: no acceptable signature found
dpkg-source: info: extracting phat in /build/reproducible-path/phat-1.7
dpkg-source: info: unpacking phat_1.7.orig.tar.gz
dpkg-source: info: unpacking phat_1.7-1.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-Correct-version-number.patch

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 phat
dpkg-buildpackage: info: source version 1.7-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Gard Spreemann <gspr@nonempty.org>
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture arm64
 debian/rules clean
dh clean --buildsystem=cmake --builddirectory=build
   debian/rules execute_before_dh_auto_clean
make[1]: Entering directory '/build/reproducible-path/phat-1.7'
rm -f build/phat.1
make[1]: Leaving directory '/build/reproducible-path/phat-1.7'
   dh_auto_clean -O--buildsystem=cmake -O--builddirectory=build
   dh_autoreconf_clean -O--buildsystem=cmake -O--builddirectory=build
   dh_clean -O--buildsystem=cmake -O--builddirectory=build
dh clean --with python3 --buildsystem=pybuild
   debian/rules execute_before_dh_auto_clean
make[1]: Entering directory '/build/reproducible-path/phat-1.7'
rm -f build/phat.1
make[1]: Leaving directory '/build/reproducible-path/phat-1.7'
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:311: python3.13 setup.py clean
running clean
removing '/build/reproducible-path/phat-1.7/.pybuild/cpython3_3.13_phat/build' (and everything under it)
'build/bdist.linux-aarch64' does not exist -- can't clean it
'build/scripts-3.13' does not exist -- can't clean it
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules binary
dh binary --buildsystem=cmake --builddirectory=build
   dh_update_autotools_config -O--buildsystem=cmake -O--builddirectory=build
   dh_autoreconf -O--buildsystem=cmake -O--builddirectory=build
   dh_auto_configure -O--buildsystem=cmake -O--builddirectory=build
	cd build && 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 ..
CMake Error at CMakeLists.txt:1 (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/2407034/ 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/154459/ 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
#1113403#12
Date:
2025-09-01 11:52:22 UTC
From:
To:
I have downgraded the bug to non-RC severity temporarily and reverted
CMake in unstable to version 3.31.6. I plan to re-upgrade in about a
month's time. I realize that despite my April announcement, the upload
to unstable came rather surprising, and I don't want to cause
unnecessary pain.

Also, the build log URL has an unfortunate mistake. The correct URL
should include the workspace, i.e.,

https://debusine.debian.net/debian/developers/artifact/XXXX

CMake 4 will also be available in experimental again, so it can be
used to verify that the bug is fixed.

Cheers
Timo