All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Armin Kuster" <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] RFC???
Date: Mon, 31 May 2021 19:11:56 +0000	[thread overview]
Message-ID: <20210531191158.964098-1-akuster808@gmail.com> (raw)

I ran into an issue with a systemd service that had a depend.
The post init error message was a bit misleading;

ERROR: security-build-image-1.0-r0 do_rootfs: Postinstall scriptlets of ['clamav-daemon'] have failed. If the intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
Details of the failure are in /home/build/builds/master/tmp/work/qemux86_64-poky-linux/security-build-image/1.0-r0/temp/log.do_rootfs.

All I found was a python trace back in the logs. I have provided a version of an
error message that I hope is acceptable. The second patch is for RPM adapting
to use the 'error message' to help provide a bit more info.

The RPM solusion has been tested and before porting this to the other
package managers, I want to make sure the 'error message' was accepted.



Armin Kuster (2):
  systemctl: Stop tracebacks use formated error messages
  package_manager/rpm: decode systemctl failures

 meta/lib/oe/package_manager/rpm/__init__.py   |  3 +++
 .../systemd/systemd-systemctl/systemctl       | 24 +++++++++++++++----
 2 files changed, 22 insertions(+), 5 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-05-31 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 19:11 Armin Kuster [this message]
2021-05-31 19:11 ` [PATCH 1/2] systemctl: Stop tracebacks use formated error messages Armin Kuster
2021-05-31 19:11 ` [PATCH 2/2] package_manager/rpm: decode systemctl failures Armin Kuster
2021-05-31 19:20 ` [OE-core] [PATCH 0/2] RFC??? 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=20210531191158.964098-1-akuster808@gmail.com \
    --to=akuster808@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.