@mackuba, yes, I understand. To me it seems like a repository circular dependency. The problem is not directly with nodejs per-se, but with the interactions with the update and other packages that it depends on. I am happy to see this is not just me. What I do not fully grok is why so few people have run across this situation? It makes me ponder if there is a certain set of conditions that need to be met for this situation to rear itself. Given the metadata shows the dependency conflict I feel it
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861712 Title: nodejs-dev package pinned to libssl 1.0.* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1861712/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
