Project

General

Profile

Actions

Bug #58615

closed

build failing due to liburing sha256 mismatch

Added by Samuel Just about 1 year ago. Updated 7 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

2023-01-30 20:13:19 URL:https://codeload.github.com/axboe/liburing/tar.gz/refs/tags/liburing-0.7 [111169/111169] -> "liburing-0.7.tar.gz" [1]
Error: failed to download liburing-0.7.tar.gz: SHA256 mismatch.
2023-01-30 20:13:19 URL:https://git.kernel.dk/cgit/liburing/snapshot/liburing-0.7.tar.gz [111169] -> "liburing-0.7.tar.gz" [1]
Error: failed to download liburing-0.7.tar.gz: SHA256 mismatch.
Error: failed to download liburing-0.7.tar.gz.

These downloads happn in download_liburing() in ceph.git/make-dist

We appear to have a target (https://codeload.github.com/axboe/liburing/tar.gz/refs/tags/liburing-0.7) and a fallback (https://git.kernel.dk/cgit/liburing/snapshot/liburing-0.7.tar.gz) for this dependency. There's hardcoded sha256 in make-dist to validate the download -- that check is what is failing here.

Complicating matters is that the two targets are not identical. The former untars into a directory tree with liburing-0.7 as the top level directory while the latter has liburing-liburing-0.7 as the top level. There's code in download_liburing to normalize that directory name, though the fallback will always fail the sha256 check.

The immediate cause here, therefore, is that https://github.com/axboe/liburing/archive/liburing-0.7.tar.gz seems to have changed from a sha256 of 8e2842cfe947f3a443af301bdd6d034455536c38a455c7a700d0c1ad165a7543 as specified in the make-dist to 2343e125d89600763ab277ef4699f1aa1d0d2076d60aba940de5737287bbc4b3.

Actions #1

Updated by Samuel Just about 1 year ago

  • Description updated (diff)
Actions #2

Updated by Samuel Just about 1 year ago

https://git.kernel.dk/cgit/liburing/snapshot/liburing-0.7.tar.gz has a copy with the original sha256 of 8e2842cfe947f3a443af301bdd6d034455536c38a455c7a700d0c1ad165a7543

Actions #3

Updated by Samuel Just about 1 year ago

We therefore have 3 versions at the moment:

8e2842cfe947f3a443af301bdd6d034455536c38a455c7a700d0c1ad165a7543 (original, hash in make-dist) https://git.kernel.dk/cgit/liburing/snapshot/liburing-0.7.tar.gz
2343e125d89600763ab277ef4699f1aa1d0d2076d60aba940de5737287bbc4b3 (new main target) https://github.com/axboe/liburing/archive/liburing-0.7.tar.gz
05d0cf8493d573c76b11abfcf34aabc7153affebe17ff95f9ae88b0de062a59d (fallback) https://git.kernel.dk/cgit/liburing/snapshot/liburing-0.7.tar.gz

The files in https://github.com/axboe/liburing/archive/liburing-0.7.tar.gz have the same hashes as the original.
The files in https://git.kernel.dk/cgit/liburing/snapshot/liburing-0.7.tar.gz differ only in the name of the top level directory.

Answer is probably to swap the sha256 in make-dist.

Actions #4

Updated by Samuel Just about 1 year ago

Oh, lol, the tarballs have the same hash once unzipped.

Actions #6

Updated by Samuel Just about 1 year ago

Actions #7

Updated by Samuel Just 7 months ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF