Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Max <max.oss.09@gmail.com>
To: alex.kanavin@gmail.com, leimaohui@fujitsu.com
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	Max Krummenacher <max.krummenacher@toradex.com>,
	stefan.agner@toradex.com
Subject: Re: [OE-core] About an issue of run-postinsts.service
Date: Thu, 23 May 2024 19:13:44 +0200	[thread overview]
Message-ID: <96674a6743679539da9ca805adaf66150540d92c.camel@gmail.com> (raw)
In-Reply-To: <CANNYZj9UpUdJ2G5ng2Evipz4MeqbK_SuQuuQDpamnnuAxY8-Pw@mail.gmail.com>

Hi

Am Donnerstag, dem 23.05.2024 um 08:23 +0200 schrieb Alexander Kanavin via lists.openembedded.org:
> On Thu, 23 May 2024 at 05:00, leimaohui via lists.openembedded.org
> <leimaohui=fujitsu.com@lists.openembedded.org> wrote:
> 
> > And I tested by qemu and on PC, there is no issue that mentioned in the patch(fd266b1b66844d660ebd8e33fe22c08c8ddaccbf) which added "--no-reload " in run-postinsts.service.
> > So, can I submit a patch to delete the "--no-reload " from run-postinsts.service?
> 
> I think yes you should. The original change feels like a hack around
> bugs in systemd, those bugs may have been solved long time ago, and if
> they have not, we need a better way to handle this (that does not
> result in systemd warnings).
> 

We since removed any pkg_postinstall_ontarget from our images built with OE master.

I now build an image with a dummy postinstall added to see if the behavior can still be reproduced.
That simple test on an i.MX6 based SoM no longer shows the issue, so likely it was fixed in systemd
/ OE / wherever.

I'm fine with the change to remove "--no-reload " in the run-postinsts.service.

Thanks for pinging us Alex.

Regards
Max

> 
> Alex
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#199778): https://lists.openembedded.org/g/openembedded-core/message/199778
> Mute This Topic: https://lists.openembedded.org/mt/106256417/3617484
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [max.oss.09@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



  reply	other threads:[~2024-05-23 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  3:00 About an issue of run-postinsts.service Maohui Lei (Fujitsu)
2024-05-23  6:23 ` [OE-core] " Alexander Kanavin
2024-05-23 17:13   ` Max [this message]
2024-05-24  0:48     ` Maohui Lei (Fujitsu)

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=96674a6743679539da9ca805adaf66150540d92c.camel@gmail.com \
    --to=max.oss.09@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=leimaohui@fujitsu.com \
    --cc=max.krummenacher@toradex.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=stefan.agner@toradex.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