Re: Manually queue Koschei build?
On Mon, Sep 5, 2022 at 6:00 PM Richard Shaw wrote: > > I was able to fix my EPEL 7 package and performed a successful build: > https://koji.fedoraproject.org/koji/buildinfo?buildID=2058266 > > So I forced a Koschei build to clear the error, but it still built the > PREVIOUS SRPM: > https://koschei.fedoraproject.org/build/13643482 IIUC, koschei takes the latest SRPM from the *buildroot*. So if you didn't file a buildroot override for the successful build, it cannot see it until it is pushed to stable. Fabio ___ 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
Manually queue Koschei build?
I noticed on the packager dashboard that I have a package that was failing for EPEL 7[1] and I have since fixed it, but I don't need to build a new package and Koschei hasn't attempted a rebuild since 6/29. While I could just ignore it, I was wondering if there was a way to force a rebuild? I see the priority field but I don't have any reference for what a good value would be, it's not particularly intuitive. Thanks, Richard [1] https://koschei.fedoraproject.org/package/OpenColorIO?collection=epel7 ___ 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
