Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Anuj Mittal <anuj.mittal@intel.com>
To: Alejandro Enedino Hernandez Samaniego
	<alejandro.enedino.hernandez-samaniego@xilinx.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] python: consolidate common patches
Date: Fri, 5 Oct 2018 09:59:20 +0800	[thread overview]
Message-ID: <82a20bf4-6fd9-7a87-b5e0-540daa8ce912@intel.com> (raw)
In-Reply-To: <ce9fd909-e46b-202c-cde8-5628ca87df9f@xilinx.com>

On 10/05/2018 03:54 AM, Alejandro Enedino Hernandez Samaniego wrote:
> Hey Anuj,
> 
> 
> On 10/03/2018 10:09 PM, Anuj Mittal wrote:
>> Move inclusion of common patches to .inc to simplify things a bit.
>>
>> Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
>> ---
>>   meta/recipes-devtools/python/python-native_2.7.15.bb | 3 ---
>>   meta/recipes-devtools/python/python.inc              | 3 +++
>>   meta/recipes-devtools/python/python_2.7.15.bb        | 3 ---
>>   3 files changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/meta/recipes-devtools/python/python-native_2.7.15.bb b/meta/recipes-devtools/python/python-native_2.7.15.bb
>> index 7c491fa3e0..ee2ec1082a 100644
>> --- a/meta/recipes-devtools/python/python-native_2.7.15.bb
>> +++ b/meta/recipes-devtools/python/python-native_2.7.15.bb
>> @@ -11,10 +11,7 @@ SRC_URI += "\
>>               file://debug.patch \
>>               file://unixccompiler.patch \
>>               file://nohostlibs.patch \
>> -            file://multilib.patch \
>> -            file://add-md5module-support.patch \
>>               file://builddir.patch \
>> -            file://parallel-makeinst-create-bindir.patch \
>>               file://revert_use_of_sysconfigdata.patch \
>>              "
>>   
>> diff --git a/meta/recipes-devtools/python/python.inc b/meta/recipes-devtools/python/python.inc
>> index 66923678b1..38cc79cb41 100644
>> --- a/meta/recipes-devtools/python/python.inc
>> +++ b/meta/recipes-devtools/python/python.inc
>> @@ -13,6 +13,9 @@ SRC_URI = "http://www.python.org/ftp/python/${PV}/Python-${PV}.tar.xz \
>>              file://0003-bpo-34834-Fix-test_ssl.test_options-to-account-for-O.patch \
>>              file://0004-bpo-34836-fix-test_default_ecdh_curve-needs-no-tlsv1.patch \
>>              file://0001-bpo-33354-Fix-test_ssl-when-a-filename-cannot-be-enc.patch \
> 
> The multilib.patch is actually a different file for the native and 
> target packages, I suggest we rename it and keep it on each recipe 
> separately.
> 

Thanks Alejandro for checking. You're right. Both patches look like they
are doing the exact same thing though and perhaps one of them should be
removed. But, this patch was supposed to be a trivial cleanup.

So, can this (2/2 only) be ignored please? I will take a look at it
later after the release.

Thanks,

Anuj


  reply	other threads:[~2018-10-05  2:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04  5:09 [PATCH 1/2] python: fix failing ssl tests Anuj Mittal
2018-10-04  5:09 ` [PATCH 2/2] python: consolidate common patches Anuj Mittal
2018-10-04 19:54   ` Alejandro Enedino Hernandez Samaniego
2018-10-05  1:59     ` Anuj Mittal [this message]
2018-10-05  1:59     ` Anuj Mittal
2018-10-04  5:35 ` ✗ patchtest: failure for "python: fix failing ssl tests..." and 1 more Patchwork

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=82a20bf4-6fd9-7a87-b5e0-540daa8ce912@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=alejandro.enedino.hernandez-samaniego@xilinx.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