Skip to content
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

Missing pycairo #15

Open
pedrohdz opened this issue Jul 8, 2021 · 10 comments · May be fixed by #17
Open

Missing pycairo #15

pedrohdz opened this issue Jul 8, 2021 · 10 comments · May be fixed by #17
Labels
bug Something isn't working

Comments

@pedrohdz
Copy link

pedrohdz commented Jul 8, 2021

Trying to run the following:

ansible-test integration --requirements --docker geerlingguy/docker-ubuntu2004-ansible --python-interpreter /usr/bin/python3

Yields the following error:

ERROR: Command "/usr/bin/python3 /root/ansible/test/lib/ansible_test/_data/quiet_pip.py check --disable-pip-version-check" returned exit status 1.
>>> Standard Output
pygobject 3.36.0 requires pycairo, which is not installed.
@geerlingguy
Copy link
Owner

ansible-test seems to be a moving target... I'm not quite sure if there's a way I can follow along with all the varying requirements for it.

pedrohdz added a commit to pedrohdz-scrap/docker-ubuntu2004-ansible that referenced this issue Jul 15, 2021
@pedrohdz pedrohdz linked a pull request Jul 15, 2021 that will close this issue
@pedrohdz
Copy link
Author

Hope this helps.. 🤓

@geerlingguy
Copy link
Owner

geerlingguy commented Jul 16, 2021

@pedrohdz - The weird thing is, I don't see either pygobject or pycairo mentioned at all in any of the ansible-test documentation.

The --requirements option seems to indicate it might be trying to install other dependencies—and maybe one of those is causing this extra requirement?

I'd rather not add cairo to just this one Docker image at all, but would be willing to maybe add it everywhere if it's truly required to make the base ansible-test work on my test images with most collections.

@pedrohdz
Copy link
Author

@geerlingguy, I'll take a look again on Monday. Maybe I'm doing something wrong, or unnecessary, on my end. Wouldn't be the first time.

If the change is needed, I would be happy to help out across the repos.

@geerlingguy
Copy link
Owner

Can you create a list of steps to reproduce the error, and test it against a collection like community.general or something else? I'm wondering if it might only be a problem in certain collections.

pedrohdz added a commit to Avinode/ansible-collection-devenv that referenced this issue Jul 19, 2021
@pedrohdz
Copy link
Author

pedrohdz commented Jul 19, 2021

Issue has been recreated in this GitHub Action:

I tried running it on my workstation without --requirements as follows and it is still complaining about pycairo as well:

ansible-test integration --docker geerlingguy/docker-ubuntu2004-ansible --python-interpreter /usr/bin/python3

What's somewhat odd is that it works just fine with geerlingguy/docker-debian10-ansible:latest.

Here are steps:

git clone [email protected]:Avinode/ansible-collection-devenv.git
cd ansible-collection-devenv
python3.9 -m venv .venv
source .venv/bin/activate
pip install -U pip
pip install ansible ansible-lint yamllint

# Optional..  Issue pops up with and without.
#cat galaxy.yml | ruby -r yaml -r json -e 'puts YAML.load($stdin.read).to_json' \
#    | jq -r '.dependencies | keys | .[]' \
#    | xargs -i ansible-galaxy collection install -p . '{}'

cd ansible_collections/avinode/devenv/
ansible-test integration --docker geerlingguy/docker-ubuntu2004-ansible --python-interpreter /usr/bin/python3

@geerlingguy
Copy link
Owner

@pedrohdz - Are you able to reproduce the issue with a fresh new collection that has no or basic content, or with a collection like community.general? It looks like the failing test is on your own devenv collection.

@pedrohdz
Copy link
Author

I’ll dig into it more on Monday. Thanks for taking a look!

@pedrohdz
Copy link
Author

@geerlingguy
Copy link
Owner

@pedrohdz - Thanks for the reproducer. I'll take a look.

@geerlingguy geerlingguy added the bug Something isn't working label Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants