From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ca-certificates: run postinst script only for -target package
Date: Mon, 19 Mar 2018 18:31:22 +0200 [thread overview]
Message-ID: <43d5b925-755b-3dbc-63b0-0df6e89396db@linux.intel.com> (raw)
In-Reply-To: <CA+chaQdRLqo0z__-qnVZ1xeJGeALjA6GbNvRP50LpRT3BVBFCA@mail.gmail.com>
On 03/19/2018 05:32 PM, Martin Jansa wrote:
> Do you already have similar patch for nativesdk-shadow somewhere?
Nope. Hopefully the maintainer of the shadow recipe can step in?
> It would be great if the output of postinst script could be extracted to
> separate file or the warning provided some simple way to re-execute just
> the failing postinst manually (e.g. with devtool). Currently I do it
> manually, which I cannot recommend to anyone (basically removing rm_work
> from INHERIT to keep rootfs after do_rootfs, then jumping to rootfs
> directory, exporting D and running the postinst from OPKGLIBDIR).
For rpm, setting ROOTFS_RPM_DEBUG will execute the postinst with -x and
log the lines and their output to log.do_rootfs. But you're right - care
to file a bug?
Alex
next prev parent reply other threads:[~2018-03-19 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 11:27 [PATCH] ca-certificates: run postinst script only for -target package Alexander Kanavin
2018-03-19 15:32 ` Martin Jansa
2018-03-19 16:31 ` Alexander Kanavin [this message]
2018-03-20 12:10 ` [PATCH 1/2] gio-module-cache.bbclass: disable update_gio_module_cache postinst script for nativesdk Martin Jansa
2018-03-20 12:10 ` [PATCH 2/2] shadow.inc: run postinst only for target Martin Jansa
2018-03-20 16:07 ` [PATCH 1/2] gio-module-cache.bbclass: disable update_gio_module_cache postinst script for nativesdk Burton, Ross
2018-03-20 17:55 ` Alexander Kanavin
2018-07-20 9:11 ` Martin Jansa
2018-07-20 16:03 ` [sumo][PATCH] " Martin Jansa
2018-07-20 16:07 ` 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=43d5b925-755b-3dbc-63b0-0df6e89396db@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@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.