If you know how to make sure nvidia is good to go, happy for you to take over. All I am doing is re
If you know how to make sure nvidia is good to go, happy for you to take over. All I am doing is rerunning the jobs and seeing if they are green
EThere's a PR for NVIDIA I opened as well. Both should be good
BI'll take a look
J3,552,280 pulls.
Jabout 2 weeks to get half a million
Jso it's definately getting faster. 
Bi think we should drop to keep it simple
BBBthe good stuff in 545 seems mostly about improving wayland support
RThat's all most people care about at the minute. Performance is quite good at almost everything.
I'm hoping Zoom starts working with Wayland sometime soon, then I can make the switch
I'm hoping Zoom starts working with Wayland sometime soon, then I can make the switch
Bok, well the akmods/main/nvidia builds seem good at the moment and PRs are merged for 545 only... huzzah
K
B
Dthanks for approving this
COh damn, that is a lot more than I thought
CI'd estimate that's 25-30,000 users
JGitHub
When Podman starts, it checks a number of critical runtime paths against stored values in the database to make sure that existing containers are not broken by a configuration change. We recently ma...
Jwe need to pin an old version
JGitHub
Issue Description Starting with version 4.8.0, I get the error below. Error: database libpod root directory (staticdir) "/home/<user>/.local/share/containers/storage/libpod" does no...
Janyone have time to pin podman in F39?
Jthis breaks podman and toolboxes
Jbut I need to step out for something
J@KyleGospo around?
KI'll take a look
KWhen is the last time we pinned it?
Jlast cycle
Jwe need to go to 4.72
Jfinding the link
RJJJthink this is what we need but would need another set of eyes
Jthe older 4.8 snapshots don't appear to be affected but I am also not sure, 4.72 seems like a reasonable pin
Jrpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2023-00c78aad58 should do itJtrying 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
J