On 3/2/22 14:14, epel-devel(a)lists.fedoraproject.org wrote:
Except that we are going to need python38-pytest, etc. in the EPEL8
if we are going to build (most of) the packages in the first place. That's
the problem I'm running into now trying to build python38-jmespath:
DEBUG util.py:444: No matching package to install: 'python38-pytest'
So I'm back to my original questions:
* Do we just make EPEL python38- packages as modules or try to hack up some
kind of build system support for it?
* If modules, every package a module or one (or a few) modules?
I have been told that the lack of python38-pytest is an issue with the
buildroot generation and so have filed:
Hopefully this will make everything simpler as nothing has to be a module or
special in any way.
IT Systems Manager 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/