Andrei Borzenkov wrote:
The problem is that end result depends on client software (and client options) and there is no configuration that would work with any combination of links and clients.
Yeah, that is also roughly the conclusion I have been getting to. Using my naive combination of wget and sha256sum, I was unable to reproduce the issue.
wget ... follows redirects but stores files under original name, so [snip] wget --trust-server-names ... will store file under redirected name, so linking checksum will work. Of course it fails now.
Interesting, I was not aware of that option.
Both firefox and chromium store file under redirected name when downloading from download.o.o; of course when downloading from something like https://rsync.opensuse.org/ there is no redirect and so filename in .sha256 would not match.
Yup. I was also going to ask the OP why he was (or appeared to be) using a mirror directly instead of going via download.o.o
Using links simplifies download frontend (get.o.o) which may have static configuration pointing at ...-Media.iso which is magically resolved to the latest image. But it is never ending source of confusion as far as I remember.
The topic certainly pops up every now and then. What if we simply told people to make sure they do their checking on : <filename>.iso <filename>.iso.sha256 What I wonder is if there is some gui or some wrapper that does this checking for them. -- Per Jessen, Zürich (20.9°C) Member, openSUSE Heroes