You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 7, 2022. It is now read-only.
I'm trying to package azure-cli for NixOS with an overlay using pypi2nix.
The very latest version(s) seem to rely on pip-10.0 (hence me filing #192) but I'm not sure they would've actually broken compatibility with older versions of pip, especially since I'm using requirements.txt.
Here's what I'm running:
#!/usr/bin/env bash
set -euo pipefail
set -x
docker run -it "microsoft/azure-cli-python:2.0.32" pip freeze \
| head -n -2 > requirements.txt
sudo rm -rf /tmp/pypi2nix
# TODO: pretty sure this shouldn't need root...
sudo pypi2nix -v \
--python-version "3.6" \
--extra-build-inputs "gcc" \
--extra-build-inputs "libffi" \
--extra-build-inputs "openssl" \
--requirements "./requirements.txt" \
| tee "log.txt"
@colemickens hey, i don't have time right now to look deeper into this, all i can promise is to come back to this in 2 weeks (if this is still the problem).
It seems we need to use the bdist_wheel wrapper provided by azure_bdist_wheel.py so that 'azure-namespace-package' option gets recognized.
Not too sure how to achieve that, because we explicitly do not install the wheel package (IIUC).
Hello.
I'm trying to package
azure-cli
for NixOS with an overlay usingpypi2nix
.The very latest version(s) seem to rely on
pip-10.0
(hence me filing #192) but I'm not sure they would've actually broken compatibility with older versions of pip, especially since I'm usingrequirements.txt
.Here's what I'm running:
Here's the output: https://gist.github.com/d26b7f152e80d1eb0902ff45c9b6e419
Research:
pip
versionwheel
I tried adding
wheel
as a--setup-requires
but it fails from a ZIP 1970 error and I'm not sure it is the right fix anyway.Any suggestions would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered: