Alrighty . . . don’t have time to dig into “dup” this morning . . . but, today is Gecko TW MATE day . . . . From two days ago where Gecko Plasma TW showed 1776 packages that took almost two hours to install . . . MATE showed 1715 and ran the install in 46 minutes!!!
Same machine . . . essentially 3 “box stock” installations of the SUSE system . . . wildly variable package upgrades and wildly variable install times . . . using “zypper dup -l” . . . .
And, with today’s upgrade . . . no 5 minutes to “purge old kernels” on the reboot . . . .
:~> ldd --version
ldd (GNU libc) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
1:~> gcc --version
bash: gcc: command not found
Hi
So it would just be branding/patterns on the new install by the looks… as in no specific gecko repo. Never used/needed to set priorities, vendor sticky-ness is now in play, switch and stay switched.
Well, those are vastly different numbers from my recent “2525 packages to upgrade” in TW, and the 1700 in Gecko . . . vastly different times to run, etc. Perhaps you are booting TW every day, or it’s running 24/7 so whenever there are packages, your “dup” app is running them through on yr Ryzen cpu? Whereas I’m booting TW essentially one time a week for a couple of hours . . . running my old Quad-core “Ivybridge” i7 from '12???
Today was LM day, had a few packages to upgrade . . . went thru fast, then rebooted to Deb Bookworm . . . apt showed “55 packages” ran thru in a couple of minutes.
Today is “Lubuntu Kinetic” day . . . in the first “major” upgrade in the system since moving from previous “jammy” iteration . . . “212 packages” in 291MB of data including “gcc-11” and “gcc-12” . . . 5 minutes to dl and install . . . .
He’s clearly argumentative and does not even understand the basics of what rebuilding the entire system with a new compiler vs simply installing a different compiler version means.
I am indeed trying to “make an argument” . . . and I would offer that argument is “falling on deaf ears” . . . but that doesn’t mean my argument is invalid, just unheard and shuttled off to Chitchat.
As I have posted in the thread a few times, I’m not “new” to SUSE, installing TW in '16 . . . and at that time “rolling” didn’t have these huugggeee package upgrades, but then in the last year plus, suddenly there they were. So, something “changed” and as a generic end user of the product I’m reporting dissatisfaction with that approach.
And, in my own thread as the OP, I’m posting my comparative “evidence” that the other 8 or so systems that I have are comparatively lower maintenance. I’m not a “crank” . . . but the two hour upgrade and machine shutting down in the middle of it . . . made me cranky . . . very cranky.
The great joy of linux is that there are options . . . but as a fairly “long” time user of TW I feel it is important to not just “put a happy face” on everything that is decided in TW. Obviously SUSE also offers many distros that are even named “experimental” . . . TW is offered on the web site right next to Leap . . . indicating it is for “public consumption” . . . . Does TW need a complete system wipe and total package re-install to maintain “freshness”???
As I posted, not even Sid seems to require these huge and time consuming upgrades . . . I would hope the devs could at least “hear” the argument . . . ???
Hi
Many things have changed of the last few years as the likes of gcc has matured that the Tumbleweed maintainers wanted to move to this.
You should look at using either a tty and multi-user target or run screen before these big updates to avoid your issues of the desktop disappearing.
Not sure of your locale, but not seen an issue with big downloads and installs with either download or mirrorcache-us (24 threads help on install…). I have multiple X86_64/aarch64 Leap and SLE systems here and updates are regular and small…
Perhaps ask on the other distribution forums a) when they will move to the later gcc and glibc, b) ask what the update will be size-wise if they did?
It does tend to fall on deaf ears so to speak since this is an User peer-to-peer technical help oriented forum
Again, see SDB:Download help - openSUSE Wiki Tumbleweed is targeted at ‘Developers’, ‘Contributors’ (thats’ me) and Enthusiasts. Leap is targeted at Sysadmins, Enterprise Developers, and “Regular” Desktop Users.
Zyppers 1 & 2 I didn’t time. Too much depends on internet connection speed.
3rd zypper was 1446 to upgrade, 17 new, which took 6m10s real, 2m33s user, 1m29s sys.
4th zypper was 11 to upgrade, 9 to downgrade, 1 new, 17 to remove, which took 0m19s real, 0m09s user, 0m03s sys.
Separate installation of newer kernel took 0m30s real, 0m25s user, 0m05s sys.
It seems eminently reasonable with an old 2 core CPU to process around 1500 packages in 7-12 minutes, regardless the reasons for the package counts.
Only when comparing comparables. I’ve been caching 64bit TW rpms on LAN server, and binding the cache to /var/cache/zypp/packages/. Thus, few files are being downloaded on each next of my 30 or so 64bit TWs, making time spent downloading lower than typical for TW users.
This too is limited to SATA 3.0, along with single core 32bit HT CPU, yet 1396 zypper up transactions consumed a modest 16m31s real, 5m15s user, 3m32s sys. Following zypper dup did 38 transactions in 2m00s real, 0m20s user, 0m10s sys.
