#1004419 nodejs:any prevents one to install nodejs package from official upstream "nodesource" repo

Package:
nodejs
Source:
nodejs
Description:
evented I/O for V8 javascript - runtime executable
Submitter:
Jérémy Lal
Date:
2022-01-27 09:51:02 UTC
Severity:
normal
#1004419#5
Date:
2022-01-27 09:24:21 UTC
From:
To:
Sometimes it's useful to be able to swap between nodejs debian package
and somewhat "official" https://deb.nodesource.com releases.

Now that packages depend on nodejs:any, it's no longer possible to do that,
at least not without uninstalling many node-* modules.

Also i don't understand why debian packages would need to depend on nodejs:any
instead of plain nodejs.

Jérémy
#1004419#12
Date:
2022-01-27 09:44:59 UTC
From:
To:
Quoting Jérémy Lal (2022-01-27 10:24:21)

That sounds like an interoperability bug in that unofficial nodejs
package, not in this package.

A fully multiarch-compatible system can contain packages compiled for
multiple architectures installed side by side.

E.g. an amd64 CPU can execute both amd64 code and i386 code - you can
install a core amd64 system and choose to install an i386 nodejs.  The
nodejs runtime would only lookup arch-independent modules and modules
for its own arch - modules compiled for i386 would need to depend on
either native nodejs or foreign nodejs/i386 on a multiarch-system with
nodejs/i386 installed.

You can even mix binaries alien to the CPU - e.g. extend an ARM64 core
system with MIPS binaries.  Possibly they would then never really be
used, or possibly (I haven't tried yet) you can install qemu and run
emulated for those binaries.


 - Jonas
#1004419#17
Date:
2022-01-27 09:48:34 UTC
From:
To:
Le jeu. 27 janv. 2022 à 10:45, Jonas Smedegaard <jonas@jones.dk> a écrit :

Right, thank you for the explanation.
I forwarded the issue.

Jérémy