http://bugzilla.opensuse.org/show_bug.cgi?id=916171 --- Comment #4 from Per Jessen --- Okay, I have just started another installation. I'm using 13.1 plus updates repo. I'm installing a xen guest via ssh+hhtp. libudev-mini1 was automagically selected, see screenshots. This is easily reproducable. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916171 --- Comment #6 from Per Jessen --- Created attachment 621873 --> http://bugzilla.opensuse.org/attachment.cgi?id=621873&action=edit yast screenshot, software selection -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916171 --- Comment #9 from Per Jessen --- (In reply to Dr. Werner Fink from comment #8)

Which package does require libudev-mini1, try to remove it in yast and show the warning resulting about this.

If I remove it, yast automatically selects the libudev and udev packages without the mini1 suffix. I'll see what else I can dig out about it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916171 Per Jessen changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(per@computer.org) | --- Comment #12 from Per Jessen --- (In reply to Dr. Werner Fink from comment #11)

(In reply to Per Jessen from comment #10)

Hmmm ... is there any package which does require systemd-mini?

No, it isn't selected for installation. I tabooed it too, no problems. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916171 --- Comment #20 from Per Jessen --- (In reply to Michael Andres from comment #19)

(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... ;)

Okay :-)

...

# 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:

I'll have a go at this over the weekend, thanks for explaining it.

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

Yes they are.

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 have worked around that, the problem is more that those -mini packages are automatically selected when I install 13.1 (32bit) in a xen guest. (installing 13.1 and upgrading to 13.2 seems to be the only way for 32bit guests in 13.2). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916171 http://bugzilla.opensuse.org/show_bug.cgi?id=916171#c28 Per Jessen changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mls@suse.com) | --- Comment #28 from Per Jessen --- (In reply to Franck Bui from comment #26)

A simple workaround exists but it requires user intervention: in my case I simply needed to replace the mini packages with:

$ zypper in udev

before updating systemd. zypper prompted me to replace udev-mini with udev.

@Per: could you confirm that you did the same workaround ? if not could you test this one if possible ?

The work-around does the trick, thanks.

@all, do you think that the manual workaround is acceptable assuming that there're very few users affected by this bug ? Of course it will be documented where appropriate.

Note that for new installations are going to be fixed as we plan to update 13.1 with systemd v210.

Both sound good. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916171 http://bugzilla.opensuse.org/show_bug.cgi?id=916171#c30 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #30 from Stephan Kulow --- As far as I understand there is nothing to fix here - 13.1's ship has sailed and there are requires in the -mini packages to avoid exactly this situation since 13.2 So in my reading this 13.1 bug was fixed in 13.2, but requires manual intervention. But just as zypper dup says so rightfully: "Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue." - a zypper dup to a pure 13.2 wouldn't have shown this problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916171 http://bugzilla.opensuse.org/show_bug.cgi?id=916171#c32 --- Comment #32 from Stephan Kulow --- you're duping to 13.2+updates - which it not the same as pure 13.2. dup has a --from option to limit the usage to the repo-oss repo after that dup you can zypper patch -- You are receiving this mail because: You are on the CC list for the bug.