NMeh
NKyle is the enabler of worlds
NOr handhelds
NOr better Gaming experiences
J
Jthat's from the first Secret Wars, for some reason this is seared in my memory
Jdid some quick copyediting on the main website, and sent a PR in for aurora
JFedora 40 Release Thread!!!
EOpened a PR to apko that supports changing the default user shell. After that's merged, I'll have complete parity between what we have now and what I've been working on
Should be able to land everything but the shell change tonight
Should be able to land everything but the shell change tonight
EThe only reason we need it is because it's generated during the build process btw ^
EAnd by it, I mean /etc/passwd
Jall the quadlet stuff is fixed, bluefin-cli is rocking and rolling now
EAdding Bluefin now - this is what the base metapackage for Wolfi will look like: https://github.com/ublue-os/packages/commit/6a9399e7535f4575e7eeb444f81c9928ae79865c
Ti will fix this
Tthanks for the heads up
EJdo you see an edit button on that page? I wanna check perms
EThis is good for a review: https://github.com/ublue-os/packages/pull/20
I want to expand on this further over the next week, but it's sufficient for our metapackages and getting apko built images out the door
I want to expand on this further over the next week, but it's sufficient for our metapackages and getting apko built images out the door
JLET'S GO
Jok so what happens next
EI need to change a few things in toolboxes. Most of the logic I've implemented already, but there's some cleanup I need to do 
Jok so say the bluefin-cli box
Jwill I be getting the packages from wolfi itself or do these actions build them on the spot?
EYou'll be getting everything but the base metapackage from Wolfi (all of the things defined as runtime deps in melange will come straight from Wolfi and you'll get updates for those). The metapackage pretty much replaces the logic that was in the Containerfile. The action in packages will build whatever packages we place there. Then they'll get uploaded as build artifacts to GitHub. They'll rebuild everytime the workflow runs and are then retrieved by the workflow that builds the Wolfi images
EIt's the best we can do without setting up a repository lol
Jthis is amazing
Jdo I need to change the package list? or does it know to just do it?
Jlike am I changing this? https://github.com/ublue-os/toolboxes/blob/main/toolboxes/bluefin-cli/packages.bluefin-cli
ENah, you don't change that. You'll change the packages you pull in via the bluefin-base metapackage in packages
EOtherwise, they can also be migrated to the apko config as well
EI'm almost finished with the base & SDK containers :). I'm going to have to call it a night soon though, but not until I wrap this up
EHow it's setup now is they're here: https://github.com/ublue-os/packages/blob/1ed1d575e353abfb4b659454f7526adc44a7bcfd/wolfi/bluefin-base.yaml#L9
GitHub
Spec files for packages published in ublue COPR repos - ublue-os/packages
Joh ok, gotcha
EE47 seconds!!!!
E1m 27s for the SDK image!
EAnd that's only because I set it up to fetch the official SDK package (less for us to do)
EThere's images up as
wolfi-basewolfi-sdkThis will push Bluefin images to a
:testingI've got to call it, but if all is well, we can roll this out in the morning
EBuild failed... let me fix that
EEWe're dragging in both coreutils and uutils somewhere...
Jbooo
EI think I need to mark it as replacing coreutils in Wolfi. I'm suprised this doesn't happen building from the image because we install coreutils there too
EI think for now.. at least to get testing images out... I can withdraw it from the metapackage temporarily
EGitHub is soooo slow right now
Jthe builders are maxed by bazzite and bluefin PRs
Jfixing a bunch of stuff
Jjust bad timing, go to bed, it's fine. 