`rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2023-00c78aad58 ` should
rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2023-00c78aad58 should do it
Jtrying it locally
Janyone have a 39 machine handy? bluefin has podmansh so there's a conflict I need to figure out and all my VMs are 38
RI have a 39 VM without podmansh
J@TheSteve0 ran into the error too
RHow can I reproduce it?
Or do you want me to just try running the override command?
Or do you want me to just try running the override command?
KIf that works out
RThe override command completed successfully. Rebooting to make sure podman is still usable, but since I couldn't reproduce, I don't know if this version is fixed or not
R
TWOOOHOOO it worked!
Jwe can ignore the 37 errors
Bhey quick question, where are the hardware checks that the updater runs are defined ?
TJawesome, now we just need to wait for the builders to catch up and then we just need to rebuild everything.
Jlol
JJoh man
T
T@j0rge should I be concerned about that "oh man"
Jno you'll be fine, it's just accounting for this in the dockerfile for us might get annoying
TThanks so much for your help!
RHave pushed a commit that fixes the builds for now. Don't know how long it will last without needing to be changed again, but it's fine currently
Jthanks so much!
Jhero
Jhwe images should be next right?
RYou talking about the order of builds? If so, no clue
Jno worries
J@Robert (p5) I can confirm my distroboxes work now, THANK YOU!
JI'll post on the forum
RGreat to hear!
It was mostly Kyle's work. I just wrapped it in a condition
It was mostly Kyle's work. I just wrapped it in a condition
J
FQuestion is there any way to downgrade the NVIDIA drivers? current ones are kinda completely broken for games for me
RSince RPMFusion stopped publishing the old v535 Nvidia drivers, we have stopped building them but the old images should still be available to rebase to. Which image are you using?
Fusing 545 here
RFYI - you're sharing links that use HTTP and require logging in. There are no redirects to HTTPS, so it's not the safest as credentials may be shared in plaintext.
Also, not sure where you got universal.blue.discourse.group from - I believe it should be universal-blue.discourse.group
Also, not sure where you got universal.blue.discourse.group from - I believe it should be universal-blue.discourse.group
RSorry, I mean Bluefin, Bazzite, main etc
Foh right using Bazzite lol forgive me I thought I was in the Bazzite channel I can move there if thats better
R@KyleGospo would be better to answer this I'm afraid...
I think you should be able to rebase to
Maybe would be best to ask the question in the Bazzite channel and Kyle or someone else who daily-drives Bazzite would be able to help
I think you should be able to rebase to
ghcr.io/ublue-os/bazzite-nvidia:39-20231130, which will be before we enabled the v545 builds, but you will no longer receive updates until you rebase back onto the original imageMaybe would be best to ask the question in the Bazzite channel and Kyle or someone else who daily-drives Bazzite would be able to help
Fcool will do sorry for asking in the wrong place lol
RAm I looking in the right place? I can't seem to find it...
https://universal-blue.discourse.group/c/general/4?ascending=false&order=activity
https://universal-blue.discourse.group/c/general/4?ascending=false&order=activity
Joh thanks, fixing
RI've taken on a new role at my company focused on cybersecurity, so a login page on http is a major red flag. These now stand out much more than they did before
JI think that was a wrong url
Jnow the post is totally missing?
RI couldn't see the post at all. Your link went to a ublue login page, and I didn't want to proceed.
And I couldn't see one on the other site
And I couldn't see one on the other site
Jyeah I think that was the old instance
Jthe URL was wrong, it was an old bookmark or something
JI fixed my bookmarks, I'll repost
Jok there we go!
