Actions
Issue #9164
closedDropping Python 3.6 and 3.7 from the 2.14 release branch was a mistake
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
It looks like this was merged prematurely on my part.
Users have reported the following:
I tried to update pulp_deb plugins using ansible but getting error as per below.
TASK [pulp.pulp_installer.pulp_common : Install prerequisites] ******************************************************************************************************************************************************************************
fatal: [pulptest008.karmalab.net]: FAILED! => {"changed": false, "msg": "No package matching 'rh-python38-python' found available, installed or updated", "rc": 126, "results": ["python-setuptools-0.9.8-7.el7.noarch providing python-setuptools is already installed", "No package matching 'rh-python38-python' found available, installed or updated"]}
Fresh installs are also suffering weird dependency effects where Python 3 is not being installed at all.
Added by quba42 over 3 years ago
Updated by pulpbot over 3 years ago
- Status changed from NEW to POST
Updated by quba42 over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset 2553e2e5aa06c4a4394b0bad628aec81c3be073f.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Re-enable Python 3.6 and 3.7 for 2.14 branch
Closes #9164 https://pulp.plan.io/issues/9164