From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"leonardo.sandoval.gonzalez"
<leonardo.sandoval.gonzalez@linux.intel.com>
Subject: Re: [PATCH 1/3] lib/oe/package: Improve filedeprunner subprocess handling
Date: Fri, 01 Sep 2017 17:45:01 +0100 [thread overview]
Message-ID: <1504284301.2175.64.camel@linuxfoundation.org> (raw)
In-Reply-To: <070bdf6fc9e8418eb8c4d514fde90573@XBOX02.axis.com>
On Fri, 2017-09-01 at 16:32 +0000, Peter Kjellerstedt wrote:
> Even with these changes applied, I still see texinfo succeed to
> build
> even when it should not (i.e., without having applied the patch to
> package_deb.bbclass that I just sent).
Right, there are some nasty bugs with python's multiprocessing
exception handling in a few places. I've sent some patches for some
others which I ran into with other problems, Leo should have a patch
for this specific issue shortly. Thanks for the colon fix!
Cheers,
Richard
prev parent reply other threads:[~2017-09-01 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 14:20 [PATCH 1/3] lib/oe/package: Improve filedeprunner subprocess handling Richard Purdie
2017-09-01 14:20 ` [PATCH 2/3] lib/oe/utils: Handle exceptions in multiprocess_exec Richard Purdie
2017-09-01 14:20 ` [PATCH 3/3] staging: Fix a logic error which caused dependency removal Richard Purdie
2017-09-01 16:32 ` [PATCH 1/3] lib/oe/package: Improve filedeprunner subprocess handling Peter Kjellerstedt
2017-09-01 16:45 ` Richard Purdie [this message]
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=1504284301.2175.64.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=leonardo.sandoval.gonzalez@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox