Concerning ticket 96161.
The issue is not resolved for other users (at least partially).
I resolved the issue for myself.
This is not a support type question as you suggest.
This is me pointing out one still existing error and corrupted files in the OpenSUSE foodchain on the
day of my download. The corruption may still exist ...
1) The following is YOUR ERROR. The internal file name of
https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256
does not match the name of the file it is supposed to verify. That is an error on your part. Users following your
directions for file verification will not get a result. (view the sha256 it with a text editor)
2) Also. There may be a file corruption problem. Evidence indicates it was in the source file and not on my end.
On the day that I reported this issue, I downloaded the dvd openSUSE 15.3 iso multiple times through the links on
https://get.opensuse.org/leap#download
After the first download using your link was unbootable, I switched to using wget to bypass any browser issue.
In wget I used the opensuse.org link:
#https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso
Still the dvd iso would not boot properly. Each of the multiple times the file downloaded I received EXACTLY
the same file as far as I could determine ... indicating it was probably not a transmission error.
So I immediately went to the Clarkson mirror for the files. (Note Clarkson does not have the "-current-" file name provided by your symbolic link. I am not sure why you need that extra complexity. You could put a similiar link for the sha256 file containing the altered name. The link certainly inserts a point of inadvertant error or file insertion.)
I used:
#https://mirror.clarkson.edu/opensuse/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64.iso
#https://mirror.clarkson.edu/opensuse/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64.iso.sha256
#https://mirror.clarkson.edu/opensuse/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64.iso.sha256.asc
The files passed the verifcation and booted properly. The Clarkson iso was different from the -current-.iso provided by opensuse.org.
The sha256 internal file name matches the file to be checked.
It seems likely that
#https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso
had a corrupted file ... but not at Clarkson.
Overall, your questions sound more like support-type questions, which I think are best addressed to one of our support channels - mailing lists or > forums or irc. I would suggest you add a little more information than "does not function" or "is useless".
"Does not function" pretty well covers it. I was using Ventoy --- which has never given me a problems and was not the problem in this case as the proper files from Clarkson demonstrated.
The "Current" filenames are all symlinks for convenience.
Your convenience ... not your users. I question how convenient it really is.
If you are going to continue the practice ... put instructions on the page
https://en.opensuse.org/SDB:Download_help#Checksums
instructing users to edit the sha256 file ... which seems counterintutive to me.
And will possibly make you look a bit foolish.
For me it generated confusion as to possible different releases (one being current and the other not so much current) ... but the sha256 used from Clarkson was the same as the one provided by opensuse.org, albeit with a different name. At least that is my recollection.
None of these is an issue a forum could fix.
Best wishes.
Dan Latenser - Nebraskan