#challengerlinux — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #challengerlinux, aggregated by home.social.
-
We have a Gitlab instance running that's not public as of yet. I wrote up a quick and dirty script in Julia which essentially takes the SRPM for a package, extracts it and rearranges it in a more sensible manner for uploading to a git repository. This script also initializes the git repository for the package, makes a commit, tags it, then finally pushes it to the gitlab. By default though repositories are made private and I'll have to manually go through each of them to set them to public.
-
Hey everyone! I just wanted to give a short update. Work is being done to setup a gitlab for Challenger Linux. So far an instance is running on the Conarium Software server. Josh O'Leary from Conarium Software has been helping me with some of the work. Were working on setting up our repositories the same way Rocky Linux does. We're also working on some tools that will help us automate this better. Initially we modified one of Skip Grube's scripts for checking commits on the CentOS Stream gitlab for exact package versions. We modified the script to automatically clone the matching commit then move around the source files to imitate the Rocky way of doing it. That seemed to work until it ran into repositories that didn't have matching commits. So I started working on a tool which will just take a SRPM and do something similar. That seems to be working quite well right now.
-
I have something to show you! Challenger Linux is now bootable in Qemu!
-
We're almost there! I gave up on trying to build grub2-pc-modules from source, so I went ahead and took the pre-built RPM from the CentOS Stream Koji. I also had to repartition my raw image to use the msdos/pc format. Right now I just need to figure out why Dracut isn't working right.
-
I just wanted to give an update on the bootstrap progress of Challenger. I'm working out some issues with grub2-pc-modules not being built when I build the grub2 source RPM. I didn't notice that the package was never built until I started working on getting a bootable image.
I initially just tried to ignore it and tried installing the bootloader with an efi configuration. It said the system didn't support efi, so that didn't work as a quick temporary hack. So I started investigating why the package didn't build.
During my investigation I found a bug report on a mailing list meant for Fedora 34. The person was having the same issue. Someone made a reply about how pc-modules build only with the i686 architecture. I'll have to try it tomorrow to see how it works out!
https://www.spinics.net/lists/fedora-packaging/msg12900.html
-
We're starting the bootstrap! 😁
-
Today I'm waiting on the rest of the sources to build. Also I got permission to use Rocky's secureboot and x509 certs, so I'll have to rebuild my debranded packages with those. I also got the skeleton setup for a local DNF repository that I'll use to bootstrap the system.
-
For now I'm keeping the CentOS Stream secure boot certs until I can get my own generated. I went back through the packages and just debranded without removing anything key and cert related. On the Rocky mattermost I was asking for help about generating kpatch and dup certs. A few people pointed me in the right direction namely Sherif Nagy, Nazunalika and Sokel. I appreciate their help a ton!
#linux #linuxengineer #centos #redhat #redhatlinux #rhel #challengerlinux
-
I've been trying to avoid using secure boot keys and kernel module signing, so I didn't have to worry about them right now. I have no other choice though. For now I'm using Rocky's keys until I sign my own. I've been using Rocky's patches and specfiles for debranding as I trust that I can safely replace Rocky/rocky with Challenger/challenger. Right now I have the kernel building after debranding.
-
Libreport does not want to play nice with debranding for whatever reason. I even used the Rocky spec and patch. The only thing I did to those files is s/Rocky/Challenger/g and s/rocky/challenger/g. I don't see the problem.
-
We have our first debranded package! It's a little wonky at the moment, but that will change. 😁