You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previous versions of the Debian nodejs packages contained a postinst script which called update-alternatives to set up /usr/bin/nodejs, but recent versions no longer do this. As a result, scripts that depended on /usr/bin/nodejs being present no longer function on newly built machines, while they do still work on machines that upgraded nodejs package from a version with that script.
(I checked by downloading the .deb file, running ar x ${file} to extract it, extracting the control file with tar -xf control.tar.*, and examining postinst if present.)
This is closely related to #1095, which is asking about Ubuntu packages, but I'm not sure if packages for Debian are distinct.
As a workaround, users can manually run the command that used to be in postinst:
Previous versions of the Debian nodejs packages contained a
postinst
script which calledupdate-alternatives
to set up/usr/bin/nodejs
, but recent versions no longer do this. As a result, scripts that depended on/usr/bin/nodejs
being present no longer function on newly built machines, while they do still work on machines that upgraded nodejs package from a version with that script.I've spot checked a few:
update-alternatives
update-alternatives
(I checked by downloading the
.deb
file, runningar x ${file}
to extract it, extracting the control file withtar -xf control.tar.*
, and examiningpostinst
if present.)This is closely related to #1095, which is asking about Ubuntu packages, but I'm not sure if packages for Debian are distinct.
As a workaround, users can manually run the command that used to be in
postinst
:The text was updated successfully, but these errors were encountered: