'Venerable Linux distribution Debian is side-stepping the Y2K38 bug – also known as the Unix Epochalypse – by switching to 64-bit time for everything but the oldest of supported hardware, starting with the upcoming Debian 13 "Trixie" release. "[We will] use 64-bit time_t on 32-bit architectures to avoid the 'year 2038 problem' when the existing 32-bit signed int rolls over (potentially setting time back to 1900)," the Debian maintainers say of the move and the problem it aims to fix. y2k illustration retro futuristic The 'nothing-happened' Y2K bug – how the IT industry worked overtime to save world's computers READ MORE "This is now less than 15 years away and plenty of systems that will have problems have already been shipped. We should stop adding to the problem." Readers of a certain vintage will remember well the "Y2K problem," caused by retrospectively shortsighted attempts to save a couple of bytes by using two-digit years – meaning that "2000" is represented as "00" and assumed to be "1900." While predictions of aircraft falling from the skies and bank balances being wiped out by negative-decades of interest did not, thankfully, come true, that was purely due to the tireless behind-the-scenes work of software developers who were able to patch affected systems before celebrating the turn of the century. There's another, less well-known clock problem looming, however: the Unix Epochalypse,which affects any systems that measure time the Unix way – in seconds elapsed since January 1, 1970. Come the very precise time of 03:14:07 UTC on January 19, 2038, the number of seconds elapsed will be larger than can be represented by a signed 32-bit integer. This would be fine if the decision hadn't been made all those years ago to store the number of seconds in exactly such a format.' -- source: https://www.theregister.com/2025/07/25/y2k38_bug_debian/ Cheers, Peter