Hi Nils, On Fri, Jul 16, 2021 at 03:19:25PM +0200, Nils Philippsen wrote: > > in order to use rpmautospec features, it needs to be available on the > builder machines (which are F34) and, for local operations, on the > machine running fedpkg or equivalent. I.e. making it available on EL8 > will help people whose work environment is RHEL8 or CentOS 8, it > shouldn't be required to be able to build an EL8 package in our > infrastructure. There seems to be a bug[1] which prevents building EL8 > packages that use %autorelease, %autochangelog, which I'm investigating > right now. Huh, the EPEL8 builders are F34? I just realized. Yeah, fedpkg --release epel8 srpm definitely behaved differently on F34 (where the macros are available) and on EPEL8 (not on my EL8 machine now so can't get the exact message, but IIRC it failed saying the changelog was invalid). > > I'd be happy to be able to offer rpmautospec client-side on EL8, too, > but as you found out in [2], this needs a newer pygit2 version than > what is available there. > pygit2 is maintained in EPEL, so there's a possibility of just upgrading it there; I'll have to check if it might break any dependencies though. Would you happen to know what is the minimum pygit2 version that would work for rpmautospec? Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/michel@xxxxxxxxxxxxxxx
Attachment:
signature.asc
Description: PGP 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
