On Wed, Nov 2, 2022 at 10:05 AM Sergey Mende <sergey@xxxxxxxxxxxx> wrote:
> On Wed, Nov 2, 2022 at 8:23 AM Troy Dawson <tdawson(a)redhat.com> wrote:
> What package(s) are you having problems with?
Troy,
the package in question is libClipper2 [0] that undergoes the review presently. It is not go-related. It requires the Google Test that is unavailable in ELN. It is not really a goal to make it included into ELN: initially the ELN builds were enabled in COPR and then started to fail after unbundling Google Test. So, the question arose if there is a need or a way to mark a package as presently incompatible with a distribution apart from putting a plain comment into the spec.
Thank you,
Sergey
[0] https://bugzilla.redhat.com/show_bug.cgi?id=2130903
Lets take a step back.
Packages are only built for ELN if
1 - They are specifically requested by the RHEL teams to be in the next RHEL release
or
2 - They are a direct runtime or build dependency of anything in (1)
If you are not expecting a new package to be in ELN, then it most likely won't be.
Having a package build on ELN should not be part of a Fedora package review.
If it has become part of it, then we need to review the process.
I'm not sure why copr was building for ELN.
I know copr *can* build for ELN, but it shouldn't be automatic.
In short, don't worry about the failed copr ELN builds.
Just make sure your package builds and is packaged correctly for Fedora Rawhide.
Troy
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
