Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: wangmy@fujitsu.com
Cc: openembedded-core@lists.openembedded.org,
	Wang Mingyu <wangmy@cn.fujitsu.com>
Subject: Re: [OE-core] [PATCH v2] systemd-boot: upgrade 256.8 -> 256.9
Date: Thu, 12 Dec 2024 09:42:16 +0200	[thread overview]
Message-ID: <Z1qT2DQ_jGIstNcY@nuoska> (raw)
In-Reply-To: <1733964540-5537-2-git-send-email-wangmy@fujitsu.com>

Hi,

On Thu, Dec 12, 2024 at 08:49:00AM +0800, wangmy via lists.openembedded.org wrote:
> From: Wang Mingyu <wangmy@cn.fujitsu.com>
> 
> Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
> ---
>  ...ystemd-boot-native_256.8.bb => systemd-boot-native_256.9.bb} | 0
>  .../systemd/{systemd-boot_256.8.bb => systemd-boot_256.9.bb}    | 0
>  meta/recipes-core/systemd/systemd.inc                           | 2 +-
>  .../recipes-core/systemd/{systemd_256.8.bb => systemd_256.9.bb} | 0
>  4 files changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-core/systemd/{systemd-boot-native_256.8.bb => systemd-boot-native_256.9.bb} (100%)
>  rename meta/recipes-core/systemd/{systemd-boot_256.8.bb => systemd-boot_256.9.bb} (100%)
>  rename meta/recipes-core/systemd/{systemd_256.8.bb => systemd_256.9.bb} (100%)
> 
> diff --git a/meta/recipes-core/systemd/systemd-boot-native_256.8.bb b/meta/recipes-core/systemd/systemd-boot-native_256.9.bb
> similarity index 100%
> rename from meta/recipes-core/systemd/systemd-boot-native_256.8.bb
> rename to meta/recipes-core/systemd/systemd-boot-native_256.9.bb
> diff --git a/meta/recipes-core/systemd/systemd-boot_256.8.bb b/meta/recipes-core/systemd/systemd-boot_256.9.bb
> similarity index 100%
> rename from meta/recipes-core/systemd/systemd-boot_256.8.bb
> rename to meta/recipes-core/systemd/systemd-boot_256.9.bb
> diff --git a/meta/recipes-core/systemd/systemd.inc b/meta/recipes-core/systemd/systemd.inc
> index 989ca667b7..b85d5b187d 100644
> --- a/meta/recipes-core/systemd/systemd.inc
> +++ b/meta/recipes-core/systemd/systemd.inc
> @@ -15,7 +15,7 @@ LICENSE:libsystemd = "LGPL-2.1-or-later"
>  LIC_FILES_CHKSUM = "file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe \
>                      file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c"
>  
> -SRCREV = "a2240d1cf9f3515728186c2c98a6f4b64a40e4da"
> +SRCREV = "f15fd96efd5ebdfb18746acb0cbb35a4331b4d8b"
>  SRCBRANCH = "v256-stable"
>  SRC_URI = "git://github.com/systemd/systemd.git;protocol=https;branch=${SRCBRANCH}"

NACK: must also update systemd and systemd-boot-native recipe versions since
systemd, systemd-boot and systemd-boot-native all use systemd.inc.

If this update is automated, then that automation needs to be fixed to update all
affected recipes. This same issue has been in a lot of update patches.

Cheers,

-Mikko


  reply	other threads:[~2024-12-12  7:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12  0:48 [OE-core] [PATCH v2] barebox: upgrade 2024.10.0 -> 2024.12.0 wangmy
2024-12-12  0:49 ` [OE-core] [PATCH v2] systemd-boot: upgrade 256.8 -> 256.9 wangmy
2024-12-12  7:42   ` Mikko Rapeli [this message]
2024-12-12  7:58     ` Alexander Kanavin
2024-12-12  8:30       ` Mikko Rapeli
2024-12-17  7:35 ` [OE-core] [PATCH v2] barebox: upgrade 2024.10.0 -> 2024.12.0 Enrico Jörns

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=Z1qT2DQ_jGIstNcY@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wangmy@cn.fujitsu.com \
    --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