Created attachment 857207 [details]
.tgz of /var/log/zypper.log

Initial Summary:
(e.g. zypper ve)  zypper claims what is provided cannot be provided

[example]
# zypper ve
...
Problem: the installed fuse-2.9.7-3.3.1.x86_64 requires 'util-linux >= 2.18',
but this requirement cannot be provided
 Solution 1: Following actions will be done:
  deinstallation of fuse-2.9.7-3.3.1.x86_64
  deinstallation of dracut-055+suse.238.gacab0df5-150400.1.6.x86_64
  deinstallation of aaa_base-84.87+git20180409.04c9dae-3.52.1.x86_64
  deinstallation of
dracut-mkinitrd-deprecated-055+suse.238.gacab0df5-150400.1.6.x86_64
  deinstallation of aaa_base-extras-84.87+git20180409.04c9dae-3.52.1.x86_64
  deinstallation of
aaa_base-malloccheck-84.87+git20180409.04c9dae-3.52.1.x86_64
  deinstallation of ghostscript-fonts-std-9.06-14.3.1.noarch
  deinstallation of mdadm-4.1-150300.24.9.1.x86_64
  deinstallation of libbd_mdraid2-2.26-150400.1.1.x86_64
 Solution 2: remove lock to allow removal of
kernel-default-5.3.18-59.34.1.x86_64
 Solution 3: break fuse-2.9.7-3.3.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel
[1/2/3/s/r/c/d/?] (c): c
# rpm -qa | grep util-linux
util-linux-systemd-2.37.2-150400.5.1.x86_64
util-linux-2.37.2-150400.5.1.x86_64
#[/example]

This example of newer util-linux and older kernel as incompatible is not new,
having gone on for too long to remember. In many cases, no "break" package
option is offered, so skip must be selected. This applies equally to TW as Leap
beta.

Background. Kernels get removed when I choose to remove them. This causes
package management to get bent out of shape when a kernel is too old to be used
with various tools for rebuilding an initrd that won't be allowed to be
saved[1], in the instant case, util-linux. It forces me to "break" the old
kernel, which is a non-issue. Old kernels' initrds here are immutable, so that
a newer util-linux or dracut or something else is not supported for rebuilding
a kernel's initrd doesn't matter.

This might not be so bad, but the behavior forces use of an X session for
running zypper upgrades, only because scrollback was removed from the kernel
around 5.7.11, and these conflicts lists are commonly more than a screenful,
making access to the reason for the conflict inaccessible, thus the best
response to the proposal impossible to determine. The 9 packages option #1 in
the example above would remove is a short list compared to many others that
should be evident in the attached zypper.log.

[1] cf. bug 1192014