From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Allow postinst functions to be verbose
Date: Fri, 14 Apr 2017 04:39:52 +0200 [thread overview]
Message-ID: <cover.1492135840.git.pkj@axis.com> (raw)
This enables tracing of the postinst functions created in base-passwd
and useradd.bbclass if BB_VERBOSE_LOGS is enabled. I found this
extremely useful during verification of the useradd functionality,
especially as there otherwise is absolutely nothing in the logs of why
a failure in a postinst function happened.
I also simplified useradd_sysroot_sstate() by only having the code to
create the postinst files once.
Feel free to squash these commits with the "base-passwd/useradd:
Various improvements to useradd with RSS" commit if you prefer.
//Peter
The following changes since commit 79ac98550f0aa25940404a9805c12744f7047c76:
base-passwd/useradd: Various improvements to useradd with RSS (2017-04-14 00:03:19 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib pkj/verbose_postinst
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/verbose_postinst
Peter Kjellerstedt (2):
useradd.bbclass: Make postinst functions verbose if BB_VERBOSE_LOGS is
set
base-passwd: Make the postinst function verbose if BB_VERBOSE_LOGS is
set
meta/classes/useradd.bbclass | 11 +++++------
meta/recipes-core/base-passwd/base-passwd_3.5.29.bb | 2 ++
2 files changed, 7 insertions(+), 6 deletions(-)
--
2.12.0
next reply other threads:[~2017-04-14 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 2:39 Peter Kjellerstedt [this message]
2017-04-14 2:39 ` [PATCH 1/2] useradd.bbclass: Make postinst functions verbose if BB_VERBOSE_LOGS is set Peter Kjellerstedt
2017-04-14 2:39 ` [PATCH 2/2] base-passwd: Make the postinst function " Peter Kjellerstedt
2017-04-14 3:01 ` ✗ patchtest: failure for Allow postinst functions to be verbose Patchwork
2017-04-14 8:49 ` [PATCH 0/2] " Richard Purdie
2017-04-14 13:10 ` Peter Kjellerstedt
2017-04-18 10:16 ` 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=cover.1492135840.git.pkj@axis.com \
--to=peter.kjellerstedt@axis.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.