On Mon, Mar 28, 2022 at 04:59:58PM +0200, Jérémy Lal wrote:
>
> Yes, actually all packages depending on libnode-dev/sid now need to depend
> on nodejs/sid, or else autopkgtest runs the tests against nodejs/testing,
> and that fails.
> I'll reupload them if that's all right.
>
> The other solution is to have /usr/bin/node12, /usr/bin/node14 and
> /usr/bin/node
> as an alternative link. Which is not going to happen for that transition.
Isn't the actual bug that the Breaks of libnode83 against libnode72 does
not cover the version in testing permitting obviously non-working
combinations of packages, and the correct solution is to make the
Breaks of libnode83 against libnode72 unversioned?
libnode is not a standalone library but a way to embed into a specific
nodejs version, is there a reason why libnode is a separate package and
not part of the nodejs package with Provides: libnode83?
Other ecosystems are doing it in a similar way, e.g. with perlapi-5.34.0
Transition happened anyway...