Someone on a forum I follow had a problem with mesa packages and wanted to rollback to the previous set. dnf history rollback is useless
The problem is that Fedora updates repo is only one deep so rollback doesn’t work. I think that dnf rollback works for Centos like distros (Alma and Rocky) because those repos do save off updates
But I think there’s some way to dig back into the Koji system to get those old rpms right?
Rolling back (downgrading) to the version in the base fedora repo has always been sufficient for me.[1] However, it looks like there is something called fedora-repos-archive (I’ve never used it):
On extremely rare occasion, I have added --releasever=<N-1> to install an even older package from the previous Fedora Linux release. ↩︎
Yes.
You can use the web interface Build System Info | koji
Or the koji command from the terminal.
$ sudo dnf in koji
$ koji list-builds --package="vim" --state="COMPLETE" --pattern "*.fc40"
Build Built by State
------------------------------------------------------- ---------------- ----------------
vim-9.0.1712-1.fc40 zdohnal COMPLETE
vim-9.0.1872-1.fc40 zdohnal COMPLETE
...
vim-9.0.2167-1.fc40 zdohnal COMPLETE
vim-9.0.2190-1.fc40 zdohnal COMPLETE
...
vim-9.1.571-1.fc40 zdohnal COMPLETE
Let’s suppose I want to install vim-9.0.2190-1.fc40
Note: in addition to the specific architecture (i.e. x86_64) some packages have architecture independent rpms, so you need noarch stuff too.[1]
$ mkdir ~/Downloads/work && cd $_
$ koji download-build --arch=$(uname -m) --arch=noarch vim-9.0.2190-1.fc40
$ sudo dnf downgrade ./*
Of course, it depends on the complexity of the package, you could incur in a bunch of unsatisfied dependencies, therefore you will have to reiterate the koji list-builds and koji download-build commands also for those dependencies.
sorry, but I’m not very well versed in terminology ↩︎
Nevermind, “fedora-repos-archive” package to setup the repos so dnf rollback works is the better option. A post on the original thread pointed that out as well
Thankfully, but inexplicably, the downgrade worked without me needing to do the extra work from here, BUT in case one needs to downgrade to “a relatively even earlier driver” this post would actually help.