From: Michael Vetter <jubalh@iodoru.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libstrophe: bump to version 0.10.1
Date: Wed, 20 Jan 2021 09:06:29 +0100 [thread overview]
Message-ID: <20210120090629.2d700397@maitreya.fritz.box> (raw)
In-Reply-To: <20210119221430.76bfaa9c@windsurf.home>
Hello Thomas,
On Tue, 19 Jan 2021 22:14:30 +0100
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello Michael,
>
> On Mon, 4 Jan 2021 11:10:54 +0100
> Michael Vetter <jubalh@iodoru.org> wrote:
>
> > Changes:
> > * Fixed compilation error when LibreSSL is used
> > * Fixed crash when NULL is provided as password
> >
> > Signed-off-by: Michael Vetter <jubalh@iodoru.org>
>
> Thanks a lot for the patch, but it doesn't work here, I don't get the
> same hash as you do for the download. Could you check this on your
> side ?
>
> Here is what I get:
>
> ERROR: libstrophe-0.10.1.tar.gz has wrong sha256 hash:
> ERROR: expected:
> 4918c47029ecdea2deab4b0f9336ca4a8bb12c28b72b2cec397d98664b94c771
> ERROR: got :
> 5bf0bbc555cb6059008f1b748370d4d2ee1e1fabd3eeab68475263556405ba39
> ERROR: Incomplete download, or man-in-the-middle (MITM) attack
I'm sorry about that. We had some disagreement at JasPer and we removed
an existing tag and created the same tag on a different commit. Thus
generating a different tarball under the same tag..
I thought I only did the buildroot update after this, but maybe I
remember wrong.
Would you mind changing the commit to use the new hash? Or should I
send a new patch?
Best,
Michael
next prev parent reply other threads:[~2021-01-20 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 10:10 [Buildroot] [PATCH 1/1] package/libstrophe: bump to version 0.10.1 Michael Vetter
2021-01-19 21:14 ` Thomas Petazzoni
2021-01-20 8:06 ` Michael Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-03 14:49 Michael Vetter
2021-03-04 7:12 ` Peter Korsgaard
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=20210120090629.2d700397@maitreya.fritz.box \
--to=jubalh@iodoru.org \
--cc=buildroot@busybox.net \
/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.