Pinning could be an option. Fixing the problem would be more fun. I hate
workarounds
--
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:
nodejs-dev conflicts with libcurl4-openssl-dev libss
Can you pin the version of nodejs (either in the command that installs
it, or in apt configuration)?
--
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:
nodejs-dev conflicts with libcurl4-o
I could, but then I would miss packages like php7.2-fpm or nginx.
--
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:
nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev,
Can you comment out universe from bionic-updates in /etc/apt/sources.list ?
That works for me, at least for now.
--
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:
nodejs-dev conflicts wit
@ddstreet The problem for my use case is: I am not abled to install npm
anymore, to use a dockerized ci, because the container do not build
anymore nor to update our 18.04 containers.
I understand WHY you did it, but I didn't expect to get a broken LTS
after half of a year. And a couple of package
Doing version transitions of popular libraries is not rocket science. It's a
hard slog.
I respect and thank the node and openssl maintainers.
I was not assigning blame, simply giving the symptom that caused my
world to explode.
--
You received this bug notification because you are a member of
@dank, nodejs isn't the only package whose -dev pkg (now) depends on
libssl1.0-dev; I think you've misassigned blame and the actual title of
this bug should be:
"libssl1.0-dev conflicts with libssl-dev (and deps), causing build
failures"
> When will ubuntu provide nodejs 10.x
that version is sti
Before: It was partial broken (in some special cases)
Now: Node is completely broken on every system
please revert the stupid changes!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Titl
This seems to have been released with this breakage in 8.10.0~dfsg-
2ubuntu0.3:
# apt-cache show nodejs | grep -Eo '(Version: .*$|libssl[^ ]*)'
Version: 8.10.0~dfsg-2ubuntu0.3
libssl1.0.0
Version: 8.10.0~dfsg-2ubuntu0.2
libssl1.1
Version: 8.10.0~dfsg-2
libssl1.1
--
You received this bug notifica
The workaround in my case is to:
apt install \
nodejs=8.10.0~dfsg-2ubuntu0.2 nodejs-dev=8.10.0~dfsg-2ubuntu0.2 \
npm \
libssl-dev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nodejs (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:
nod
When will ubuntu provide nodejs 10.x (said to depend on openssl 1.1)?
cosmic would be none too soon.
(I kind of wish Debian and Ubuntu allowed simultaneous installs of node8
and node10 ecosystems... e.g. by installing nodejs 10 to
/usr/lib/node/10 and using node10 prefixes on package names, and us
12 matches
Mail list logo
