On 2024-05-06, Simon Tournier wrote: > -------------------- Start of forwarded message -------------------- > Subject: bug#69800: kcalendarcore is a time bomb > To: 69...@debbugs.gnu.org > Date: Thu, 14 Mar 2024 20:20:43 +0100 > From: Vivien Kraus via Bug reports for GNU Guix <bug-g...@gnu.org> > > Dear Guix, > > Kcalendarcore does not build anymore. According to CI, it stopped > working this march, on gnome-team and rust-branch (I can’t build it > either on master). > > http://ci.guix.gnu.org/search?query=kcalendarcore > > Best regards, > > Vivien > -------------------- End of forwarded message -------------------- > > and this fix: > > * gnu/packages/kde-frameworks.scm (kcalendarcore) [#:phases]: Add > 'disable-failing-test. > > My question is: Could we automatically detect by CI such time-related > test? > > > Other said, would it be possible to have one (or more) node that build > with a date in the future? Say 3 years. In Bordeaux? Or in Berlin? > Using the “Dolorean VM” [2], it could be nice to setup one node.
This would also be good for checking reproducible builds, as time is one of the harder things to normalize in the guix (or any) build environment! I would recommend using some padded days, e.g. 3 x 365 days + 31 days + 1 day (leap years) + 1 day (for good measure), as this maximises the chance that embedded day, month and year will always be different. > PS: Do we speak about bug of year 2038? ;-) Either speak now or wait for the inevitible! :) live well, vagrant
signature.asc
Description: PGP signature
