Comment # 6 on bug 1041443 from Michael Andres

(In reply to Jeroen Pluimers from comment #5)
> 1. why does a plain `zypper dist-upgrade` indicate nothing should  be done?
> 
> I just re-checked:
> 
> ```
> # zypper dist-upgrade
> Loading repository data...
> Reading installed packages...
> Computing distribution upgrade...
> 
> Nothing to do.
> ```

It's due to the way the resolver operates. The 'job' is to make sure the
kernel-default-4.11.1 is installed. As this is already true, both calls will
perform no action. As 'dist-upgrade' per default allows vendor changes, the
solver does not see any policy violation here.

When performing 'dist-upgrade --no-allow-vendor-change' the resolver sees a
policy violation, as the vendor changes from
'obs://build.opensuse.org/devel:ARM' to 'openSUSE'. 

It smells a bit like a false-alarm, because the package is already installed
and no action needs to be performed. But I'll have to discuss this with the
solver experts first.


> 2. where did you get the list of kernels from?

You attached the solver-testcase. It contains all information that's needed to
replay (and debug) the transaction locally.

This includes the dependency information of all packages installed
(solver-system.xml) and available in repos (*-package.xml); also the resolver
settings and the job you executed (solver-test.xml).