Comment 2 for bug 1967048

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.