To distro-sync or not distro-sync?
zbyszek at in.waw.pl
Mon Oct 26 17:39:23 UTC 2015
On Mon, Oct 26, 2015 at 06:24:43PM +0100, Miroslav Suchý wrote:
> I am trying to upgrade to F23 (I know still not finished but...)
> In past I always done 'distro-sync'. Albeit with yum.
> Now I tried:
> dnf system-upgrade download --releasever=23 --distro-sync
> dnf system-upgrade download --releasever=23 --distro-sync --best
> dnf system-upgrade download --releasever=23 --distro-sync --best --allowerasing
> And all of them fail. See below for full log.
> On the other hand:
> dnf system-upgrade download --releasever=23
> Actually most of the problem are caused by retired or obsoleted packages. E.g fedup-dracut or rubygem-celluloid (this
> one reported as BZ 1275030).
FTR, fedup-dracut was obsoleted today morning
> My question is should we use --distro-sync at all? Are users supposed to remove obsoleted packages manually?
--distro-sync is now (in git, I don't think this version was released yet)
the default in dnf-plugin-system-upgrade.
> # dnf system-upgrade download --releasever=23 --distro-sync --best --allowerasing
> Error: package rubygem-celluloid-0.15.2-2.fc22.noarch requires rubygem(timers) < 1.2, but none of the providers can be
> package fedup-dracut-0.9.2-1.fc22.x86_64 requires librpm.so.3()(64bit), but none of the providers can be installed
What version of dnf/libsolv are you using? The last update
(libsolv-0.6.14-2.fc22,dnf-1.1.3-1.fc22) solved a bunch of
More information about the devel