From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Martin Jansa <martin.jansa@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] gio-module-cache.bbclass: disable update_gio_module_cache postinst script for nativesdk
Date: Tue, 20 Mar 2018 19:55:35 +0200 [thread overview]
Message-ID: <580eec70-ffc4-fa12-b52d-28717c0c21a5@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LY26Yp5tgyc3CJLGbeNioRB0Bu_SRd0o3CgAeHzvO8+=w@mail.gmail.com>
On 03/20/2018 06:07 PM, Burton, Ross wrote:
> Can you file a bug for this? Probably best to fix instead of working
> around, as this leaves gio modules broken.
I also wonder if the shadow recipe's postinst needs to be fixed properly
(instead of removing it altogether for nativesdk). On the other hand
these two have been broken for a long time, and no one noticed, so maybe
they don't need working nativesdk postinst at all.
Alex
next prev parent reply other threads:[~2018-03-20 18:02 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
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 [this message]
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=580eec70-ffc4-fa12-b52d-28717c0c21a5@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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