ci(build): EL RPM builds not currently available #1264
Labels
No labels
Abandoned
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#1264
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Runner image aside, the main stumbling block with running an EL-based build is that that the
rpkgpackage 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 runningpython3 setup.py install.I'm currently working up an EL actions runner image based on Tom Foster's
act-runnerwork. 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?
Forgejo doesn't seem to let me assign you 🤔
Forgejo only lets you assign people/teams with access to the repo for some reason
Update: as of at least
cb3ebcf24eand 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.)
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).