New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2022.2 reports "Only supports linux, mac WSL" (approximately) #65733
Comments
I'm running on FreeBSD and it still works fine, the OS check needs to be a little broader. For now I'm working around it with the switch '--ignore-os-check' |
You can work around using https://github.com/home-assistant/architecture/blob/master/adr/0016-home-assistant-core.md |
Thanks, I can add that to my startup script. I hadn't seen that, and have been running Core on NetBSD since well before 2020-07. It's been obvious that it's mostly targetted at Linux, but python is very portable. I do see it a breaking change: I upgraded and my installation failed. I see your point about "never supported", but it's a huge leap from "we don't claim it works and won't necessarily address your bug reports, but clean PRs welcome" to "we will outright fail to run, even though there's no evidence anything doesn't work." I rarely encounter open source software with explicit failures on other than a small list of systems. I wonder if there a real problem this change is intended to address? As somone not using the 95% common OS, I'm used to occasional rough edges, and resolving them by figuring it out and sending portability patches. I've done that for some of the things used by plugins (openzwave, I think, and a few things zwave-js relies on). For HA Core itself, I haven't found anything at all in terms of code that was non-portable to BSD. So from my minority-OS viewpoint, this change seems to just cause non-Linux people grief and not do anything useful. But I don't know what kind of complaints you are getting, of course. |
Maintenance also involves support in e.g, issues like (for example) this one. Greetings from a heavy Linux user 😉 |
It doesn't apply when restarting from within HA though it seems (have opened a separate issue for that) Perhaps a warning rather than a hard fail may have been a better option? |
This issue only happened because it was a hard fail, not a warning. I really doubt you are getting silly issues from NetBSD users. I realize you probably don't mean it, but this comes across as "you are not from my tribe so you are unwelcome here; please go away". |
Unfortunately, it happens quite a bit, same for other unsupported platforms (as this change is not limited to NetBSD of course).
Sorry, I'm just bringing up reality. The reality is: "I run something you don't support and you broke it". The issue here is, you are running something we don't support. And yes; that is not our choice or issue. No hard feelings, and don't mean it harsh, it is what it is. |
@tdejneka I don't get your response, this report is not related to Supervised... |
🤦♂️ My mistake; post deleted. |
The problem
I have been running what is now called HA core for a long time, maybe 2 years, on NetBSD. With a few minor hiccups in integrations, it's been working fine. I am trying to update from 2021.12.9 to 2022.2.2. I've been updating multiple times a month for at least a year. This time, I got a message saying that HA only supports 3 particular operating systems. I had read the release notes, and this was not mentioned. I went back and searched, and can't find it.
What version of Home Assistant Core has the issue?
2022.2.2
What was the last working version of Home Assistant Core?
2021.12.9
What type of installation are you running?
Home Assistant Core
Integration causing the issue
No response
Link to integration documentation on our website
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
It seems pretty clear that the problem is new code designed to make HA Core fail. This seems buggy. IT seem to me that a program written in python should attempt to rely on what POSIX requires and python provides, to the extent that this is reasonable, and not fail artificially.
The text was updated successfully, but these errors were encountered: