[Bug 1139915] New: Inconsistent names of Tumbleweed image for Raspberry Pi 1B in repository
http://bugzilla.opensuse.org/show_bug.cgi?id=1139915 Bug ID: 1139915 Summary: Inconsistent names of Tumbleweed image for Raspberry Pi 1B in repository Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv5 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: freek@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- The latest Tumbleweed image for the Rasberry Pi 1B has two names on the web page: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-Current.raw.xz and openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2019.05.17- Snapshot20190607.raw.xz, which is what it should be. The corresponding sha256 files have the same content. The fourth line in these files contains the sha256 checksum followed by the name of the image. However this name is: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2019.05.17-Build1.43.raw So one needs to rename the image file before doing the checksum to this name. Changing the name in this file invalidates the signing of this file. This name should however also have .xz added at the end. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1139915
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1139915
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1139915
http://bugzilla.opensuse.org/show_bug.cgi?id=1139915#c1
--- Comment #1 from Andreas Färber
http://bugzilla.opensuse.org/show_bug.cgi?id=1139915
http://bugzilla.opensuse.org/show_bug.cgi?id=1139915#c2
--- Comment #2 from Freek de Kruijf
It sounds like there are two separate issues here:
1) No .xz: Have you checked that the checksum actually matches the compressed .raw.xz file? Or is it rather the checksum of the extracted .raw file and just missing one for the compressed file?
The sha256 checksum is the checksum of the .raw.xz file and gives a good when the downloaded file, whether it be the one with Current or Snapshot in the name, is renamed to the name in the .sha256 file. Although it is then named .raw, it is still a .raw.xz file.
2) -Current: Those files either get symlink'ed or copied to the generic name, so some additional postprocessing would need to happen to match the new filename.
Apparently the checksum file .sha256 is generated when the file has the extension .raw and is named with Build in its name, although the file in fact is a .raw.xz type file. This .sha256 file is then signed with the Gpg code. The proper procedure is generate the file with Build in it name and give it the right extension raw.xz. Rename that file as it should appear in the repository. Generate the sha256 checksum file with this name and sign it with the Gpg code. Last make the symlinks with Current to these two files. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com