I decided to have a go with the new zypper features. Whatever I did has resulted in blazing fast downloads , but I’d like to check to see if the steps I took were appropriate and/or necessary before repeating them on other Tumbleweed installations.
1) I edited /etc/zypp/zypp.conf to change:
# download.max_concurrent_connections = 5
to
download.max_concurrent_connections = 8
Would I still have had concurrent connections without removing the hash mark from this line?
2) I created a bash script to dup to new snapshots:
Yes. The text above this setting in zypp.conf describes that the standard setting is 5 concurrent connections. Only when you want to use another number, you have to uncomment (remove the hash) this line.
If you use the openSUSE-repos-Tumbleweed package (which provides a repo service), you don’t need to set any environment variables, as ZYPP_PCK_PRELOAD=1 and mediahandler=curl2 is enabled by default.
Users of openSUSE-repos on Tumblweed gained mediahandler=curl2 as part of the repository urls as well as preset ZYPP_PCK_PRELOAD=1 via /etc/profile.d/opensuse_repos.sh with the latest openSUSE-repos update.
Also have a look at the Youtube video linked in the official announcement, which explains exactly that.
You need to have the package openSUSE-repos-Tumbleweed installed…as demonstrated in the video and written in the announcement.
And yes, you need an properly upgraded system or you may have not recieved/installed the updates which contain the features yet.
windeath:/home/dart # zypper in openSUSE-repos-Tumbleweed
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
openSUSE-repos-Tumbleweed
1 new package to install.
Package download size: 18.5 KiB
Package install size change:
| 1.2 KiB required by packages that will be installed
1.2 KiB | - 0 B released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):
Preloading: openSUSE-repos-Tumbleweed-20250324.7d1bc96-1.1.x86_64.rpm
Preloading: openSUSE-repos-Tumbleweed-20250324.7d1bc96-1.1.x86_64.rpm [done]
Preload finished. [success (18.5 KiB/s) ] ....................................................[done]
Retrieving: openSUSE-repos-Tumbleweed-20250324.7d1bc96-1.1.x86_64 (Main Repository (OSS))
(1/1), 18.5 KiB
Checking for file conflicts: .................................................................[done]
Content of download.opensuse.org-oss.repo will be newly managed by zypp-services.
Storing old copy as /etc/zypp/repos.d/download.opensuse.org-oss.repo.rpmsave
Content of download.opensuse.org-non-oss.repo will be newly managed by zypp-services.
Storing old copy as /etc/zypp/repos.d/download.opensuse.org-non-oss.repo.rpmsave
Content of download.opensuse.org-tumbleweed.repo will be newly managed by zypp-services.
Storing old copy as /etc/zypp/repos.d/download.opensuse.org-tumbleweed.repo.rpmsave
(1/1) Installing: openSUSE-repos-Tumbleweed-20250324.7d1bc96-1.1.x86_64 ......................[done]
%posttrans(openSUSE-repos-Tumbleweed-20250324.7d1bc96-1.1.x86_64) script output:
Adding service 'openSUSE'...
Service 'openSUSE' has been successfully added.
URI : dir:/usr/share/zypp/local/service/openSUSE
Enabled : Yes
Autorefresh : Yes
Refreshing service 'openSUSE'.
All services have been refreshed.
Running post-transaction scripts .............................................................[done]
If you install openSUSE-repos-Tumbleweed-NVIDIA it will automatically pull in openSUSE-repos-Tumbleweed. But not vice versa. If you do a fresh installation of Tumbleweed and the system detects Nvidia hardware, openSUSE-repos-Tumbleweed-NVIDIA gets installed automatically as a recommend.
On grown systems which have as example new-recommends disabled, package isntallation must be done manually.
The openSUSE-repos-xxxx packages already exist for some time and have many advantages for new users. But only Nvidia owners get the packages installed automatically to make the overall system experience better (correct drivers).
There are different ways to keep a Tumbleweed system upgraded. Everybody is free to choose the method which he/she wants. But the majority of experienced system administrators prefer to keep control over the upgrade process and their systems. This includes watching the factory mailing list, checking the list of the to be upgraded packages and make system adjustements if needed. Shifting the upgrade process of Tumbleweed into the background without possibility for interactions, is kind of loosing the control over your system.
But as noted above…everybody is free to maintain (or not) his/her system as liked…
, but I’d like to check to see if the steps I took were appropriate and/or necessary before repeating them on other Tumbleweed installations.
