So, is it OK to update from 15.1 to 15.2?
I am in process of doing that on my old hp desktop, but asking if it is ‘officially’ released so I can start on the laptops.
And should I do updates via Ethernet instead of WiFi?
2nd thought, would it be better to wait for 15.2.1 later this year for the laptops?
I have done 9 laptops from 15.1 to 15.2 all with no issues. I posted some notes in the install section on my migrations - with wifi you do have to worry about packagekit messing with the repos.
2 were ethernet and 7 only had wifi.
No issues on any - All only used ext4 files systems for / and fat for UEFI boot.
I like to keep it simple.
@larryr - yeah I want things as simple as possible too. Thanks for your response!
general comments:
I knew going in I would have to remove a boat load of things I didn’t want.(a PITA).
Update went smooth,(with a LOT of blues in the processes).
So I’m sure it is know KDE5 but how do I make sure qt4 is updated (or removed) since it is going away in the next release(I think)?
PS can I update from a console or do I have to use a virtual terminal?
Not really sure what you mean by “update”.
If you are planning on an online upgrade from 15.1 to 15.2 (say via “zypper dup” after having edited the repos so they point to 15.2) that is best done on a console, since that is going to upgrade the whole desktop/GUI, NetworkManager applet and other things and the chance of loosing the virtual terminal and aborting an incomplete install is high, possibly leaving you with an unbootable or otherwise unstable system.
If you mean the routine “update” of a few packages (say via “zypper up”) that can be done on a virtual terminal (konsole on KDE or other terminal emulators) most of the time; but if you see that parts of the graphics stack (e.g. Mesa-xxx) or parts of KDE or NetworkManager are going to be updated, I would still recommend not to begin the actual update and use a console instead (I mean a VT terminal, Ctrl+Alt+F1 or the like).
There are workarounds using “screen”, but since things changed there recently, I cannot advise on that (maybe @nrickert can, if he is reading this).
This can sound confusing. By “console” you might mean “konsole” (a GUI terminal emulator). Some people will read “console” as implying a real console, such as when you boot to single user mode.
The safest for upgrade is to use a virtual terminal. That is to say, use CTRL-ALT-F1 to get to a command line.
However, for later updates when you are already at 15.2 and just want to update it – that’s probably also safest from a virtual terminal, but I always do that from the GUI and that has never been a problem in Leap. (Once, several years ago, it was a problem in factory. That was back when factory was being tested on openQA, but had not yet been renamed to “Tumbleweed”. From back then, I seem to recall one update that crashed the GUI during a zypper update, and left the system without a functioning zypper to continue. But these days, even Tumbleweed tries to avoid crashing the GUI during an update.
Sorry my bad, this old engine is not working on all cylinders.
yes I meant a GUI terminal(konsole).
instead of ‘update’ I should have said ‘upgrade’,
as in upgrade from 15.1 to 15.2.
So I will use a virtual terminal (CTRL-ALT-F1).
thanks for all the responses.
For safety, I use tmux as my terminal emulator when doing a distro update.
If you use sed to update the repos, I had a problem on all three machines of sed randomly failing to update all the repos correctly and I had to edit a few manually on each machine. Otherwise, everything went smoothly on all three machines.
Maybe you had a problem similar to what is discussed here? https://forums.opensuse.org/showthread.php/540585-The-upgrade-method-from-official-wiki-doesn-t-work-(Leap-15-1-gt-15-2)?p=2939521#post2939521
Not quite the same as sed randomly converted different repos on three different machines; so they would not all have been in the same starting condition.