On 2021/09/20 17:16, Simon Lees wrote:
A temporary workaround can be to find a good mirror near you and point to it rather then download.opensuse.org
I can do that manually, but I'm trying to run scripts to cache the latest release. This time, I got stopped on a different file: .*Failure: (url=http://download.opensuse.org/tumbleweed/repo/oss/x86_64/babe-1.2.1.1-1.3.x86...), GET http://download.opensuse.org/tumbleweed/repo/oss/x86_64/babe-1.2.1.1-1.3.x86...: 404 Not Found +1.67 163㎳; 1858 (1.1K/11K) MISS/302 <Ishtar [GET http://download.opensuse.org/tumbleweed/repo/oss/x86_64/babe-1.2.1.1-1.3.x86... - 195.135.221.134 text/html] +0.04 29㎳; 279 (8.3K/9.4K) MISS/301 <Ishtar [GET http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/babe-1... - 149.20.37.36 -] +0.07 62㎳; 5356 (80K/84K) TUNNEL/200 <Ishtar [CONNECT mirrors.edge.kernel.org:443 - 147.75.69.165 -] +0.18 166㎳; 1858 (11K/11K) MISS/302 <Ishtar [GET http://download.opensuse.org/tumbleweed/repo/oss/x86_64/babe-1.2.1.1-1.3.x86... - 195.135.221.134 text/html] +0.03 27㎳; 279 (9.1K/10K) MISS/301 <Ishtar [GET http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/babe-1... - 149.20.37.36 -] [0923_164110.00] 61㎳; 5356 (82K/86K) TUNNEL/200 <Ishtar [CONNECT mirrors.edge.kernel.org:443 - 147.75.69.165 -] +0.22 168㎳; 1858 (8.6K/11K) MISS/302 <Ishtar [GET http://download.opensuse.org/tumbleweed/repo/oss/x86_64/babe-1.2.1.1-1.3.x86... - 195.135.221.134 text/html] +0.03 26㎳; 279 (9.1K/10K) MISS/301 <Ishtar [GET http://sfo-korg-mirror.kernel.org/opensuse/tumbleweed/repo/oss/x86_64/babe-1... - 149.20.37.36 -] It looks like it was referred to 5-6 caches before it gave up as unable to be found. I found a possible temporary workaround -- if regular http fetch fails, maybe try https. Not guaranteed to work, but at least another programatic thing I can try. Problem with this is that it changes often, but generally causes a new download to fail because the script writer believes that If they are told the file is on a mirror -- then it should be there. Otherwise, it should try to refetch from the original. Someone said that they though that's what happened but only with an http fetch. Is there a reason why something like that would be limited to https?