83
Y2K38 bug? Debian switching to 64-bit time for everything (www.theregister.com)
submitted 1 day ago by sabreW4K3@lazysoci.al to c/linux@programming.dev
14 comments fedilink hide all child comments

cross-posted from: https://lazysoci.al/post/30920734

all 15 comments
sorted by: hot top controversial new old
[-] Ephera@lemmy.ml 9 points 1 day ago

Hmm, Debian and other long-term support distros are kind of in a tricky position with problems like these. On the one hand, they don't want to break things, so they'll often make changes like these relatively late. But on the other hand, someone might still run a current version of the distro in 2038, so they actually want to solve it as early as possible, too.

[-] fargeol@lemmy.world 34 points 1 day ago

Relevant XKCD: https://xkcd.com/607/

[-] Tja@programming.dev 18 points 1 day ago

But that's not a solution, it's just postponing the problem!!1!one

[-] AnarchistArtificer@lemmy.world 8 points 1 day ago

"it's just postponing the problem!!1!one" The thing of including a "one" to make the irony of your exclamation abundantly clear is a delightful bit of internet-ese. I always find it funny when I see it

[-] teawrecks@sopuli.xyz 2 points 14 hours ago

For me the giveaway was 2^64 being 1.8*10^19 years from now.

[-] Tja@programming.dev 2 points 21 hours ago

Thanks! I find it nicer than including "/s" at the end :)

[-] Rhaedas@fedia.io 10 points 1 day ago

True, but only if the latest theories on Big Crunch being back on the table don't hold up. Debian ought to not only push out 64 bit time, but place "now" right in the middle to cover any discoveries of an older universe. Hell, they ought to do that and make it 128 bit, to cover anything.

Exponentials can be profound when you grasp them for that fleeting second.

[-] over_clox@lemmy.world 15 points 1 day ago

'...(potentially setting time back to 1900)...'

From my understanding, unless I'm mistaken, wouldn't the 32 bit time reset back to 1970 after the overflow/rollover?

[-] fargeol@lemmy.world 22 points 1 day ago

https://en.wikipedia.org/wiki/Year_2038_problem

Timestamps that use signed int will go back to 1901 (-2,147,483,647)

[-] over_clox@lemmy.world 11 points 1 day ago

Oh shit, I missed that part, I always thought it was an unsigned int.. ๐Ÿคฆโ€โ™‚๏ธ

Well today I learned ๐Ÿ‘

[-] schnurrito@discuss.tchncs.de 7 points 1 day ago

you're wrong, but so was the article, so I guess that cancels out :D it's late 1901

[-] eah@programming.dev 17 points 1 day ago

There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors.

[-] glimse@lemmy.world 1 points 1 day ago

That's just a really solid joke.

[-] data1701d@startrek.website 8 points 1 day ago

The actual transition happened ages ago - 2024 or so. A bunch of transitional packages in Testing and Sid had -t64 appended for a while.

this post was submitted on 25 Jul 2025
83 points (100.0% liked)

Linux

8602 readers
888 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev