From: Peter Korsgaard <peter@korsgaard.com>
To: "Sébastien Szymanski" <sebastien.szymanski@armadeus.com>
Cc: Zoltan Gyarmati <zgyarmati@zgyarmati.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libusb-compat: fix hash
Date: Thu, 30 Nov 2023 23:15:58 +0100 [thread overview]
Message-ID: <878r6e99b5.fsf@48ers.dk> (raw)
In-Reply-To: <20231130083340.16983-1-sebastien.szymanski@armadeus.com> ("Sébastien Szymanski"'s message of "Thu, 30 Nov 2023 09:33:40 +0100")
>>>>> "Sébastien" == Sébastien Szymanski <sebastien.szymanski@armadeus.com> writes:
> Upstream re-released the v0.1.8 tarballs with autotools related stuff. [1]
> That makes the hash test to fail:
> ERROR: while checking hashes from package/libusb-compat//libusb-compat.hash
> ERROR: libusb-compat-0.1.8.tar.bz2 has wrong sha256 hash:
> ERROR: expected: 698c76484f3dec1e0175067cbd1556c3021e94e7f2313ae3ea6a66d900e00827
> ERROR: got : b692dcf674c070c8c0bee3c8230ce4ee5903f926d77dc8b968a4dd1b70f9b05c
> ERROR: Incomplete download, or man-in-the-middle (MITM) attack
> Update the hash and drop LIBUSB_COMPAT_AUTORECONF.
> [1] https://github.com/libusb/libusb-compat-0.1/issues/28#issuecomment-1759400548
> Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com>
Argh, that is a annoying, as then our cached copy on
sources.buildroot.org will not have the correct hash :/
I've changed it to use .tar.gz instead to not conflict with the cached
.tar.bz2 and committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-30 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 8:33 [Buildroot] [PATCH 1/1] package/libusb-compat: fix hash Sébastien Szymanski
2023-11-30 22:15 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878r6e99b5.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=sebastien.szymanski@armadeus.com \
--cc=zgyarmati@zgyarmati.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.