| 3 Jan 2025 |
 @hexa:lossy.network | but also powering it down | 12:51:10 |
| @hexa:lossy.network | https://github.com/esphome/home-assistant-voice-pe/issues/261 | 15:22:43 |
| @hexa:lossy.network | IoT devices shoulld support IPv6, change my view | 15:23:05 |
 Frédéric Christ | I don't think you can call it IoT if it doesn't support IPv6. | 17:53:40 |
| @hexa:lossy.network | https://github.com/Koenkk/zigbee2mqtt/discussions/24198 | 22:34:41 |
| 4 Jan 2025 |
|  macaroniskengz joined the room. | 00:01:21 |
| macaroniskengz | What is recommended, OCI containers or NixOS containers with HASS NixOS module? | 00:02:48 |
 mjm | Do you need containers at all? | 02:57:02 |
| macaroniskengz | I need at least some kind of isolation since I don't trust all components of my smart home installation | 20:39:35 |
| mjm | what components are you running here that you don't trust? | 20:40:23 |
| mjm | generally speaking, containers are not a very strong security boundary | 20:40:49 |
| macaroniskengz | For example HACS add-ons | 20:40:50 |
|  @rcouto:matrix.org left the room. | 21:08:22 |
| @hexa:lossy.network | we have set up pretty strong isolation for home-assistant in nixos | 21:48:25 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/blob/nixos-24.11/nixos/modules/services/home-automation/home-assistant.nix#L668-L722 | 21:49:03 |
| 5 Jan 2025 |
| @hexa:lossy.network | home-assistant 2025.1.0 merged | 03:03:10 |
| @hexa:lossy.network | enjoy | 03:03:15 |
| @hexa:lossy.network | and now to read the changelog 🤓 | 03:03:24 |
| @hexa:lossy.network | https://www.home-assistant.io/blog/2025/01/03/release-20251/ | 03:03:35 |
| @hexa:lossy.network | CRTified: urgh, tandoor-recipes uses the common clause, which makes it non-free software | 03:41:47 |
| @hexa:lossy.network | and we misrepresent it as agpl3.0-only since basically forever | 03:42:18 |
| @hexa:lossy.network | init at 1.4.1 | 03:42:22 |
| @hexa:lossy.network | common clause was put in place in version 0.10.0 | 03:43:26 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/371053 | 03:48:33 |
|  Xiyan (Sesquipedalio) joined the room. | 07:16:37 |
 ibizaman | Does everyone need to build triton-llvm locally these days or do I have some issue in my config? The approximative commit that still allows me to pull from the cache is https://github.com/NixOS/nixpkgs/commit/4a35f2b7eb8a8ad8ca54fd1358d8805b620af9b2, then 1 day afterwards until today any commit I tried requires me to build it.
The dependency of why I even need triton-llvm in the first place is (from nom):
┃ │ │ ┌─ ⏵ triton-llvm-19.1.0-rc1 (buildPhase) ⏱ 1m35s
┃ │ │ ┌─ ⏸ python3.12-triton-3.1.0
┃ │ │ ┌─ ⏸ python3.12-torch-2.5.1
┃ │ │ ┌─ ⏸ python3.12-safetensors-0.4.5
┃ │ │ ┌─ ⏸ python3.12-transformers-4.47.1
┃ │ │ ┌─ ⏸ python3.12-ctranslate2-4.5.0
┃ │ │ ┌─ ⏸ python3.12-faster-whisper-1.1.0
┃ │ │ ┌─ ⏸ wyoming-faster-whisper-2.2.0
┃ │ ├─ ⏸ unit-wyoming-faster-whisper-tiny-fr.service
┃ ├─ ⏸ system-units
┃ ┌─ ⏸ etc
┃ ⏸ nixos-system-baryum-25.05pre-git
I'm happy to bisect the commits more if needed.
| 10:23:53 |
| @hexa:lossy.network | There was a broken test | 10:57:46 |
| ibizaman | This, right? https://github.com/NixOS/nixpkgs/commit/b4240209aae34579d2e8e3de3203285d0c005f22
I tried that earlier but it still required me to build triton-llvm. But now it works!
That makes me think, is there a way to know beforehand what is in the NixOS cache? | 11:26:55 |
| ibizaman | * This is the fix, right? https://github.com/NixOS/nixpkgs/commit/b4240209aae34579d2e8e3de3203285d0c005f22
I tried that earlier but it still required me to build triton-llvm. But now it works!
That makes me think, is there a way to know beforehand what is in the NixOS cache? | 11:29:38 |
| ibizaman | * This is the fix, right? https://github.com/NixOS/nixpkgs/commit/b4240209aae34579d2e8e3de3203285d0c005f22
I tried that earlier but it still required me to build triton-llvm. But now it works!
That makes me think, is there a way to know beforehand what is in the NixOS cache? Like at least something saying this package in this nixpkgs commit is available in the cache? | 11:32:34 |
