On 29 December 2016 at 12:53, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2016-12-29 13:49, Robert Kaiser wrote:
There are more chances of yast crashing than zypper crashing.
Sure, but it's very very rare that it doesn't run through without issue, esp. on TW - actually, I can't remember having any issue at all since TW started (I sometimes did with Factory). On Leap, I do zypper dup for a new version and the YaST variant(s) for in between and I never had an issue there with that.
I have. Whole desktop crash during upgrades. I run zypper in a text mode console for that reason.
and that's why my 'zypper-twup' alias does "sudo screen zypper dup --no-allow-vendor-change" The screen means the upgrade will continue regardless of whether or not the desktop or tty I am running it from explodes spectacularly, even though it happens very rarely. for the equivalent of 'zypper up', openSUSE GNOME also takes care of this problem by using the GNOME Software update mechanism. Packagekit downloads all of it's patches, then offers the user to reboot to install them. When that user choses to reboot, systemd boots into a special 'upgrade' target, which only patches the system and then reboots again into the patched system. This is a stupid way of doing things, of course doesn't do the upgrade as completely as a dup --n-a-v-c would, but it does avoid the problems of desktop crashes during upgrades borking upgrades using a graphical tool at least. In the future, I'm most excited about the prospect of proper 'transactional updates' for Tumbleweed, such as you can see working in concept here: https://github.com/thkukuk/transactional-update -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org