I'm looking forward to fifteen years from now, when Easter Sunday falls on Thursday January 1, 1970.

@th Well well, someone's Linux server isn't using 64-bit integer dates yet.

Which also means it's running quite an old unupdated distro... Yikes.

@MontgomeryGator @th afaik 32 bit archs on recently updated distros are still using 32 bit integers. Unless things have progressed more than they had the last time I read about it, which may have happened since I know that people are working on it *right now*

@valhalla @th Oh, I stand corrected. Sorry for beinging so confidently incorrect. 😆

I kinda assumed that the appropriate patches for core distros would have been made, and trickled down to everything else to tackle the 2048 problem

@MontgomeryGator @th my understanding (from lurking on a relevant mailing list as an ignorant bystander) is that the patches / solution are available, but would break binary compatibility, so releasing them in a sane way in the distributions (and testing that nothing breaks even after recompiling) is going to take way more effort than the patches themselves.

And things are made worse by the fact that of the two mayor 32 bit archs one (x86, the other one(s) being the various arm variants) is mostly used for binary compatibility, these days.

AFAIK a lot of distros have just solved the issue by dropping support for 32 bit archs altogether :(

@th welcome to the Epochalypse. It must be Thursday, I never could get the hang of Thursdays.

@th @donmelton Hmm … so whatever patches they did for Y2K weren’t comprehensive. 🤦🏼‍♀️

@th Well, at least the app recognizes the problem in a way, because it does not fall back to 1901 and the numbers of days are not a very high positive number, but not printed.

Sign in to participate in the conversation
(void *) social site