https://bugzilla.novell.com/show_bug.cgi?id=460751 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |jkupec@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=460751 User ma@sernet.de added comment https://bugzilla.novell.com/show_bug.cgi?id=460751#c2 Michael Adam <ma@sernet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@sernet.de --- Comment #2 from Michael Adam <ma@sernet.de> 2009-01-06 03:23:55 MST --- Hi Jan, thanks for your comments! (In reply to comment #1 from Jan Kupec)

First, you need to be more specific. All you have said is "11.0's zypper dup failed (you didn't say how, you just said it was 'incomplete') and after upgrading to 11.1's zypper it worked all right".

I am saying more than just it "did not work": The return code and messages of "zypper dup" created the impression that everything was complete and correctly updated. But this was wrong. A reboot rendered the system unusuable. I had to hack the system, manually set up networking and install zypper of 11.1 (find out first that this was needed), then zypper dup again.

Second, if the 11.1 version works fine, i believe it does not make much sense to search for the problem and eventually backport the fix to 11.0's zypper/zypp/satsolver

Well, I am saying that the _upgrade-path_ from 11.0 to 11.1 from within the running system using zypper is broken, not that there is a fix in 11.1 that can be backported to zypper of 11.0. (Maybe there is, but I don't know enough of the internal workings of zypper...)

since installing the 11.1 stack (as you suggest) is an easy workaround.

That is right. But people have to be _aware_ of the workaround. Or else they will run into the same trap as me. The point I am making is that the zypper of 11.0 should be aware of the problem and force update of zypper (and rpm) first. Then ask the user to re-run zypper dup (or even do this by itself). This is rather what I was thinking of... :-) At least there should be a warning for the user somewhere.

But maybe Michael (CCing him) will want investigate this if you provide more details.

Note that people upgrading to 11.1 using an installation DVD won't have this problem, since the software management stack is the new one there.

Sure. You might of course argue that a user who wants to update not using installation/update media but by changing the repositories and running zypper dup from within the running system is bound trouble. But I usually like to upgrade "the debian way" (*hide*) ... :-) And for future updates, it would really be nice if this kind of update could be performed more smoothly.

Closing as WONTFIX, Michael reopen, if you want to investigate.

Cheers - Michael PS: btw - the zypper-dup upgrade seemed to be not as complete as the installation-dvd-upgrade even after using the above workaround. the branding of the grub and boot screen somehow did not seem to have been updated. (I did not invesitgate this further yet, just the look is still the 11.0 one in the "zypper-dup"-ed system...) I could open a new bug report if this is in any way interesting to know. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.