I downloaded OML 6.0 with GNOME for x86_64 from SourceForge and found my computed SHA-256 sum does not match the value in the sha256sum file that I also downloaded.
Filename:
openmandriva-6.0-gnome.x86_64.iso
SHA-256 for the download:
1d1d160f7c2d1b1a1ae2b1ce4c9f33a55d875fe55f1e636fcf8cf25faf886718
Corresponding entry in sha256sum file:
2c561d8c1249536c32c5323398d5867d1276e6a01168209ee833592620a8caf0
Comparing the files at SourceForge, all are dated 2025-04-22 except the GNOME ISO, which is dated 2025-05-03.
Going over to GitHub, I found Product ID 3909, which represents the Rock build for GNOME on x86_64. Downloading the ISO and running sha256sum on it yields a checksum that matches the one in the sha256 file on the above SourceForge page.
Can someone explain why the ISO on SourceForge is not the one from the Github release build, or why the sha256sum file was not updated after 2025-05-03?
Hi.
The ROCK 6.0 GNOMe ISO was released with a small bug caused by the repository management application mistakenly enabling the Cooker repository. This happened when the user attempted to activate repositories disabled by default, such as Extra, Non-Free, or Restricted, or all at once. The application queried the system from the currently available release, such as Rolling, Rock, or Cooker. However, if the response contained an unidentified release (in this case, ROCK instead of Rock), it automatically enabled a fallback to the Cooker repository. This meant that the user could have two repository types enabled incorrectly.
After noticing the bug, it was patched, and the entire ISO was replaced with a new one containing the aforementioned fix.
The SHA-256 was generated on the old ISO, and we apparently forgot to regenerate it with the new, fixed ISO.
We’ll try to address this.
