centos-sig-hyperscale / sig

#54 automate package updates
Closed by oidoming. Opened by dcavalca.

Closed
Reopen Issue

For packages that we rebuild in the SIG (e.g. util-linux), occasionally CentOS Stream will move forward and its version will start superceding the SIG one. When this happens, we should rebase and bump our build (or drop it if the changes we needed had been upstreamed). This should be automated -- e.g. have a CI job of some kind that checks package versions and files a ticket when something is due for an update.

The mqtt stuff at the end of https://wiki.centos.org/Sources is promising for this

I would like to work on this, so with the mqtt server we want to get notifications when a commit has been pushed on a package on a specific branch (like the c8s branch in https://git.centos.org/rpms/util-linux) and then create an issue here https://pagure.io/centos-sig-hyperscale/sig/issues with that notification? I want to make sure I understood

So, the high level goal here is to get a notification whenever a package upstream is updated to a version > than the version we currently have in Hyperscale, so that we can update ours. The original idea I had was to watch MQTT for CentOS Stream package updates and file tickets (probably on https://pagure.io/centos-sig-hyperscale/package-bugs), but there's probably other options for implementing this (e.g. watching Koji builds), so we're not married to a specific implementation. To file tickets, you should be able to use the Pagure API.

Once we have this logic implemented somewhere, we'd likely end up running it on our OpenShift CI like we currently do for the systemd CI/CD scripts we have in systemd-releng.

Hi @oidoming , I see there is activity going on in https://pagure.io/test-oidoming/issues \o/.
Just reaching out to know if there is anything you may need help/support with?

Hi, right now I'm testing the script, the script will create an issue like https://pagure.io/test-oidoming/issue/4, the issue will have a tag with the package version (to avoid possible duplicates), also if there is an open issue with a package version tag (created by the script) and there is a new update, the script will leave a comment on the previous issue, close it and create a new one (e.g. https://pagure.io/test-oidoming/issue/8).

What do you think?, anything you would like to change?

Create a new repo and PR https://pagure.io/centos-sig-hyperscale/package-updates/pull-request/1

Just did a first pass review now, thanks for putting this together!

Metadata Update from @dcavalca:
- Issue assigned to oidoming

Metadata Update from @oidoming:
- Assignee reset

Metadata Update from @oidoming:
- Issue assigned to oidoming

Is there a bot account for this?

Metadata Update from @dcavalca:
- Issue marked as depending on: #113

PR merged and working https://pagure.io/centos-sig-hyperscale/package-updates/issues

Metadata Update from @oidoming:
- Issue status updated to: Closed (was: Open)

@oidoming thanks, this is great! It was a no brainer to find what packages need to be updated and I am working on it now :)
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.