User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/112.0 Build Identifier: I have some dangling symlinks in /usr/ that seem to be owned by nodejs18 SRPM: $ ls -alh /usr/share/man/man5/package-json.5.gz lrwxrwxrwx. 1 root root 128 Apr 2 20:00 /usr/share/man/man5/package-json.5.gz -> ../nodejs-18/man5/builddir/build/BUILDROOT/nodejs18-18.15.0-6.fc38.x86_64/usr/lib/node_modules_18/npm/man/man5/package-json.5.gz This file doesn't exist, and also the BUILDROOT text in the path makes me think the path is computed incorrectly based on the build machine, and not the on-disk installation. $ find /usr/ -iname package-json.5.gz /usr/share/man/man5/package-json.5.gz /usr/share/man/nodejs-18/man5/package-json.5.gz /usr/share/man/nodejs-20/man5/package-json.5.gz $ rpm -qf /usr/share/man/man5/package-json.5.gz nodejs-npm-9.5.0-1.18.15.0.6.fc38.x86_64 This seems to affect a number of other npm man pages too? Reproducible: Always
FEDORA-2023-330f8b21f6 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-330f8b21f6
FEDORA-2023-29324909b4 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-29324909b4
FEDORA-2023-44b3119b5c has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-44b3119b5c
FEDORA-2023-5f266896a8 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5f266896a8
FEDORA-2023-330f8b21f6 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-330f8b21f6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-330f8b21f6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-44b3119b5c has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-44b3119b5c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-44b3119b5c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-5f266896a8 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5f266896a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5f266896a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.