Mailinglist Archive: opensuse-bugs (4297 mails)

< Previous Next >
[Bug 1041443] Raspberry Pi 3: zypper unclear conflict resolution problem message
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 31 May 2017 13:25:10 +0000
  • Message-id: <bug-1041443-21960-laPNJq6c1X@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1041443
http://bugzilla.suse.com/show_bug.cgi?id=1041443#c7

Michael Schröder <mls@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |mls@xxxxxxxx

--- Comment #7 from Michael Schröder <mls@xxxxxxxx> ---
I can somewhat explain the behavior: dist-upgrade makes sure that all of the
installed packages come from the configured repositories. There's a bit of
special handling for "multiversion" packages like the kernel, though.

With vendor changing allowed, the solver sees that kernel-default-4.4.68 is old
and not in a repository, but there's a newer version available and the
installed version can upgrade to it. So it forces the update, which is a no-op
in your case because it is already installed. The old 4.4.68 kernel is
considered "orphaned", i.e. the solver will deinstall it if it gets in the way,
but it does not mind that it stays installed.

With vendor changing disabled, the solver does not have an valid update
available for the old kernel. But there is a kernel with a different vendor. So
it does not know what to do. The solution part is missing a "deinstall obsolete
kernel" option, though.

The "distupgrade with restrictions" mode needs some more work, I admit. ;)

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References