Instead of commenting in your usual way, you could have read up. The mirrors provide matching sets of ISOs and sha256 indepentend of using chrome or curl or whatever. It’s easy to see and understand:
For my first download, I used “wget”, and ended up with the file “openSUSE-Leap-15.4-CR-DVD-x86_64-Media.iso”.
For my second download, I used “aria2c” (which used the meta2 download method) and ended up with the file “openSUSE-Leap-15.4-CR-DVD-x86_64-Build31.329-Media.iso”. So the final file name does indeed depend on how it is downloaded. If you download with a browser, it will depend on the browser and perhaps on browser extensions.
Yes. And if you download “matching” set of openSUSE-Leap-15.4-CR-DVD-x86_64-Media.iso and corresponding sha256 they will not match.
The problem is not what is available on download, but that the official site to download openSUSE gets it wrong. And if you say “you must download different ISO under different name” the next obvious question will be “how do I know it is the same ISO? It is not what official site tells me to download”.
I was pointing out a way to circumvent the problem with the official donload page. If you access the mirror directly (no matter with a browser or whatever) you will see and find matching ISO/sha256 pairs as shown in this comment
And surprisingly the sha256sum -c will pass “OK” on this pairs…
And this way is also “official” as the link to the mirror is also presented on the advanced download page. So you download an official ISO and sha256 from an official openSUSE download server…
I only wanted to show a way for some users who have some basic knowledge how to access a mirror…
Yes, but it doesn’t actually circumvent the problem, depending on how you download.
I normally use “aria2c” for downloading, and I can run into the problem with that.
This uses the meta download. The meta-file for the download includes a list of mirrors and checksums for segment. This allows parallel downloading from various mirrors, which can speed things up. And the checksums improve the reliability.
But they do not prepare two versions of the meta file. So you finish up with the file name that the meta file is based on.
