[EPEL-devel] Re: arch-specific package in CS10 blocking EPEL 10 request

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



V Wed, Sep 04, 2024 at 09:15:23AM +0100, Paul Howarth napsal(a):
> 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

EPEL can barely answer this. You should open a ticket for CentOS Stream at
<https://issues.redhat.com/> against "RHEL" project and "xorg-x11-util-macros"
component.

> 2. If this *is* intentional, what should be done to facilitate building
> rgb and similarly-affected packages in EPEL?
> 
I guess a procedure for missing binary packages
<https://docs.fedoraproject.org/tr/epel/epel-faq/#rhel_8_has_binaries_in_the_release_but_is_missing_some_corresponding__devel_package._how_do_i_build_a_package_that_needs_that_missing__devel_package>
applies here. You import xorg-x11-util-macros sources under
"xorg-x11-util-macros-epel" name and disable building on aarch64, maybe
changing the package from noarch to fullarch will be necessary.

-- Petr

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, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux