The package currently depends on compat-openssl10-devel which will be removed. It needs to be ported to OpenSSL 1.1 API and built against regular openssl-devel package. If you need help with porting the package feel free to contact me.
(In reply to Tomas Mraz from comment #0) > The package currently depends on compat-openssl10-devel which will be > removed. It needs to be ported to OpenSSL 1.1 API and built against regular > openssl-devel package. > > If you need help with porting the package feel free to contact me. This *cannot* happen. We need this to remain for F27 (but we can drop it in F28). The reason is that Node.js upstream has only added support for OpenSSL 1.1 as of version 9.x. However, 9.x will be EOL before Fedora 28 is (it ends all support in July 2018). There has also been a long and involved upstream discussion about this support[1] and why it had to wait until 9.x. As a result, we need to continue to carry Node.js 8.x in Fedora until Fedora 29. In May 2018, Node.js will release version 10.x which we will carry in F29 and F30, which supports OpenSSL 1.1. In short, please don't remove compat-openssl10-devel in Fedora 28, as it will force us to be unable to ship Node.js in that release. This is a critical piece of software. Also, changes of this magnitude really need to go through the https://fedoraproject.org/wiki/Mass_package_changes process, which this did not. In particular, there was no gaining of consensus. Also, a change like this probably should go to FESCo via the Change Process, since it affects a huge amount of software. [1] https://github.com/nodejs/node/issues/4270
I did not say when it will be removed. I just said it will be at some point.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
Node.js 10.x (slated to be default in Fedora 29) has upstream support for OpenSSL 1.1.
Node.js v8.x is compatible with both versions of openssl