ci(build): EL RPM builds not currently available #1264

New issue

Open

opened 2026-01-05 02:40:45 +00:00 by julian45 · 2 comments

julian45 commented

2026-01-05 02:40:45 +00:00

Member

Spinning this off from #1240...

As noted in the above issue, the current RPM builds are not usable on Enterprise Linux (AlmaLinux, Rocky Linux, etc.), manifesting as a glibc version mismatch issue.

Attempts to slightly edit the existing Fedora build process to produce EL-compatible images by way of mock were not successful due to arcane errors produced by mock. Based on preliminary successes of building an RPM locally on EL 10 (namely, RHEL 10 x86_64), it appears necessary to create a new EL-based actions runner image with which EL-compatible RPMs can be built.

Spinning this off from #1240... As noted in the above issue, the current RPM builds are not usable on Enterprise Linux (AlmaLinux, Rocky Linux, etc.), manifesting as a glibc version mismatch issue. Attempts to slightly edit the existing Fedora build process to produce EL-compatible images by way of [mock](https://rpm-software-management.github.io/mock/) were not successful due to arcane errors produced by mock. Based on preliminary successes of building an RPM locally on EL 10 (namely, RHEL 10 x86_64), it appears necessary to create a new EL-based actions runner image with which EL-compatible RPMs can be built.

julian45 commented

2026-01-05 02:46:30 +00:00

Author

Member

Runner image aside, the main stumbling block with running an EL-based build is that that the rpkg package is only available on Fedora at this time, not in EPEL or in any mainstream EL's base/AppStream/CRB/etc. repos. The local RHEL 10 build was only successful due to manually downloading the rpkg-util repo from Pagure, manually copying some binaries from that repo to /usr/local/bin, grabbing a few build dependencies from EPEL, and running python3 setup.py install.

Runner image aside, the main stumbling block with running an EL-based build is that that the `rpkg` package is *only* available on Fedora at this time, not in EPEL or in any mainstream EL's base/AppStream/CRB/etc. repos. The local RHEL 10 build was only successful due to manually downloading the rpkg-util repo from Pagure, manually copying some binaries from that repo to `/usr/local/bin`, grabbing a few build dependencies from EPEL, and running `python3 setup.py install`.

julian45 commented

2026-01-05 02:48:38 +00:00

Author

Member

I'm currently working up an EL actions runner image based on Tom Foster's act-runner work. After that, it should be a matter of adjusting the Fedora build workflow to handle the rpkg issue described above, then incorporating runners with said image into the c10y build infra.

In the meantime, could a maintainer please assign this issue to me?

I'm currently working up an EL actions runner image based on Tom Foster's [`act-runner`](https://git.tomfos.tr/tom/act-runner) work. After that, it should be a matter of adjusting the Fedora build workflow to handle the rpkg issue described above, then incorporating runners with said image into the c10y build infra. In the meantime, could a maintainer please assign this issue to me?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

continuwuation/continuwuity#1264

No description provided.

Rows
Columns