On 12/3/20 14:06, Andrew C Aitchison wrote:
On Thu, 3 Dec 2020, Michel Alexandre Salim wrote:Apart from the usual package-not-available story (which I want to fix as part of my work bringing up the EPEL Packagers SIG), my current snag is that python-tox-current-env uses %generate_buildrequires which does not work on CentOS 8: CentOS 8 is still on RPM 4.14: <mock-chroot> sh-4.4# rpm -q rpm rpm-4.14.2-37.el8.x86_64 I'll put up a patch to hardcode dependencies for non-Fedora releases, though that sorts of defeat the purpose of dynamic build requirements. Then again, this is only needed for EPEL8, since EPEL9 will have a new enough RPM.Given that %generate_buildrequires is the selling point of pyproject- rpm-macros, I'm guessing a better way forward for EPEL8 would be to not require it on EPEL8 since there's no way it would work, since RH won't update RPM? https://src.fedoraproject.org/rpms/pyproject-rpm-macros
I've been playing around with a hacked version of pyproject-rpm-macros which at least allows some basic functionality in EPEL8. Comments welcome.
https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/284 -- Orion Poplawski he/him/his - surely the least important thing about me 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
