@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 packages on a standard "LAMP stack" (also for other non php web environments) depend on libssl-dev. So my question is: how do I fix this in an automated way on several hundred container? Do I really have to package my own stuff? Do I have to open a bug in the libssl bugtracker? -- 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, causing build failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1794589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
