| Beerbelott | Hey :) | 02:24 |
|---|---|---|
| Beerbelott | Was anyone aware of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813226#10 ? | 02:24 |
| Beerbelott | > I don't think it is a bug. The correct way to configure the timezone has always been to change /etc/localtime symlink, ie in your case by doing "ln -sf /usr/share/zoneinfo/Asia/Tokyo /etc/localtime". This is what desktop environments do when changing the timezone and it is what systemd expects. | 02:24 |
| Beerbelott | WTH | 02:25 |
| Beerbelott | "This is what systemd expects" | 02:25 |
| Beerbelott | So in short writing /etc/timezone and make dpkg-reconfigure tzdata run over it won't produce the previously obtained & thus expected results | 02:25 |
| Beerbelott | I just discovered that, many years later. Is there a way to "fix" this mess at the Devuan level? | 02:26 |
| Beerbelott | The truth source pivoted from /etc/timezone to /etc/localtime | 02:27 |
| mason | Beerbelott: /etc/localtime as a symlink varies system by system but is in no way new. /etc/timezone is something else. | 14:40 |
| mason | That said, dpkg-reconfigure -fnoninteractive tzdata certainly does something unexpected at least in Beowulf. | 14:45 |
| gnu_srs1 | LeePen: Did you reset the debian/changelog when branching elogind for Debian (losing history)? | 17:16 |
| LeePen | Not completely. Just tried to make it accurately reflect the changes. | 17:18 |
| LeePen | I actually have a common branch where most elogind work happens. Then debian and devuan branches with the distro specific stuff. | 17:18 |
| LeePen | Merge common into each of those as required. | 17:19 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!