Wiki documentation for pinned node versions causes GPG key conflict.

[bridzius]

The Wiki indicates that the install script should not be used when pinning a Node version. It makes sense, because the install script always installs the latest minor version of a given major. When following the pinned node version documentation - one ends up with a GPG key conflicts because of different gpg keys that are used for the rpm and the binary.

One thing that the install script does, is update the GPG key from the default rpm key to https://rpm.nodesource.com/gpgkey/ns-operations-public.key.

Distribution Information:

• OS: RPM-based Linux

Node Version:

• Node: 20.10.0

To Reproduce
Steps to reproduce the behavior:

1. Follow Wiki to setup the fetching of a pinned node version, f.ex 20.10.0:

# install Node.js
NODEJS_VERSION=20.10.0 && \
(NODEJS_MAJOR_VERSION="${NODEJS_VERSION:0:2}" && \
dnf install https://rpm.nodesource.com/pub_$NODEJS_MAJOR_VERSION.x/nodistro/repo/nodesource-release-nodistro-1.noarch.rpm -y) && \
dnf install nodejs-$NODEJS_VERSION-1nodesource --setopt=nodesource-nodejs.module_hotfixes=1 -y 

Expected behavior
Installation should either succeed with the standard repo GPG key or the wiki instructions could include the step to update the repo with a custom gpg key as the setup_20.x script does.

[paulrutter]

@bridzius is there an update on this? It's currently breaking all of our builds not being able to install Node.js.

[paulrutter]

  dnf install --nogpgcheck -q -y https://rpm.nodesource.com/pub_20.x/nodistro/repo/nodesource-release-nodistro-1.noarch.rpm && \
  dnf install --nogpgcheck -q -y nodejs-20.9.0-1nodesource --setopt=nodesource-nodejs.module_hotfixes=1 && \

Probably also works as temporary workaround; running it now...

[JesusPaz]

I've already updated the wiki to use the new scripts