64-bit time_t transition in progress

The goal of this transition is to ensure that 32-bit architectures in trixie
(whether they are currently release architectures, or out of archive, etc)
will be capable of handling current and future timestamps referring to times
beyond 2038.

The release goal is described here:

https://wiki.debian.org/ReleaseGoals/64bit-time

The implementation of this plan, as discussed on debian-devel[1], involves
mass-NMUs of > 1200 library packages to rename them for (presumed)
ABI-breaking changes.

https://lwn.net/ml/debian-devel-anno...mer.dodds.net/

After observing and hearing about Debian's 'forced enforcement' of Systemd, it's high time Debian had better start arguing now to get the hassle over by 2038 :-P.

Personally, I don't think anyone outside of a museum will be using 32bit CPUs in 2038. There was a lively discussion on LKML back in 2005 on this very subject when I had to enroll to get my usb bug sorted. So why doesn't Debian do whatever LKML decided to do in 2005/6?