On Sun, 2017-11-12 at 23:34 -0500, Felix Miata wrote:
Simon Lees composed on 2017-11-13 14:04 (UTC+1030):
Felix Miata wrote:
Basil Chupin composed on 12 Nov 2017 09:01:45 (+1100):
Felix Miata wrote:
Very broken for me. No zypper is very bad: https://bugzilla.opensuse.org/show_bug.cgi?id=1067737 Is there any possibility to fix what I have rather than starting all over (and arriving in the same place unless first something is fixed)? Zypper is working perfectly for me. On a freshly made upgrade from 42.x like I tried to do? But why are you doing it like that?
Long before I discovered SuSE, urpmi would upgrade itself and its deps, then restart before installing everything unrelated to package management. It made sense then, and still did when I learned how to use zypper many moons ago.
I thought I was emulating this urpmi safety feature via an emulating script. This was the first time it failed me after too many years to remember of working as expected with distribution releases, Factory, and TW.
Why it makes sense is pretty simple, bad stuff happens, Hi
It seems that bad stuff that happened here is triggered somewhere between chair and display. Also note that for regulary maintained releases, zypper patch will update package management stack (zypper, libzypp, rpm) befor installing other updates. This does not make sense for dist upgrade where exactly stuff that happened to you would happen - but hey I guess you know better then developers of distribution. Good luck with shooting yourself in leg (and I hope that you will keep us updated) Martin