From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] package/glibc: update hash of LICENSES file for ARC version
Date: Wed, 21 Nov 2018 10:22:02 +0100 [thread overview]
Message-ID: <8736ruoked.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181121081845.23739-1-thomas.petazzoni@bootlin.com> (Thomas Petazzoni's message of "Wed, 21 Nov 2018 09:18:45 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> In commit 5d4f23cbe65c79826b1b2071e972803a453934cb ("toolchain: Bump
> ARC tools to arc-2018.09-rc1"), the glibc version for the ARC
> architecture was bumped, but the hashes of the license files were not
> updated accordingly, causing a build failure during "legal-info":
> ERROR: LICENSES has wrong sha256 hash:
> ERROR: expected: 61abdd6930c9c599062d89e916b3e7968783879b6be0ee1c6229dd6169def431
> ERROR: got : 35bdb41dc0bcb10702ddacbd51ec4c0fe6fb3129f734e8c85fc02e4d3eb0ce3f
> The changes between the previous LICENSES file and the new one are:
> - The text related to libidn has been removed from the LICENSES file,
> following the switch to libidn2:
> https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=7f9f1ecb710eac4d65bb02785ddf288cac098323#patch2
> - The text related to stdio-common/tst-printf.c has been removed from
> the LICENSES file, following the removal of this non-free code from
> glibc:
> https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=5a357506659f9a00fcf5bc9c5d8fc676175c89a7#patch2
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to next, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-11-21 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 8:18 [Buildroot] [PATCH next] package/glibc: update hash of LICENSES file for ARC version Thomas Petazzoni
2018-11-21 9:22 ` 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=8736ruoked.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox