From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] systemd.bbclass: support template files with dots
Date: Wed, 22 Oct 2025 07:46:12 -0600 [thread overview]
Message-ID: <53820a85-7956-44f5-9f00-4fa147c59511@linux.intel.com> (raw)
In-Reply-To: <3FAF0AA8-5867-4822-9D3F-BFA43D40EA4C@arm.com>
On 10/22/2025 4:40 AM, Ross Burton wrote:
> On 15 Oct 2025, at 15:59, Bills, Jason M via lists.openembedded.org <jason.m.bills=linux.intel.com@lists.openembedded.org> wrote:
>>
>> If the SYSTEMD_SERVICE variable contains a template instance that has
>> dots in the name such as "xyz.openbmc_project.my@instance.service", the
>> regex splits on all the dots resulting in the following python
>> exception:
>>
>> Exception: ValueError: too many values to unpack (expected 3)
>>
>> To continue to support service files with dots in the name, this changes
>> to first split only on the '@' to isolate the name, then split the
>> second half on the dot to get the remaining two parameters.
>>
>> Confirmed when building that the three parameters for template instances
>> without dots came out the same and that template instances with dots
>> include the full name with dots in the first parameter.
>>
>> Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
>> ---
>> meta/classes-recipe/systemd.bbclass | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/classes-recipe/systemd.bbclass b/meta/classes-recipe/systemd.bbclass
>> index 5a0550b287..fcd47809b2 100644
>> --- a/meta/classes-recipe/systemd.bbclass
>> +++ b/meta/classes-recipe/systemd.bbclass
>> @@ -247,7 +247,8 @@ python systemd_populate_packages() {
>> if not systemd_service_exists(service, user, d):
>> continue
>> if '@' in service and '@.' not in service:
>> - (servicename, instance, service_type) = re.split('[@.]', service)
>> + (servicename, postfix) = service.split('@')
>> + (instance, service_type) = postfix.split('.')
>
> The assumption here is that the service name only contains a single dot and the instance isn’t something like foo.bar, right? Are we certain that is the case?
>
> Ross
>
This splits first on the '@', so the assumption is the whole thing
contains only one '@' and the service name can have many dots. But the
instance is assumed to have no dots which is currently the case in
OpenBMC, but I don't know is guaranteed in systemd.
The documentation ([1]) isn't explicit, but assuming "instance name"
allows the same characters as "unit name prefix", then it looks like
it's possible.
I will rework the second split to split on the last dot to allow for the
case where someone may use an instance with dots.
[1]:
https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html
-Jason
prev parent reply other threads:[~2025-10-22 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 14:59 [PATCH] systemd.bbclass: support template files with dots Jason M. Bills
2025-10-22 10:40 ` [OE-core] " Ross Burton
2025-10-22 13:46 ` Bills, Jason M [this message]
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=53820a85-7956-44f5-9f00-4fa147c59511@linux.intel.com \
--to=jason.m.bills@linux.intel.com \
--cc=Ross.Burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
/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