From: Patrick Ohly <patrick.ohly@intel.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] update_gio_module_cache: fix host user contamination
Date: Thu, 30 Mar 2017 13:46:48 +0200 [thread overview]
Message-ID: <1490874408.6396.448.camel@intel.com> (raw)
In-Reply-To: <9d94d2771cd34d5fa5f1f3df1ee52ffa@XBOX02.axis.com>
On Wed, 2017-03-29 at 23:54 +0000, Peter Kjellerstedt wrote:
> One thing that confuses me though is the “(Output: b'')” part in the
> warning below:
>
>
>
> WARNING: core-image-base-1.0-r0 do_rootfs: The postinstall intercept
> hook 'update_gio_module_cache' failed (exit code: 1)! See log for
> details! (Output: b'')
>
>
>
> What does that b'' mean?
A empty binary string - that's what Python 3 uses when it deals with raw
bytes instead of text with a known encoding.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-03-30 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 16:14 [PATCH 0/3] A few misc fixes Mentor is carrying Christopher Larson
2017-03-28 16:14 ` [PATCH 1/3] update_gio_module_cache: fix host user contamination Christopher Larson
2017-03-29 20:33 ` Andrea Adami
2017-03-29 20:40 ` Christopher Larson
2017-03-29 21:08 ` Andrea Adami
2017-03-30 8:54 ` Jussi Kukkonen
2017-03-29 23:54 ` Peter Kjellerstedt
2017-03-30 8:57 ` Richard Purdie
2017-03-30 11:46 ` Patrick Ohly [this message]
2017-03-30 9:27 ` Alexander Kanavin
2017-03-28 16:14 ` [PATCH 2/3] sysroot-relativelinks: also consider links to dirs on the host Christopher Larson
2017-03-28 16:14 ` [PATCH 3/3] systemd-boot: write startup.nsh Christopher Larson
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=1490874408.6396.448.camel@intel.com \
--to=patrick.ohly@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 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.