Package Details: azure-cli 2.19.1-1

Git Clone URL: https://aur.archlinux.org/azure-cli.git (read-only, click to copy)
Package Base: azure-cli
Description: Command-line tools for Azure.
Upstream URL: https://github.com/Azure/azure-cli
Licenses: MIT
Conflicts: python-azure-cli
Submitter: pallxk
Maintainer: pallxk
Last Packager: pallxk
Votes: 20
Popularity: 1.07
First Submitted: 2019-12-30 09:10
Last Updated: 2021-02-13 04:45

Dependencies (1)

Required by (3)

Sources (3)

Latest Comments

1 2 Next › Last »

acascais commented on 2021-01-25 09:42

Hello.

edit: restarting the router solved the problem :|

I'm trying to upgrade the azure-cli and I also had the problem with Python. I did what djjlewis recommended (uninstall, remove folders and installed again) but I see the installer stuck:

-- Downloading virtualenv package from https://pypi.python.org/packages/source/v/virtualenv/virtualenv-16.7.7.tar.gz.

I tried to curl this endpoint and I get a "moved permanently":

$ curl https://pypi.python.org/packages/source/v/virtualenv/virtualenv-16.7.7.tar.gz
<html><head><title>301 Moved Permanently</title></head><body><center><h1>301 Moved Permanently</h1></center></body></html>

Is it possible that the installer is not following the redirection correctly?

djjlewis commented on 2020-12-04 15:52

To fix the error while loading shared libraries: libpython3.8.so.1.0: cannot open shared object file: No such file or directory issue below, I removed the package, deleted the cache and re-installed e.g

$ yay -Rns azure-cli
$ rm -rf ~/.cache/yay/azure-cli
$ yay -S azure-cli

felipebalbi commented on 2020-12-04 08:56

After an upgrade today, python switched to 3.9 and azure-cli doesn't work anymore:

$ az help
/opt/azure-cli/bin/python: error while loading shared libraries: libpython3.8.so.1.0: cannot open shared object file: No such file or directory

jlohr commented on 2020-11-30 09:20

I get these warnings when installing. Will the package still work?:

ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.

We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.

pyopenssl 20.0.0 requires cryptography>=3.2, but you'll have cryptography 2.9.2 which is incompatible.
azure-cli-core 2.15.1 requires azure-mgmt-core==1.2.1, but you'll have azure-mgmt-core 1.2.2 which is incompatible.

enihcam commented on 2020-11-16 09:32

/opt/azure-cli/lib/python3.8/site-packages/requests/init.py:89: RequestsDependencyWarning: urllib3 (1.26.0) or chardet (3.0.4) doesn't match a supported version! warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "

csullivannet commented on 2020-11-12 13:57

I was receiving this warning:

/opt/azure-cli/lib/python3.8/site-packages/requests/__init__.py:89: RequestsDependencyWarning: urllib3 (1.26.0) or chardet (3.0.4) doesn't match a supported version!
  warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "

This caused my terraform configurations for Azure to fail.

I resolved the issue by reinstalling requests in the azure-cli venv:

sudo su -
cd /opt/azure-cli/bin
./pip3 --user install requests

This fixed the version mismatch between urllib3 and requests.

pallxk commented on 2020-10-21 07:32

@hgabreu Thanks for the info! I think I've found this out.

You'll need a writable $HOME or $HOME/.azure directory to run az. I've updated pkgver() to always use $srcdir as HOME, so that the build can succeed even if $HOME is not writable.

Note: You'll still need a writable HOME to run az after installation. Otherwise, you will get

PermissionError: [Errno 13] Permission denied: '/home/user/.azure'

hgabreu commented on 2020-10-20 16:26

I encountered the same pkgver issue when running makepkg in a blank archlinux image (docker pull archlinux), but not on my laptop. I didn't really investigate it, but that might be a way for you to reproduce the problem @pallxk

pallxk commented on 2020-08-29 02:37

Hi @Jammie, I couldn't reproduce the error. Did previous versions work for you? What's the version of your system python?

Jammie commented on 2020-08-28 10:26

There seems to be an issue with pkgver

==> ERROR: pkgver is not allowed to be empty.
==> ERROR: pkgver() generated an invalid version: