From: "Grygorii Tertychnyi (gtertych)" <gtertych@cisco.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: "xe-linux-external\(mailer list\)" <xe-linux-external@cisco.com>
Subject: Re: [PATCH] lib/oe/utils: add eol to format_pkg_list()
Date: Wed, 3 Oct 2018 17:22:46 +0000 [thread overview]
Message-ID: <1538587366618.96980@cisco.com> (raw)
In-Reply-To: <6cb0ab6264c5d5b65759d18594c116ae01a8d801.camel@linuxfoundation.org>
From: Richard Purdie <richard.purdie@linuxfoundation.org>
Sent: Wednesday, October 3, 2018 5:23 PM
gt> Append '\n' to the formatted string before return. If you write it
gt> to the (manifest) file, it will ensure file ends with a newline.
gt>
gt> Many GNU utilities have problems processing the last line of a file
gt> if it is not '\n' terminated. E.g. if the last line is not terminated
gt> by a newline character, then "read" will read it but return false,
gt> leaving the broken partial line in the read variable(s).
gt> It can also break or adversely affect some text processing tools,
gt> that operate on the file.
gt>
gt> Signed-off-by: grygorii tertychnyi <gtertych@cisco.com>
gt> ---
gt> meta/lib/oe/utils.py | 2 +-
gt> 1 file changed, 1 insertion(+), 1 deletion(-)
RP> If you enable buildhistory (INHERIT += 'buildhistory' in local.conf)
RP> and then "bitbake buildtools-tarball", you'll see:
RP> | DEBUG: Python function buildhistory_list_installed_sdk_target finished
RP> | NOTE: Executing buildhistory_get_sdk_installed_target ...
RP> | DEBUG: Executing shell function buildhistory_get_sdk_installed_target
RP> | basename: missing operand
RP> | Try 'basename --help' for more information.
RP> | WARNING: /home/pokybuild/yocto-worker/nightly-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/buildtools-tarball/1.0-r0/temp/run.buildhistory_get_sdk_installed_target.13414:1 exit 123 from 'xargs -n1 basename > $1/installed-packages.txt'
RP> | DEBUG: Python function do_populate_sdk finished
RP> | ERROR: Function failed: buildhistory_get_sdk_installed_target (log file is located at /home/pokybuild/yocto-worker/nightly-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/buildtools-tarball/1.0-r0/temp/log.do_populate_sdk.13414)
RP> which is buildhistory choking on the blank line.
chances are that we need to revert 98230d2d049c742c349f35b256b13afbc3d26235
to avoid empty lines
let me check
next prev parent reply other threads:[~2018-10-03 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 15:47 [PATCH] lib/oe/utils: add eol to format_pkg_list() grygorii tertychnyi
2018-10-03 14:23 ` Richard Purdie
2018-10-03 17:22 ` Grygorii Tertychnyi (gtertych) [this message]
2018-10-04 5:33 ` Grygorii Tertychnyi (gtertych)
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=1538587366618.96980@cisco.com \
--to=gtertych@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=xe-linux-external@cisco.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.