From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
Joe Rutledge <joe.rutledge@phabrix.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] python-3.5: Include _posixsubprocess in package
Date: Tue, 15 May 2018 10:07:10 +0000 [thread overview]
Message-ID: <f9e8f05eb45141ca9a2890b581fae2d3@XBOX02.axis.com> (raw)
In-Reply-To: <7fa347cd-dfcc-fe71-8807-08e3a7d45710@linux.intel.com>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Alexander Kanavin
> Sent: den 15 maj 2018 11:40
> To: Joe Rutledge <joe.rutledge@phabrix.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] python-3.5: Include _posixsubprocess in
> package
>
> On 05/15/2018 12:45 PM, Joe Rutledge wrote:
> > Change the python-3.5-manifest.inc file to also include:
> > lib-dynload/_posixsubprocess.*.so
> >
> > This is needed for Python subprocess support but was not included.
>
> You need to include [krogoth] in the subject to indicate which release
> this is for.
>
> > - "lib-dynload/xreadlines.*.so types.* platform.* ${bindir}/python* " +
> > + "lib-dynload/xreadlines.*.so types.* platform.* ${bindir}/python* " +
>
> What has changed here?
A trailing space has been removed (not seen above, but it can be seen
in the original mail).
> Alex
//Peter
prev parent reply other threads:[~2018-05-15 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 9:45 [PATCH] python-3.5: Include _posixsubprocess in package Joe Rutledge
2018-05-15 9:40 ` Alexander Kanavin
2018-05-15 10:07 ` Peter Kjellerstedt [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=f9e8f05eb45141ca9a2890b581fae2d3@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=joe.rutledge@phabrix.com \
--cc=openembedded-core@lists.openembedded.org \
/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