Critical use of machine time to run TW zypper dup -l tsunami distro upgrades
"I don't know what this error exactly means. Me, I would download the filesystem-84.87-7.1.x86_64 rpm somewhere (manually) (it may be cached locally), and install it (rather update) manually with the rpm command, which will be more verbose. It worked for me not long ago with another problem I had. -- Cheers / Saludos, Carlos E. R." Folks: New to this list, I guess I subscribed a month or so back when TW had the previous "rolling" upgrades of 2434 packages . . . followed by another 434 a day later, and then again a bit after that. I posted a thread on the forum complaining about this **recent** development in TW involving these large numbers of packages that take up machine/power time to do . . . and now then a month or so later, again? I believe I've been running TW since 2016 . . . as an "end-user" kicking around in linux since '07 . . . w/o formal training. There weren't these huge numbers of packages to mess with in TW until, when, the last year or so?? How did TW previously survive without them??? "Rolling" distro involves a regular upgrading of a regular number of packages . . . TW has become a "dump" distro with these huge data dumps that we either process or now the number accrues and "gather's interest"?? I saw someone on the list yesterday mentioned "5900" packages . . . so the numbers are just going up. From my thread Karl Mistelberger clued me in to setting up a script to run "dupa" . . . but, the issue there is the machine has to be running the distro until the install is complete, which is "hidden." I run about 8 distros of linux on a '12 Mac Pro . . . I'm an actual "tumbleweed" when it comes to distros. TW is the only distro that uses these large "tsunami" style package upgrades. Deb Sid keeps it to around 100 per week . . . Manjaro as well . . . I think the other day Manjaro hit me with a massive "400" packages to process . . . . I'm posting here because I like TW, I've liked it since '16 . . . but today in one of my Gecko rolling installs on a newer Sys76 laptop from '20 . . . 10th gen i7 cpu . . . NVMe drive . . . her system's zypper request was for "1655" packages (she seems to reduce the number from TW) . . . on a 500MB FIOS connection it took over 30 minutes to download the packages . . . with one "curl error" 20 minutes in . . . hit "r" and it just refired to finish and then 16 minutes to install them. And that machine is generally very fast. It seems like the SUSE server can't handle the sheer volume of packages that are needed by TW users to stay current??? Monday is my TW day . . . and it's running on a Xeon cpu i7 installing into an HDD . . . I'm assuming that the package request will be higher than the Gecko . . . and the time to run zypper will likely be more than double . . . making it a "bridge too far" via ye olde zyppering; the previous 2434 took several hours to process with all of the "curl errors" and re-trying. The only thing that makes sense to stay in the TW groove is as Carlos mentioned . . . download the latest .iso file and run a "fresh" install to get beyond these 5K package upgrade tsunami's . . . which brings its own set of hurdles. This was the written request for TW to return to the days of, when 2021 when it was a "rolling" distro, the distro that was there to serve us, rather than we it . . . . : - 0 F
Am Sonntag, 4. September 2022, 01:28:51 CEST schrieb Fritz Hudnut:
"I don't know what this error exactly means. Me, I would download the filesystem-84.87-7.1.x86_64 rpm somewhere (manually) (it may be cached locally), and install it (rather update) manually with the rpm command, which will be more verbose.
It worked for me not long ago with another problem I had.
Please check my thread "Critcal crash after Tumbleweed snapshot 20220826 update of "filesystem" package" And Bug Report: https://bugzilla.opensuse.org/show_bug.cgi?id=1202840 Thanks Ulf
On 2022-09-04 15:01, ub22@gmx.net wrote:
Am Sonntag, 4. September 2022, 01:28:51 CEST schrieb Fritz Hudnut:
"I don't know what this error exactly means. Me, I would download the filesystem-84.87-7.1.x86_64 rpm somewhere (manually) (it may be cached locally), and install it (rather update) manually with the rpm command, which will be more verbose.
It worked for me not long ago with another problem I had.
Please check my thread "Critcal crash after Tumbleweed snapshot 20220826 update of "filesystem" package"
No, Fritz Hudnut was not replying to that email. He tried a thread hijack. The actual post was below that section. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
participants (3)
-
Carlos E. R.
-
Fritz Hudnut
-
ub22@gmx.net