just did upgrade from 13.2 to Leap 42.1
the upgrade was done by upgrading all the repositories to their L42.1 counterpart and choosing update all packages in YaST2 / Software management.
had a number of conflicts and chose not to upgrade a number of packages to the most recent version to solve those as well as removing 6 packages.
have been updating my config this way since 12(.1 i think) without problem until now.
after rebooting the boot ends at the command prompt login where i can login and startx
not really good as system is supposed to start and always started in the past to runlevel 5.
once there YaST2 is not starting with
Command: /sbin/yast2 repositories &
The config 'root' does not exist. Likely snapper is not configured.
See 'man snapper' for further instructions.
terminate called after throwing an instance of 'YUIPluginException'
what(): Couldn't load plug-in qt
YaST got signal 6 at file /usr/share/YaST2/modules/Wizard.rb:782
sender PID: 5797
/sbin/yast2: line 440: 5797 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
Invalid snapshot ''.
Command: /sbin/yast2 sw_single &
The config 'root' does not exist. Likely snapper is not configured.
See 'man snapper' for further instructions.
terminate called after throwing an instance of 'YUIPluginException'
what(): Couldn't load plug-in qt
YaST got signal 6 at file /usr/share/YaST2/modules/Wizard.rb:782
sender PID: 5843
/sbin/yast2: line 440: 5843 Aborted $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
Invalid snapshot ''.
i’m using ext3 for all my Linux partitions because i’m still using (happily) partimage to backup all my OSes on my system and ext3 is the latest that partimage supports + never had any problems with ext3 and really don’t care about all the “new” features.
Probably not, because YaST will be amongst the packages upgraded. Also, the OP does not say so, but he could even mean he used YaST from his desktop and thus more packages in use upgraded.
I am also pretty sure that doing this through YaST software manager as described by the OP is nowhere documented as a valid method.
Maybe the best starting point is to show to people here what your situation is now:
as i mentioned i have been upgrading my openSuSE setup for as long as i can remember. i mentioned as starting point 12(.1) because a couple years ago i ran into problems where a fresh install seemed the easiest way out.
anyway, did i mention partimage? i can roll back to 13.2 and try the zypper dup approach.
how does zypper handle conflicts? there were quite a few and i see no reason they wouldn’t appear with zypper, no?
Your repos look OK to me. Apart from the non-openSUSE ones for which I have no comment. IIRC the recommendation is to at least disable them during the zypper dup that does the upgrade. And then after that is succesfull, to change them to their 42.1 versions (if applicable), enable them again and install from them what you need. This includes Packman. First disable it, then after the zypper dup, change to Packman 42.1 and do “the switch” (e.g. zypper dup --from <something-that-identifies-the-Packman-repo>)
My advice: disable all except OSS, non-OSS and their Updates repos. Then do a
zypper dup
to get the LEAP 42.1 packages replacing the 13.2 packages.
Please try that to see if you get any error messages (you can say no to abort it before it does something).
When in doubt first ask here (of course posting the messages).
I notice you have KDE3 repo so I assume that is the desktop you use?? Possible point of conflict.
Also the error you showed concerns snapper and you use ext3 which I doubt hardly anyone else uses these days. In theory any way snapper is supposed to be usable in ext4 but not in ext3. I suppose that the developers never considered anyone would still use ext3 for the root.
It may be time to move from the dark ages into the light and do a new install using more modern systems.
