From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Martin Bark <martin@barkynet.com>,
Daniel Price <daniel.price@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/nodejs: fix legal info
Date: Mon, 6 Nov 2023 22:06:09 +0100 [thread overview]
Message-ID: <20231106220609.7645d540@windsurf> (raw)
In-Reply-To: <20231106201509.8600-1-fontaine.fabrice@gmail.com>
On Mon, 6 Nov 2023 21:15:09 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> For an unknown reason, hash added by commit
> c1d5eada4d4db9eeaa1c44dd1dea95a67c8a70ca is wrong:
>
> >>> host-nodejs-src 20.9.0 Collecting legal info
> ERROR: LICENSE has wrong sha256 hash:
> ERROR: expected: a6871483905199033882d66453649675f0e88ffaa07f9f8acb257ce7504bc758
> ERROR: got : 93ac846282ce6c5255e00fada2fd2e7e292255239fe58d5502b0a554859e6a3e
>
> Fixes:
> - http://autobuild.buildroot.org/results/a199f128bc1d59a311f3ae683dcc14a1d6f3bb7b
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/nodejs/nodejs.hash | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-06 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 20:15 [Buildroot] [PATCH 1/1] package/nodejs: fix legal info Fabrice Fontaine
2023-11-06 21:06 ` Thomas Petazzoni via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-14 16:04 Fabrice Fontaine
2022-05-14 20:40 ` Yann E. MORIN
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=20231106220609.7645d540@windsurf \
--to=buildroot@buildroot.org \
--cc=daniel.price@gmail.com \
--cc=fontaine.fabrice@gmail.com \
--cc=martin@barkynet.com \
--cc=thomas.petazzoni@bootlin.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox