> Theoretically Canonical could upgrade bionic's nodejs to use the
system's primary openssl.
This isn't possible. It would resurface bug 1779863. The nodejs version
in Ubuntu Bionic requires a specific version of OpenSSL to remain
compatible with external third party modules, since the version of
I have the same problem (bionic):
- aptitude is showing 2 uninstalled updates, libmysqlclient-dev and
libmysqlclient20
- I can't update them, because they require libssl-dev
- if I decide to install libssl-dev, I need to uninstall libssl1.0-dev
- if I do that, I would need to remove nodejs-dev
another day wasted trying to work out why things were not running on
Ubuntu 20.04 and its because of libssl1.0-dev needed which conflicts
with libssl-dev ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, it's hard to imagine that working, I fear.
Theoretically Canonical could upgrade bionic's nodejs to use the system's
primary openssl.
That is also not likely to happen, though, as it is a lot of work, and still
might not please nodejs users fully. (Plus it could break some users.)
--
You
Would it be possible to pick one openssl version and statically compile
the ones that use other, or have some simple tool that helps you point a
build process to the required version ?
e.g. that the libssl package tries *less* to be a seamless upgrade, when
it is not a seamless upgrade either
Well, yes. And as a result, the nodejs package on bionic is completely broken
when you actually try to use it for any project.
So, I guess one should avoid bionic if one uses nodejs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Default implementation of openssl in bionic is 1.1.1.
There is a small amount of packages that uses openssl1.0 at runtime in bionic,
because packages in question did not migrate to 1.1.1 in time for bionic
release.
It is not possible to co-install openssl 1.1.1 & 1.0 development headers and
** Tags added: bionic-openssl-1.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage notifications about this bug go to:
Still happens on 18.04 , nodejs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage notifications about this bug go to:
Affects me too. We are having to (re-)package our own version of
nodejs-dev with depend on libssl-dev instead of libssl1.0-dev in order
to use nodejs without uninstalling hundreds of other debian package on
an 18.04 system.
Surprised this is still open over a year after reporting.
--
You
Trying to build https://github.com/mit-pdos/noria without removing
node.js Ubuntu 18.04 needs to fix it's node.js package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
Yeah... I suspect the OpenSSL folks are painfully aware of that, and
future versions will likely be much better at preserving compatibility.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
While not relevant to nodejs, I'll add an anecdote that I was trying to build
older versions of php via phpbrew on 18.04 for development purposes, and ran
into a similar issue due to this libssl1.0-dev vs libssl1.1-dev issue.
The issue is that seemingly some of the -dev libraries required to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: net-snmp (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
** Also affects: net-snmp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: net-snmp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: net-snmp (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
It's worse than that. Developers who use nodejs in their apps, and have
to use libssl-dev, are simply screwed. Even moving to a container won't
help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
nodejs 8.x series uses libssl1.0-dev (OpenSSL 1.0.2) across all linux
distributions and upstream.
nodejs 10.x series uses libssl-dev (OpenSSL 1.1.0+) across all linux
distributions and upstream.
libssl1.0-dev and libssl-dev are intentionally non-coinstallable, as
they both own the same include
I see that people who use nodeenv potentially can get trapped, because
of:
$ apt show nodeenv | grep -e Package -e Depends
Package: nodeenv
Depends: python3-pkg-resources, python3, python3:any (>= 3.3.2-2~), make, gcc
(>= 4:4.9.1) | nodejs, g++ (>= 4:4.9.1) | nodejs, libssl-dev | nodejs,
** Changed in: nodejs (Ubuntu Bionic)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage notifications
I was able to install the nodejs package (8.11.4~dfsg-0ubuntu1)
https://packages.ubuntu.com/cosmic/nodejs
on Ubuntu 18.10 with "sudo apt-get install nodejs", but when I tried to install
npm (5.8.0+ds-2)
https://packages.ubuntu.com/cosmic/npm
It failed due to nodejs-dev depending on
Even with lxd or schroot, you won't be able build anything against libssl-dev
if your build script happens to need any of the nodejs modules that use openssl.
So that's not really much of a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Sun, Feb 24, 2019 at 10:26:54PM -, David wrote:
> Steve Langasek, when you wrote
> > The workaround is for each software component to be built in its own
> > separate environment with the -dev packages that it requires.
> what did you mean by "separate environment"?
> Do I have to buy a
I think the advice is harder to follow than it looks. Many node packages
require libssl-1.0-dev,
and you can't install them on a system used to develop c/c++ apps that require
libssl-dev.
To wit:
$ sudo apt install -s node-websocket libssl-dev
...
node-websocket : Depends: nodejs-dev (>=
Steve Langasek, when you wrote
> The workaround is for each software component to be built in its own
> separate environment with the -dev packages that it requires.
what did you mean by "separate environment"?
Do I have to buy a separate computer to use nodejs, or is there some way to
have
Le mer. 13 févr. 2019 à 18:55, Dan Kegel a écrit :
> In hopes of being able to create a ppa that reduces the pain level a
> bit, I tried rebuilding a newer nodejs for ubuntu 18.04 using the
> debian/ubuntu nodejs git repo.
>
> Using the source from 19.04's runs into quite a few test failures (
>
In hopes of being able to create a ppa that reduces the pain level a
bit, I tried rebuilding a newer nodejs for ubuntu 18.04 using the
debian/ubuntu nodejs git repo.
Using the source from 19.04's runs into quite a few test failures (
https://github.com/nodejs/help/issues/1760 ).
I just re-read kapouer's comments. They seem spot on.
I also re-read vorlon's comments. They have a vaguely disturbing
attitude along the lines of 'Why are you using Ubuntu to develop
software on? It's only for running software somebody else built
already.'
--
You received this bug
You could try
https://github.com/nodesource/distributions/blob/master/README.md
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage
I hit this too and If I understand this correctly the only way out is
now to install a custom version of nodejs and npm as both packages
forces install of libssl1.0-dev and I can not allow that package in as
it breaks other builds.
:( really nasty error this one. fails on 18.04 and 18.10.
any
** Changed in: nodejs (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage notifications about
That was the correct solution, and I sympathise with your rant.
Node is an ecosystem, and shipping a version of node that can't handle
native libraries is like sticking a fork in the eyes of the users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I fixed this by installing the newer nodejs version from upstream, which
is better for our students anyway. Sorry about the rant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
I am maintaining Ubuntu installations here at University of Helsinki,
where I try to provide a single environment for as many users as
possible, where the students and researchers are also developers, and
can't always be given administrator rights. Our students need nodejs for
their studies, but
I uploaded the backports of xmltooling, xml-security-c, and opensaml2 to
https://launchpad.net/~dank/+archive/ubuntu/openssl-uplift
and wrote it up at http://kegel.com/linux/openssl-ubuntu18.04-snafu/
That might be enough to let us limp by now that we've given up on the
nodejs packaged with
Those two weren't hard; I also had to backport opensaml2-tools. I can
imagine a little ppa with those three packages and maybe a few more;
using the ppa would let you rebuild your app using the backported
packages (and prevent you from building against the old packages, as the
new -dev's would
The next place this reared its ugly head was libxmltooling7 / libxml-
security-c-dev, and I don't see an alternate available.
Looks like ubuntu 18.10 has solved that bit. Maybe the answer for me is
to give up on 18.04 and use 18.10 / 19.04 / 19.10 / 20.04. I really
don't think our product folks
{Thank,curse} you for offering that solution. I will have a look!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage notifications about
On Fri, Nov 02, 2018 at 11:51:20PM -, Dan Kegel wrote:
> Our project also links against libssh-dev (sorry, I meant to mention that),
> which has the same problem, but lacks a libssh-openssl1.0-dev.
Ok. But it does have a libssh-gcrypt-dev, is there any chance this meets
your needs?
--
You
Our project also links against libssh-dev (sorry, I meant to mention that),
which has the same problem, but lacks a libssh-openssl1.0-dev.
Also, it's somewhat jarring to have to change dependency names
when we build against ubuntu 18.04 vs. 16.04; we can do that,
and have done it, but it adds a
On Fri, Nov 02, 2018 at 09:19:56PM -, Dan Kegel wrote:
> Yup, I have a package that uses node and requires libssl-dev and
> libcurl-openssl.
Ok, thanks for clarifying.
But there is a build of libcurl-openssl linked against libssl1.0 in 18.04,
and therefore compatible with nodejs
I've been really happy with Ubuntu for ten years, but this particular situation
is making me scratch my head. Might want to get Mark's input here -- is Ubuntu
intended to be a
curated ecosystem that works well as a platform for both proprietary and open
source software?
--
You received this
Yup, I have a package that uses node and requires libssl-dev and
libcurl-openssl.
It was rather jarring when it stopped building because of the update to
node.
If you're saying that Ubuntu is not suitable for developing proprietary
software that uses node, libssl, and libcurl, well, I guess
On Fri, Nov 02, 2018 at 08:01:23PM -, Dan Kegel wrote:
> The following packages have unmet dependencies:
> nodejs-dev : Depends: libssl1.0-dev (>= 1.0.2) but it is not going to be
> installed
> E: Unable to correct problems, you have held broken packages.
> In other words, the current
Here's a short way to see the failure:
1) make sure /etc/apt/sources.list has bionic-updates enabled for universe (and
multiverse?)
2) sudo apt update
3) sudo apt install nodejs-dev libssl-dev
...
The following packages have unmet dependencies:
nodejs-dev : Depends: libssl1.0-dev (>= 1.0.2)
Le ven. 2 nov. 2018 à 20:01, Steve Langasek
a écrit :
> On Fri, Nov 02, 2018 at 06:19:54PM -, kapouer wrote:
> > - the NODE_MODULE_VERSION advertised by ubuntu or debian does not match
> the
> > one provided by upstream, so it needs to be changed.
>
> How do you mean? The previous SRU of
On Fri, Nov 02, 2018 at 06:19:54PM -, kapouer wrote:
> - the NODE_MODULE_VERSION advertised by ubuntu or debian does not match the
> one provided by upstream, so it needs to be changed.
How do you mean? The previous SRU of nodejs was specifically intended to
address the issue of binary
On November 2, 2018 11:04:43 AM PDT, Dan Kegel wrote:
>Then my original bug report was correct. nodejs needs to be updated to
>a
>version that uses ubuntu 18.04's openssl instead of using the
>incompatible one. Shall I refile?
Could you please clarify what it is you're trying to achieve?
If
Le ven. 2 nov. 2018 à 19:10, Dan Kegel a écrit :
> Then my original bug report was correct. nodejs needs to be updated to a
> version that uses ubuntu 18.04's openssl instead of using the
> incompatible one. Shall I refile?
>
There are actually two issues:
- the one you just talked about
** Bug watch added: github.com/nodejs/node/issues #18770
https://github.com/nodejs/node/issues/18770
** Bug watch added: github.com/nodejs/TSC/issues #621
https://github.com/nodejs/TSC/issues/621
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Then my original bug report was correct. nodejs needs to be updated to a
version that uses ubuntu 18.04's openssl instead of using the
incompatible one. Shall I refile?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Le ven. 2 nov. 2018 à 18:41, Steve Langasek
a écrit :
> This is expected behavior. These two stacks are incompatible, and while
> they use symbol versions so will not cause overt ABI problems when
> loaded into the same namespace, there are still some opaque structures
> that could be problems
This is expected behavior. These two stacks are incompatible, and while
they use symbol versions so will not cause overt ABI problems when
loaded into the same namespace, there are still some opaque structures
that could be problems when passed between two libraries that each
depend on different
** Changed in: openssl1.0 (Ubuntu Bionic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: openssl1.0 (Ubuntu Cosmic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: openssl1.0 (Ubuntu Bionic)
Status: In Progress => Confirmed
** Changed in:
** Changed in: openssl1.0 (Ubuntu Bionic)
Importance: High => Medium
** Changed in: openssl1.0 (Ubuntu Cosmic)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
As an example of some of the packages that conflict with libssl1.0-dev,
due to conflict:
$ sudo apt install libssl1.0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
I've updated the bug title and description to more accurately reflect
the issue. As this isn't a bug in nodejs, i marked it as "invalid", and
added openssl1.0 as the target to fix.
** Description changed:
+ [impact]
+
+ The libssl1.0-dev package conflicts with the libssl-dev package, so this
+
** Summary changed:
- nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev, causing
build failures
+ libssl1.0-dev conflicts libssl-dev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
59 matches
Mail list logo
