JLET'S GOOOOOOOOOOOOOOOOOOOOOOOOOO
NUblue Asahi variant?
EThe first thing we're going to need to do is build out images for aarch64. This should be rather simple. We can't build for CI test so we'll need to build from the official images on quay. I'll be working on this today and hopefully have main images up by days end. This will entail splitting packages by arch and ensuring our CI can accommodate builds. We don't technically need ARM runners for this since we can simply pass what arch we want to buildah but that would significantly speed up the process
I'm looking through a project right now created by a Red Hat eng for providing Asahi Silverblue images to get a better idea of what that will entail but we have to tackle the prior first and foremost
I'm looking through a project right now created by a Red Hat eng for providing Asahi Silverblue images to get a better idea of what that will entail but we have to tackle the prior first and foremost
EYup!
FAre all Ublue packages available as arm64?
Jcheck the ARM thread with @ecurtin's work!
ENo. We'll need to build them out
Jwe just need to finish off what he started, and it probably needs to be caught up
EDefinitely will!
Jthere's a few arm issues in github
NMaybe I will hold off doing mutable Asahi Fedora Remix for a bit.
EActually impressed with Fedora Asahi Remix. I haven't rebooted into MacOS since installing it. And software support is not nearly as bad as I thought it would pan out to be. Not having brew does burn a bit though
EI'm hoping we can replace a lot of what I use there in Wolfi ^
Jgithub will have general arm linux servers this year, no committed date though, so hopefully not too long, but let's wolfi the world anyway, mwhahaha
EThat's awesome! Can't wait for that. In the meantime: https://github.com/ublue-os/main/pull/524
Going to go see Ghostbusters but I will be resuming work on this after
Going to go see Ghostbusters but I will be resuming work on this after
BI really want to get some stuff cleaned up in HWE builds before we do this
(see ublue HWE (hardware enablement) image builds )
(see ublue HWE (hardware enablement) image builds )
ESwore I pulled an aarch64 image locally using the same tag
EWe can't do this out of hwe
Bi didn't say we could
Bbut i'm kinda tired of adding more and more complexity without cleaning things up
EHave a list of items/an open issue? I'd really like to move this forward
Jhuh are we pulling from quay.io/fedora now?
Bno
Jand not timothee's repo? Sorry on a plane can't look it up rn
EJust for aarch64
ETimothees repo doesn't appear to support aarch64
Bah
Joh dang I should have asked him about arm builders, I was supposed to make sure he hooked up with equinix... fuuuuu that's on me
EI didn't realize until today lol
EWould prefer by a mile to continue using his images
Bi'm still unclear if quay.io/fedora images will be published reliably starting with F40
Jthey will, they will not be signed
Bthat's good but since quay.io/fedora doesn't publish a "base" image, we are still hurting slightly where we use that...
Jdo we know what they're publishing ARM wise?
Bi think they do publish both arm and x86_64 for all the atomic desktop images
Joh that doesn't sound so bad
Bsorry, i'm kinda taking this thread over RJ, i'm just in flight on the F40 preview stuff, which will remove some images for the future
plus started working on hwe merging (see the thread I linked)... and I see those things as cleanup which would be nice to do before adding more complexity...
plus started working on hwe merging (see the thread I linked)... and I see those things as cleanup which would be nice to do before adding more complexity...
Jshould we add an order of operations?
Band @j0rge no word yet from Timothee on the names for thsoe F40 images, so i'm about just do what we have now
JYOLO
Jrename later if need be
Bmaybe aarch64 isn't actually blocked, i just feel sick and tired (literally) and don't feel like dealing with more shiny right now
Jack
Jlet's reconvene tomorrow or so, he's seeing a movie and I'm over the atlantic lol
JI didn't know we had started on hwe, I thought we were on f40 enablement
Bre: F40... i'm fine with YOLO, i just kinda expected more of our core contributors to weigh in
Bi thought Noel created a PR/issue, but maybe he didn't... i can do so... I have some stuff I started locally, but my brain is mush
Jmight be time to trim active approvers then
Jor we can actively start pinging approvers directly
E@bsherman I can't read through this rn (in a rush) but I'll take a look when I get back