I got a request to build rgb for EPEL 10 (https://bugzilla.redhat.com/show_bug.cgi?id=2309102), which is not surprising as I did the same for EPEL 9. A local test build of that package failed due to a missing dependency of 'pkgconfig(xorg-macros)', so I requested an EPEL 10 build of xorg-x11-util-macros to resolve that (https://bugzilla.redhat.com/show_bug.cgi?id=2309121). That package request was then declined: fedpkg request-branch epel10 Could not execute request_branch: This package is already an EL package, therefore it cannot be in EPEL. If this is a mistake.... Looking at the compose metadata, it appears that xorg-x11-util-macros is in CRB, but only for the aarch64 architecture. So, my questions are: 1. Is this intentional (seems unlikely, given that this is fundamental to building just about anything using xorg-x11), and 2. If this *is* intentional, what should be done to facilitate building rgb and similarly-affected packages in EPEL? Any thoughts? Regards, Paul. -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
