Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	robert_joslyn@selinc.com,
	openembedded-core@lists.openembedded.org
Subject: Re: Backport OpenSSL 1.0.2n
Date: Wed, 14 Feb 2018 09:26:19 -0800	[thread overview]
Message-ID: <b2346dc6-5649-8924-044b-1a193dd5adc6@gmail.com> (raw)
In-Reply-To: <1518623907.24236.115.camel@linuxfoundation.org>



On 02/14/2018 07:58 AM, Richard Purdie wrote:
> On Tue, 2018-02-13 at 08:27 -0800, akuster808 wrote:
>> On 02/12/2018 01:08 PM, robert_joslyn@selinc.com wrote:
>>> I'm working with the pyro release, and noticed that it's still
>>> using 
>>> openssl 1.0.2k. The latest version in the 1.0.2 series is 1.0.2n,
>>> which is 
>>> already available on master. Is there a reason that the newer
>>> version 
>>> hasn't made it back to pyro (or rocko, which is on 1.0.2m)? 
>> openssl 1.1 was added and the openssl files got restructured making
>> simple cherry-picking not an option for older releases.
>>
>> 1.0.2n hit master 7 days ago, sorry for the delay.
>>
>> 1.0.2n is now in stable/rocko-next and will migrate to rocko when
>> appropriate.
> It is? Not pushed maybe?
it is.. just not in poky-contrib ;) its over on oe-contrib. Its where I
queue up things

- armin
>
> Cheers,
>
> Richard



      reply	other threads:[~2018-02-14 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 21:08 Backport OpenSSL 1.0.2n robert_joslyn
2018-02-13  7:02 ` Alexander Kanavin
2018-02-13 16:27 ` akuster808
2018-02-13 19:53   ` robert_joslyn
2018-02-14 15:58   ` Richard Purdie
2018-02-14 17:26     ` akuster808 [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=b2346dc6-5649-8924-044b-1a193dd5adc6@gmail.com \
    --to=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=robert_joslyn@selinc.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