From: Gyorgy Sarvari <skandigraun@gmail.com>
To: steve@sakoman.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][scarthgap 8/8] systemd: Rename systemd_v255.21 to systemd_255.21
Date: Wed, 18 Jun 2025 09:08:55 +0200 [thread overview]
Message-ID: <3285382b-51c5-4ea2-9784-91267d1180ac@gmail.com> (raw)
In-Reply-To: <db02a4cc542d0e7e563ec46c91bf9a7313a71d02.1750176125.git.steve@sakoman.com>
On 6/17/25 18:04, Steve Sakoman via lists.openembedded.org wrote:
> From: Savvas Etairidis <setairidis@gmail.com>
>
> The recipe was accidentally renamed with a 'v'
> prefix in 29e623b2ad00555788412fa520fbb9ffec794cbb.
>
> Signed-off-by: Savvas Etairidis <setairidis@gmail.com>
> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> ---
> .../systemd/{systemd_v255.21.bb => systemd_255.21.bb} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename meta/recipes-core/systemd/{systemd_v255.21.bb => systemd_255.21.bb} (100%)
>
Personally I'm not affected by this issue, and have no problem with this
patch, but a few weeks ago there were people who were unhappy when a
similar issue popped up in Walnascar with autoconf (though it was caught
before merging), which makes me wonder if this is the way to go.
Systemd already has a PE[1], exactly because of the same situation: "v"
was removed from the start of ${PV} - maybe it's time to bump.
Anyway, as this patch does no harm to me, this is not a complaint
against it, but I thought it would be worth to mention it at least.
[1]:
https://git.yoctoproject.org/poky/commit/?id=f95bbe35b2aab929e50471db8ba50781d5027a01
next prev parent reply other threads:[~2025-06-18 7:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 16:04 [OE-core][scarthgap 0/8] Patch review Steve Sakoman
2025-06-17 16:04 ` [OE-core][scarthgap 1/8] net-tools: patch CVE-2025-46836 Steve Sakoman
2025-06-17 16:04 ` [OE-core][scarthgap 2/8] ffmpeg: fix CVE-2025-1373 Steve Sakoman
2025-06-17 16:04 ` [OE-core][scarthgap 3/8] python3-requests: upgrade 2.32.3 -> 2.32.4 Steve Sakoman
2025-06-17 16:04 ` [OE-core][scarthgap 4/8] scripts/install-buildtools: Update to 5.0.10 Steve Sakoman
2025-06-17 16:04 ` [OE-core][scarthgap 5/8] gcc: Upgrade to GCC 13.4 Steve Sakoman
2025-06-17 16:04 ` [OE-core][scarthgap 6/8] tune-cortexr52: Remove aarch64 for ARM Cortex-R52 Steve Sakoman
2025-06-17 16:04 ` [OE-core][scarthgap 7/8] libpng: Add ptest Steve Sakoman
2025-06-17 16:04 ` [OE-core][scarthgap 8/8] systemd: Rename systemd_v255.21 to systemd_255.21 Steve Sakoman
2025-06-18 7:08 ` Gyorgy Sarvari [this message]
2025-06-18 7:24 ` ChenQi
2025-06-18 7:29 ` Gyorgy Sarvari
2025-06-18 7:36 ` ChenQi
2025-06-18 7:42 ` Gyorgy Sarvari
2025-06-18 7:53 ` Martin Jansa
2025-06-18 8:20 ` Alexander Kanavin
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=3285382b-51c5-4ea2-9784-91267d1180ac@gmail.com \
--to=skandigraun@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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