On Fri, Jan 8, 2021 at 12:44 pm, Jonas Smedegaard <jo...@jones.dk>
wrote:
I don't understand - how is node-babel7 affected by how yarnpkg
declares
(build-)dependencies against it?
node-babel7 will still be affected by the update-alternatives bug when
manpages missing.
What I suggest is to improve the package yarnpkg to replace any
runtime
and build-time package relations on node-babel7 to instead be on each
actually needed node-$module package, virtual or not.
(and yes, it should work fine for autopkgtest as well - a previous
failure I caused was due to lack of appending (>= 7) for a virtual
package also provided by older babel6 package).
That is tangential to this particular bug. That is an improvement, yes,
but will not solve this bug without separate binary for @babel/runtime
module, as it will still pull in node-babel7 and missing man pages will
trigger this bug.
