On 20/04/2019 15.09, Neil Rickert wrote:
On 4/20/19 6:33 AM, Hans-Peter Jansen wrote:
anybody out there with a working caching scheme for zypper updates/upgrades?
I am using what I call "the Carlos method", because it is based on an email message from Carlos in May 2015. Check the archives, where there is a longish discussion on the topic.
:-D
I blogged about how I set this up:
https://nwrickert2.wordpress.com/2015/09/04/sharing-updates-with-opensuse/
:-)
There's a link to the message by Carlos in that blog post. I'm still using that method, and it is working pretty well. Ignore the comments about "NetworkManager" in that post. The problem that they describe has long since been fixed. And note that I am using this over wired connections. It generates a lot of NFS network traffic (home network only), which I prefer to keep off wifi.
One note for your blog: the directory name is also what zypper calls the "alias" of the repo, not its name. "zypper lr --details" prints both. And there is a command that changes it, beside editing the files directly, but see the comment below. Also, you can not do "zypper clean". I think it was that one. I have emptied the cache accidentally more than once one or another way. Like accidentally having one computer without "keep packages" activated. Unfortunately "zypper lr --details" does not print it. Instead: grep keeppackages /etc/zypp/repos.d/*repo or grep "keeppackages=0" /etc/zypp/repos.d/*repo The command "zypper renamerepo" deletes the repo contents, too (Bug 1054328). However, as Per says, why use https? Mirrorbrain doesn't support it. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org