On Tue, Apr 08, 2025 at 04:50:58PM -0500, Richard Laager wrote:
Option C would also keep the whole system consistent. But in that scenario, installing python-tz indirectly adds system-wide timezone values. I'm hesitant about that idea; it feels like "spooky action at a distance".
FWIW, that's how I feel about stuff that worked literally for decades up and disappearing for no apparent reason, but that's neither here nor there.
As a sysadmin, I could see that leading me to troubleshoot, "Why does this systemd timer that uses US/Pacific work on system A, but not system B?" or "Why does `TZ=US/Pacific date` work on some terminals and not others?" The answer, "Because system A installed software P that depends on python-tz, so that pulled in tzdata-legacy.", would feel surprising once I found it. This is heavily my personal opinion, though.
It's IMO much easier to understand this outcome in a debian context as dpkg -S US/Pacific
will clarify things pretty quickly.
