Hello Carlos. thanks for the reply... On Fri, 19 Jul 2019 11:47:53 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 16/07/2019 12.17, Ralph wrote:
[Leap 15.0, xfce]
A week or so ago I started to upgrade a Leap 15.0 system to 15.1 from DVD but yast installer could not find my wifi dongle. No functioning ethernet wire on this machine. The kernel in 15.1 does not have the drivers for the dongle (nor does 15; I use a kernel from stable which does have the module).
In that situation you would have to do a DVD upgrade without network, which will not cover all the packages, nor those that come from extra repos and will be replaced by versions in OSS, or left alone. And a lot of questions.
An alternative is zypper dup with download in advance.
I instead bought a cheap Leap-supported ethernet board to replace the lightning-blown ethernet port (lightning striking a tree very near to the pole carrying the cable wire sent a sympathetic charge through the cable wire, burning out the 'protecting' ups the coax was threaded thru, the cable modem, and the motherboard ethernet ports of two machines, but apparently the rest of the two motherboards survived fine.)
Since I am going to upgrade to bigger nvme hardware on this machine soon, and thus will have to do a fresh install on the new hardware anyway, I just simply aborted the current really unnecessary upgrade through the normal yast installer buttons.
At which point in the process did you abort?
At the point the install asked me to define the network if I want to enable online repositories. This is very early in the process.
Today I noticed that the repositories were all messed up. The extra repositories which I had elected to keep and manually edited from 15.0 to 15.1 during the preliminary upgrade process were still there, now correctly returned to their 15.0 versions, but the standard opensuse repositories were completely gone (oss, non-oss, updates, the dvd). No 15.0 versions nor 15.1 versions.
I've manually reinstalled the standard 15.0 repositories but it seems to me this might be a bug in yast installer if it doesn't automatically completely revert a properly aborted upgrade process to its original configuration. Yes, bug? Or is this simply a case of "don't do that (abort an upgrade) and you won't ever have this problem"?
If the process had really started, what it changed is unpredictable to us.
But up to a point you can abort with nothing written.
That was the gist of my original message. Nothing should have been 'written' permanently at the point I aborted the install. Or at least that is what I always assumed: until you get the 'point-of-no-return' message from the installer you can abort without any changes being made. So my question if it is a bug or just a 'don't do that' (like being able to stand on the tracks in front of a moving train is not a bug, but just a 'don't do that' kind of thing ;-) Thanks. Ralph -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org