<div dir="ltr">Yes, the 'revert' works for me, thanks.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 21, 2017 at 11:29 AM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, 2017-08-18 at 19:29 +0200, Martin Jansa wrote:<br>
> Even with that patch to rename openssl10 back to openssl we still<br>
> need to solve the openssl-native which wasn't reverted back to 1.0.<br>
><br>
> Upstream nodejs isn't going to be openssl-1.1 for a bit longer as<br>
> explained:<br>
> <a href="https://github.com/nodejs/node/pull/14761" rel="noreferrer" target="_blank">https://github.com/nodejs/<wbr>node/pull/14761</a><br>
> <a href="https://github.com/nodejs/node/pull/11828" rel="noreferrer" target="_blank">https://github.com/nodejs/<wbr>node/pull/11828</a><br>
> so it would make sense to revert native and nativesdk versions as<br>
> well - if it isn't done in oe-core, I'll do it in our own layers to<br>
> keep the builds going.<br>
<br>
</span>Hopefully we have a working 'revert' back to 1.0 in master now as there<br>
was simply too much breakage for this release.<br>
<br>
I would ask that people do try and figure out how to solve some of the<br>
1.1 issues in the meantime, hopefully people can enable 1.1 with some<br>
PREFERRED_VERSION tweaks.<br>
<br>
Cheers,<br>
<br>
Richard<br>
</blockquote></div><br></div>