| 6 Apr 2025 |
 @hexa:lossy.network | all of these were in the last channel bump | 17:54:23 |
 Geoffrey Frogeye | Also bumping python3Packages.tzdata to 2025.1 (corresponds to not-the-python-package tzdata 2025a) was not enough, hence I went with 2025.2 | 17:55:30 |
| @hexa:lossy.network | which is funny, since we bumped tzdata and python3.pkgs.tzdata is independent 🤔 | 17:56:50 |
| @hexa:lossy.network | and ical consumes the python version | 17:57:22 |
| @hexa:lossy.network | are you mixing channels? | 17:57:49 |
| 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 |
