[Pkg-javascript-devel] Bug#1117466: [3]3 messages in conversationRe: Bug#1117466: npm: Executing command npm always fails
Jérémy Lal
kapouer at melix.org
Sun Nov 9 10:07:39 GMT 2025
Le dim. 9 nov. 2025 à 04:33, horsey_guy <horsey_guy at proton.me> a écrit :
> A new error appears with an update of `nodejs` to version
> `22.19.0+dfsg+~cs22.18.0-1` from `22.18.0+dfsg+~cs22.17.2-2`, although I am
> not sure if that is the reason:
>
> ```
> Cannot load externalized builtin:
> "internal/deps/amaro/dist/index:/usr/share/nodejs/amaro/dist/index.js".
> ----- Native stack trace -----
>
> 1: 0x7f72a4ca0b58
> node::builtins::BuiltinLoader::AddExternalizedBuiltin(char const*, char
> const*) [/usr/lib/x86_64-linux-gnu/libnode.so.127]
> 2: 0x7f72a4c33897 node::Environment::Environment(node::IsolateData*,
> v8::Isolate*, std::vector<std::__cxx11::basic_string<char,
> std::char_traits<char>, std::allocator<char> >,
> std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>,
> std::allocator<char> > > > const&,
> std::vector<std::__cxx11::basic_string<char, std::char_traits<char>,
> std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char,
> std::char_traits<char>, std::allocator<char> > > > const&,
> node::EnvSerializeInfo const*, node::EnvironmentFlags::Flags,
> node::ThreadId) [/usr/lib/x86_64-linux-gnu/libnode.so.127]
> 3: 0x7f72a4ba7f9c node::CreateEnvironment(node::IsolateData*,
> v8::Local<v8::Context>, std::vector<std::__cxx11::basic_string<char,
> std::char_traits<char>, std::allocator<char> >,
> std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>,
> std::allocator<char> > > > const&,
> std::vector<std::__cxx11::basic_string<char, std::char_traits<char>,
> std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char,
> std::char_traits<char>, std::allocator<char> > > > const&,
> node::EnvironmentFlags::Flags, node::ThreadId,
> std::unique_ptr<node::InspectorParentHandle,
> std::default_delete<node::InspectorParentHandle> >)
> [/usr/lib/x86_64-linux-gnu/libnode.so.127]
> 4: 0x7f72a4d2cce9
> node::NodeMainInstance::CreateMainEnvironment(node::ExitCode*)
> [/usr/lib/x86_64-linux-gnu/libnode.so.127]
> 5: 0x7f72a4d2ce31 node::NodeMainInstance::Run()
> [/usr/lib/x86_64-linux-gnu/libnode.so.127]
> 6: 0x7f72a4c76a74 node::Start(int, char**)
> [/usr/lib/x86_64-linux-gnu/libnode.so.127]
> 7: 0x7f72a3a29f68 [/usr/lib/x86_64-linux-gnu/libc.so.6]
> 8: 0x7f72a3a2a025 __libc_start_main [/usr/lib/x86_64-linux-gnu/libc.so.6]
> 9: 0x55d3bf91c031 _start [node]
> zsh: IOT instruction (core dumped) npm
>
That's fine, I uploaded nodejs 22 to experimental, because it was...
experimental.
I'm working on a new upload soon.
Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20251109/a06e52ac/attachment.htm>
More information about the Pkg-javascript-devel
mailing list