The spec file has:
%if 0%{?fedora} == 39 || 0%{?fedora} == 40 || 0%{?rhel} == 10
%global nodejs_default %{nodejs_pkg_major}
%endif
But nodejs20-20.11.1-1.fc41 was built in Fedora 41.
As a result, there is no /usr/bin/node.
The following packages are broken:
$ repoquery -q --repo=rawhide{,-source} --whatrequires /usr/bin/node
cjdns-tools-0:21.1-14.fc40.noarch
csslint-0:1.0.5-11.fc40.noarch
jowl-0:2.2.0-2.fc38.noarch
magicmirror-0:2.26.0-1.fc40.noarch
magicmirror-module-airnow-0:1.0.0^20200824gitefddeb3-4.fc40.noarch
magicmirror-module-onthisday-0:0.1.1^20220120git459fd61-2.fc39.noarch
mediawiki-0:1.40.0-3.fc40.noarch
nodejs-bash-language-server-0:5.1.1-3.fc40.noarch
nodejs-buble-0:0.20.0-9.fc40.noarch
nodejs-diagnostic-language-server-0:1.15.0-4.fc40.noarch
nodejs-less-0:4.1.2-10.fc40.noarch
nodejs-linefix-0:0.1.1-17.fc40.noarch
nodejs-marked-0:2.0.0-8.fc40.noarch
nodejs-packaging-0:2023.10-4.fc40.noarch
nodejs-replace-require-self-0:1.1.1-18.fc40.noarch
pnpm-0:8.12.0-3.fc40.noarch
python-nodeenv-0:1.8.0-6.fc40.src
qt5-qtwebchannel-examples-0:5.15.12-3.fc40.x86_64
rubygem-ejs-0:1.1.1-20.fc40.src
rubygem-execjs-0:2.8.1-8.fc40.src
rubygem-sprockets-0:4.2.0-4.fc40.src
statsd-0:0.8.6-9.fc40.noarch
typescript-0:5.1.3-3.fc40.noarch
uglify-js-0:3.17.4-3.fc40.noarch
yarnpkg-0:1.22.19-8.fc40.noarch
Other packages might be broken as well.
Reproducible: Always
Steps to Reproduce:
1 BuildRequire /usr/bin/node
2 build the package in rawhide Koji or non-mirrored mock
3 it fails to install /usr/bin/node
Actual Results:
failure
Expected Results:
success
Comment 1Stephen Gallagher
2024-02-15 14:02:07 UTC
Thanks for spotting this, Miro. Indeed, I forgot that I need to temporarily keep Node.js 20 in F41 until they release v22 (probably in April).
I've just kicked off a build to fix this.
Comment 2Fedora Update System
2024-02-15 17:59:14 UTC
Comment 3Fedora Update System
2024-02-15 18:03:29 UTC
FEDORA-2024-36311c673e (nodejs20-20.11.1-2.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 4Stephen Gallagher
2024-02-15 20:39:15 UTC
*** Bug 2264473 has been marked as a duplicate of this bug. ***