So, in the last week my various opensuse installs have had large upgrades of approx 1500 packages, run in GUI console via zypper dup -l and that more or less went “OK.” Today I cycled back to my main channel OpenSUSE TW install and it showed “2174 packages” . . . so I blithely ran them via sudo zypper dup -l . . . and around package 564 it came to a halt for "failing to download wayland xxxxxx after 5 attempts . . . " . . . so I hit “ignore” and it brought a “You have chosen to ignore this critical package, this may cause your whole system to blow up . . . .”??? words to that effect. It found two other packages that it tried to download 5 times but failed to do, but continued to run through the process after I also hit “ignore” . . . . I went and ate breakfast.
When I came back the cursor was back and it said in red, “Installation completed with errors.” So, whereas in the ubuntu land they have “apt -f install” to run to repair potential problems, so far zypper doesn’t seem to be able to do that, so I ran zypper ref && dup -l again . . . and it still showed “2174 packages to install”??? So I rebooted, thinking that the upgrades just weren’t “registering” . . . and then I decided, well let’s do this in a TTY . . . so I ran the zypper there and this time it showed most of the packages were “in cache” but now there were 2189 packages to install . . . . This time it took maybe a full half an hour to install all of the packages, and in that process none of those three packages that had previously failed to download, and were ignored, nothing showed up asking me to abort, retry, or ignore . . . and even though there was a bunch of “dracut” at the end, no errors were reported in the upgrade???
I rebooted back into TW and I’ve typed a few posts here and looking up at the toolbar update notifier is asking me if I want to “Install updates”???
I’m just reporting what happened with this large upgrade, zypper saying “install completed” but it actually wasn’t . . . . I know from my short lifespan with Siduction that they wanted ALL upgrades run as “su” and in a TTY . . . but up until now I haven’t had any issues with TW upgrades run in GUI console, and there have been a few “failure to download” but “ignore” seemed to allow install to move forward and complete without “pretending we did a good job” . . . ??? What’s up with dat??
Hi
Normally that happens with incomplete mirrors being used, yes glibc was updated so a big update I saw it the other week as well, just run zypper dup a few times until all packages are cached… it’s been a busy time in Tumbleweed land… might also be the python 3.6 dropping of numpy as well if your using that at all… We do have Forum notifications for snapshots now, but still pays to keep an eye on the Factory Mailing List…
Thanks for the reply . . . looks like zypper might be caught up . . . it found two more packages . . . .
“Factory Mailing list”??? I guess I’m not on that list . . . for the most part I’ve been “issue free” in TW for quite awhile . . . but Gecko has been “finicky” . . . . This one was the “el reverso” . . . .
Ah, OK, thanks for the link . . . yes, I see that #5 would have warned me to, “brace for impact” . . . . I mean seeing the “2174 packages” was sort of giving me the idea that there was a “balloon payment” coming due . . . . But, forewarned is forearmed, etc.
I’ll check into joining the list . . . to keep up to date on the tumbling weed . . . .
No, not “that bad” . . . but, not exactly “seamless” for a rolling system upgrade either. And based upon the Factory list-serve “discussion” it was a bit of a mess . . . as one gent put it, “to upgrade one package” . . . 2178 other packages were “needed”???
Arguments are moot at this point, but it was both time and energy consuming, for what I thought was a “major” system upgrade in TW . . . akin to jumping up in version number . . . but seemingly just a “package upgrade”??? : - ))))
It’s OK, I’m a “snowflake” . . . . My question revolved around why would zypper declare “installation completed” . . . when in fact it wasn’t, packages had just been cached, etc, and nothing had been installed???
I’m not a zypper specialist, but “installation completed with errors” should mean that the process got to the end (i.e. was not aborted and did not crash) but there were errors, and apparently some extensive ones.
After downloading the packages to cache, zypper performs a “checking for conflicts” and if a conflicting package is found, that package is not installed.
Due to the nature of that big upgrade in which almost everything depended on the new glibc and you chose to ignore three apparently critical packages, I guess that the conflicts were so extensive that nothing was installed in the end.
You should be able to find the whole story reading /var/log/zypp/history
In my case some 500 packages were installed before the user session crashed (and the zypper process with it), so I didn’t see any “installation completed”…
OK, well since my user session didn’t crash I do count myself as one “lucky” snowflake . . . zypper just provided me with “misleading” data . . . . But considering that zypper gave me a long “conversation” about my decision to “ignore” those three packages . . . I don’t know why zypper couldn’t tell me at the end, “packages have been downloaded, but couldn’t be installed at this time and have been cached, please try again in a minute.” ???
And, if it was my selection of “ignore” that messed everything up, what happened to those three packages when I ran the zypper in a TTY?? for the second attempt at it It didn’t ask me about them again and there were no “conflicts or errors” reported in that process??
I know that from past experience in the recent months that packages get flagged and if I pick “abort” the update session is cancelled w/o hesitation. Yesterday zypper said “We tried 5 times to download this package” . . . so pointless to choose “retry” . . . therefore my only option out of the three choices provided was “ignore” . . . . Unless I had had some knowledge that I could lock the packages or something else that would allow the upgrading to move forward . . . without adding some tweak in the mix. But, I had no plan, so I tried to ignore my way out of it . . . as has been very popular in the last year or so.
I saw it the other week as well, just run zypper dup a few times until all packages are cached… it’s been a busy time in Tumbleweed land… might also be the python 3.6 dropping of numpy as well if your using that at all… We do have Forum notifications for snapshots now, but still pays to keep an eye on the Factory Mailing List…