+1
I would love this for Rawhide. This would also allow `dnf downgrade` to
work, which would be very useful when things go south. In stable
releases, you could in theory downgrade from version in `updates`
repository to version from `fedora` repository`, but that is not
possible in Rawhide :/
Vít
Dne 24. 03. 20 v 1:12 Michel Alexandre Salim napsal(a):
Hi,
We run a diverse fleet of Linux laptops and desktops (at Facebook), and sometimes there
are regressions that affect some of our fleet but not others.
To pick the latest example:
- pulseaudio 1.3.99.1 (both -1 and -2) breaks Bluetooth support on a Dell XPS 15:
https://bugzilla.redhat.com/show_bug.cgi?id=1814556
- but it fixes HDA audio input on ThinkPad T490s and X1 Carbon:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c3e19f5098
We've had similar issues with kernel regressions (e.g. 5.4 kernels had issues with
Intel GPUs, and on ThinkPads with Nvidia GPUs).
(Ideally we catch all this before they land -- over the medium term I'm trying to
find a way to encourage our users to help test updates)
Would it be possible to keep 2 or 3 versions of the same package in the updates repo, so
we can easily keep some of our fleet at a previous version known to work on that
particular hardware? And is there a process for proposing this (e.g. file a ticket on
Pagure)?
Our workaround right now is to check in the older versions in our internal repo.
Thanks,