| 6 Feb 2025 |
 dotlambda | In reply to @hexa:lossy.network
and we can probably just pick that as patch I don't think that's a good idea. Might inadvertently break things | 01:55:34 |
| dotlambda | Let's wait till March | 01:55:40 |
 @hexa:lossy.network | frankly, python-update cycles are nuts | 01:56:25 |
| @hexa:lossy.network | too few people chiming in | 01:56:30 |
| dotlambda | Sorry, I'm not helping either. Other priorities I guess :/ | 01:59:57 |
| @hexa:lossy.network | yeah, I get that | 02:00:28 |
| dotlambda | I'll make a PR for paho-mqtt v2 by default some time this week | 02:00:31 |
| @hexa:lossy.network | the feedback cycles are much better than years ago | 02:00:43 |
| dotlambda | Thanks for your herculean efforts with every python-updates cycle! | 02:01:23 |
| @hexa:lossy.network | rebasing quickly to get rid of the llama failures hopefully | 02:04:22 |
| @hexa:lossy.network | done | 02:07:39 |
| @hexa:lossy.network | looks like we're not getting any CI | 02:10:32 |
| @hexa:lossy.network | going to sleep | 02:22:02 |
 Sandro 🐧 | LOL, Home-Assistant blueprints (https://github.com/NixOS/nixpkgs/pull/377688) broke my blueprints module https://github.com/NuschtOS/nixos-modules/blob/15948a3fbca97409ad6ebf0a459fa77082c8476b/modules/home-assistant.nix#L10-L29 😂 | 15:52:58 |
| @hexa:lossy.network | time to migrate to the upstream version, enjoy | 16:01:37 |
| dotlambda | @sandro:supersandro.de: Any feature my version is missing? | 16:22:35 |
| dotlambda | home-assistant.tests.components.stream segfaults | 16:24:45 |
| dotlambda | Anyway, I think 2025.2.0 is ready barring a rebase | 16:25:31 |
| Sandro 🐧 | In reply to @robert:funklause.de
@sandro:supersandro.de: Any feature my version is missing? I didn't took a deeper look yet but probably not. Mine was pretty basic but if I find anything I'll let you know | 16:25:59 |
| @hexa:lossy.network | bisecting that as we speak | 16:26:34 |
| @hexa:lossy.network | also home-assistant-component-tests.sensor complains about a missing translation string, and that it should be added to a strings.json | 16:27:44 |
| @hexa:lossy.network | but it is already there | 16:27:53 |
| @hexa:lossy.network | would be good to understand why that breaks | 16:28:00 |
| @hexa:lossy.network | Failed: Translation not found for sensor: `issues.state_class_removed.description`. Please add to homeassistant/components/sensor/strings.json
| 16:29:16 |
| @hexa:lossy.network | anyway, merging now is pretty pointless, given that staging-next was just merged and that will clog hydra for two days or so | 16:46:57 |
| dotlambda | In reply to @hexa:lossy.network
anyway, merging now is pretty pointless, given that staging-next was just merged and that will clog hydra for two days or so It would prevent merge conflicts. | 17:07:59 |
| @hexa:lossy.network | and fix regressions, yeah | 17:08:21 |
| dotlambda | I probably won't have time to look into the handful of component tests that are still failing for a few days | 17:09:46 |
|  SomeoneSerge (utc+3) changed their display name from SomeoneSerge (Gand St. Pieters) to SomeoneSerge (UTC+U[-12,12]). | 17:48:15 |
| @hexa:lossy.network | rebased and merged | 18:09:11 |
