https://bugzilla.novell.com/show_bug.cgi?id=826592 https://bugzilla.novell.com/show_bug.cgi?id=826592#c2 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |libzypp AssignedTo|ma@suse.com |zypp-maintainers@forge.prov | |o.novell.com QAContact|jsrain@suse.com |qa-bugs@suse.de --- Comment #2 from Michael Andres 2013-07-02 09:38:16 CEST --- The mandatory part IMO should be libzypp reloading the settings from an existing system upon TargetInit. (The same probably applies to other zypp.conf settings as well, e.g. vendor settings, solver settings,..). This just requires yast to call TargetInit upon an system update before software selection starts; but AFAIK they already do. OPTIONAL: The above takes care that inst_sys basically uses the same settings as the system does. In case we also want to tell the user that we now support multiple kernel versions being installed in parallel, and we even recommend this, then we need some dialog in yast. We IMO can't silently change the systems settings. -- 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=826592 https://bugzilla.novell.com/show_bug.cgi?id=826592#c3 --- Comment #3 from Ludwig Nussel 2013-09-19 16:15:24 CEST --- on distro upgrade it doesn't make much sense to keep the old kernels of the previous distro around though IMHO -- 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=826592 https://bugzilla.novell.com/show_bug.cgi?id=826592#c5 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |coolo@suse.com InfoProvider|coolo@suse.com | --- Comment #5 from Stephan Kulow 2013-09-27 12:09:23 CEST --- Obsolete: kernel < 3.11 ? I guess I can do that :) -- 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=826592 https://bugzilla.novell.com/show_bug.cgi?id=826592#c7 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER- --- Comment #7 from Stephan Kulow 2013-09-27 17:03:39 CEST --- I added that conflict now - but I can't see how this is P1 when there is still a global zypp lock :) -- 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=826592 https://bugzilla.novell.com/show_bug.cgi?id=826592#c9 --- Comment #9 from Michael Schröder 2013-10-09 11:04:25 UTC --- How's that a zypper problem? You probably mean "add the old kernel versions to the droplist". (This maybe needs a little libzypp patching, so that versioned droplist entries work.) -- 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=826592 https://bugzilla.novell.com/show_bug.cgi?id=826592#c11 --- Comment #11 from Michael Andres 2013-10-10 08:48:01 CEST --- (In reply to comment #9)

How's that a zypper problem?

The original problem; when opening a target with --root, libzypp does not re-scann the targets zypp.conf. Thus from instsys we will update with multiversion kernel turned on, but it might be the underlying system has multiversion turned off. -- 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.