Hello, On Sun, 01 Dec 2019, Anton Aylward wrote:
On 01/12/2019 19:51, David Haller wrote:
(and if in doubt and you're sure, use '--nodeps --force' as zypp does)...
I suspect that this "--force" would get around the 42.3 > 15.0 revision number issue, but it makes me very nervous. How many more of these?
Just until 'zypper dup --dry-run' works. You successfully borked your system by using the wrong combination of 'zypper up' and repo config (or something amounting to the same thing), so don't be a wuss, get zypper running again via the process I described in that long mail (using rpm directly; if needed from a rescue system). Then fix your /etc/zypp/repos.d/*! ALL OF It! Prune it to the single plain 'oss' repo if neccesssary[3] (just move the rest to another (versioned) subdir of /etc/zypp/ or /root/ or whereever). I just messed up/forgot[1][2] about the '-ivh' issue, but '-Uvh', '-Uvh --oldpackage', or '-Uvh --nodeps --force' (try in that order) may be required. If you're sure you've got the right packages, grab the big hammer and use the '--force'. And add '--nodeps' if you're sure. No need to be scared about it, you can't break it much more than it already is. Basically, you'll supplant your (broken) base install by a hopefully sane and working one. Oh, pro-Tip: download an install ISO from SUSE! That contains a (sane) set of tools like zypper (and all deps needed). Loop-mount that ISO (just like that or from a rescue system, say, to /mnt/DLS/ or /mnt/ISO/ or wherever), and then apply my strategy using the packages from that mountpoint. And, in your case, following the whole shebang up with a 'zypper dup' once zypper works again (repeatedly, until it tells you there's nothing to do), it should all be clear without leftovers... HTH, -dnh PS: You'll be happy to have fixed your system "from the ground up" [1] it's been a while, ISTR I migrated from 11.2 32bit to 11.4 64bit, 10 years ago? Anyway, details get lost in memory corruption... [2] the principle, i.e. fix it via rpm (via rescue system) is still valid. And I put that to the test more recently (Gen)too ;) [3] I've always kept other repos live while updating. Well, those where the new version was available which I checked _BEFORE_ ... The rest got disabled/moved away. There's pros and cons about that during the 'zypper dup', and I understand that it's recommended to disable all other repos but 'oss'. Going through each repo and checking that each repo is live and well for the to-be-dup-ed-to version is, well, a bit tedious and not "end-user-compatible" or something like that... --
What is it with word processors anyway? "Well, you've seen what food processors do to food...." -- Steve Willoughby and Alan Shutko quoting (IHRC) David Carlisle in asr
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org