| 13 Jun 2021 |
 Ekleog | lukegb (he/him): Agree with you that there was little else you could do, but IMO in this kind of cases where there's no literal aggression, closing the issue can be perceived as us abusing our rights, so maybe just doing nothing (including not replying would have “solved” the issue | 20:30:51 |
 lukegb (he/him) | I'd rather discussion about this general issue happen on Discourse tbh :p | 15:43:56 |
| Ekleog | basically letting the issues die in the usual nixpkgs cemetery, and then in three years someone from triage comes across them and closes because they made no sense in the first place (one shouldn't make their code open if they don't want it to be actually used) | 20:31:38 |
| Ekleog | * lukegb (he/him): Agree with you that there was little else you could do, but IMO in this kind of cases where there's no literal aggression, closing the issue can be perceived as us abusing our rights, so maybe just doing nothing (including not replying) would have “solved” the issue | 20:31:54 |
| Ekleog | (I know that if I came across this issue with no comments for like 1 month, I'd have closed with a comment like “Nixpkgs wants to package home-assistant, and as of today home-assistant depends on this library; so as of today we can't just remove this package. Alternative options have been provided in the thread but appear to not be interesting to the issue reporter, so let's close as there is nothing actionable here.”) | 20:34:22 |
| Ekleog | * lukegb (he/him): Agree with you that there was little else you could do, but IMO in this kind of cases where there's no literal aggression, locking the issue can be perceived as us abusing our rights, so maybe just doing nothing (including not replying) would have “solved” the issue | 20:34:49 |
| Ekleog | * lukegb (he/him): I'm with you that there was little else you could do, but IMO in this kind of cases where there's no literal aggression, locking the issue can be perceived as us abusing our rights, so maybe just doing nothing (including not replying) would have “solved” the issue | 20:35:32 |
| Ekleog | TL;DR: in this kind of cases, IMO slowing down the discussion by responding slowly (or not at all) is the best thing to do, as it gives emotions time to flatten | 20:37:12 |
| Ekleog | * TL;DR: in this kind of cases, IMO slowing down the discussion by responding slowly (or not at all) is the best thing to do, as it gives everyone's emotions time to flatten | 20:38:51 |
 dotlambda | If someone wants to help making Home Assistant upstream a little happier by packaging more dependencies, I suggest comparing the directories in https://github.com/home-assistant/core/tree/2021.6.4/tests/components with the list of componentTests because packages whose component is tested should be safe to add. | 23:20:02 |
 @hexa:lossy.network | I bulk added component tests quite recently | 23:38:28 |
| dotlambda | For packages that are already there I assume. I'm talking about those that are missing but for which component tests exist. | 23:51:49 |
| 14 Jun 2021 |
| @hexa:lossy.network | the reasoning that they would be happier if we packaged all component packages is unreasonable | 17:11:07 |
| @hexa:lossy.network | the enable toggle of home-assistant should clarify that users should not expect support from upstream home-assistant I guess | 18:35:20 |
| lukegb (he/him) | it would be nice if home-assistant upstream had a toggle for "this is a distribution package, not one of the home-assistant supported distribution models, you should not ask for support with HA, please ask <here> instead" | 19:17:08 |
| @hexa:lossy.network | oh yeah | 19:17:16 |
| lukegb (he/him) | but I don't think they're interested in that | 19:17:30 |
| lukegb (he/him) | unless you could sell it to them as a "this is a way of upselling people to HA OS" | 19:17:38 |
| @hexa:lossy.network | fwiw, it advertises itself as Installation method: core | 19:17:59 |
| @hexa:lossy.network | https://analytics.home-assistant.io/ | 19:18:19 |
| lukegb (he/him) | yeah, but core installation method is explicitly unsupported if it's using "the distribution Python" | 19:18:28 |
| @hexa:lossy.network | with 4,2% the smallest installation type, and probably very heterogeneous | 19:18:40 |
| lukegb (he/him) | iirc you have to use a virtualenv | 19:18:45 |
| @hexa:lossy.network | reasonable :) | 19:18:55 |
| lukegb (he/him) | https://github.com/home-assistant/architecture/blob/master/adr/0016-home-assistant-core.md#supported-python-versions | 19:19:36 |
| lukegb (he/him) | ah, it's collected here: https://sourcegraph.com/github.com/home-assistant/core/-/blob/homeassistant/helpers/system_info.py?utm_source=share#L42:9 | 19:21:57 |
| lukegb (he/him) | I'm guessing we somehow always manage to trigger is_virtual_env or something | 19:22:18 |
| @hexa:lossy.network | diff --git a/nixos/modules/services/misc/home-assistant.nix b/nixos/modules/services/misc/home-assistant.nix
index 1e33381de24..9c5d5b0eb02 100644
--- a/nixos/modules/services/misc/home-assistant.nix
+++ b/nixos/modules/services/misc/home-assistant.nix
@@ -66,7 +66,7 @@ in {
meta.maintainers = teams.home-assistant.members;
options.services.home-assistant = {
- enable = mkEnableOption "Home Assistant";
+ enable = mkEnableOption "Home Assistant. Please note that NixOS distribution of Home Assistant is unsupported upstream.";
configDir = mkOption {
default = "/var/lib/hass";
| 20:42:28 |
| @hexa:lossy.network | * diff --git a/nixos/modules/services/misc/home-assistant.nix b/nixos/modules/services/misc/home-assistant.nix
index 1e33381de24..9c5d5b0eb02 100644
--- a/nixos/modules/services/misc/home-assistant.nix
+++ b/nixos/modules/services/misc/home-assistant.nix
@@ -66,7 +66,7 @@ in {
meta.maintainers = teams.home-assistant.members;
options.services.home-assistant = {
- enable = mkEnableOption "Home Assistant";
+ enable = mkEnableOption "Home Assistant. Please note that the NixOS distribution of Home Assistant is unsupported upstream.";
configDir = mkOption {
default = "/var/lib/hass";
| 20:42:36 |
| @hexa:lossy.network | * diff --git a/nixos/modules/services/misc/home-assistant.nix b/nixos/modules/services/misc/home-assistant.nix
index 1e33381de24..9c5d5b0eb02 100644
--- a/nixos/modules/services/misc/home-assistant.nix
+++ b/nixos/modules/services/misc/home-assistant.nix
@@ -66,7 +66,7 @@ in {
meta.maintainers = teams.home-assistant.members;
options.services.home-assistant = {
- enable = mkEnableOption "Home Assistant";
+ enable = mkEnableOption "Home Assistant. Please note that the NixOS distribution of Home Assistant is unsupported upstream";
configDir = mkOption {
default = "/var/lib/hass";
| 20:42:43 |
