| 15 Jun 2021 |
 @hexa:lossy.network | and then use that as the package set checked in parse-requirements.py | 13:23:09 |
| @hexa:lossy.network | diff --git a/pkgs/servers/home-assistant/default.nix b/pkgs/servers/home-assistant/default.nix
index c2eae375658..805306a2d9c 100644
--- a/pkgs/servers/home-assistant/default.nix
+++ b/pkgs/servers/home-assistant/default.nix
@@ -799,6 +799,7 @@ in with py.pkgs; buildPythonApplication rec {
tests = {
inherit (nixosTests) home-assistant;
};
+ pythonPackages = py;
};
meta = with lib; {
diff --git a/pkgs/servers/home-assistant/parse-requirements.py b/pkgs/servers/home-assistant/parse-requirements.py
index 27de7a60f37..1eeb0f1356c 100755
--- a/pkgs/servers/home-assistant/parse-requirements.py
+++ b/pkgs/servers/home-assistant/parse-requirements.py
@@ -32,7 +32,7 @@ from rich.console import Console
from rich.table import Table
COMPONENT_PREFIX = "homeassistant.components"
-PKG_SET = "python3Packages"
+PKG_SET = "home-assistant.pythonPackages"
# If some requirements are matched by multiple Python packages,
# the following can be used to choose one of them
| 13:24:55 |
| @hexa:lossy.network | looks to be working, but parse-requirements doesn't yet find all packages again | 13:25:11 |
| @hexa:lossy.network | * diff --git a/pkgs/servers/home-assistant/default.nix b/pkgs/servers/home-assistant/default.nix
index c2eae375658..805306a2d9c 100644
--- a/pkgs/servers/home-assistant/default.nix
+++ b/pkgs/servers/home-assistant/default.nix
@@ -799,6 +799,7 @@ in with py.pkgs; buildPythonApplication rec {
tests = {
inherit (nixosTests) home-assistant;
};
+ pythonPackages = py.pkgs;
};
meta = with lib; {
diff --git a/pkgs/servers/home-assistant/parse-requirements.py b/pkgs/servers/home-assistant/parse-requirements.py
index 27de7a60f37..1eeb0f1356c 100755
--- a/pkgs/servers/home-assistant/parse-requirements.py
+++ b/pkgs/servers/home-assistant/parse-requirements.py
@@ -32,7 +32,7 @@ from rich.console import Console
from rich.table import Table
COMPONENT_PREFIX = "homeassistant.components"
-PKG_SET = "python3Packages"
+PKG_SET = "home-assistant.pythonPackages"
# If some requirements are matched by multiple Python packages,
# the following can be used to choose one of them
| 13:26:28 |
| @hexa:lossy.network | nvm, works | 13:26:45 |
| @hexa:lossy.network | https://github.com/home-assistant/core/releases/tag/2021.6.5 | 19:18:20 |
| @hexa:lossy.network | new dependency in a minor release 😒 | 19:18:37 |
| @hexa:lossy.network | https://github.com/NixOS/nixpkgs/pull/126984 | 19:36:36 |
| @hexa:lossy.network invited  balsoft. | 20:11:20 |
| balsoft joined the room. | 20:11:37 |
| balsoft | First of all, thank you all for packaging home assistant, it's awesome to blink my lights from NixOS :) | 20:25:57 |
| balsoft | But, as you might have guessed, I came with some feedback re: the drama that happened. I think it would be better for the image of the Nix community if instead of immediately merging stuff without reaching some consensus or at least understanding and thus producing extra drama, we would just wait a couple of days and let things cool down. Obviously not stating this as fact, just my opinion you're free to disregard. | 20:28:29 |
| balsoft | Although, to be fair, I applaud the way you handled the issue otherwise, calm, polite and constructive. | 20:29:16 |
| balsoft | * Although, to be fair, I applaud the way you handled the issue otherwise: calm, polite and constructive. | 20:29:23 |
| @hexa:lossy.network | Yes, we all learned a great deal on how to handle such an oddball in the future! | 21:03:41 |
|  Linux Hackerman joined the room. | 23:42:43 |
| 16 Jun 2021 |
|  CRTified joined the room. | 08:35:35 |
| CRTified | Wow, I've somehow missed the whole debacle around that ambee package. Combined with HA moving away from YAML more and more, I'm really starting to hope that there's a sensible alternative available 🤔 I mean, most components are probably easy to move to "just MQTT", but the number of available integrations is hard to ignore. | 08:47:02 |
| CRTified | * Wow, I've somehow missed the whole debacle around that ambee package (Although the maintainer was at least somewhat reasonable in the end).
Combined with HA moving away from YAML more and more, I'm really starting to hope that there's a sensible alternative available 🤔 I mean, most components are probably easy to move to "just MQTT", but the number of available integrations is hard to ignore. | 09:01:31 |
| 17 Jun 2021 |
 dotlambda | Has frenck been made aware of the sentence added to https://nixos.org/manual/nixos/unstable/options.html#opt-services.home-assistant.enable? (It's not actually on the website yet cause the channel has yet to advance.) | 21:33:23 |
| dotlambda | I'm asking because of his comment from 3.5h ago: https://github.com/NixOS/nixpkgs/pull/126047#issuecomment-863449031. | 21:33:56 |
| @hexa:lossy.network | what | 21:34:37 |
| @hexa:lossy.network | how did that come up again?! | 21:34:40 |
| dotlambda | We can also mention that we support 2/3 of HA's components, though I'm not sure how large that number feels to him. | 21:39:54 |
| dotlambda | And tell him that without his package we can't bring it to 100%. | 21:41:34 |
 Zhaofeng Li | Wait, again? Seriously? | 21:43:14 |
| @hexa:lossy.network | let's leave it until the weekend | 21:58:54 |
| @hexa:lossy.network | or later | 21:58:55 |
| balsoft | I suppose it may be best to just fork these packages, rename them, remove all contact information (but keep the copyright notice as per the license) and ship those? I think it's best for everybody. | 22:10:19 |
| balsoft | That way, if it "harms user experience" it no longer harms upstream, since the project's name is completely different | 22:12:04 |
