Cno we do use it
Mhah…?
Tis there any way i can statically link to libhelium cuz i dont think i can install libhelium on c10s :clueless:
Mterra for c10
Cwe use it on iso installs
Coem images being switched to taidan in my pr only
JYo thread this
Mdidn't test but
JWe gotta do other things in here
MI see
NYup, move to Live ISO thread please.
Theh the huge emoji
Cme when noto emoji
Msorry for being a karen in your restaurant /hj
A@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.
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.
Jwhat llm did you use lol
Atesting the new gemini
Abut damm that is a lot of things you guys are planning to do
Jdragonfly isn't f42 material
Jmostly we just gotta clamper down and fix bugs
Jif there's some f42 test week or something we could remind people to use the beta channel, etc.
A
Gis there any way to "customize" the partition layout or FS or is it all automatic?
ZYou have to make it yourself. to-disk is not meant to be a fully fleshed installer
GI see, so the partitioning is done before hand?
ZYep
Gnice
Gso readymade is perfect then
MIt's a demo according to the documentation. It recommends to-filesystem with a bring your own partitioning
CA 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?
RIf 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.
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.
COk that’s a very cool approach. I’ll be playing with this stuff tomorrow! Thanks!
Z@Robert how is the SBOM stuff with syft/grype going? It seems you've gone back and forth a couple times on it in the repos
RIt'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
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
ZThat'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?
ROnce the issues are ironed out, it's definitely something we should put in the template!
MIf we're going to use packages repo... we need to actually keep it up to date
RCan we add all approvers as reviewers? I don't get notified about any of these
Jyeah it's our biggest pain point right now, agreed.
Jthe devpod flatpak is almost done
J@Robert this sbom run on lts took like 3 minutes?
Jthat was way slower before
RGDX took 7 minutes... Think this was the main one causing problems
Jah right!
Jwell, other than that this is smoooooooth.
RBut if by "before", you're referring to 6 months ago, when we first tried SBOMs, then yes! It was 30ish minutes
Jheheh
JI think once we have a semi permanent ampere box to ssh to that we should be fine
MRight now attestation is the next challenge. I'm wondering if there is a limit to the sbom size for attaching?
MMy smaller images are working fine. But the larger ones the push to the registry is failing