[EPEL-devel] Re: What to do about python 3.4 in EPEL7?
On 07. 05. 20 19:57, Kevin Fenzi wrote: Would it be needed if we moved from say python 3.6 to python 3.8? If there is enough people going to work on this, python 3.8 can be introduced as %python3_other. But I guess python 3.6 is going to be maintained the entire life of rhel7? AFAIK that's how RHEL works. (For those who are not up to speed, RHEL 7 now contains Python 3.6.) -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What to do about python 3.4 in EPEL7?
On Thu, May 07, 2020 at 12:11:58PM +0200, Miro Hrončok wrote: > On 07. 05. 20 11:46, Dominik 'Rathann' Mierzejewski wrote: > > Question: should I be using %{python3_pkgversion} at all? Some packages > > still use it, e.g. python3-ply (python36-ply binary package), and > > some don't. > > 0) It is no longer required from technical point of view. > 1) There was no announcement not to use it. > 2) There was never a hard rule to use it. > 3) I'd personally still use it, for consistency. Would it be needed if we moved from say python 3.6 to python 3.8? But I guess python 3.6 is going to be maintained the entire life of rhel7? kevin signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What to do about python 3.4 in EPEL7?
On 07. 05. 20 11:46, Dominik 'Rathann' Mierzejewski wrote: Question: should I be using %{python3_pkgversion} at all? Some packages still use it, e.g. python3-ply (python36-ply binary package), and some don't. 0) It is no longer required from technical point of view. 1) There was no announcement not to use it. 2) There was never a hard rule to use it. 3) I'd personally still use it, for consistency. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What to do about python 3.4 in EPEL7?
On Thursday, 07 May 2020 at 05:07, Orion Poplawski wrote: > On 5/6/20 4:31 AM, Miro Hrončok wrote: > > On 06. 05. 20 3:39, Orion Poplawski wrote: > > > This is related to my breaking of various packages by dropping > > > python34-six. Should we: > > > > > > - re-add python34-six > > > > For now, yes please. This will need a big announcement and coordination, > > in the meantime, users are impacted. > > Agreed - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d06905e9a7 Thanks! > > > - Make an announcement and start removing python34- from EPEL7 Definitely. I assume bugs will be filed against all affected packages. Question: should I be using %{python3_pkgversion} at all? Some packages still use it, e.g. python3-ply (python36-ply binary package), and some don't. Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What to do about python 3.4 in EPEL7?
On 07. 05. 20 5:07, Orion Poplawski wrote: FWIW, leaves appear to be: # repoquery --disablerepo=* --enablerepo=epel* --whatrequires python34 | while read pkg; do [ -z "$(repoquery --disablerepo=* --enablerepo=epel* --whatrequires $pkg --alldeps --recursive)" ] && echo $pkg; done Not sure how this works, but my repoquery disagrees wrt src packages (does your --enablerepo=epel* include epel-source?), see some examples inlined: avogadro2-0:1.90.0-7.el7.x86_64 python34-Cython-0:0.28.5-1.el7.x86_64 $ repoquery --repo=epel7{,-source} --whatrequires python34-Cython python3-numpy-0:1.12.1-3.el7.src python34-HepMC3-rootIO-0:3.2.1-2.el7.x86_64 python34-HepMC3-search-0:3.2.1-2.el7.x86_64 python34-PyYAML-0:3.12-1.el7.x86_64 python34-apsw-0:3.7.17.r1-3.el7.x86_64 python34-argcomplete-0:1.7.0-4.el7.noarch python34-asn1crypto-0:0.24.0-7.el7.noarch python34-backports-ssl_match_hostname-0:3.5.0.1-1.el7.noarch python34-blosc-0:1.2.8-5.el7.x86_64 python34-bottle-0:0.12.13-3.el7.noarch python3-pycurl-0:7.43.0-7.el7.src python34-bsddb3-0:6.2.6-4.el7.x86_64 python34-certifi-0:2018.10.15-5.el7.noarch python34-click-0:6.7-8.el7.noarch python34-cups-0:1.9.74-4.el7.x86_64 python34-d2to1-0:0.2.12-1.post1.el7.noarch python34-debug-0:3.4.10-5.el7.x86_64 python34-empy-0:3.3.3-2.el7.noarch python34-httmock-0:1.2.6-2.el7.noarch python34-iso3166-0:1.0.1-1.el7.noarch python34-jupyroot-0:6.20.04-1.el7.x86_64 python34-lark-parser-0:0.7.1-1.el7.noarch python34-leveldb-0:0.194-2.el7.x86_64 python34-lhapdf-0:6.2.1-6.el7.x86_64 python34-markdown-0:2.4.1-4.el7.noarch python34-mock-0:2.0.0-2.el7.noarch python3-pytest-0:2.9.2-4.el7.src python34-setuptools-0:39.2.0-4.el7.src python34-numpy-f2py-0:1.12.1-3.el7.x86_64 python34-parso-0:0.3.1-2.el7.noarch python34-pip-0:8.1.2-12.el7.noarch python-setuptools_scm-0:1.17.0-3.el7.src python34-setuptools-0:39.2.0-4.el7.src python34-preludedb-0:5.1.0-2.el7.x86_64 python34-prettytable-0:0.7.2-19.el7.noarch python34-process-tests-0:1.0.0-11.el7.noarch python3-pytest-cov-0:2.5.1-3.el7.src python34-psutil-0:5.6.7-1.el7.x86_64 python-blosc-0:1.2.8-5.el7.src python34-psycopg2-tests-0:2.7.7-2.el7.x86_64 python34-py4j-0:0.10.7-4.el7.noarch python34-pycryptodomex-0:3.9.7-1.el7.x86_64 python34-pycurl-0:7.43.0-7.el7.x86_64 python34-pygraphviz-0:1.3-2.rc2.el7.2.x86_64 python34-pyscard-0:1.9.7-1.el7.x86_64 python34-pytest-cov-0:2.5.1-3.el7.noarch python34-pythia8-0:8.2.43-1.el7.x86_64 python34-pyvirtualize-0:0.10-2.20191018gitdc2d971.el7.noarch python34-rfc3986-0:1.3.0-1.el7.noarch python34-setuptools_scm-0:1.17.0-3.el7.noarch python34-snowballstemmer-0:1.2.1-9.el7.noarch python34-sqlalchemy-0:1.1.3-3.el7.x86_64 python3-sphinx-0:1.2.3-6.el7.src python34-tabulate-0:0.8.3-8.el7.noarch python34-uwsgidecorators-0:2.0.17.1-2.el7.x86_64 python34-uwsgidecorators-0:2.0.18-7.el7.x86_64 python34-virtualenv-0:15.1.0-5.el7.noarch python3-pytest-cov-0:2.5.1-3.el7.src python34-whoosh-0:2.7.4-5.el7.noarch python3-sphinx-0:1.2.3-6.el7.src python34-xrootd-1:4.11.3-1.el7.x86_64 slack-cleaner-0:0.5.0-2.el7.noarch -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
[EPEL-devel] Re: What to do about python 3.4 in EPEL7?
On 5/6/20 4:31 AM, Miro Hrončok wrote: On 06. 05. 20 3:39, Orion Poplawski wrote: This is related to my breaking of various packages by dropping python34-six. Should we: - re-add python34-six For now, yes please. This will need a big announcement and coordination, in the meantime, users are impacted. Agreed - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d06905e9a7 - 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. See https://pagure.io/epel/issue/70 This has been already proposed 9 months ago. It "just" needs somebody to drive it. I am happy to *help*, but I am not available to coordinate this. $ repoquery --repo=epel7 --whatrequires python34 avogadro2-0:1.90.0-7.el7.x86_64 python34-Cython-0:0.28.5-1.el7.x86_64 python34-HepMC3-0:3.2.1-2.el7.x86_64 python34-HepMC3-rootIO-0:3.2.1-2.el7.x86_64 python34-HepMC3-search-0:3.2.1-2.el7.x86_64 python34-PyYAML-0:3.12-1.el7.x86_64 python34-apsw-0:3.7.17.r1-3.el7.x86_64 python34-argcomplete-0:1.7.0-4.el7.noarch python34-asn1crypto-0:0.24.0-7.el7.noarch python34-backports-ssl_match_hostname-0:3.5.0.1-1.el7.noarch python34-blosc-0:1.2.8-5.el7.x86_64 python34-bottle-0:0.12.13-3.el7.noarch python34-bsddb3-0:6.2.6-4.el7.x86_64 python34-certifi-0:2018.10.15-5.el7.noarch python34-chardet-0:3.0.4-1.el7.noarch python34-click-0:6.7-8.el7.noarch python34-coverage-0:4.0.3-5.el7.x86_64 python34-cups-0:1.9.74-4.el7.x86_64 python34-dateutil-1:2.4.2-5.el7.noarch python34-debug-0:3.4.10-4.el7.x86_64 python34-devel-0:3.4.10-4.el7.x86_64 python34-docutils-0:0.14-1.el7.noarch python34-empy-0:3.3.3-2.el7.noarch python34-httmock-0:1.2.6-2.el7.noarch python34-idna-0:2.7-2.el7.noarch python34-iso3166-0:1.0.1-1.el7.noarch python34-jinja2-0:2.11.1-1.el7.noarch python34-jsmva-0:6.20.04-1.el7.noarch python34-jupyroot-0:6.20.04-1.el7.x86_64 python34-lark-parser-0:0.7.1-1.el7.noarch python34-leveldb-0:0.194-2.el7.x86_64 python34-lhapdf-0:6.2.1-6.el7.x86_64 python34-libs-0:3.4.10-4.el7.x86_64 python34-markdown-0:2.4.1-4.el7.noarch python34-markupsafe-0:0.23-3.el7.x86_64 python34-mock-0:2.0.0-2.el7.noarch python34-nose-0:1.3.7-4.el7.noarch python34-numpy-0:1.12.1-3.el7.x86_64 python34-numpy-f2py-0:1.12.1-3.el7.x86_64 python34-parso-0:0.3.1-2.el7.noarch python34-pbr-0:4.2.0-3.el7.noarch python34-pip-0:8.1.2-12.el7.noarch python34-prelude-0:5.1.1-1.el7.x86_64 python34-preludedb-0:5.1.0-2.el7.x86_64 python34-prettytable-0:0.7.2-19.el7.noarch python34-process-tests-0:1.0.0-11.el7.noarch python34-psutil-0:5.6.7-1.el7.x86_64 python34-psycopg2-0:2.7.7-2.el7.x86_64 python34-psycopg2-tests-0:2.7.7-2.el7.x86_64 python34-py-0:1.4.32-2.el7.noarch python34-py4j-0:0.10.7-4.el7.noarch python34-pycryptodomex-0:3.9.7-1.el7.x86_64 python34-pycurl-0:7.43.0-7.el7.x86_64 python34-pygments-0:2.2.0-3.el7.noarch python34-pygraphviz-0:1.3-2.rc2.el7.2.x86_64 python34-pyscard-0:1.9.7-1.el7.x86_64 python34-pysocks-0:1.6.8-7.el7.noarch python34-pytest-0:2.9.2-4.el7.noarch python34-pytest-cov-0:2.5.1-3.el7.noarch python34-pythia8-0:8.2.43-1.el7.x86_64 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-rfc3986-0:1.3.0-1.el7.noarch python34-root-0:6.20.04-1.el7.x86_64 python34-setuptools-0:39.2.0-4.el7.noarch python34-setuptools_scm-0:1.17.0-3.el7.noarch python34-slack_cleaner-0:0.5.0-2.el7.noarch python34-slacker-0:0.12.0-4.el7.noarch python34-snowballstemmer-0:1.2.1-9.el7.noarch python34-sphinx-0:1.2.3-6.el7.noarch python34-sqlalchemy-0:1.1.3-3.el7.x86_64 python34-tabulate-0:0.8.3-8.el7.noarch python34-test-0:3.4.10-4.el7.x86_64 python34-tkinter-0:3.4.10-4.el7.x86_64 python34-tools-0:3.4.10-4.el7.x86_64 python34-urllib3-0:1.25.6-1.el7.noarch python34-uwsgidecorators-0:2.0.17.1-2.el7.x86_64 python34-virtualenv-0:15.1.0-5.el7.noarch python34-whoosh-0:2.7.4-5.el7.noarch python34-xrootd-1:4.11.3-1.el7.x86_64 slack-cleaner-0:0.5.0-2.el7.noarch uwsgi-plugin-python34-0:2.0.17.1-2.el7.x86_64 $ repoquery --repo=epel7{,-source} --whatrequires python34-devel HepMC3-0:3.2.1-2.el7.src lhapdf-0:6.2.1-6.el7.src libprelude-0:5.1.1-1.el7.src libpreludedb-0:5.1.0-2.el7.src py4j-0:0.10.7-4.el7.src pyscard-0:1.9.7-1.el7.src pythia8-0:8.2.43-1.el7.src python-apsw-0:3.7.17.r1-3.el7.src python-argcomplete-0:1.7.0-4.el7.src python-asn1crypto-0:0.24.0-7.el7.src python-blosc-0:1.2.8-5.el7.src python-bottle-0:0.12.13-3.el7.src
[EPEL-devel] Re: What to do about python 3.4 in EPEL7?
On 06. 05. 20 3:39, Orion Poplawski wrote: This is related to my breaking of various packages by dropping python34-six. Should we: - re-add python34-six For now, yes please. This will need a big announcement and coordination, in the meantime, users are impacted. - 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. See https://pagure.io/epel/issue/70 This has been already proposed 9 months ago. It "just" needs somebody to drive it. I am happy to *help*, but I am not available to coordinate this. $ repoquery --repo=epel7 --whatrequires python34 avogadro2-0:1.90.0-7.el7.x86_64 python34-Cython-0:0.28.5-1.el7.x86_64 python34-HepMC3-0:3.2.1-2.el7.x86_64 python34-HepMC3-rootIO-0:3.2.1-2.el7.x86_64 python34-HepMC3-search-0:3.2.1-2.el7.x86_64 python34-PyYAML-0:3.12-1.el7.x86_64 python34-apsw-0:3.7.17.r1-3.el7.x86_64 python34-argcomplete-0:1.7.0-4.el7.noarch python34-asn1crypto-0:0.24.0-7.el7.noarch python34-backports-ssl_match_hostname-0:3.5.0.1-1.el7.noarch python34-blosc-0:1.2.8-5.el7.x86_64 python34-bottle-0:0.12.13-3.el7.noarch python34-bsddb3-0:6.2.6-4.el7.x86_64 python34-certifi-0:2018.10.15-5.el7.noarch python34-chardet-0:3.0.4-1.el7.noarch python34-click-0:6.7-8.el7.noarch python34-coverage-0:4.0.3-5.el7.x86_64 python34-cups-0:1.9.74-4.el7.x86_64 python34-dateutil-1:2.4.2-5.el7.noarch python34-debug-0:3.4.10-4.el7.x86_64 python34-devel-0:3.4.10-4.el7.x86_64 python34-docutils-0:0.14-1.el7.noarch python34-empy-0:3.3.3-2.el7.noarch python34-httmock-0:1.2.6-2.el7.noarch python34-idna-0:2.7-2.el7.noarch python34-iso3166-0:1.0.1-1.el7.noarch python34-jinja2-0:2.11.1-1.el7.noarch python34-jsmva-0:6.20.04-1.el7.noarch python34-jupyroot-0:6.20.04-1.el7.x86_64 python34-lark-parser-0:0.7.1-1.el7.noarch python34-leveldb-0:0.194-2.el7.x86_64 python34-lhapdf-0:6.2.1-6.el7.x86_64 python34-libs-0:3.4.10-4.el7.x86_64 python34-markdown-0:2.4.1-4.el7.noarch python34-markupsafe-0:0.23-3.el7.x86_64 python34-mock-0:2.0.0-2.el7.noarch python34-nose-0:1.3.7-4.el7.noarch python34-numpy-0:1.12.1-3.el7.x86_64 python34-numpy-f2py-0:1.12.1-3.el7.x86_64 python34-parso-0:0.3.1-2.el7.noarch python34-pbr-0:4.2.0-3.el7.noarch python34-pip-0:8.1.2-12.el7.noarch python34-prelude-0:5.1.1-1.el7.x86_64 python34-preludedb-0:5.1.0-2.el7.x86_64 python34-prettytable-0:0.7.2-19.el7.noarch python34-process-tests-0:1.0.0-11.el7.noarch python34-psutil-0:5.6.7-1.el7.x86_64 python34-psycopg2-0:2.7.7-2.el7.x86_64 python34-psycopg2-tests-0:2.7.7-2.el7.x86_64 python34-py-0:1.4.32-2.el7.noarch python34-py4j-0:0.10.7-4.el7.noarch python34-pycryptodomex-0:3.9.7-1.el7.x86_64 python34-pycurl-0:7.43.0-7.el7.x86_64 python34-pygments-0:2.2.0-3.el7.noarch python34-pygraphviz-0:1.3-2.rc2.el7.2.x86_64 python34-pyscard-0:1.9.7-1.el7.x86_64 python34-pysocks-0:1.6.8-7.el7.noarch python34-pytest-0:2.9.2-4.el7.noarch python34-pytest-cov-0:2.5.1-3.el7.noarch python34-pythia8-0:8.2.43-1.el7.x86_64 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-rfc3986-0:1.3.0-1.el7.noarch python34-root-0:6.20.04-1.el7.x86_64 python34-setuptools-0:39.2.0-4.el7.noarch python34-setuptools_scm-0:1.17.0-3.el7.noarch python34-slack_cleaner-0:0.5.0-2.el7.noarch python34-slacker-0:0.12.0-4.el7.noarch python34-snowballstemmer-0:1.2.1-9.el7.noarch python34-sphinx-0:1.2.3-6.el7.noarch python34-sqlalchemy-0:1.1.3-3.el7.x86_64 python34-tabulate-0:0.8.3-8.el7.noarch python34-test-0:3.4.10-4.el7.x86_64 python34-tkinter-0:3.4.10-4.el7.x86_64 python34-tools-0:3.4.10-4.el7.x86_64 python34-urllib3-0:1.25.6-1.el7.noarch python34-uwsgidecorators-0:2.0.17.1-2.el7.x86_64 python34-virtualenv-0:15.1.0-5.el7.noarch python34-whoosh-0:2.7.4-5.el7.noarch python34-xrootd-1:4.11.3-1.el7.x86_64 slack-cleaner-0:0.5.0-2.el7.noarch uwsgi-plugin-python34-0:2.0.17.1-2.el7.x86_64 $ repoquery --repo=epel7{,-source} --whatrequires python34-devel HepMC3-0:3.2.1-2.el7.src lhapdf-0:6.2.1-6.el7.src libprelude-0:5.1.1-1.el7.src libpreludedb-0:5.1.0-2.el7.src py4j-0:0.10.7-4.el7.src pyscard-0:1.9.7-1.el7.src pythia8-0:8.2.43-1.el7.src python-apsw-0:3.7.17.r1-3.el7.src python-argcomplete-0:1.7.0-4.el7.src python-asn1crypto-0:0.24.0-7.el7.src python-blosc-0:1.2.8-5.el7.src python-bottle-0:0.12.13-3.el7.src python-bsddb3-0:6.2.6-4.el7.src python-certifi-0:2018.10.15-5.el7.src python-click-0:6.7-8.el7.src