On 03/16/2018 07:06 AM, Tim Orling wrote:
I looked into 3.6 as well, but the sheer number of patches we apply is a
pain point to rebase.
I am inclined to vote for 3.6 first and pick up 3.7 when it matures a
bit and is more widely supported. I have fears of rather massive
failures in our pytho
I looked into 3.6 as well, but the sheer number of patches we apply is a
pain point to rebase.
I am inclined to vote for 3.6 first and pick up 3.7 when it matures a bit
and is more widely supported. I have fears of rather massive failures in
our python ecosystem (especially in meta-python). Perhap
I'm about half through the 3.6 updates. I was hoping to get time in the
next two weeks to finish it up. I can just look at going to 3.7 if that's
preferred. I don't have a personal preference at this point.
On Thu, Mar 15, 2018 at 1:06 PM, Alexander Kanavin <
alexander.kana...@linux.intel.com>
On 03/15/2018 06:37 PM, Derek Straka wrote:
Definitely. I just didn't do the git add. I'll send out the v2
shortly. Thanks for catching that!
While we're on the subject of python upgrades, I'd like to ask, what
kind of plan do you have for 3.6/3.7? Is anything in progress? When you
have so
On 15 March 2018 at 17:00, Derek Straka wrote:
> I'll stop failing eventually... I'm surprised I didn't get a bounce from
> the patch test script. In any case, I sent the native version.
>
>
Git does the right thing and does the merge, so the patch applies.
Ross
--
I'll stop failing eventually... I'm surprised I didn't get a bounce from
the patch test script. In any case, I sent the native version.
On Thu, Mar 15, 2018 at 12:31 PM, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> On 03/15/2018 06:37 PM, Derek Straka wrote:
>
>> Definitely.
Whoops, didn't notice that on my review. Thanks for spotting Alex.
Ross
On 15 March 2018 at 16:25, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> On 03/12/2018 12:18 AM, Derek Straka wrote:
>
>> License-Update: checksum change is due to bump in copyright year
>>
>> Resolves CVE
On 03/15/2018 06:37 PM, Derek Straka wrote:
Definitely. I just didn't do the git add. I'll send out the v2
shortly. Thanks for catching that!
The change is already in master, so you need to rebase.
Alex
--
___
Openembedded-core mailing list
Openem
Definitely. I just didn't do the git add. I'll send out the v2 shortly.
Thanks for catching that!
On Thu, Mar 15, 2018 at 12:25 PM, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> On 03/12/2018 12:18 AM, Derek Straka wrote:
>
>> License-Update: checksum change is due to bump in
On 03/12/2018 12:18 AM, Derek Straka wrote:
License-Update: checksum change is due to bump in copyright year
Resolves CVE-2017-1000158 and other potential security issues
See https://docs.python.org/3.5/whatsnew/changelog.html#python-3-5-5-final
Signed-off-by: Derek Straka
---
meta/recipes-
License-Update: checksum change is due to bump in copyright year
Resolves CVE-2017-1000158 and other potential security issues
See https://docs.python.org/3.5/whatsnew/changelog.html#python-3-5-5-final
Signed-off-by: Derek Straka
---
meta/recipes-devtools/python/{python3_3.5.4.bb => python3_3.
11 matches
Mail list logo
