On 8/26/24 12:23, Dan Horák wrote:
Hi, isn't there a problem with rpminspect-data-fedora used in the bodhi automated tests? My recent build of s390utils failed on stuff that was no problem 2 weeks ago. Does rpminspect-data-fedora need branching? See eg. https://bodhi.fedoraproject.org/updates/FEDORA-2024-bb726e3bd3 and https://bodhi.fedoraproject.org/updates/FEDORA-2024-70c403f743
Probably. A lot of the data files are mapped from the dist tag. Any time a new dist tag is created, that is not automatically created in rpminspect-data-fedora. The owner of the data has to do that. That's been entirely manual on my part so far.
I solicited for volunteers to take over ownership and maintenance of rpminspect-data-fedora and have neglected to follow through on the hand over to them. I imagine people could come up with clever ways to automatically set up placeholder data files for new dist tags when we make a new dist tag for rawhide builds.
As it stands right now, anyone can submit a PR with data file updates. Any time a PR is merged, it triggers a snapshot rebuild of the package in a Copr repo. These builds are what's used in gating. Ideally the "released" versions of rpminspect-data-fedora (and rpminspect-data-centos) would be more closely aligned with any snapshot builds, but that requires one or more package maintainers. That's why I was seeking out help.
Thanks, -- David Cantrell <dcantrell@xxxxxxxxxx> Red Hat, Inc. | Boston, MA | EST5EDT -- _______________________________________________ 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
