Please remove node-puppeteer source and binaries from jammy

[Bryce Harrington]

node-puppeteer provides an API to control Chrome or Chromium in a headless environment.
The package has dependencies on chromium and chromium-sandbox, but unlike Debian we do not carry these packages in Ubuntu main or universe, so node-puppeteer is blocked from being accepted into Ubuntu:

node-puppeteer (- to 13.1.0+dfsg-4)

    Migration status for node-puppeteer (- to 13.1.0+dfsg-4): BLOCKED: Rejected/violates migration policy/introduces a regression
    Issues preventing migration:
    node-puppeteer/amd64 has unsatisfiable dependency
    Additional info:
    uninstallable on arch amd64, not running autopkgtest there
    38 days old

There are no rdepends for this package (obviously; it's never been present in any Ubuntu release), and its use case is narrow even if we did ship Chromium, so there does not seem to be any compelling reason to include this.

Please delete node-puppeteer source and binary packages from jammy-proposed, and also please add a sync block so this doesn't attempt to autoresync going forward.

[Christian Ehrhardt  (paelzer)]

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 :-)

[Christian Ehrhardt  (paelzer)]

The rest is as reported, it makes sense to be removed and really is only present in jammy-proposed.

$ rma node-puppeteer
Debian
node-puppeteer | 13.4.1+dfsg-1 | testing | source, all
node-puppeteer | 13.4.1+dfsg-1 | unstable | source, all
Ubuntu:
node-puppeteer | 13.1.0+dfsg-4 | jammy-proposed/universe | source, all

And as you see it is also outdated compared to what is in debian as it is stuck since being synced and no more synced since then. The new version has only updated versions in the dependencies - not a fix to the problem.

Source and binary have the same name, no other binaries or rdeps.

Ack and done

$ ./remove-package -m "unsatisfiable chrome dependency (LP: #1967048)" --suite jammy-proposed node-puppeteer
Removing packages from jammy-proposed:
 node-puppeteer 13.1.0+dfsg-4 in jammy
  node-puppeteer 13.1.0+dfsg-4 in jammy amd64
  node-puppeteer 13.1.0+dfsg-4 in jammy arm64
  node-puppeteer 13.1.0+dfsg-4 in jammy armhf
  node-puppeteer 13.1.0+dfsg-4 in jammy i386
  node-puppeteer 13.1.0+dfsg-4 in jammy ppc64el
  node-puppeteer 13.1.0+dfsg-4 in jammy riscv64
  node-puppeteer 13.1.0+dfsg-4 in jammy s390x
Comment: unsatisfiable chrome dependency (LP: #1967048)
Remove [y|N]? y
1 package successfully removed.