Describe what you would like us to do:

+1 On this. If nobody has seen, here is the current fix:

cd Downloads
wget https://kojipkgs.fedoraproject.org//packages/rpm-ostree/2021.1/3.fc33/x86_64/rpm-ostree-2021.1-3.fc33.x86_64.rpm && wget https://kojipkgs.fedoraproject.org//packages/rpm-ostree/2021.1/3.fc33/x86_64/rpm-ostree-libs-2021.1-3.fc33.x86_64.rpm && wget https://kojipkgs.fedoraproject.org//packages/libsolv/0.7.15/1.fc33/x86_64/libsolv-0.7.15-1.fc33.x86_64.rpm
sudo rpm-ostree usroverlay && sudo rpm -Uvh rpm-ostree-{,libs-}*.rpm
systemctl restart rpm-ostreed.service
rpm-ostree override replace libsolv-0.7.15-1.fc33.x86_64.rpm

xref forum thread: https://discussion.fedoraproject.org/t/cannot-upgrade-silverblue/26652

I'm not sure I am clear what you are asking for here.

I guess we are talking about https://bodhi.fedoraproject.org/updates/FEDORA-2021-136fec7edc ?
We have no way to 'revoke' a already stable update from the normal update stream. We need to revert the changes and push a newer update out.

Or does this just need changed in ostree repo? How would things be affected by reverting that there?

Side note: @adamw I wonder if we could add a openqa rpm-ostree tester for updates to catch things like this?

We have no way to 'revoke' a already stable update from the normal update stream.

rpm-ostree on the server side fully supports it; that's what the linked PR for FCOS will do.

I mean...as you know, I've been working on making this a "normal event" for close to 10 years now: https://lwn.net/Articles/513015/

"I wish the article had highlighted more what I consider the biggest issue - the inability of both dpkg and rpm to go backwards. I'd revert Fedora rawhide for example back to a state where it could start GDM this very second if it were possible. Reverting is not always the right answer of course - it's important to debug things. But it's a lot more important to have a constantly usable development tree."

And yes, almost 10 years later people are still talking about "core desktop broken in rawhide" bugs...

Recently we introduced the "updates archive" repo in CoreOS for this reason and it also is now enabled in Silverblue client side. We weren't enabling it server side, but this PR does: https://pagure.io/workstation-ostree-config/pull-request/190
And that will revert libsolv - remember, rpm-ostree very intentionally allows packages to downgrade.

I think that linked PR should just work; I'd forgotten we'd introduced the updates archive rpm-md repo and when I filed this ticket I thought we'd need to do it "manually" by introducing an rpm-md with the reverted libsolv.

So tentatively closing this.