| 6 Apr 2025 |
 Geoffrey Frogeye | On unstable it's fine because the bump of both tzdata are happening in the same staging batch (not sure that's the right terminology), it's a 24.11-only problem. | 17:58:31 |
 @hexa:lossy.network | oh, python itself depends on tzdata | 17:58:45 |
| @hexa:lossy.network |
ical> E FileNotFoundError: [Errno 2] No such file or directory: '/nix/store/zpkj9lmgkrcinkwa9k458viszgmncx29-python3.12-tzdata-2024.2/lib/python3.12/site-packages/tzdata/zoneinfo/America/Coyhaique'
| 18:01:03 |
| @hexa:lossy.network | so it clearly looks into the python tzdata package | 18:01:12 |
| @hexa:lossy.network | which has not been bumped | 18:01:36 |
| @hexa:lossy.network | and neither has ical been bumped | 18:01:42 |
| Geoffrey Frogeye | ical can survive without being bumped | 18:02:14 |
| @hexa:lossy.network | I am thoroughly confused how this started failing | 18:02:16 |
| @hexa:lossy.network | python3.pkgs.ical reads zone information from python3.pkgs.tzdata | 18:02:37 |
| @hexa:lossy.network | neither were updated, but now python3.pkgs.ical fails to test | 18:02:48 |
| @hexa:lossy.network | instead tzdata was updated | 18:02:57 |
| Geoffrey Frogeye | I haven't dug too much there, but I think: the list of timezones is provided by pkgs.tzdata. But python3.pkgs.ical does tests which requires additional data provided by python3.pkgs.tzdata? | 18:04:02 |
| @hexa:lossy.network | either way, bumping python3.pkgs.tzdata will take 2-3 weeks at least | 18:06:09 |
| @hexa:lossy.network | https://wiki.nixos.org/wiki/Home_Assistant#Tracking_the_latest_release | 18:08:25 |
| @hexa:lossy.network | you can use this snippet to track the latest release from unstable instead for the time being | 18:08:38 |
