|
I use docker and rpmbuild to generate the RPMS, and I have successfully built and tested packages for EL8 and EL9 on amd64 and aarch64. Things don’t build on EL10 for a couple of reasons; I think some work will be required to get things working properly there (a combination of dependencies being renamed/deleted as well as some build errors probably triggered by the latest versions of gcc. I’ve included the non-working EL10 setup in case anyone wants to take a stab at fixing the problems.
The use of docker allows us (hopefully) to have a reproducible, pristine build environment, and also allows RPMS to be built from non-linux platforms without needing to have a linux system set up.
There are notes in the repo above that describe how to build the docker build images, and then use them to prepare (S)RPMS, as well as the basic steps needed to support new versions of Enterprise Linux.
I did notice a minor problem on Oracle Linux 9 with there being odd dependencies that couldn’t be resolved (Java related, mainly and as per the usual).You can ignore them or better yet, break them into a sub-package.
I’ll try to make time to upload my builds later today or tomorrow.
Comments/questions/suggestions are welcome, as always.
Bill
On Dec 6, 2025, at 9:00 PM, Maksim AbuAjamieh <eng.maksim@gmail.com> wrote:MaksimHi Bill,Thanks so much for the update and for taking the time to clean things up and make them accessible.I’ll look forward to the SRPMs whenever you’re ready to share them, but it is perfectly fine if you would prefer to just share what you already have. I really appreciate the effort you are putting into this.Best regards,On Wed, Nov 19, 2025 at 7:41 AM <william@welliver.org> wrote:Hi-
That would be my fault... I've always been so focused on the rpms but
the srpm is an artifact I seem to forget to upload the SRPM.
I have a spec file that's never been checked into version control, as
well as some scripts that I've used to produce the RPMs available for
download... Part of the reason it's always languished on my build system
is that the spec file needs changing for various el releases, and
there's a separate dependency installation step required to get the
builds to work. I didn't want a proliferation of files in the pike
packaging directory. I will try to clean those up a bit and put them
somewhere publicly accessible.
Note: pike doesn't seem to build properly on el10, I suspect due to the
version of gcc in use. The fix is a one-liner, but a patch is necessary
until a new release is made.
Stand by for an update on this, probably in a day or two.
Best,
Bill