On Mon, Mar 30, 2020 at 02:40:03PM +0200, Miroslav Suchý wrote:
Dne 27. 03. 20 v 8:55 Zbigniew Jędrzejewski-Szmek napsal(a):
> In current "offline upgrade" scheme, the upgrade
> tools are running on the real system, with udev active.
This thread has mostly died, but I didn't want to leave this unanswered.
How the "offline upgrade" works under hood?
It's essentially a 'dnf upgrade --releasever=NN', except that it runs
is sandwiched between two reboots (to avoid things running during the
upgrade, and to restart everything after the ugprade).
See
https://www.freedesktop.org/software/systemd/man/systemd.offline-updates.....
Do I understand correctly that even "offline ugprade" will
have
problem with upgrade from F32 to F33 because of rpmdb?
No, there shouldn't be any problem. New rpm will still support the old
database, fully in F33, and then probably read-only in F34+. At some
point the rpm --rebuilddb operation will need to happen, but we have
plenty of time to do it. The discussion was mostly about whether it
should happen automatically on upgrades, and when. The effect of *not*
doing the upgrade automatically during upgrades to F33 is less use and
testing, not breakage.
Zbyszek