Dependency conflict with Home Assistant 0.103.2
See original GitHub issueVersion of HACS
0.20.3
Describe the bug
Upgrading HACS from 0.19.0 to 0.20.3 fails due to dependency conflict with aiohttp=3.6.2 (homeassistant requires aiohttp=3.6.1), there were also other conflicts but they all seem to be related to aiohttp.
Since HACS needs to “live” in the same environment as Home Assistant, it seems that we need to establish some parity in the requirements, otherwise it creates a mess when trying to upgrade HACS with incompatible requirements.
log
ERROR: homeassistant 0.103.2 has requirement aiohttp==3.6.1, but you'll have aiohttp 3.6.2 which is incompatible.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
0.103: Happy Holidays, Service calls, StarLine, GeoNet NZ ...
Home Assistant 0.103 is released, which is the last major release for this ... which wasn't always the case, and therefore inconsistent.
Read more >Problems with dependencies - Home Assistant
Almost all integrations have external dependencies to communicate with your devices and services. Sometimes Home Assistant is unable to install the ...
Read more >Can't upgrade due to cryptography (and pip)
I get this: ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the ......
Read more >HA 0.103.0 update broke HACS (Requirements for hacs not ...
The main one missing is HACS, when i check the log files i see the following. 2019-12-13 17:47:56 ERROR (MainThread) [homeassistant.setup] Setup ...
Read more >0.103: Unable to import timer component - Configuration
Component error: timer - cannot import name 'ENTITY_SERVICE_SCHEMA' from 'homeassistant.helpers.config_validation' ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thanks @ludeeus, in my case this issue seem to be related to permissions, since I’m running the HASS container with non-root UID/GID (you know, for security 😄) the user only has write permissions to
/config
and this happens:this seems to be related to this https://community.home-assistant.io/t/installing-ha-in-docker-on-ubuntu-as-non-root-user/48424/24 and looks like getting things to work with a non-root user is a bit tricky… will close this, as it doesn’t seem to be related to HACS but a more general issue for any of us running HASS with non-root user.
This issue is closed, closed issues are ignored.
If you have issues similar to this, please open a seperate issue. https://github.com/custom-components/hacs/issues/new/choose
And remember to fill out the entire issue template 😃