References to time zones should not be kept

  • Open
  • quality assurance status badge
Details
One participant
  • Leo Famulari
Owner
unassigned
Submitted by
Leo Famulari
Severity
normal
L
L
Leo Famulari wrote on 26 Apr 2020 22:23
(address . bug-guix@gnu.org)
20200426202348.GA1187@jasmine.lan
Time zones of Earth are changed several times per year, both for future
and past dates. In order to ensure that our clocks display the correct
time, Guix needs to keep our time zone package (tzdata) up to date.

However, the current situation makes this impractical, because changing
tzdata causes ~1400 package rebuilds per-architecture (`guix refresh -l
tzdata`).

We should make sure that packages which use time zones look up the time
zones dynamically, at run-time, rather than recording a store reference
to the tzdata package, which will be obsolete in months, at the latest.

I used `guix graph --type=reverse-package tzdata` to start, and found
that the main culprit here is bluez, which depends on tzdata via
libical.

Using the attached patch, we can make libical look up time zones at
runtime with the $TZDIR environment variable. Bluez still builds with
this; I'm not sure what it does with libical and if it still works
correctly.

However, this makes evolution-data-server test suite fail. I'm not sure
how to fix evolution-data-server correctly. The fine points of looking
up time zones in evolution-data-server were already discussed:
L
L
Leo Famulari wrote on 26 Apr 2020 22:36
(address . bug-guix@gnu.org)
20200426203650.GA3428@jasmine.lan
Go packages are also keeping references to tzdata, probably because of
the tzdata-path variable in our Go compiler package definitions.
?