Am Sonntag, 30. August 2020, 15:37:16 CEST schrieb Berthold HÃ¶llmann:
Thorsten Kukuk <kukuk(a)suse.de> writes:
On Sat, Aug 29, Andrei Borzenkov wrote:
29.08.2020 23:05, Jan Engelhardt Ð¿Ð¸ÑÐµÑ:
On Saturday 2020-08-29 20:23, Adam Mizerski
> Error "File '...' not found on medium" usually means you need to
> "zypper update". If that doesn't help, then wait a bit. If that
Not update but refresh.
That normally should happen automatically on every zypper operation (at
least when invoked by root).
No, zypper caches the data for a short time. If the server get's
updated during this time (or while zypper dup is running), this
"not found on medium" errors will happen.
did the trick.
I find the caching strategy quite annoying.
Make sure that all repos have autorefresh enabled.
This doesn't seem to be the default for zypper ar, which should IMO be changed.
Not sure whether there's already a bug report about that.
Quite often in a larger
update via "dup" packages are missing and the update process has to be
restarted, which is a hassle, when you leave the update process alone
and after hours nothing is achieved. Would it be possible to leave
deleted packages on the servers
AFAIK that's what happens already, the file only fails to download if all
available mirrors deleted it.
for lets say 2 hours to ensure the
update process does not fail?
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org