After looking at this further, I think this is the best we can do for noble.
Among other things, the reason the downstream patch that supported /etc/timezone in systemd was dropped is that it was difficult to keep correct as the locations in the codebase which referenced /etc/localtime grew/changed. While other components may use /etc/timezone, that file is owned by tzdata, and so that package is responsible for updating the contents. I think pointing to this[1] discourse post, and in particular this[2] comment, is the best way to document the expected behavior. [1] https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu-using-the-command-line/35307 [2] https://discourse.ubuntu.com/t/how-to-change-the-time-zone-in-ubuntu-using-the-command-line/35307/2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103839 Title: timedatectl set-timezone does not update /etc/timezone, leaving system with inconsistent time zone setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2103839/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
