From: Khem Raj <raj.khem@gmail.com>
To: wangmy <wangmy@fujitsu.com>, openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-perl] PATCH] logcheck: upgrade 1.3.23 -> 1.3.24
Date: Tue, 19 Jul 2022 09:40:30 -0400 [thread overview]
Message-ID: <3a331d56-ee77-c023-b0f9-2a96bae3098b@gmail.com> (raw)
In-Reply-To: <1658211328-2951-4-git-send-email-wangmy@fujitsu.com>
On 7/19/22 2:15 AM, wangmy wrote:
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
> .../logcheck/{logcheck_1.3.23.bb => logcheck_1.3.24.bb} | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
> rename meta-perl/recipes-extended/logcheck/{logcheck_1.3.23.bb => logcheck_1.3.24.bb} (96%)
>
> diff --git a/meta-perl/recipes-extended/logcheck/logcheck_1.3.23.bb b/meta-perl/recipes-extended/logcheck/logcheck_1.3.24.bb
> similarity index 96%
> rename from meta-perl/recipes-extended/logcheck/logcheck_1.3.23.bb
> rename to meta-perl/recipes-extended/logcheck/logcheck_1.3.24.bb
> index b40d52ab94..ea3dd5a4c9 100644
> --- a/meta-perl/recipes-extended/logcheck/logcheck_1.3.23.bb
> +++ b/meta-perl/recipes-extended/logcheck/logcheck_1.3.24.bb
> @@ -14,9 +14,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=c93c0550bd3173f4504b2cbd8991e50b"
> SRC_URI = "${DEBIAN_MIRROR}/main/l/${BPN}/${BPN}_${PV}.tar.xz \
> file://99_logcheck \
> "
> -SRC_URI[sha256sum] = "a2188ba549fff4412c82074b271884ff66d25f3fdb2a41916e817ce676855b29"
> -
> -S = "${WORKDIR}/${BPN}"
S is not needed to be set here anymore ? Is this change documented
somewhere
> +SRC_URI[sha256sum] = "5e304adf2880967c3b155bcf98e4f0809417a16bf91adb372fa065f38ab2c0cf"
>
> inherit useradd
>
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#97894): https://lists.openembedded.org/g/openembedded-devel/message/97894
> Mute This Topic: https://lists.openembedded.org/mt/92477643/1997914
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2022-07-19 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 6:15 [oe] [meta-networking] [PATCH] nbdkit: upgrade 1.31.10 -> 1.31.12 Wang Mingyu
2022-07-19 6:15 ` [oe] [meta-networking] [PATCH] ndisc6: upgrade 1.0.5 -> 1.0.6 Wang Mingyu
2022-07-19 13:39 ` Khem Raj
2022-07-19 6:15 ` [oe] [meta-oe] [PATCH] modemmanager: upgrade 1.18.8 -> 1.18.10 Wang Mingyu
2022-07-19 6:15 ` [oe] [meta-perl] PATCH] logcheck: upgrade 1.3.23 -> 1.3.24 Wang Mingyu
2022-07-19 13:40 ` Khem Raj [this message]
2022-07-20 0:02 ` wangmy
2022-07-20 0:34 ` Khem Raj
2022-07-19 6:15 ` [oe] [meta-oe] [PATCH] pegtl: upgrade 3.2.6 -> 3.2.7 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=3a331d56-ee77-c023-b0f9-2a96bae3098b@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@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 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.