Project

General

Profile

Actions

tickets #96161

closed

Problem with sha256 file for Leap 15.3 --- internal file name does not match distribution iso name. Checksum?

Added by latenser@protonmail.com over 2 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2021-07-28
Due date:
% Done:

100%

Estimated time:

Description

Using https://get.opensuse.org/leap#download

Downloaded these via wget.

https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso
https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256.asc
https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256

Internal file name of sha256 does not match Leap ____Current.iso file name.

Plus, for me the *Current.iso file does not function.
(despite multiple downloads).
Live XFCE does seem okay ... but useless.

Renaming the distribution iso file to match sha256 does not give a checksum verification.

So ....
perhaps you could clarify the situation.

Not an auspicious start (coming from a fellow that started with Slackware in 1992 ...coming from HP Unix ... and Xenix in 1984.)

Connundrum:
Slackware is a mess
Redhat is a mess (Centos etc.) No reliable open source distribution.
Oracle has smoothed out Redhat ... but GNOME! For the brain dead. Crippleware!
Ubuntu 20.04 cannot even provide a functional vim (VIM 8.2 is a mess ... so do not switch.)
... let alone a distribution without regular predictable problems
.... and a distribution that installs a miniscule swap file by default.
.... and a faulty encrypted partition installation

FreeBSD ... the best Engineering software has not been ported.

So ... you are it ... perhaps.

Hopefull you live up to the claim: "The Maker's" Linux.

As I said ... not an auspicious start.

Thank you,
Dan Latenser

Actions #1

Updated by pjessen over 2 years ago

  • Subject changed from Problem with ___sha256 file for Leap 15.3 --- internal file name does not match distribution iso name. Checksum? to Problem with sha256 file for Leap 15.3 --- internal file name does not match distribution iso name. Checksum?
  • Private changed from Yes to No

latenser@protonmail.com wrote:

Using https://get.opensuse.org/leap#download

Downloaded these via wget.

https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso
https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256.asc
https://download.opensuse.org/distribution/leap/15.3/iso/openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256

Internal file name of sha256 does not match Leap Current.iso file name.

The "Current" filenames are all symlinks for convenience.

Plus, for me the *Current.iso file does not function.
(despite multiple downloads).
Live XFCE does seem okay ... but useless.

Renaming the distribution iso file to match sha256 does not give a checksum verification.

Unable to reproduce - I have just downloaded "openSUSE-Leap-15.3-DVD-x86_64-Current.iso", then I edited the sha256 file to update the filename:

per@office25:~> sha256sum -c openSUSE-Leap-15.3-DVD-x86_64-Current.iso.sha256
openSUSE-Leap-15.3-DVD-x86_64-Current.iso: OK

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".
(admin@opensuse.org is linked to a ticketing system for infrastructure issues).

Actions #2

Updated by pjessen over 2 years ago

  • Status changed from New to Resolved
  • Assignee set to pjessen
  • % Done changed from 0 to 100
Actions #3

Updated by latenser@protonmail.com over 2 years ago

  • Status changed from Resolved to New

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

Actions #4

Updated by pjessen over 2 years ago

  • Status changed from New to Rejected

latenser@protonmail.com wrote:

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)

I suggest you open a bugzilla for that issue - https://bugzilla.opensuse.org. I think it makes a lot of sense for those convenience filenames / links to be listed too, but I have no control over the generation. My personal(!) view is that anyone who is using the ISO and is keen on verifying it, will also know how to work around this minor issue.

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.

Given the complete lack of diagnostic information, I suggest this is still a support issue.

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.

Clarkson only copies what we provide.

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.

Are you trolling? How is anyone supposed to debug anything based on that information?

Actions

Also available in: Atom PDF