On 25/06/2020 05.00, Carlos E. R. wrote:
On 25/06/2020 04.45, Darryl Gregorash wrote:
On 2020-06-24 8:19 p.m., David C. Rankin wrote:
On 06/24/2020 04:48 PM, Felix Miata wrote:
...
I'm making decent progress in getting this sorted out; thanks to everyone who has contributed so far.
For Carlos: read paragraph 4. of the first url you posted: https://en.opensuse.org/SDB:System_upgrade You'll find it very enlightening re: zypper --releasever=xxxx dup :D
Ok, I'll read it tomorrow - 5 AM here now :-) I'm just having a quick look before hibernating.
I almost forgot, so I just read it :-) Yes, it is interesting. Still, I may keep using the manual mode of editing the repositories manually, because I take the chance to also edit names for consistency, disable some repos I really to not want to keep during the upgrade, whatever. I noticed this warning: Warning: It is strongly recommended that you run the upgrade outside the X-window graphical mode. Thus it is recommended you run the command from either runlevel 3 (text + network), or a virtual console. Unfortunately many times the WIFI connection is managed/available only in runlevel 5, so a virtual text console may be best while staying logged into the graphical console behind the scenes. People had their X session stopped/crashed during the upgrade, causing the upgrade to abort, which in turn left the system in an inconsistent state. To change to runlevel 3, see SDB:Switch_runlevel. To remain in runlevel 5, but use a "virtual console", type control-alt-F1 (as an example). We should add instructions to recover the network in text mode, using nmcli or nmtui. If the package is not installed by default, install it prior to the dup. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)