onkelbeh / homeassistantrepository Goto Github PK
View Code? Open in Web Editor NEW:house_with_garden: Home Assistant on Gentoo Linux.
Home Page: https://git.edevau.net/onkelbeh/HomeAssistantRepository
License: GNU General Public License v3.0
:house_with_garden: Home Assistant on Gentoo Linux.
Home Page: https://git.edevau.net/onkelbeh/HomeAssistantRepository
License: GNU General Public License v3.0
Hello Andreas,
there is a typo in the dependencies for 0.115.6 - there should be underscore instead of hyphen in dev-python/importlib_metadata-1.6.0, i.e. dev-python/importlib_underscore_metadata-1.6.0.
Thanks for your work
All the best
Rasto
There is syntax error in HomeAssistantRepository/app-misc/homeassistant/files/homeassistant.logrotate.
From man 8 logrotate
, I found info below:
su user group
Rotate log files set under this user and group instead of
using default user/group (usually root). user specifies the
user name used for rotation and group specifies the group used
for rotation. If the user/group you specify here does not
have sufficient privilege to make files with the ownership
you've specified in a create instruction, it will cause an
error. If logrotate runs with root privileges, it is
recommended to use the su directive to rotate files in
directories that are directly or indirectly in control of non-
privileged users.
So the last line su homeassistant.homeassistant
should be su homeassistant homeassistant
Since I use your overlay, I wish to have an ebuild for node-red that I use, install and update actually by hand:
https://github.com/node-red/node-red
SDIST uploaded to nextcloud
SDIST uploaded to nextcloud
The app-misc/homeassistant depends on dev-python/PyChromecast in this repository. But dev-python/pychromecast in Gentoo repository supply the same files with dev-python/PyChromecast.
Change the package name to lowercase may fix it.
The app-misc/homeassistant depends on dev-python/importlib-metadata in this repository. But dev-python/importlib_metadata in Gentoo repository supply the same files with dev-python/importlib-metadata.
Hello,
As I can see, there are a few missing dependencies:
dev-python/cleo
dev-python/clikit
dev-python/tomlkit
Moreover, after installing them manually, I am facing another problem - ModuleNotFoundError: No module named 'poetry.core'
, but when I try to install dev-python/poetry-core::gentoo
, I receive package collision:
* Package: dev-python/poetry-core-1.0.8
* Repository: gentoo
* Maintainer: [email protected]
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python3_9 userland_GNU
* FEATURES: network-sandbox preserve-libs sandbox userpriv usersandbox
>>> Unpacking source...
>>> Unpacking poetry-core-1.0.8.gh.tar.gz to /var/tmp/portage/dev-python/poetry-core-1.0.8/work
>>> Source unpacked in /var/tmp/portage/dev-python/poetry-core-1.0.8/work
>>> Preparing source in /var/tmp/portage/dev-python/poetry-core-1.0.8/work/poetry-core-1.0.8 ...
* Build system packages:
* dev-python/gpep517 : 3
* dev-python/installer : 0.5.1
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-python/poetry-core-1.0.8/work/poetry-core-1.0.8 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-python/poetry-core-1.0.8/work/poetry-core-1.0.8 ...
* python3_9: running distutils-r1_run_phase distutils-r1_python_compile
* Building the wheel for poetry-core-1.0.8 via poetry.core.masonry.api
* Installing poetry_core-1.0.8-py2.py3-none-any.whl to /var/tmp/portage/dev-python/poetry-core-1.0.8/work/poetry-core-1.0.8-python3_9/install
>>> Source compiled.
* Skipping make test/check due to ebuild restriction.
>>> Test phase [disabled because of RESTRICT=test]: dev-python/poetry-core-1.0.8
>>> Install dev-python/poetry-core-1.0.8 into /var/tmp/portage/dev-python/poetry-core-1.0.8/image
* python3_9: running distutils-r1_run_phase distutils-r1_python_install
* Optimize Python modules for /usr/lib/python3.9/site-packages
* Using python3.9 in global scope
* python3_9: running distutils-r1_run_phase distutils-r1_python_install_all
>>> Completed installing dev-python/poetry-core-1.0.8 into /var/tmp/portage/dev-python/poetry-core-1.0.8/image
* Final size of build directory: 2084 KiB (2.0 MiB)
* Final size of installed tree: 1328 KiB (1.2 MiB)
* checking 304 files for package collisions
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at https://bugs.gentoo.org/ unless you report exactly
* which two packages install the same file(s). See
* https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
* to solve the problem. And once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /usr/lib/python3.9/site-packages/poetry/__init__.py
* /usr/lib/python3.9/site-packages/poetry/__pycache__/__init__.cpython-39.opt-2.pyc
* /usr/lib/python3.9/site-packages/poetry/__pycache__/__init__.cpython-39.opt-1.pyc
* /usr/lib/python3.9/site-packages/poetry/__pycache__/__init__.cpython-39.pyc
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* dev-python/poetry-1.1.6:0::HomeAssistantRepository
* /usr/lib/python3.9/site-packages/poetry/__init__.py
* /usr/lib/python3.9/site-packages/poetry/__pycache__/__init__.cpython-39.opt-1.pyc
* /usr/lib/python3.9/site-packages/poetry/__pycache__/__init__.cpython-39.opt-2.pyc
* /usr/lib/python3.9/site-packages/poetry/__pycache__/__init__.cpython-39.pyc
*
* Package 'dev-python/poetry-core-1.0.8' NOT merged due to file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
I am unsure what exactly is wrong (maybe there are issues with my setup), thus your help will be highly appreciated.
fatal: unable to access 'https://git.edevau.net/onkelbeh/HomeAssistantRepository.git/': The requested URL returned error: 503
SDIST uploaded to nextcloud
Hello,
thanks for improving HomeAssistant! It seems home-assistant-frontend has been moved from app-misc to dev-python, yet app-misc/home-assistant-frontend is still required in homeassistant-0.111.4.ebuild:
All the best
Rasto
Is it possible to make hass-nabucasa optional dependency that's enabled only when cloud
flag is present for basic and full packages?
https://github.com/onkelbeh/HomeAssistantRepository/blob/master/app-misc/homeassistant-full/homeassistant-full-0.117.5.ebuild#L62
SDIST uploaded to nextcloud
dev-embedded/esptool-3.1 won't build without dev-python/pip and dev-python/wheel, but these aren't declared in BDEPEND.
Hey, I'm having warnings of portage trying to update pip and pillow to the latest stable amd64 versions, and the ebuilds from homeassitant-min not letting it do so, it seems that HA requires pip to be <20.3.0 when that version is not on the main tree anymore, also it requires pillow to be ~8.2.0 when we have newer stable versions.
Can you unlock such limits in the ebuild? Is there any reason to cap HA to those specific versions? Regards,
Hello and thanks for the big work involved in this overlay.
I'm currently migrating my HA from a rpi3 to a x86 64 bits box.
As I need 'harmony' USE flag for HA, portage complain about a new dependency that have appeared in last dev-python/aioharmony-0.1.13:
!!! The ebuild selected to satisfy ">=dev-python/slixmpp-1.4.2" has unmet requirements.
- dev-python/slixmpp-1.4.2::HomeAssistantRepository USE="-test" PYTHON_TARGETS="-python3_6"
The following REQUIRED_USE flag constraints are unsatisfied:
python_targets_python3_6
The above constraints are a subset of the following complete expression:
any-of ( python_targets_python3_6 )
(dependency required by "dev-python/aioharmony-0.1.13::HomeAssistantRepository" [ebuild])
(dependency required by "app-misc/homeassistant-9999::HomeAssistantRepository[harmony]" [ebuild])
(dependency required by "homeassistant" [argument])
SDIST uploaded to nextcloud
SDIST uploaded to nextcloud
Current Runtime Dependencies contains
>=dev-python/reedsolomon-1.5.3[${PYTHON_USEDEP}]
<=dev-python/reedsolomon-1.5.4[${PYTHON_USEDEP}]
but portage contains only dev-python/reedsolomon in version 1.5.4-r1 and is not considered due to the version restriction. Because of that the emerge of esphome is blocked in the end.
app-misc/homeassistant-0.110.0 depends on >=dev-python/pytz-2020.1 but prevent by dev-python/convertdate-2.1.3, which is requried by dev-python/dateparser-0.7.1.
(dev-python/pytz-2020.1:0/0::gentoo, ebuild scheduled for merge) USE="" ABI_X86="(64)" PYTHON_TARGETS="python3_7 -pypy3 -python2_7 -python3_6 -python3_8" pulled in by
>=dev-python/pytz-2020.1[python_targets_python3_7(-)?,python_targets_python3_8(-)?,-python_single_target_python3_7(-),-python_single_target_python3_8(-)] required by (app-misc/homeassistant-0.110.0:0/0::HomeAssistantRepository, ebuild scheduled for merge) USE="asuswrt caldav cast cli miio mqtt mysql recorder scrape ssl version -abode -adguard -ambiclimate -ambient_station -amcrest -androidtv -apprise -atmo -atv -aurora -avea -aws -axis -bitcoin -blink -blockchain -bmw_connected_drive -bravia-tv -buienradar -ciscomobilityexpress -coronavirus -daikin -darksky -denonavr -discogs -dyson -emulated_roku -enigma -enocean -envoy -esphome -everlights -flume -flunearyou -fronius -gpiozero -growl -harmony -heos -here -hkavr -holidays -homekit -homematic -homematicip -hpilo -hs100 -hue -icloud -incomfort -influxdb -ipma -jewish_calendar -kef -maxcube -maxcube_hack -mikrotik -mobile_app -musiccast -myq -nederlandse_spoorwegen -openwrt -owntracks -ozw -plex -plugwise -qnap -ring -roku -roomba -rxv -samsungtv -shodan -signal -simplisafe -sma -socat -socialblade -somfy -sonos -speedtest -synologydsm -systemmonitor -test -tradfri -ubee -unifi -vallox -velbus -vera -webostv -wemo -wink -withings -wled -wwlln -xknx -yeelight -youtube -z-wave -zigbee -zoneminder" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-python3_8)"
^^ ^^^^^^
(dev-python/pytz-2019.3:0/0::gentoo, installed) USE="" ABI_X86="(64)" PYTHON_TARGETS="python3_7 (-pypy3) -python2_7 -python3_6 (-python3_8)" pulled in by
<dev-python/pytz-2020 required by (dev-python/convertdate-2.1.3:0/0::HomeAssistantRepository, installed) USE="-test" ABI_X86="(64)" PYTHON_TARGETS="python3_7 -python3_6 -python3_8"
When updating home assistant I got this error:
These are the packages that would be merged, in order:
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy "~app-crypt/acme-1.4.0".
(dependency required by "dev-python/hass-nabucasa-0.34.7::HomeAssistantRepository" [ebuild])
(dependency required by "app-misc/homeassistant-0.112.5::HomeAssistantRepository" [ebuild])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
I checked the current version for acme, it's 1.6. Could you please update the ebuild dependencies?
Thanks!
Cristian
in file app-misc/homeassistant/homeassistant-0.108.9.ebuild
braviatv? ( ~dev-python/braviatv-1.0.1 )
should be
braviatv? ( ~dev-python/bravia-tv-1.0.1 )
Since I use your overlay, I wish to have an ebuild for zigbee2mqtt that I use, install and update actually by hand:
https://www.zigbee2mqtt.io/
https://github.com/koenkk/zigbee2mqtt
Update homeassistant to 0.108.3-r1 but it crashed when start.
/var/log/homeassistant/server.log shows
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.7/hass", line 6, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3251, in <module>
@_call_aside
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3235, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3264, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master
ws.require(__requires__)
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'ciso8601==2.1.3' distribution was not found and is required by homeassistant
After emerge dev-python/ciso8601, HA works. So dev-python/ciso8601 should be added to the "RDEPEND" of homeassistant.
Hello,
I tried to install latest home assistant 3.0.
When updating, I got an error when emerging envs 1.4
error in envs setup command: 'extras_require' must be a dictionary whose values are strings or list of strings containing valid project/version requirement specifiers.
In my case I have this use flags: "-cli% -test"
Python targets: python 3.9
I will try to add the cli use flag, maybe this will solve the issue
emerge: there are no ebuilds to satisfy "~dev-python/google-api-core-1.31.2[python_targets_python3_8(-)?,python_targets_python3_9(-)?,python_targets_python3_10(-)?]".
(dependency required by "app-misc/homeassistant-min-2021.10.0::HomeAssistantRepository" [ebuild])
(dependency required by "homeassistant-min" [argument])
Hello
Always thought bavaria was a dutch beer brand :)
not all ebuilds have the arm or arm64 flag .
Hello,
First, thank you so much about this repo, this is a huge time saver, so many dependencies!
I have almost sorted my various issues, and I think that this is the last one...
I can see that the dependency home-assistant-frontend is installed, but hass complains about missing hass_frontend module.
Looking at the python site-package, I can indeed see that home-assistant-frontend eggfile is here, but not the hass_frontend folder.
When emerging the package, I can see a lot of yarn warning, but nothing serious... at the end, I see also that the packaging is not using the hass_frontend folder...
I wonder, because I found this other way of installing the package and it's totally different: https://github.com/openlumi/homeassistant_on_openwrt/blob/21.02/ha_install.sh
They are getting the archive from pypi and just copy its content (after removing uneeded files)
I'm of course using latest ~amd64, python3.9.
By the way, I tried to build it myself, without ebuild, when doing python setup.py install, I can see that hass_frontend is indeed installed in the build directory.
If you have an idea on why, it will help! Thank you!
SDIST uploaded to nextcloud
SDIST uploaded to nextcloud
I've updated my domotic box with homeassistant version 111.0 this week end and I got two notifications telling me that cloud and default_config component was not properly loaded.
In log I got:
2020-06-16 15:24:57 ERROR (MainThread) [homeassistant.setup] Setup failed for cloud: Unable to import component: No module named 'ecdsa'
2020-06-16 15:25:04 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of default_config. Setup failed for dependencies: cloud
2020-06-16 15:25:04 ERROR (MainThread) [homeassistant.setup] Setup failed for default_config: Could not set up all dependencies.
So I installed dev-python/ecdsa then restart homeassistant and the problem is solved.
Note: I don't use cloud component.
SDIST uploaded to nextcloud
Hi! The dev-python/bt-proximity
ebuild is missing a dependency on dev-python/pybluez
.
Sure, most people using this overlay will install a bunch of other packages that will end up pulling pybluez. In my case, I enabled the overlay just because I wanted to try one single package, and got surprised when it didn't work.
please check on my main Git server if it's already filed.
Thanks a lot.
I'm trying to install home assistant from the overlay but it looks like pynacl-1.3.0 is a dependency which is no longer available. I have 1.4.0 installed but that does not satisfy the ebuild.
homeassistant` ~ # emerge -av app-misc/homeassistant
These are the packages that would be merged, in order:
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy "~dev-python/pynacl-1.3.0[python_targets_python3_7(-)?,python_targets_python3_8(-)?,-python_single_target_python3_7(-),-python_single_target_python3_8(-)]".
(dependency required by "app-misc/homeassistant-0.114.4::HomeAssistantRepository" [ebuild])
(dependency required by "app-misc/homeassistant" [argument])
Trying to pull the specific version:
homeassistant ~ # emerge -1av =dev-python/pynacl-1.3.0
These are the packages that would be merged, in order:
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy "=dev-python/pynacl-1.3.0".
Showing the latest version of pynacl is installed.
homeassistant ~ # emerge -1av dev-python/pynacl
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] dev-python/pynacl-1.4.0::gentoo USE="-test" PYTHON_TARGETS="python3_7 -python3_6 -python3_8 (-python3_9)" 0 KiB
Total: 1 package (1 reinstall), Size of downloads: 0 KiB
Thank you for maintaining the overlay.
SDIST uploaded to nextcloud
/usr/lib/python-exec/python3.8/esphome: this Python implementation (python3.8) is not supported by the script.
since dev-embedded/esphome-1.15.0 (was ok with beta3)
I think it would be good for newcomers to update installation documentation related to python 3.7 that is now the default version on gentoo so that we don't need anymore to force it to be using:
So resulting documentation can be clearer by removing these parts:
Good job anyway :)
Hello,
I believe there is an issue with emoji-1.5.0 dependency, when building for x86
(1) emoji-1.5.0 has been removed from standard gentoo portage tree - so portage cannot get it from there
or
(2) dev-python/emoji/emoji-1.5.0.ebuild included in HomeAssistantRepository does not have x86 nor ~x86 keyword
I'm sorry, but I do not have enough experience to suggest solution.
Thank you for all the work
Rasto
The ecobee integration now uses pyecobee
(https://pypi.org/project/pyecobee/) instead of python-ecobee-api
.
As an added problem, python-ecobee-api
uses the same ecobee
python module name as pyecobee
, and having it installed prevents homeassistant's built-in dep resolver from fixing the issue, and causes this error:
Aug 15 03:58:10 durex hass[13825]: 2021-08-15 03:58:10 ERROR (MainThread) [homeassistant.setup] Setup failed for ecobee: Unable to import component: cannot import name 'ECOBEE_API_KEY' from 'pyecobee' (unknown location)
Aug 15 04:05:15 durex hass[13825]: 2021-08-15 04:05:15 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration ecobee: cannot import name 'ECOBEE_API_KEY' from 'pyecobee' (unknown location)
At a minimum, the ecobee
use flag and python-ecobee-api
package should be removed. Best case, you could add an ebuild for pyecobee.
There is a small chance I might attempt to tackle a pull request for this myself, if you're disinterested :).
SDIST uploaded to nextcloud
SDIST uploaded to nextcloud
>>> Downloading 'https://github.com/home-assistant/home-assistant/archive/0.106.2.tar.gz'
--2020-03-03 13:14:46-- https://github.com/home-assistant/home-assistant/archive/0.106.2.tar.gz
Resolving github.com... 140.82.118.4
Connecting to github.com|140.82.118.4|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/home-assistant/core/archive/0.106.2.tar.gz [following]
--2020-03-03 13:14:47-- https://github.com/home-assistant/core/archive/0.106.2.tar.gz
Reusing existing connection to github.com:443.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/home-assistant/core/tar.gz/0.106.2 [following]
--2020-03-03 13:14:47-- https://codeload.github.com/home-assistant/core/tar.gz/0.106.2
Resolving codeload.github.com... 140.82.114.10
Connecting to codeload.github.com|140.82.114.10|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘/var/cache/distfiles/homeassistant-0.106.2.tar.gz.__download__’
/var/cache/distfiles/homeassistant- [ <=> ] 5.01M 1.61MB/s in 3.1s
2020-03-03 13:14:50 (1.61 MB/s) - ‘/var/cache/distfiles/homeassistant-0.106.2.tar.gz.__download__’ saved [5255006]
!!! Fetched file: homeassistant-0.106.2.tar.gz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got: 5255006
!!! Expected: 5255766
Refetching... File renamed to '/var/cache/distfiles/homeassistant-0.106.2.tar.gz._checksum_failure_.e812oi1b'
!!! Couldn't download 'homeassistant-0.106.2.tar.gz'. Aborting.
* Fetch failed for 'app-misc/homeassistant-0.106.2'
If I force to regenerate manifest I got:
>>> Emerging (1 of 1) app-misc/homeassistant-0.106.2::HomeAssistantRepository
* homeassistant-0.106.2.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking homeassistant-0.106.2.tar.gz to /var/tmp/portage/app-misc/homeassistant-0.106.2/work
>>> Source unpacked in /var/tmp/portage/app-misc/homeassistant-0.106.2/work
* ERROR: app-misc/homeassistant-0.106.2::HomeAssistantRepository failed (prepare phase):
* The source directory '/var/tmp/portage/app-misc/homeassistant-0.106.2/work/home-assistant-0.106.2' doesn't exist
*
* Call stack:
* ebuild.sh, line 762: Called __ebuild_main 'prepare'
* phase-functions.sh, line 1054: Called __dyn_prepare
* phase-functions.sh, line 384: Called die
* The specific snippet of code:
* die "The source directory '${S}' doesn't exist"
*
* If you need support, post the output of `emerge --info '=app-misc/homeassistant-0.106.2::HomeAssistantRepository'`,
* the complete build log and the output of `emerge -pqv '=app-misc/homeassistant-0.106.2::HomeAssistantRepository'`.
* The complete build log is located at '/var/tmp/portage/app-misc/homeassistant-0.106.2/temp/build.log.gz'.
* The ebuild environment file is located at '/var/tmp/portage/app-misc/homeassistant-0.106.2/temp/environment'.
* Working directory: '/var/tmp/portage/app-misc/homeassistant-0.106.2/homedir'
* S: '/var/tmp/portage/app-misc/homeassistant-0.106.2/work/home-assistant-0.106.2'
SDIST uploaded to nextcloud
SDIST uploaded to nextcloud
SDIST uploaded to nextcloud
SDIST uploaded to nextcloud
>>> Emerging (1 of 1) dev-python/httpcore-0.14.3::HomeAssistantRepository
>>> Downloading 'https://github.com/encode/httpcore/archive/0.14.3.tar.gz'
--2021-12-08 08:56:54-- https://github.com/encode/httpcore/archive/0.14.3.tar.gz
Resolving github.com... 140.82.121.3
Connecting to github.com|140.82.121.3|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/encode/httpcore/tar.gz/0.14.3 [following]
--2021-12-08 08:56:54-- https://codeload.github.com/encode/httpcore/tar.gz/0.14.3
Resolving codeload.github.com... 140.82.121.10
Connecting to codeload.github.com|140.82.121.10|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘/usr/distfiles/httpcore-0.14.3.tar.gz.__download__’
/usr/distfiles/http [ <=> ] 63,13K --.-KB/s in 0,06s
2021-12-08 08:56:55 (1001 KB/s) - ‘/usr/distfiles/httpcore-0.14.3.tar.gz.__download__’ saved [64650]
!!! Fetched file: httpcore-0.14.3.tar.gz VERIFY FAILED!
!!! Reason: Filesize does not match recorded size
!!! Got: 64650
!!! Expected: 45893
Refetching... File renamed to '/usr/distfiles/httpcore-0.14.3.tar.gz._checksum_failure_.y_yp3nez'
!!! Couldn't download 'httpcore-0.14.3.tar.gz'. Aborting.
* Fetch failed for 'dev-python/httpcore-0.14.3', Log file:
* '/var/tmp/portage/dev-python/httpcore-0.14.3/temp/build.log'
>>> Failed to emerge dev-python/httpcore-0.14.3
plz fix, k thx bye :)
I have Gentoo arm64 running on Raspberry Pi 4 B (installed using sakaki-/gentoo-on-rpi-64bit).
Add HomeAssistantRepository
to your portage overlays.
emerge -av gpiozero
[ebuild N ] dev-python/gpiozero-1.5.1::HomeAssistantRepository USE="-test" PYTHON_TARGETS="python3_6 python3_7 -python3_8" 140 KiB
Check if everything was installed: equery files gpiozero
… Many files, but mostly: …
/usr/bin/pinout -> ../lib/python-exec/python-exec2
/usr/lib/python3.7/site-packages/gpiozero-1.5.1-py3.7.egg-info…
/usr/lib/python3.7/site-packages/gpiozero/…
/usr/lib/python3.7/site-packages/gpiozerocli/__init__.py
/usr/lib/python3.7/site-packages/gpiozerocli/pinout.py
/usr/lib64/python3.6/site-packages/gpiozero-1.5.1-py3.6.egg-info/…
/usr/lib64/python3.6/site-packages/gpiozero/…
/usr/lib64/python3.6/site-packages/gpiozerocli/__init__.py
/usr/lib64/python3.6/site-packages/gpiozerocli/pinout.py
Try running the gpiozerocli tool: pinout
$ pinout
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.7/pinout", line 6, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3251, in <module>
@_call_aside
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3235, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3264, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master
ws.require(__requires__)
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'colorzero' distribution was not found and is required by gpiozero
It should printout a text-based pinout on the terminal. Look at the screenshots:
$ ipython
Python 3.7.8 (default, Jul 2 2020, 17:08:45)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.16.1 -- An enhanced Interactive Python. Type '?' for help.
In [1]: import gpiozero
---------------------------------------------------------------------------
ModuleNotFoundError Traceback (most recent call last)
<ipython-input-1-d4c0b0396b91> in <module>
----> 1 import gpiozero
/usr/lib/python3.7/site-packages/gpiozero/__init__.py in <module>
95 MCP3304,
96 )
---> 97 from .output_devices import (
98 OutputDevice,
99 DigitalOutputDevice,
/usr/lib/python3.7/site-packages/gpiozero/output_devices.py in <module>
43 from threading import Lock
44 from itertools import repeat, cycle, chain
---> 45 from colorzero import Color
46 from collections import OrderedDict
47 try:
ModuleNotFoundError: No module named 'colorzero'
Because gpiozero
depends on colorzero
python module.
Someone has to write an ebuild for colorzero
, add it to the overlay, and add it as dependency of gpiozero
(since version 1.5.0).
SDIST uploaded to nextcloud
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.