Bugzilla – Bug 1203982
tcl FTBFS in 2038
Last modified: 2023-04-07 08:46:19 UTC
While working on reproducible builds for openSUSE, I found that our tcl package stops to build after 2038-01-19 from some y2k38 issue To reproduce osc co openSUSE:Factory/tcl && cd $_ osc build --vm-type=kvm --noservice --clean \ --build-opt=--vm-custom-opt="-rtc base=2038-01-20T00:00:00" standard Actual results: ==== interp-34.3 basic test of limits - pure bytecode loop FAILED ==== interp-34.3 FAILED ==== interp-34.3.1 basic test of limits - pure inside-command loop FAILED ==== interp-34.3.1 FAILED ==== interp-34.8 time limits trigger in vwaits FAILED ==== interp-34.8 FAILED ==== interp-34.11 time limit extension in callbacks FAILED ==== interp-34.11 FAILED ==== interp-34.12 time limit extension in callbacks FAILED ==== interp-34.12 FAILED
AFAIK this is already being taken care of upstream, but I'll double-check.
I had a closer look and found that Tcl's time handling in general is y2k38 safe already with the [interp limit time -seconds] command being the only exception that breaks all the tests mentioned in comment 0. Opened an upstream bug: https://core.tcl-lang.org/tcl/tktview/3e8074aea74539cfd981ad6912c52c1488fc89c4
Committed the proposed fix from upstream to the devel project, and it passes the test suite with no failures when building as given in comment 0. Bernhard, please double-check before I submit to Factory.
I tested devel:languages:tcl/tcl and it builds fine now. Thanks.
Thanks, closing.