On Fri, May 15, 2026 at 11:13 AM Cristian Le via devel < [email protected]> wrote:
> On 2026/05/15 9:51, Dimitris Soumis wrote: > > > Hello, > > > > I am writing regarding a deprecated rpminspect-data-fedora build that > > is used during the CI tests of a bodhi update. More specifically, > > https://bodhi.fedoraproject.org/updates/FEDORA-2026-3652066c48. > > > > Although I made changes to the rpminspect-data-fedora repo, see > > > https://codeberg.org/rpminspect/rpminspect-data-fedora/commit/3dab2796a29ab280007aaf0662daaf89435f7ed5, > > > those changes haven't been pulled yet and the tests are failing. > > Hi Dimitris, > > We did not hook up that repo to a copr repo so that we can pull in the > latest commit in Fedora-CI, but Omair just recently raised the same > question, and we are discussing hooking the automation to do that. > > Right now the only automation we have is when we do a release, which we > have not made plans on how to handle it. I would have 2 options to propose: > - We make an automation to cut a release for every commit that lands, or > just push PRs downstream without cutting releases > - We hook this to copr and pull it from Fedora-CI, and occasionally cut > releases so that users can test it locally more easily as well > > Any thoughts on which workflow sounds better? > > -- > _______________________________________________ > devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected] > Do not reply to spam, report it: > https://forge.fedoraproject.org/infra/tickets/issues/new Hi Cristian, +1 for the second option. I think treating every commit as a formal release would add noise and overhead. The main problem we need to solve is ensuring Fedora CI quickly picks up policy fixes, especially when those fixes unblock Bodhi updates. A Copr-based workflow seems better. Kind regards, Dimitris Soumis
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
