Remove all images with `ostree-2024.10-1...
GitHub
Remove all images with
ostree-2024.10-1.fc41 (across all variants...This update / version of ostree was never pushed to the stable repos (https://bodhi.fedoraproject.org/updates/FEDORA-2024-e7abdb1f24) as it includes a change that is causing issues (ostreedev/ostre...
37 Replies
so... finding that could be fun?
dude I tried
but I also don't know if we enable testing repos, so if we don't we should be good?
they have been enabled in different builds at different times
mostly when folks try to build pre-release images
so how cooked are we
not cooked
thank god
he just recommended a boot arg, I wonder if we should explicitly set that just in case? I swear they've flip flopped on composefs a few times?
Who knows how many images have it enabled at this point. I don't think finding all of the images historically that include it would be easy. We can disable it in Bluefin/Bazzite in the hw setup script (not sure if Bluefin has one but will check and write a service that appends it if not) and suggest any users on those builds update
If we enable the testing repo at any point, we should also be careful about how it's being used. It might have just impacted Bazzite
I don't think we've turned on a testing repo have we?
I'll look
Bazzite may have
You can jq rechunk manifests to get the ostree version
In any case adding that kernel arg is very doable @Kyle Gospo
Testing isn't enabled explicitly in tree for Bazzite or Bluefin. Interesting. Disabling composefs now
was thinking just explicitly in main so things in herit it?
like, "we're pretty sure you're not affected but we'll explicitly keep this off."?
can someone update the issue? Looks like timothee was moving fast to let us know, would be nice to let him know we're unaffected afawct?
Do we append kargs in main now?
dunno where, there's a bootc way to do it but I don't know if we're still using the old way or if we're doing it the bootc way
it's a toml file, but we're not using bootc in main. 😦
Will be nice to have when it is available in main. I PR'd Bluefin and Bazzite for now
❤️
ok so looks like we're in the clear on this one?
hey
just FYI I was PMing with a reddit user to fix that on his bazzite legion go.
Unfortunatley
rpm-ostree kargs --append will requires ostree-finalize-staged to set the deployment
so the karg needs to be manually added from the grub menu
this way you boot without composefs and can update
we were able to fix this person's system that way
I was writing a PSA post on the bazzite subreddit but thought "hey, I never posted there, maybe mods want to do something more official"I updated the issue here https://github.com/ublue-os/main/issues/712#issuecomment-2618452811
GitHub
Remove all images with
ostree-2024.10-1.fc41 (across all variants...This update / version of ostree was never pushed to the stable repos (https://bodhi.fedoraproject.org/updates/FEDORA-2024-e7abdb1f24) as it includes a change that is causing issues (ostreedev/ostre...
I tried inspecting manifests on a few bazzite-deck images but could not find one with the problematic version of ostree
let me know if I want me to proceed with that reddit post
yeah I haven't been finding anyway
but I am on the lookout
is this the only one you've seen so far?
We're clear. We never should have had it
Testing wasn't ever enabled in main, Bluefin, or Bazzite
yeah but you know how I live in fear hahaha
😆 If we had a seamless way to go through the rechunker manifests, that may help for stuff like this. I don't know (aside from nuances like this) how helpful that would be though
well this person had it, and they sure did not have any idea this was all about so it probably slipped through
@jorge so far yes, I stumbled on that thread yesterday
for coreOS we have the build browser for that, really helpful !
https://builds.coreos.fedoraproject.org/browser?stream=stable&arch=x86_64
are you guys still deriving on the atomic desktop images or doing compose from scratch ?
you know I wonder if it ended up in bazzite's testing branch?
still from timothee's atomic images, not official yet.
I totally just want to derive from coreOS from the ground up and "skip" silverblue.
interesting, why is that ?
you should have a cincinnati instance if so, because we rely on barriers 🙂
I'm unsure on that one
well we found one device with it, so who knows.
so the pitch I gave to timothee is that fedora should be like coreos: stable, testing, and next. And users just consume a rolling tag instead of explicit versions. Which, are still there just hidden from the end users. That and coreOS holding back the kernel is really useful, we're actually pinned on 6.11.8 from coreOS because of amd regressions. But normally when we're not pinning we use the coreos kernel versions, it's saved us quite a few times with major regressions.
basically I want to build silverblue right from CoreOS, which we agreed was a good idea, just a lot of work. Bluefin and Aurora fake it pretty good though.
In the desktop mindset most people see rebasing as "oh neat I can switch between desktops" but that doesn't make sense to me
But if I can rebase a desktop product between centos, fedora -1, and fedora bases it offers a consistent experience between different use cases. Risk averse and the kid who wants GNOME right away use "the same thing".
I don't think we're in a world were we're rebasing between centos and fedora/rawhide but conceptually ... (hahah)
feel free to submit that as a fedora change 🙂
That's a good idea IMHO
yeah it's in my someday pile hahah. There's so much more important work that needs to land. 😦
anyway : do I close that reddit PSA draft post ?
"I wish we could convince fedora to be as excited about bootc as much as ublue and red hat are." are words I have spoken hahaha.
let me read it
yeah I would just make it clear it's cautionary and you've only found one in the field.
otherwise everyone is going to assume that their existing problem is related to it and people will confuse themselves.
these handheld users are mostly brand new linux users. Like, brand brand new.
https://paste.centos.org/view/cb09b6b2
yeah, that's why I want to be as helpful as possible to not scare people off 🙂
haha
yeah it wouldn't hurt I don't think, we did find one so something for sure is amiss.
@supermaki are you torqueoverHP on reddit?
wonderful handle, that's amazing.