Bug ID 1041443
Summary Raspberry Pi 3: zypper unclear conflict resolution problem message
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component libzypp
Assignee zypp-maintainers@forge.provo.novell.com
Reporter jeroen.forums.opensuse.org@pluimers.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Created attachment 726808 [details]
part of zypper.solverTestCase files

# Steps leading into this

1. Install Tumbleweed on Raspberry Pi 3 from
https://web.archive.org/web/20170526140155/http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/RaspberryPi3/images/openSUSE-Tumbleweed-ARM-LXQT-raspberrypi3.aarch64-2017.05.23-Build3.1.raw.xz 
2. On 20170525 perform `zypper --versbose refresh --force` and `zypper
dist-upgrade`
3. On 20170528 perform `zypper dist-upgrade --no-allow-vendor-change`

Expected: succeed

Actual:

```
# zypper dist-upgrade --no-allow-vendor-change
Loading repository data...
Reading installed packages...
Computing distribution upgrade...

Problem: problem with installed package kernel-default-4.4.68-7.1.aarch64
 Solution 1: keep obsolete kernel-default-4.4.68-7.1.aarch64

Choose the above solution using '1' or cancel using 'c' [1/c] (c):
```

Two important points:

1. Basically both the 1 and c will abort the upgrade so there is no way to
perform `--no-allow-vendor-change` upgrades any more.

2. The reason for the "problem" is not revealed so it is unclear to get out
of 1.


Details: https://gist.github.com/jpluimers/a9ed0802d4314ba3bd662663c2b219a9
which has all the zypper.solverTestCase files


You are receiving this mail because: