To distro-sync or not distro-sync?

[Honza Šilhan]

> From: "Miroslav Suchý" <msuchy at redhat.com>
> 
> >> # 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
> >> installed.
> >> 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
> > upgrade problems.
> 
> Exactly dnf-1.1.3-1.fc22

The distro-sync changes happened in libsolv-0.6.14-2 - it should be a requirement of 
dnf-plugin-system-upgrade-0.7.0.

You can exclude the conflicting packages to proceed the system-upgrade i.e.:
"dnf system-upgrade download --releasever=23 --distro-sync -x rubygem-celluloid --allowerasing"

> From: "Reindl Harald" <h.reindl at thelounge.net>
> To: devel at lists.fedoraproject.org
> Sent: Thursday, October 29, 2015 10:56:47 AM
> Subject: Re: To distro-sync or not distro-sync?
> 
> From: "Reindl Harald" <h.reindl at thelounge.net>
> the software upgrade just have to mention the conflicting packages and
> stop until somebody enables a --force switch and in general DNF has to
> be much more verbose in case of dependency problems instead just saying
> "can't do anything because broken deps"

dnf has `--allowerasing switch - it will resolve the conflicts by uninstallation
of conflicting packages. Installing the packages regardless the dependencies by
`--force` is really dangerous and will not be supported by DNF.

> currently we have some sort of blackbox with no output how to solve
> dependency problems

It outputs the last package conflict found by depsolver. The improvement is on
the agenda [1].


Honza

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1148627