-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
home-assistant: make hass cloud integration work #38653
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rebase on staging, pycryptodome has been updated there.
pkgs/top-level/python-packages.nix
Outdated
@@ -317,6 +317,14 @@ in { | |||
|
|||
pycryptodome = callPackage ../development/python-modules/pycryptodome { }; | |||
|
|||
pycryptodome_3_3 = self.pycryptodome.overridePythonAttrs (oldAttrs: rec { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a policy of having only a single version of each package in pythonPackages
sha256 = "0vl22411k394biizkjqg1ydclbf6fw5hxixzm1g7jlpzx4z6j9lj"; | ||
}; | ||
|
||
propagatedBuildInputs = [ cryptography ecdsa future pycryptodome_3_3 six ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can probably just patch requirements.txt
in postPatch
.
sha256 = "0gw3crg64p1zx3k5js0wh0x5bldgs7viy4g8hld9xbka8q0374hi"; | ||
}; | ||
|
||
propagatedBuildInputs = [ boto3 envs python-jose-cryptodome requests ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I opened capless/warrant#98 for using python-jose instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should be able to use that as a patch, which would get rid of all problems.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@peterhoeg Did you try applying that patch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, haven't touched this yet. This weekend!
sha256 = "0vl22411k394biizkjqg1ydclbf6fw5hxixzm1g7jlpzx4z6j9lj"; | ||
}; | ||
|
||
propagatedBuildInputs = [ cryptography ecdsa future pycryptodome_3_3 six ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mhm this could be a big hassle if python-jose-cryptodome
is mixed with something depending on pycryptodome
. Then there are two different versions. which should be avoided.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a newer version could be used here? https://github.com/mpdavis/python-jose/blob/master/setup.py#L58
, cryptography, ecdsa, future, pycryptodome_3_3, six }: | ||
|
||
buildPythonPackage rec { | ||
pname = "python-jose-cryptodome"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also why did you add another python-jose
?
Your issues have been addressed @dotlambda and @Mic92 |
Success on aarch64-linux (full log) Attempted: home-assistant Partial log (click to expand)
|
No need to use staging anymore, has been merged into master. |
@GrahamcOfBorg build python2.pkgs.envs python3.pkgs.envs |
Success on aarch64-linux (full log) Attempted: python2.pkgs.envs, python3.pkgs.envs Partial log (click to expand)
|
@GrahamcOfBorg build python2.pkgs.warrant python3.pkgs.warrant |
Success on aarch64-linux (full log) Attempted: python2.pkgs.warrant, python3.pkgs.warrant Partial log (click to expand)
|
|
||
propagatedBuildInputs = [ boto3 envs python-jose requests ]; | ||
|
||
# all the checks are failing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Their Travis build fails, too. So this is to be expected.
Success on aarch64-linux (full log) Attempted: home-assistant Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: python2.pkgs.envs, python3.pkgs.envs Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: python2.pkgs.warrant, python3.pkgs.warrant Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: home-assistant Partial log (click to expand)
|
Motivation for this change
I'd like to use my "Amazon ~~~spy-device~~~ Echo" to control home assistant.
I haven't actually tried to use it to control HA yet but at least it's connecting.
Should I separate out the pycryptodome override into its own file?
Cc: @dotlambda @FRidh
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)