[Bug 1794589] Re: libssl1.0-dev conflicts libssl-dev

[RedScourge]

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 build various php modules use different versions of ssl, and so if you choose to build one, you cannot build the other, unless you take some convoluted path involving downloading source and compiling half the known universe, or simply not using certain php modules entirely. I did not encounter this same difficulty on 16.04 LTS as it seems that more of the -dev packages were built against 1.0.

Obviously I would not expect Ubuntu to support building versions of php
which are no longer in support, but I just wanted to mention that this
libssl-dev thing may cause lots of other issues in rarer use cases. Too
bad the openssl team did not have a better option to facilitate backward
compatibility between these versions.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssl1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1794589

Title:
  libssl1.0-dev conflicts libssl-dev

Status in net-snmp package in Ubuntu:
  Confirmed
Status in nodejs package in Ubuntu:
  Invalid
Status in openssl1.0 package in Ubuntu:
  Invalid
Status in net-snmp source package in Bionic:
  Confirmed
Status in nodejs source package in Bionic:
  Invalid
Status in openssl1.0 source package in Bionic:
  Invalid
Status in net-snmp source package in Cosmic:
  Confirmed
Status in nodejs source package in Cosmic:
  Invalid
Status in openssl1.0 source package in Cosmic:
  Invalid

Bug description:
  [impact]

  The libssl1.0-dev package conflicts with the libssl-dev package, so
  this leads to all packages that depend on libssl1.0-dev to conflict
  with all packages that depend on libssl-dev; as well as all packages
  that depend on those packages (and so on).

  [test case]

  On a Bionic system (or Cosmic), install libssl-dev, and/or any package that depends on it:
  http://qa.ubuntuwire.org/rdepends/v1/bionic/any/libssl-dev

  Then, try to install libssl1.0-dev, or any package that depends on it:
  http://qa.ubuntuwire.org/rdepends/v1/bionic/any/libssl1.0-dev

  see comment 15 for an example of some packages that are force-removed
  when installing libssl1.0-dev, due to conflict.

  [regression potential]

  TBD after fix is determined

  [other info]

  Original description:

  ---

  The fix for https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1779863
  is, not surprisingly, somewhat traumatic for some users.

  In my case, installing libssl1.0-dev causes libcurl4-openssl-dev,
  libssh-dev, and libssl-dev to be uninstalled, which makes some of our
  internal packages fail to build.

  Commenting out universe from bionic-updates in /etc/apt/sources.list
  would work around this, but that's not going to fly for everybody.

  nodejs appears to be the tail wagging the dog now, and that's rather
  uncomfortable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nodejs-dev (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 26 11:03:51 2018
  SourcePackage: nodejs
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (148 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1794589/+subscriptions