From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: wangmy <wangmy@fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] libjitterentropy: upgrade 3.3.1 -> 3.4.0
Date: Tue, 22 Mar 2022 18:13:48 +0100 [thread overview]
Message-ID: <YjoDzJmFADk54g4a@piout.net> (raw)
In-Reply-To: <1647945489-5242-3-git-send-email-wangmy@fujitsu.com>
Hello,
I'm pretty sure this is the cause of:
https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/4937/steps/11/logs/stdio
On 22/03/2022 18:38:08+0800, wangmy wrote:
> License-Update: year updated to 2022
>
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
> ...opy_3.3.1.bb => libjitterentropy_3.4.0.bb} | 4 ++--
> 1 file changed, 21 insertions(+), 2 deletions(-)
> rename meta/recipes-support/libjitterentropy/{libjitterentropy_3.3.1.bb => libjitterentropy_3.4.0.bb} (58%)
>
> diff --git a/meta/recipes-support/libjitterentropy/libjitterentropy_3.3.1.bb b/meta/recipes-support/libjitterentropy/libjitterentropy_3.4.0.bb
> similarity index 58%
> rename from meta/recipes-support/libjitterentropy/libjitterentropy_3.3.1.bb
> rename to meta/recipes-support/libjitterentropy/libjitterentropy_3.4.0.bb
> index 38b48908a3..f80ed11cc1 100644
> --- a/meta/recipes-support/libjitterentropy/libjitterentropy_3.3.1.bb
> +++ b/meta/recipes-support/libjitterentropy/libjitterentropy_3.4.0.bb
> @@ -5,12 +5,12 @@ stamp. It is a small-scale, yet fast entropy source that is viable in almost \
> all environments and on a lot of CPU architectures."
> HOMEPAGE = "http://www.chronox.de/jent.html"
> LICENSE = "GPL-2.0-or-later | BSD-3-Clause"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=1c94a9d191202a5552f381a023551396 \
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=64a87180908540620ce364b5e69b3b03 \
> file://LICENSE.gplv2;md5=eb723b61539feef013de476e68b5c50a \
> file://LICENSE.bsd;md5=66a5cedaf62c4b2637025f049f9b826f \
> "
> SRC_URI = "git://github.com/smuellerDD/jitterentropy-library.git;branch=master;protocol=https"
> -SRCREV = "887c9871ea110e397812ff7f3b28a6269f0a2ffc"
> +SRCREV = "2e5019cfe63038faaa405ce53715effe4ea580e4"
> S = "${WORKDIR}/git"
>
> # remove at next version upgrade or when output changes
> --
> 2.25.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#163539): https://lists.openembedded.org/g/openembedded-core/message/163539
> Mute This Topic: https://lists.openembedded.org/mt/89949054/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-03-22 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 10:38 [OE-core] [PATCH] libdazzle: upgrade 3.42.0 -> 3.44.0 Wang Mingyu
2022-03-22 10:38 ` [OE-core] [PATCH] libhandy: upgrade 1.5.0 -> 1.6.1 Wang Mingyu
2022-03-23 4:52 ` Alexandre Belloni
2022-03-22 10:38 ` [OE-core] [PATCH] libjitterentropy: upgrade 3.3.1 -> 3.4.0 Wang Mingyu
2022-03-22 17:13 ` Alexandre Belloni [this message]
2022-03-22 10:38 ` [OE-core] [PATCH] libsolv: upgrade 0.7.21 -> 0.7.22 Wang Mingyu
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=YjoDzJmFADk54g4a@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.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