From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 5C64C782FD for ; Mon, 21 Aug 2017 09:29:48 +0000 (UTC) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.15.2/8.15.2/Debian-3) with ESMTPSA id v7L9Tl7g017457 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 21 Aug 2017 10:29:48 +0100 Message-ID: <1503307787.32591.59.camel@linuxfoundation.org> From: Richard Purdie To: Martin Jansa , Khem Raj Date: Mon, 21 Aug 2017 10:29:47 +0100 In-Reply-To: References: <1502969638.13978.209.camel@linuxfoundation.org> X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (dan.rpsys.net [192.168.3.1]); Mon, 21 Aug 2017 10:29:48 +0100 (BST) X-Virus-Scanned: clamav-milter 0.99.2 at dan X-Virus-Status: Clean Cc: Patches and discussions about the oe-core layer Subject: Re: openssl10 unusable for many components X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2017 09:29:49 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2017-08-18 at 19:29 +0200, Martin Jansa wrote: > Even with that patch to rename openssl10 back to openssl we still > need to solve the openssl-native which wasn't reverted back to 1.0. > > Upstream nodejs isn't going to be openssl-1.1 for a bit longer as > explained: > https://github.com/nodejs/node/pull/14761 > https://github.com/nodejs/node/pull/11828 > so it would make sense to revert native and nativesdk versions as > well - if it isn't done in oe-core, I'll do it in our own layers to > keep the builds going. Hopefully we have a working 'revert' back to 1.0 in master now as there was simply too much breakage for this release. I would ask that people do try and figure out how to solve some of the 1.1 issues in the meantime, hopefully people can enable 1.1 with some PREFERRED_VERSION tweaks. Cheers, Richard