Comment # 19 on bug 916171 from
(In reply to Stephan Kulow from comment #14)
> how is this my bug?

Maybe mls@ wanted to tell you that 'nothing provides
this-is-only-for-build-envs' in 13.2, 
although systemd-mini, udev-mini and libudev-mini1 in the 13.2 update repo
require it?

Just a guess, but if it was less obvious he would have written a comment,
wouldn't he?



(In reply to Per Jessen from comment #18)
> Unfortunately I have no idea how to interpret log output, who can help me understand it?

That's not easy to explain (usually the reporter is asked to provide a solver
testcase, and we do the debugging... ;)

>    # zypper dup --debug-solver
>    ...
>    Generating solver test case...
>    Solver test case generated successfully at /var/log/zypper.solverTestCase.  

Then pack the output directory and attach it to the bugreport.
In case the testcase exceeds the 10MB limit for bugzilla uploads, 
you can use 'split' to divide the file into smaller pieces:

>  $ cd /tmp
>  $ tar cvjf zypper.solverTestCase.tar.bz2 /var/log/zypper.solverTestCase/
>  $ split -b 9M --additional-suffix=-zypper.solverTestCase.tar.bz2 \
>    zypper.solverTestCase.tar.bz2

The created pieces will be named like this:

>  xaa-zypper.solverTestCase.tar.bz2
>  xab-zypper.solverTestCase.tar.bz2
>  xac-zypper.solverTestCase.tar.bz2
>  ...

Anyhow. To me it looks like systemd-mini/udev-mini/libudev-mini1 were provided
and installable on 13.1.

On 13.2 however they are provided (by the update repo), but no longer
installable (due to the missing this-is-only-for-build-envs requirement). 

The fact that those packages are installed on your 13.1 prevents you from
upgrading to 13.2.

I suppose it was not intended that those -mini packages are installed outside a
build environment. So the solution for you is most probably to replace the
-mini packages by systemd/udev/libudev before performing the update to 13.2. 

Someone may correct me if I'm wrong.


@coolo/mls: Do we need to investigate why the installation in c#17 selects the
-mini packages? 
            Or is it a known issue?


You are receiving this mail because: