On 2021-10-23 at 23:11 +0200, Peter Boy wrote:
I just tried to upgrade one of my test boxes F34 to F35 using dnf
system-upgrade download --refresh --releasever=35
It failed at transaction test:
/usr/libexec/osbuild-composer/dnf-json (from Installation of) osbuild-
composer-core-31-1.fc35.x86_64 ( collides with file from package)
(the message here was localised in German, my translation here)
On 2 other test boxes the upgrade completed without error (one without
any additions to the basic install and the other with just postgresql
The test box was basic install an lvm virtualisation.
Did someone else tested an update of Server with kvm installed?
And what is the way to get around that issue?
From what I know, "--refresh --releasever=35" is not officially
supported upgrade option. In Your case, dnf-json functionality was split
from the bigger package. Sometimes dnf will not "upgrade" python39 to
python310, because python310 is entirely different package.
Officially the upgrade should be done via dnf system-upgrade plugin. I
can deal with minor conflicts, so I don't bother to reboot twice. Even
typical package combinations (mostly PHP, Pearl, Python and Java
specific) than have to be upgraded between releases are so huge, that
each one has to be tested individually. Which means "just do it".