Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Martin Siegumfeldt" <mns@gomspace.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [walnascar][PATCH 3/3] systemd.bbclass: Make systemd_postinst run as intended
Date: Wed, 24 Sep 2025 23:36:59 -0700	[thread overview]
Message-ID: <20743.1758782219733650322@lists.openembedded.org> (raw)
In-Reply-To: <DB5PR02MB10213F2B4B71975FD52650035EF1CA@DB5PR02MB10213.eurprd02.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]

Thanks Peter,

Below is what I expect to be the relevant part of the log file:

Created symlink '/home/martin/work/distro-gomspace_tmp/build/tmp/work/nanomind_z7020_zed-gomspace-linux-gnueabi/nanomind-dev-image/1.0/rootfs/etc/systemd/system/multi-user.target.wants/busybox-klogd.service' → '/usr/lib/systemd/system/busybox-klogd.service'.
Created symlink '/home/martin/work/distro-gomspace_tmp/build/tmp/work/nanomind_z7020_zed-gomspace-linux-gnueabi/nanomind-dev-image/1.0/rootfs/etc/systemd/system/multi-user.target.wants/sysstat.service' → '/usr/lib/systemd/system/sysstat.service'.
Failed to enable unit: Refusing to operate on template unit nanomind-gpio-ctrl@.service when destination unit multi-user.target is a non-template unit
Failed to enable unit: Refusing to operate on template unit nanomind-bank-ctrl@.service when destination unit multi-user.target is a non-template unit
Created symlink '/home/martin/work/distro-gomspace_tmp/build/tmp/work/nanomind_z7020_zed-gomspace-linux-gnueabi/nanomind-dev-image/1.0/rootfs/etc/systemd/system/multi-user.target.wants/redis.service' → '/usr/lib/systemd/system/redis.service'.
.
.
.
Configuring sysstat.
Configuring nanomind-gpio-ctrl.
nanomind-gpio-ctrl.postinst returned 1, marking as unpacked only, configuration required on target.
Configuring nanomind-bank-ctrl.
nanomind-bank-ctrl.postinst returned 1, marking as unpacked only, configuration required on target.
Configuring bash-completion.
Configuring libiio-bash-completion.

The particular service file is described as:

[Unit]
Description=GPIO Control Service (%i)
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/gpioset --daemonize --chip gpiochip0 %i=1
ExecStartPost=/bin/sleep .3
ExecStopPost=/usr/bin/gpioset --toggle 0 --chip gpiochip0 %i=0
ExecStopPost=/bin/sleep .3
[Install]
WantedBy=multi-user.target

AFAICT, the issue only applies for template units - other seem to install/configure fine.

What puzzles me is why I am seemingly the only one running into this - I consider both the recipe and service file to be quite standard...

[-- Attachment #2: Type: text/html, Size: 2446 bytes --]

  reply	other threads:[~2025-09-25  6:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-12 15:57 [walnascar][PATCH 1/3] systemd-systemctl-native: Use += instead of :append Peter Kjellerstedt
2025-09-12 15:57 ` [walnascar][PATCH 2/3] systemd-systemctl-native: Install systemd-sysv-install Peter Kjellerstedt
2025-09-12 15:57 ` [walnascar][PATCH 3/3] systemd.bbclass: Make systemd_postinst run as intended Peter Kjellerstedt
2025-09-24 18:03   ` Martin Siegumfeldt
2025-09-24 19:44     ` [OE-core] " Peter Kjellerstedt
2025-09-25  6:36       ` Martin Siegumfeldt [this message]
2025-09-29  5:52         ` Martin Siegumfeldt

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=20743.1758782219733650322@lists.openembedded.org \
    --to=mns@gomspace.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