so what's the plan for F42 now that coreos stable got bumped with the kernel with 63 as releasever?
so what's the plan for F42 now that coreos stable got bumped with the kernel with 63 as releasever?
Bsounds like you are asking about bluefin/ucore stable specifically?
G(continuing from here)
Gwell everything that depends on akmods coreos flavor
BI think we need to wait for 6.14.3
Bthere's a few reasons... 1) the release 63 thing is quite odd 2) there's no 6.14.0 for fc41 3) it's a.0 release 
Bas things sit right now, i think this waiting will be automatic as 6.14.0-63 .fc42 won't auto build on akmods, i don't believe
Gcorrect, stable won't build
Gi'm fine waiting another week for F42, but with the current logic stable builds will fail instead of targeting F41
Jyeah, and we need to get a fix out of bluefin stable 41.
Jso kind of a bummer
Jok so what's the plan, no stable builds for 2 weeks? that kind of sucks.
Jnot moving to f42 for 2 weeks is fine but we need to still get builds out right?
G@antheas going to use this hack rather than adding an rpm-ostree fallback
Git works
BBluefin builds will still be fine, but kernel/kmods will be paused at last successful build of coreos stable.
This is all working as planned really.
This is all working as planned really.
Joh ok because they failed this morning
Jlet me doublecheck
BOh link me.
JBMaybe I misunderstood.
BOk, yeah then we probably need to override that to get builds for next few weeks.
Jright but we can stay on 41 though right?
Jif we can stay on 41 that's ideal because the installer is still not functional. 
BYeah we need to override bluefin stables version
ISame issue on Auroras stable
Bi'm looking for solutions
Bi think the answer might be a kernel override on akmods for coreos-stable
MFor bluefin and Aurora stable I believe the kernel-pin should work for setting the fedora version.
Ucore is kinda in a lurch though
Ucore is kinda in a lurch though
Bdon't we have a kernel pin for it?
MFor Ucore we pinned kernel-cache
Bahhh
MLast time we were in this situation
Bi'm going to PR the kernel pin for bluefin now
MByep, i just verified that too
BM2 cycles in a row.... Who else is working with timothee on coreOS?
BIThanks sherman
NYou are the goat, tysm! 
Jthen after this merges and explicit run of GTS and stable to update the tags right?
MYes. Get the hostname fix.
And we'll be sitting here for a few weeks.
And we'll be sitting here for a few weeks.
Bi need to add kernel pin to ucore
Jgood, I prefer the knife pointed squarely at me instead of resting against my neck. 
NIs this something we would want to carry upstream in akmods? https://github.com/ublue-os/bazzite/issues/1864
GitHub
Describe the package I'd like to request the support of Apple Macs, that use the Apple T2 security chip (like the MacBook Pro (16-inch, 2019) or the MacBook Pro (13-inch, 2020, 2 Thunderbolt 3 ...
Nlooking at the copr repo, there are not many users affected.
BGitHub
FCOS 42.20250410.3.1contains kernel 6.14.0-63 a rawhide kernel. We want to delay this release and the only good way at this time is to delay the stable update by one cycle.
This forcibly downgrades...
This forcibly downgrades...
Jsherman I understood that one!
Mhttps://github.com/ublue-os/main/pull/832
this moves initramfs generation to after nvidia driver install
this moves initramfs generation to after nvidia driver install
J
