On Wed, Nov 2, 2022 at 6:42 AM Stephen Gallagher <sgall...@redhat.com>
wrote:

>
>
> On Wed, Nov 2, 2022 at 12:26 AM Benson Muite <benson_mu...@emailplus.org>
> wrote:
>
>> If there is a build failure for a package on ELN, does anything need to
>> be added to a package spec file?  Currently
>
>
> It varies wildly from package to package. Sometimes things can be handled
> with a spec file conditional, other times it may be more complicated (like
> the compiler flags for RHEL are revealing a coding bug that the Fedora
> flags happen to miss or optimize out).
>
>
>
> reviewing a package where
>> there is a missing dependency, but helpful to also
>
>
> A new package review shouldn’t be expected to build on ELN, and failing to
> do so shouldn’t block the review, in general. (Exception: a new package
> that is Obsoleting a package currently in ELN might need special handling).
>
> know if anything
>> should be done in general. The documentation at [0] is not clear on
>> this.  Unclear also if ExcludeArch: ELN with a comment for the reason
>> for build failures on ELN would be a useful thing to have in new spec
>> files.
>
>
> ELN is not an arch, so that would have no effect whatsoever. ELN already
> only rebuilds packages that are needed by RHEL 10 or ELN-Extras packages.
> See https://tiny.distro.builders for the list.
>

Stephen is correct, ELN is not an arch, but there are some packages that do
not build on all arches of ELN but do in rawhide.
The biggest one is golang.

What package(s) are you having problems with?

Troy
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to