Recipe systemd version was changed #scarthgap
Hi all,
we noticed that the systemd recipe in the scarthgap brach was renamed from systemd_255.18.bb to systemd_v255.21.bb was this indetional? The reanme adds a v before the version number. This change has influence on the CVE task we have running.
Should I create a commit to revert this name change?
Thanks in advance,
Savvas
Yes, that needs to be corrected from _v255.21 to _255.21.
Autobuilder jobs will have problem with "version-going-backwards" warning/error since the "v" was already merged, I guess bumping PE to "2" will do the job.
Peter
Quoted 18 lines
-----Original Message-----
From: [email protected] <openembedded- [email protected]> On Behalf Of Savvas Etairidis via lists.openembedded.org
Sent: Friday, June 13, 2025 15:23
To: [email protected]
Subject: [OE-core] [scarthgap] Recipe systemd version was changed #scarthgapHi all,
we noticed that the systemd recipe in the scarthgap brach was renamed from systemd_255.18.bb to systemd_v255.21.bb was this indetional?
The reanme adds a v before the version number. This change has influence on the CVE task we have running.
Should I create a commit to revert this name change?Thanks in advance,
Savvas
Thanks for spotting this. Problem came from me :( I used “v255.21” when upgrading with devtool and didn’t spot this change.
I added a patch to fix this.