CMake 4 upload to unstable

[Timo Röhling]

Hi,









Cheers
Timo


[1] See https://lists.debian.org/debian-devel/2025/04/msg00310.html



--
⢀⣴⠾⠻⢶⣦⠀   ╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling                                       │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄⠀⠀⠀⠀   ╰────────────────────────────────────────────────────╯

this is a heads-up that I'm planning to upload the next minor release of CMake 4 to unstable. The release is scheduled about two weeks from now, around October 8th. Once CMake 4 hits unstable (again), I will upgrade the remaining open CMake 4 FTBFS bugs to serious. Virtually all those bugs are caused by asking for compatibility settings for CMake older than 3.5 (cmake_minimum_reqired() and friends), but very few packages actually rely on outdated behavior. Thus, most bugs can be trivially resolved [1]. Feel free to contact me for CMake debugging assistance if your package is one of the few unlucky ones. And many thanks to everyone who fixed their packages already! TL;DR: Bump version in cmake_minimum_required() or pass -DCMAKE_POLICY_VERSION_MINIMUM=3.5 via dh_auto_configure.

signature.asc
Description: PGP signature