Theres currently no defined way that I know of on how to get the OS installed on your system correct
Theres currently no defined way that I know of on how to get the OS installed on your system correctly
![[[xenofembutch]]](https://cdn.discordapp.com/avatars/423616003117940747/c812f8002fc4f9134b5fae4b05e815ca.webp?size=40)
MMAdditionally, while I like the digests right now.... Timothee's builds get garbage collected since he doesn't increment the version on a mid day rebuild.
RYeah. This has been raised, and there's a plan to resolve it.
Renovate picks up on new digests anyway, so builds won't be broken for long
Renovate picks up on new digests anyway, so builds won't be broken for long
Mmostly annoying during the PR having to merge main in multiple times
F@j0rge This issue of mine was just fixed, next release of Gnome Software will include the fix
thanks to the maintainer for quick response & fix
https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/2259
thanks to the maintainer for quick response & fix
https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/2259
FI see the milestone is for 49.alpha version, but I believe they will backport this fix
Jamazing thanks for tracking this!
MYeah. It's not too bad. Just need to know what's happening.
And it's not an actual issue most of the time
And it's not an actual issue most of the time
Jideally I'm asleep!
GGI think this works for
uupdbetter than setting the selinux context, since everything works from shell just fine
G
Gso 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
