| 6 Apr 2025 |
|  nikongen joined the room. | 17:41:20 |
 @hexa:lossy.network | backporting tzdata is a bit much 😊 | 17:47:41 |
| @hexa:lossy.network | what is the "calendar-enabled" home assistant? | 17:49:27 |
| @hexa:lossy.network | oh, something broke the ical packaging on 24.11? meh | 17:50:12 |
 Geoffrey Frogeye | Anything installation with local_calendar, local_todo or google, maybe more | 17:52:20 |
| Geoffrey Frogeye | * Any installation with local_calendar, local_todo or google, maybe more | 17:52:44 |
| @hexa:lossy.network | commit 6dbc44e8109c30a6523e0543a7ced88777e3d1dd
Merge: ebc05ccbb4d0 db07b2139708
Author: VladimÃr ÄŒunát <v@cunat.cz>
Date: Sun Mar 23 18:54:15 2025 +0100
tzdata: 2025a -> 2025b (#392462)
commit db07b21397089d01aebfe736181947ba65a9b42c
Author: Sergei Trofimovich <slyich@gmail.com>
Date: Sun Mar 23 06:30:20 2025 +0000
tzdata: 2025a -> 2025b
Changes: https://github.com/eggert/tz/compare/2025a...2025b
(cherry picked from commit 0e22650f6956c978a4dc68bfb3bb8c40b78070c1)
commit ebc05ccbb4d0342242fbae049aef758dce1e2808
Merge: 017303ab3b6f 4652098e774d
Author: VladimÃr ÄŒunát <v@cunat.cz>
Date: Sun Mar 23 18:52:21 2025 +0100
tzdata: 2024b -> 2025a (#392460)
commit 4652098e774d130001e046737792ffde1122c5ce
Author: Sergei Trofimovich <slyich@gmail.com>
Date: Sat Jan 18 06:11:58 2025 +0000
tzdata: 2024b -> 2025a
Changes: https://github.com/eggert/tz/blob/2025a/NEWS
(cherry picked from commit 892f0edfb10f1b74bc2bf6fa2b49eef170819b0f)
| 17:52:51 |
| @hexa:lossy.network | these look like plausible causes | 17:52:57 |
| Geoffrey Frogeye | Pretty sure it's 2025a -> 2025b | 17:53:31 |
| Geoffrey Frogeye | It added the "America/Coyhaique" timezone https://lists.iana.org/hyperkitty/list/tz-announce@iana.org/thread/6JVHNHLB6I2WAYTQ75L6KEPEQHFXAJK3/ | 17:54:21 |
| @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 |
| 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 |
