I agree it doesn't make sense as-is and should be removed from jammy. I do not (yet) agree on a sync blocker. Other packages that modify/enhance/need chrome* are doing it differently: Example: Package: chrome-gnome-shell ... Suggests: chromium | chromium-browser, firefox Breaks: firefox (<< 56), firefox-esr (<< 56) Enhances: chromium, chromium-browser, firefox
Instead I'd ask you to make a trivial proposal to Debian to either generally reduce this dependency (totally fine if it could also control remote chromiums) or one of the "if ubuntu then suggest". If there is hard refusal, well then yes the use case is rather special and it might be blocked. But I'd not give up immediately :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967048 Title: Please remove node-puppeteer source and binaries from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-puppeteer/+bug/1967048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
