On 3/2/22 14:14, epel-devel@xxxxxxxxxxxxxxxxxxxxxxx wrote: > Except that we are going to need python38-pytest, etc. in the EPEL8 buildroot > 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: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=83570866 > 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: https://pagure.io/releng/issue/10679 Hopefully this will make everything simpler as nothing has to be a module or special in any way. -- Orion Poplawski IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@xxxxxxxx Boulder, CO 80301 https://www.nwra.com/
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
