pip installs failing, starting release_19.05

[drosofff]

I am scratching my head on the following issue:

Starting sunday Jan 12, pip install of requirements.txt is failing for galaxy versions > 19.01 with the pip error ERROR: Package 'setuptools' requires a different Python: 2.7.12 not in '>=3.5'. This results in error in this playbook for the indicated versions.

My guess from that it is related to upgrades in https://wheels.galaxyproject.org/simple/ or in https://pypi.python.org/simple or to the use of --index-url or --extra-index-url parameters by this role.

Any insights would be appreciated.

[mvdbeek]

So python 2 is officially not supported anymore (https://pythonclock.org/), and I guess some dependency brings in a setuptools version that doesn't pin python 2. Do you have some logs for this ?

[drosofff]

No log, but indeed pip install of requirements.txt with this role ends up with setuptools==45.0.0, whereas I see that local deployment of a git cloned galaxy (release_19.09) ends up with setuptools==44.0.0

Moreover, I just fixed this role install by manually forcing the install of setuptools==44.0.0

Is it acceptable then if we pin the setuptools in this role to 44.0.0 using a specific ansible task as in #99 ??

[mvdbeek]

I would only do this if the python version used for Galaxy is 2.7, I'm not sure how the conditional should look like in that case. I'd go ahead with switching to python 3.6 (3.7 can be problematic with uwsgi atm.) though, Galaxy is compatible since 19.01, and I think the last bugs have been ironed out in 19.09

[drosofff]

Ok @mvdbeek I'll work on the 3.6 python switch in the ansible roles.

I'm not sure how the conditional should look like in that case.

In the meantime (my wish is to keep these ansible repos working for everyone), is it an issue to test python with a
when: ansible_python_version is version('3', '<') in the pinning task, associated to gather_facts: True in the playbook ?

An alternative would to be to set a setup task to gather facts about remote hosts in the main.yml.
Or just to shell python --version and register the output.

[MichaelDBA]

So the error I am getting on Ubuntu 20.04 for installing python-pip dependency is:
fatal: [192.168.1.133]: FAILED! => {"changed": false, "msg": "No package matching 'python-pip' is available"}
which makes sense since I have the package for version 3: python3-pip.

Should I just change the dependency to python3-pip instead?

And I guess the only reason I would need this is for python support in doing backup and PITR stuff, right?

Is there a way to substitute another backup utility like pgbackrest or barman instead of using pg_basebackup?