Found by Rhonda, example URLs is (currently) http://noone.org/blog/2038/
It's a classical Unix timestamp issue:
Cannot handle date (0, 0, 0, 1, 11, 2038) at /etc/blosxom/plugins/calendar line 214
http://rt.cpan.org/Public/Bug/Display.html?id=39209
It's not the fault of the calendar plugin, it's rooted in perl core, so the fix is not on us.
Yes, a Perl Grant is running to fix this! http://www.perlfoundation.org/make_localtime_and_gmtime_work_past_2038
The new Perl package Time::y2038 fixes the problem, i think.
Log in to post a comment.
http://rt.cpan.org/Public/Bug/Display.html?id=39209
It's not the fault of the calendar plugin, it's rooted in perl core, so the fix is not on us.
Yes, a Perl Grant is running to fix this!
http://www.perlfoundation.org/make_localtime_and_gmtime_work_past_2038
The new Perl package Time::y2038 fixes the problem, i think.