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

Closed
opened 2026-01-05 02:40:45 +00:00 by julian45 · 6 comments
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.
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`.
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?
Owner

Forgejo doesn't seem to let me assign you 🤔

Forgejo doesn't seem to let me assign you 🤔
Owner

Forgejo only lets you assign people/teams with access to the repo for some reason

Forgejo only lets you assign people/teams with access to the repo for some reason
Author
Member

Update: as of at least cb3ebcf24e and this message in the packaging room which was in response to a question about that commit, MSRV is currently 1.88; EL 9 and 10 have hit exactly this minimum as of OS versions 9.7 and 10.1, respectively.

(For EL 8, rust 1.88 is only available using dnf modules in upstream RHEL, and mileage may vary in Alma/Rocky/etc, particularly in package-building situations. In any case, EL 8 is much closer to end-of-life than later major versions.)

Update: as of at least cb3ebcf24e and [this message in the packaging room which was in response to a question about that commit](matrix:roomid/c10y-sohgfFQGnMbeLBk4dBf3vYTUtk-ri0jVfouYPE/e/UK1af6H9OEVcoN1oLzWNRX5rt83C4vnEJlPegqWce5s?via=julian45.net&via=explodie.org&via=matrix.org), MSRV is currently 1.88; EL 9 and 10 have hit exactly this minimum as of OS versions 9.7 and 10.1, respectively. (For EL 8, rust 1.88 is only available using dnf modules in upstream RHEL, and mileage may vary in Alma/Rocky/etc, particularly in package-building situations. In any case, EL 8 is much closer to end-of-life than later major versions.)
Author
Member

This is now resolved/moot, as I've contributed packages for both stable and nightly Continuwuity to Terra that include EL (10+) releases. I overhauled documentation for RPM-packaged deployment options in !1912 (which was finally deployed after the merge of !1917 due to a dead link I missed in the first go-around).

This is now resolved/moot, as I've contributed packages for both stable and nightly Continuwuity to Terra that include EL (10+) releases. I overhauled documentation for RPM-packaged deployment options in !1912 (which was finally deployed after the merge of !1917 due to a dead link I missed in the first go-around).
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
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.