From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org, peter.kjellerstedt@axis.com
Subject: Re: [PATCH 0/2] Allow postinst functions to be verbose
Date: Tue, 18 Apr 2017 13:16:39 +0300 [thread overview]
Message-ID: <cb98dab5-e932-a66a-311e-7aa5b2484652@linux.intel.com> (raw)
In-Reply-To: <5d709f7eb9fa49fd89cd95818ddf4018@XBOX02.axis.com>
On 04/14/2017 04:10 PM, Peter Kjellerstedt wrote:
>> I'm afraid I can't take these since these scripts get written into the
>> sstate objects for the recipes in question and this would make the
>> sstate change depending on the parameters you call bitbake with. I
>> think we'd both agree that is undesirable.
>
> Bother. Did not think of that (I am so used to having it enabled in all my
> builds).
>
>> Not sure what we can do but this needs more thought.
>
> Yeah, it would be great if the output from the postinst scripts was actually
> captured. But we can think of that for 2.4.
Are you using rpm? If you are, we already have ROOTFS_RPM_DEBUG variable
which, if enabled, directs rpm to output a lot more to the log.do_rootfs
than it normally would. Can you switch it on in your local.conf and see
if you get what you need?
If the log still isn't verbose enough, please write a comment to this bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11096
explaining what kind of output from rpm would be useful to have, and we
can patch rpm to do that.
Alex
prev parent reply other threads:[~2017-04-18 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 2:39 [PATCH 0/2] Allow postinst functions to be verbose Peter Kjellerstedt
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 [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=cb98dab5-e932-a66a-311e-7aa5b2484652@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.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