Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Nikolay Merinov" <n.merinov@inango-systems.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: yocto <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Switching to OpenSSL 1.1.1 in Yocto Morty release
Date: Wed, 15 Jan 2020 12:23:22 +0200 (IST)	[thread overview]
Message-ID: <1501856576.95307.1579083802759.JavaMail.zimbra@inango-systems.com> (raw)
In-Reply-To: <739d894e1e5b9cae0fa7a1fddfb1193aec4eb782.camel@linuxfoundation.org>

Hi Richard,

Thank you for your answer. We'll consider this possibility.

Regards,
Nikolai

----- Original Message -----
> From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
> To: "n merinov" <n.merinov@inango-systems.com>, "yocto" <yocto@lists.yoctoproject.org>
> Sent: Wednesday, January 15, 2020 3:08:27 AM
> Subject: Re: [yocto] Switching to OpenSSL 1.1.1 in Yocto Morty release

> On Tue, 2020-01-14 at 15:50 +0200, Nikolay Merinov via
> Lists.Yoctoproject.Org wrote:
>> Our company interested in updating an old Yocto releases (especially
>> the Morty release) to use the OpenSSL version 1.1.1.
>> 
>> Can Yocto Project integrate all necessary changes if Inango prepares
>> all required modification to compile all the code that exists in Poky
>> Morty distribution with OpenSSL 1.1.1b (version used for Thud
>> release)?
> 
> Our new stable branch maintenance plans are here:
> 
> https://wiki.yoctoproject.org/wiki/LTS
> 
> Have a look at those, particularly the community section to see whether
> this may qualify as a community maintained mixin style layer for morty?
> 
> We couldn't integrate these into morty itself but this could be
> potentially be acceptable as a mixin type piece of work that could be
> shared.
> 
> Cheers,
> 
> Richard

      reply	other threads:[~2020-01-15 10:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 13:50 Switching to OpenSSL 1.1.1 in Yocto Morty release Nikolay Merinov
2020-01-14 14:00 ` [yocto] " Nicolas Dechesne
2020-01-14 14:03 ` Alexander Kanavin
2020-01-14 22:08 ` Richard Purdie
2020-01-15 10:23   ` Nikolay Merinov [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=1501856576.95307.1579083802759.JavaMail.zimbra@inango-systems.com \
    --to=n.merinov@inango-systems.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto@lists.yoctoproject.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