-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
ADS integration Exec format error #458
Comments
The problem is with the pyads library not being built for the different platforms. Before the switch to musllinux, the packages were built per platform, but were named the same and seemed platform independant: I can't find info on how/when the wheel is built by HA and how it is defined to only produce the *py3-none-any.whl file |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I found some time to search the problem, and I think I found the reason why this has been failing all along. The library would need a special switch to let setuptools build the wheel with a platform specific name.
So probably nothing to do with the way HA is building the wheels. I have made a pull request on the library in the hope they will include it. |
Referring to home-assistant/core#74067 (and related home-assistant/core#74952
After some initial research I believe the ADS package issue correlates with home-assistant/docker#236 where the transition seems to be done to move to musllinux wheel.
I am willing to dive into this codebase and logic - when I find time - to identify what can be done to fix this, if someone can confirm this is a viable path. I am however not a python dev so it'll take me some time to catch up with wheels and how they interact with the codebase in terms of identification of requirements and how to identify which need different architecture targets.
The text was updated successfully, but these errors were encountered: