Debian 12.15 ends 32-bit x86 era for the distro

Debian 13.6 and 12.15 land together

Debian has pushed out two new point releases: Debian 13.6 (“Trixie”) and Debian 12.15 (“Bookworm”). Both are routine updates, but Bookworm’s 12.15 build carries extra weight.

According to the project, Debian 12.15 is the final point release of Debian 12. There will be no Debian 12.16, and regular support for 12.x is now ending.

Bookworm moves to LTS

With 12.15 out, Debian 12 transitions to the Long Term Support (LTS) team. That reduced level of support is planned to run until mid-2028.

Security and critical fixes will continue under LTS, but users shouldn’t expect the same cadence or breadth of updates as during mainstream support.

End of the road for 32-bit x86 in Debian

The final Bookworm point release also quietly closes a long-running chapter: mainstream Debian support for 32-bit x86 is effectively over.

Recommended reading

Mira Murati’s lab unveils Inkling, a 975B open model

The Register notes that Debian 12.15 is the last point release that fully supports 32-bit x86 in the usual way. Debian 13 still supports some 32-bit Arm chips via the armhf port, but not 32-bit x86 as a first-class architecture.

As previously flagged in 2023, Debian 13 requires a 64-bit x86 CPU. The distro can still run 32-bit packages and libraries, so legacy 32-bit apps remain usable on 64-bit installs. However, installing Trixie directly on a 32-bit x86 CPU now means compiling your own kernel.

That’s not just theoretical. As reported in late 2025, WindowMaker Live 13.2 and antiX Linux both take this route on 32-bit hardware.

Firmware updater hits 2.0.20 and secure boot warning

Both new Debian point releases ship with an updated fwupd from the Linux Vendor Firmware Service, now at version 2.0.20.

The Arch wiki notes that fwupd can only update firmware on systems booted in UEFI mode, not legacy BIOS. That limitation matters less than it sounds, because the tool can also update UEFI secure-boot signing certificates and databases.

That capability suddenly matters. Red Hat warned last month that Microsoft’s original 2011 secure-boot certificates have expired. If you rely on secure boot and your machines haven’t rebooted in some time, you could run into issues.

The article stresses that problems are not likely, and there is a simple workaround: disabling secure boot if something breaks. Still, updating the certificates via fwupd is strongly advised. The Debian Wiki has further guidance, and Linux Weekly News offers a full technical rundown of the secure-boot issue.

GeoIP database rolled back over licensing

Not all changes are upgrades. The geoip-database package has been downgraded to a 2019 version.

The project cites changes in the MaxMind EULA for newer GeoLite releases that clash with the Debian Free Software Guidelines. To avoid the license conflict, Debian has reverted to an older release of the database.

The release notes take an unusually direct tone with users:

“Consumers of this data are strongly encouraged to obtain a GeoLite license directly and cease reliance on the 'geoip-database' package.”

For Debian admins, the message is clear: if you need current GeoLite data, you’ll have to get it straight from MaxMind, not from Debian’s default packages.