@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?
@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?