NEWS: announce bump of required minimum version of several components in next release

Distro            EOL     kernel  glibc meson  python  openssl cryptsetup util-linux elfutils libxcrypt libfido2 libseccomp
Ubuntu 24.04 LTS  2029-06 6.8     2.39  1.3.2  3.12.3  3.0.13  2.7.0      2.39.3     0.190    4.4.36    1.14.0   2.5.5
Ubuntu 25.04      2026-01 6.14    2.41  1.7.0  3.13.3  3.4.1   2.7.5      2.40.2     0.192    4.4.38    1.15.0   2.5.5
Ubuntu 25.10      2026-07 6.16    2.41  1.7.0  3.13.5  3.5.0   2.8.0      2.41       0.193    4.4.38    1.16.0   2.6.0
CentOS 9          2027-05 5.14.0  2.34  0.63.3 3.9.23  3.5.1   2.7.2      2.37.4     0.193    4.4.18    1.13.0   2.5.2
CentOS 10         2030-01 6.12.0  2.39  1.4.1  3.12.11 3.5.1   2.7.5      2.40.2     0.193    4.4.36    1.14.0   2.5.6
Debian 12         2026-06 6.12.38 2.36  1.7.0  3.11.2  3.0.17  2.6.1      2.38.1     0.192    4.4.33    1.12.0   2.5.4
Debian 13         2028-08 6.12.41 2.41  1.7.0  3.13.5  3.5.1   2.7.5      2.41       0.192    4.4.38    1.15.0   2.6.0

kernel releases: https://en.wikipedia.org/wiki/Linux_kernel_version_history
glibc releases: https://en.wikipedia.org/wiki/Glibc
python releases: https://en.wikipedia.org/wiki/History_of_Python
openssl releases: https://en.wikipedia.org/wiki/OpenSSL

See also #38608.
This commit is contained in:
Yu Watanabe
2025-08-18 01:27:26 +09:00
parent 1441f2e992
commit fd8c620751

15
NEWS
View File

@@ -174,6 +174,21 @@ CHANGES WITH 258 in spe:
Only nftables backend will be supported by systemd-networkd and
systemd-nspawn since v259.
* Required minimum version of following components is planned to be
bumped in the next release:
* Linux kernel >= 5.10 (recommended >= 5.14),
* glibc >= 2.34,
* libxcrypt >= 4.4.0 (libcrypt by glibc will be no longer supported),
* util-linux >= 2.37,
* elfutils >= 0.177,
* openssl >= 3.0.0,
* cryptsetup >= 2.4.0,
* libfido2 >= 1.5.0,
* libseccomp >= 2.4.0,
* python >= 3.9.0.
Please provide any feedback on systemd-devel if those removal of old
version support would cause problems.
Service manager/PID1:
* The PrivateUsers= unit setting now accepts a new value "full", which