#2038

2 posts · Last used 21d

Back to Timeline
openSUSE Linux @opensuse@fosstodon.org · Jul 24, 2026
#Y2K38 isn't a distant problem; #openSUSE developers have been finding real breakages by #testing with #2038 clocks. #GCC now has -Wtime_t-conversion warnings, and #Leap 16 ships 2038-safe by default. The #community is tackling this head-on. https://news.opensuse.org/2026/01/20/os-community-tackling-y2k38-epoch/
4
0
2

You've seen all posts