How can I downgrade podman to the latest version in Fedora?
There has been an update to podman version 3.2.0-rc1 which is unstable and should not have been pushed to stable.
Ok, mistakes happen. But how to recover from such? The post says that version 3.1.2 should now be used, but I cannot get it. dnf update does not updated podman to the latest stable version. dnf --enablerepo=updates-testing update does not help either. dnf distrosync does not work either. dnf downgrade podman wants to downgrade all the way to podman version 3.1.0
Looking at bodhi does not help me much either. There, podman-3.2.0-0.1.rc1.fc34 is marked as stable, podman-3.1.2-2.fc34 (which is a more recent build) is marked as obsolete and podman-3.1.2-3.fc34 is marked as pending → testing.
Looking into more detail at bodhi, podman-3.1.2-2.fc34 has been submitted to stable a day ago.
So the situation is very confusing. Which version of podman is the most recent stable version? 3.1.2 as written in the mailing list post? Or 3.1.0 as dnf downgrade wants to use?
Also, imagine that I would not have checked about the podman status, when would I have gotten a stable podman version through the regular update channels?
Seems to me as if the process of retracting updates has a lot of friction. Should I report this as a bug to dnf, or rpm?
EDIT: Just noted that after downgrading to podman 3.1.0 via dnf downgrade podman, dnf update immediately wants to update to the broken 3.2.0-rc1 again. So I guess the update was not retracted after all.
Sorry, I don’t quite see that this obsoletes 3.2.0-rc1. On the bodhi page I only see that it obsoletes 3.1.2-2. Am I missing something there?
Also, if that update is stuck in testing for a week, does that mean that Fedora keeps shipping a broken package instead of shipping the old version for another week? Seems less then ideal to me.
I meant that the new update obsoleted the old update. Whether that package build obsoletes the previous package build is a different thing, and depends on the full version. Bodhi only shows the Version and Release of a build, but if you check the builds on koji, the Epoch was increased to 3. This overrules the Version entirely and allows going ‘backwards’.
It already has enough karma to go stable now, but it needs to go to testing first, and whether it goes to stable now or later depends on when the maintainer pushes it.
Ah, thanks, I was not aware that epoch works like that.
Well, I guess it was a deliberate decision to try to fix the issue with a “new” version (3.1.2) instead of just increasing epoch of the old stable 3.1.0. I have to say that I disagree with that decision though.