On 2021/09/23 08:21, Marco Calistri wrote:
As per the subject. Today I get over 3000 packages to update and I had to frequently hit the "R" during zypper dup, in order to force curl to download the package again.
I don't know if you are hitting the same or a related problem, I'm trying script and browser downloads and getting 404's on some packages due to sites trying to force https and then not forwarding if they don't have the package. Sent this to the TW list a bit ago: ---- problem in kernel mirrors (et al) I Asked for: 389-ds-2.0.10~git0.21dd2802c-1.1.x86_64.rpm from: http:download.opensuse.org Got Miss/302 (redirect) (this from my squid log) +0.17 164㎳; 2002 (12K/12K) MISS/302 <Ishtar [GET http://download.opensuse.org/tumbleweed/repo/oss/x86_64/389-ds-2.0.10~git0.2... - 195.135.221.134 text/html] to sfo-korg-mirror gave 301, "moved permanently": +0.03 19㎳; 295 (13K/15K) MISS/301 <Ishtar [GET http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/389-ds... - 149.20.37.36 -] and that forwarded me to https on mirrors.edge.k.o: https://mirrors.edge.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/389-ds-2... THAT HAD NO COPY and returned 404 (instead of forwarding) The 404 in my squidlog, BTW, was hidden in the https/tunnel which is one reason this is a pain to track down. I caught it in my browser which ended up on their 404 page: (Sorry, we cannot find your kernels) the 301 (permanently moving) kills forwarding to the next mirror if it isn't present (another variable, if it is present, will work, if not, won't), but sites trying to force upgrades to https kill the forwarding mechanism.