@j0rge I am following correctly? Current Universal Blue Initiatives Summary:
Immediate priorities center on bolstering infrastructure security through comprehensive SBOM (Software Bill of Materials) generation, image signing, and automated repository scanning. Concurrently, intensive Fedora 42 (F42) testing is underway to address stability.
Strategically, Universal Blue is being positioned as a manufacturing process rather than a monolithic product, empowering customized image creation. Reflecting this, the Bluefin image will adopt a pure image mode for F42, moving away from local package layering, and will utilize the Anaconda installer for official ISOs. Enhanced upstream collaboration with Fedora teams is formalized through regular meetings, focusing on atomic desktop advancements and tracking initiatives like the proposed F43 removal of Fedora Flatpaks.
Key technical developments involve evaluating uupd as a potential default update mechanism, standardizing on Titanoboa for liveCD builds, and prototyping Dragonfly for peer-to-peer (p2p) LAN updates. Ensuring rebase helper integrity between CentOS and Fedora streams is also crucial. Access to dedicated ARM hardware aims to accelerate GDX development.
Overall efforts focus on refining tooling, improving security posture, ensuring a stable F42 release, and strengthening upstream alignment.
A question for you knowledgable folks; I’m working on figuring out how to get a couple of proprietary system level pieces of software to work nicely on Bluefin. Currently I’m building rpms and layering them for testing with view to build a custom image. In the new bootc world this approach won’t be possible, so what is the best way of tinkering before I commit to a long GitHub actions run?
If the components you are adding can be validated in a terminal, you can use podman-bootc to run the image from your local containers storage https://github.com/containers/podman-bootc
I also tend to run a local OCI registry, push a new image there and bootc switch to it in a VM.
It's working well in Bluefin LTS - we just need to switch it back on. Generating the SBOM fails in Bluefin for some reason. I've not had a chance to investigate yet. I think M2 said we need to create a large swap file for it to succeed. Once Bluefin is fixed, we can copy and paste the code over to main, Aurora and uCore
That's interesting but exciting news! I'm looking at doing the same in my repos. I can take a look as well. You think there's any benefit in putting this in the image template as well? So everyone can get them as artifacts?