This is related to my breaking of various packages by dropping
python34-six. Should we:
- re-add python34-six
- Make an announcement and start removing python34- from EPEL7 starting
with:
# repoquery --whatrequires python34-six --recursive --disablerepo=*
--enablerepo=epel* | sort -u
python34-dateutil-1:2.4.2-5.el7.noarch
python34-httmock-0:1.2.6-2.el7.noarch
python34-mock-0:2.0.0-2.el7.noarch
python34-pyvirtualize-0:0.10-2.20191018gitdc2d971.el7.noarch
python34-pyvmomi-0:6.7.3-4.el7.noarch
python34-requests-0:2.14.2-2.el7.noarch
python34-slack_cleaner-0:0.5.0-2.el7.noarch
python34-slacker-0:0.12.0-4.el7.noarch
python34-urllib3-0:1.25.6-1.el7.noarch
python36-collada-0:0.4-16.el7.noarch
slack-cleaner-0:0.5.0-2.el7.noarch
Upstream python 3.4 is EOL.
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301
https://www.nwra.com/