From: Patrick Ohly <patrick.ohly@intel.com>
To: Khem Raj <raj.khem@gmail.com>, Olev Kartau <olev.kartau@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] useradd.bbclass: Strip trailing '; ' in cmd params
Date: Mon, 23 May 2016 10:07:53 +0200 [thread overview]
Message-ID: <1463990873.3095.13.camel@intel.com> (raw)
In-Reply-To: <CAMKF1sqUdo1X0v1ET1_udjGb8-7pg8sucv5yZ3=PuYacvtGQwA@mail.gmail.com>
On Wed, 2016-05-18 at 12:38 -0700, Khem Raj wrote:
> This fix was not sufficient and there has to be extra fix done to also
> consider the case
> when sysroot is created during image build time. I have updated it in
> pull request here
>
> http://git.openembedded.org/openembedded-core-contrib/commit/?h=kraj/pu&id=642c6cf0b6a0371de476513162bd0cefa9c438b3
That now fails for cases where the USERADD_PARAM ends in trailing white
space after the last valid opts. The reason is that the 'if test "x
$opts" = "x$remaining"; then break; fi' check does not get triggered
anymore, because $remaining has the trailing white space whereas "$opts"
does not.
I'm not sure what the best approach is in this case. Perhaps also strip
trailing whitespace from all assignments to $remaining?
The case were we see this is:
USERADD_PARAM_iot-rest-api-server="--system --home /var/lib/empty --no-create-home --shell /bin/false --gid restful restful "
The build then hangs because the useradd preinst loops forever.
--
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:[~2016-05-23 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 4:40 [PATCH 0/5] systemd and nios2 fixes Khem Raj
2016-05-18 4:40 ` [PATCH 1/5] useradd.bbclass: Strip trailing '; ' in cmd params Khem Raj
2016-05-18 19:38 ` Khem Raj
2016-05-23 8:07 ` Patrick Ohly [this message]
2016-05-23 9:35 ` Richard Purdie
2016-09-29 0:59 ` Denys Dmytriyenko
2016-09-29 1:07 ` Denys Dmytriyenko
2016-09-29 1:31 ` Denys Dmytriyenko
2016-05-18 4:40 ` [PATCH 2/5] systemd: Create missing sysusers offline Khem Raj
2016-05-19 7:36 ` Richard Purdie
2016-05-19 8:02 ` Richard Purdie
2016-06-17 9:32 ` Enrico Joerns
2016-06-17 14:26 ` Khem Raj
2016-05-18 4:40 ` [PATCH 3/5] pixman: Fix build on arches not defining FE_INVALID exception Khem Raj
2016-05-18 4:40 ` [PATCH 4/5] kernel: fitimage: Repair misuse of shell test command Khem Raj
2016-05-18 4:40 ` [PATCH 5/5] sysprof: Disable nios2 support Khem Raj
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=1463990873.3095.13.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=olev.kartau@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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.