On Wed, Mar 11, 2020 at 8:23 AM Stefan Bluhm <redhat....@bluhm-de.com> wrote:
> Hello all,
> TLDR: Spacewalk packages build and can be installed on CentOS 8.
> as I am working on getting Spacewalk to run on CentOS8/RHEL8, I would like to 
> share my progress here with you, in the hopes that you can contribute or 
> share your experience/knowledge. I am not company sponsored, not a developer 
> nor do I have much other knowledge of Linux.
> Around three weeks ago, I forked the GIT repo and the COPR repositories. So 
> that is the basis of my current work:
> https://github.com/sbluhm/spacewalk
> https://copr.fedorainfracloud.org/coprs/sbluhm/nightly/           # Contains 
> the packages from the original spacewalk nightly
> https://copr.fedorainfracloud.org/coprs/sbluhm/java-packages/     # Contains 
> 421 Java related and other random packages
> https://copr.fedorainfracloud.org/coprs/sbluhm/python-packages/   # Contains 
> 115 Python, Perl and other random packages
> http://dev2.bluhm-de.com/packages                                 # Custom 
> repo for locally compiled or added packages that I was not yet able to build.
> Primary objective was to hack everything together to get everything to build.
> I have added and built all required dependencies (mainly Python 2 and Java) 
> and modified the RPM spec files so that it is possible to successfully build 
> all Spacewalk packages. It is also possible to install all Spacewalk packages 
> apart from spacewalk-proxy* and spacewalk-oracle* which I have no idea (or 
> currently care) how to set up.
> Unfortunately, spacewalk-setup fails due to a postgresql configuration error 
> (unrecognized configuration parameter "checkpoint_segments"), otherwise this 
> would have been an additional great achievement.

This is amazing progress! Congratulations!

> Next few steps I see (in no real particular order):
> - Clean up and verify the git changes and push them to the Spacewalk master. 
> Michael, you will see quite a few SHORT pull requests coming from me in the 
> future. It would be great, if you could sanity check them (as mentioned 
> above, I am not a developer nor do I know what I am doing).
> - Fix the compile issues from my local repository and add them to the COPR 
> repos.
> - Clean up the repos. I probably have more packages built than required. 
> Including already existing RHEL8 packages and/or module conflicts.
> - Start moving code to Python 3 to get rid of the many custom built Python 2 
> packages.
> Open questions from my side:
> - What do I do with those build packages in my repos? How/where do I add them 
> to hand my work over? Please give some assistance where to put what (git, 
> nightly, python-packages, java-packages) and how.

It'd be good to get this back into Fedora. Get in touch on the Fedora
development mailing list to help integrate this packages back in the
distribution. They could also be built into EPEL 7/8 for reusability

> - Is there a reason to keep Python 2 or can everything be moved to Python 3?

Everything should move to Python 3, since Python 2 is now EOL and RHEL
7 has a Python 3 interpreter (and EPEL provides a lot of Python 3
packages). Any missing Python 3 packages can be backfilled into EPEL.

> - What are the supported OS? I would say RHEL>=7 (remove 6 code), Fedora >= 
> 29 (28 is EOL in May and I doubt we will be ready for a release by then). 
> What about SLES? I have seen SLES specific code in there.

I would say the server should be able to run on RHEL 7 (CentOS 7) or
greater and SLE 15 (openSUSE Leap 15) or greater. That means you can
rely on DNF being available and port over all the YUM code to get rid
of the YUM dependency.

> Do you see the next steps in the same way? Do you have any other suggestions, 
> recommendations, guidelines?

I pretty much agree with your approach. Suggestions made above about
how to handle this more sustainably.

> How can you assist?

I can certainly try to help where I can with package reviews on the
Fedora side and reviewing/testing code changes. Not sure how much code
work I can commit to at the moment, though.

真実はいつも一つ!/ Always, there's only one truth!

Spacewalk-devel mailing list

Reply via email to