public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: ChenQi <Qi.Chen@windriver.com>,
	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:29:21 +0200	[thread overview]
Message-ID: <9470af8d-87e5-40bc-a79d-cddbf58c92ca@gmail.com> (raw)
In-Reply-To: <582ab22a-f015-4611-b1d5-3c2c624585a1@windriver.com>

On 6/18/25 09:24, ChenQi wrote:
> The author's V1 patch bumped PE.
> I replied to that patch, asking the author to not bump PE.
> My reason is that we'll need to bump PE in later releases too 
> (walnascar, master) if we bump PE in scarthgap.

My main question would be if bumping PE is worse than breaking this
recipe in this release. Maybe it is - I just didn't see much discussions
over this.

>
> Regards,
> Qi
>
> On 6/18/25 15:08, Gyorgy Sarvari via lists.openembedded.org wrote:
>> 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
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#218970): https://lists.openembedded.org/g/openembedded-core/message/218970
>> Mute This Topic: https://lists.openembedded.org/mt/113692551/7304865
>> Group Owner: openembedded-core+owner@lists.openembedded.org
>> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [Qi.Chen@eng.windriver.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>



  reply	other threads:[~2025-06-18  7:29 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
2025-06-18  7:24     ` ChenQi
2025-06-18  7:29       ` Gyorgy Sarvari [this message]
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=9470af8d-87e5-40bc-a79d-cddbf58c92ca@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=Qi.Chen@windriver.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