On 2026-07-01 02:52, Dag-Erling Smørgrav wrote:
I have no idea what this refers to
It refers to whether to allow TZ settings like
TZ="../zoneinfo-leaps/America/Los_Angeles", where I'm assuming "make
REDO=posix_right" in the default TZDB build. More generally, it's
whether relative TZ strings should be allowed to escape from
/usr/share/zoneinfo and to read from any file on the system.
The traditional tzcode behavior was to allow this in nonprivileged
programs, but reject it in privileged programs. In tzdb 2025c I changed
things to reject it for nonprivileged programs also. However, when 2025c
was merged into FreeBSD this change was explicitly omitted, and
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290520#c5> says that
this omission was because it caused some unit tests to fail. So
yesterday in commit ef93554c322b689f9e310a0e7ac699da86e1a70a I changed
tzcode back to its traditional behavior in this area.
I am still waiting for a reaction
to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290520#c5
The last time I changed tzcode's behavior to be more like FreeBSD's, in
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290520#c3> you
indicated a preference to wait until after a tzcode release before
taking the time to integrate the resulting tzcode into FreeBSD. With
that in mind, I had planned to bring this new matter up in the FreeBSD
bug report after the next tzcode release.
I wish you would make an effort to talk directly to us instead of
leaving passive-aggressive notes in the tzcode change log.
It's unfortunate that this attempt to work with you was misinterpreted
as being passive-aggressive. That was not the intent.
This time around would you prefer to merge immediately, rather than wait
for the next tzcode release? The next tzcode release should be fairly
soon, if that matters.
