-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
homeassistant: update to version 2021.8.8 #4580
Conversation
Is this PR going to be merged sometime this year? This PR was created 14 day's ago against 2021.4.6, and 2 day's ago 2021.5.1 was released https://github.com/home-assistant/core/releases/tag/2021.5.1 What's holding it? |
@Sweepr 3 failing CI checks. Unfortunately windows docker isn't supported, which leaves me currently unable to investigate. Any chance you have experience in this area? |
Be patiant, I am working on this. One open target is to reduce the package size by download of pure python packages at installation time. |
@hgy59 No rush, just asking.
Sadly no, same problem ;-) |
aed28a6
to
0934080
Compare
"All checks have passed", any e.t.a. on merge into master so we can pull from the package manager? |
0934080
to
1fcb57e
Compare
Makred as WIP, because armv7 packages do not work until the *.whl files are renamed with correct machine name (armv7l instead of arm). |
hello, we should expect HA for DSM7 can there be an approximate date? |
Thanks. Thanks for your job. |
Finally solved the wheel file naming by renaming the wheels at installation time. This might even work for armv5 (88f6281) but could not test that due to missing such a device. The real problem behind the naming of cross compiled wheels is, that crossenv names the 32-bit arm platform "arm" instead of "armv7l" and that pip uses the wheel file name to validate compatibility (wheels still define Tag: cp38-cp38-linux_arm instead of cp38-cp38-linux_armv7l in the WHEEL file) A special rename for pycryptodome is needed, as the tag is cp35-abi3-linux_armv7l and not cp38-cp38-linux_armv7l. By excluding pure python wheels from the package, the spk file size is reduced from > 110MB to < 33MB. As homeassistant has such a lot of dependent python packages there are still incompatible packages after installation. When an integration fails to install within homeassistant, this can often be solved by restarting homeassistant (either with restart in homeassistant or stop/run in the DSM package center). |
TESTERs are welcome, particular for ARMv5 (88f6281) and QorIQ (PPC) archs like DS-213air, DS-213, DS-413j, DS-213+, DS-413 or DS-x12. |
- avx-512f patch is now integrated in upstream
- introduce Makefile variable EXCLUDE_PURE_PYTHON_WHEELS to exclude pure python wheels from spk - adjust service_postinstall to install wheel files from package and remaining dependencies from index - use SYNOPKG_PKGVAR folder for config and migrate config folder for DSM6 -> DSM7 upgrades
- add cross/asyncstdlib to work around dependencies for devonavr
- use dedicated requirements file for postinst
- update numpy - update homeassistant, home-assistant-frontend, hass-nabucasa and dependencies
- separate requirements for default_config and components - add pycryptodomex - keep original name of wheels (fix for *-abi3-*.whl)
- revert specific wheel file names at build time - rename cross compiled wheels at installation time - use the real platform-tag to rename cross compiled wheels: the real problem behind the naming of cross compiled wheels is, that crossenv names the 32-bit arm platform "arm" instead of "armv7l" and that pip uses the wheel file name to validate compatibility (wheels still define Tag: cp38-cp38-linux_arm instead of cp38-cp38-linux_armv7l in the WHEEL file) - a special handling for pycryptodome is still needed, as the tag is cp35-abi3-linux_armv7l and not cp38-cp38-linux_armv7l
8245cfb
to
18eba06
Compare
Thanks, this version 2021.8.8 is ok for DS116 (armv7), installation and launch ok. |
Any e.t.a. on when it will be available in the https://packages.synocommunity.com/ Package Center? |
Hello Always KO for : NAS Model: DS416j Thanks for your help |
@Lylrok thanks for the feedback. |
Hello @hgy59 I don't know if you made any changes but I managed to reinstall the package and it seems to work again thank you so much |
@Lylrok you can do something for you: do not post your public URL 🤝 |
Just updated on DS216+, works like a charm, thank you for the hard work! |
A little feedback on the use of HA A big thank you again |
hello. after upgrading to DSM 7.0, I was able to repair the installation with no problem, but I lost the configuration. When I access, it asks me for data to create a new installation but I cannot continue, the button does not work. how could i solve it? Thanks a lot. I forgot to mention that I have a DS213j in case it's relevant |
Motivation: Update homeassistant to include security updates for pyyaml, Jinja2 and urllib3
Linked issues: #4475, closes #4490. closes #4458, #4519, closes #4761
Checklist
all-supported
completed successfullynew integrations installable from UI (since 2021.1.5-13)
Integrations that do not work