It appears that nodejs-yarn package only has "nodejs-yarn" command, not "yarn". This is very counterintuitive. /usr/bin/yarn is provided by cmdtest. Could it be provided by nodejs-yarn instead? $ rpm -q nodejs-yarn nodejs-yarn-1.9.2-1.fc29.noarch Thanks.
I also think, that there should be a symlink from /usr/bin/yarn to /usr/bin/nodejs-yarn.
I wanted to avoid having conflicts, as /usr/bin/yarn is provided by cmdtest and hadoop-yarn (https://bugzilla.redhat.com/show_bug.cgi?id=1507312) and I didn't want to add another one. Requesting needinfo from package maintainers for some more opinions on this issue.
I'm not familiar with nodejs-yarn at all, nor cmdtest, but it may be possible for hadoop-yarn to just use /usr/bin/hadoop-yarn and avoid /usr/bin/yarn completely. I'll reopen that rhbz#1507312 for that.
I think /usr/bin/yarn should be provided. Some script use it by default. Users can choose which packages to install. $ git clone https://github.com/Microsoft/vscode $ cd vscode $ yarnpkg /bin/sh: yarn: command not found child_process.js:651 throw err; ^ Error: Command failed: yarn -v /bin/sh: yarn: command not found May be, we can use `alternatives` to provides a command link. $ alternatives --install /usr/bin/yarn yarn /usr/lib/node_modules/yarn/bin/yarn.js 90
alternatives should not be sued to flip between totally different things with name collision. This needs a cooperation between the package maintainers. I can tell that the "yarn" command missing is a big deal when dealing with nodejs. However I have never heard of cmdtest or hadoop-yarn at all. I realize that my view here is limited. Maybe we should reach out to devel@?
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
$ repoquery --repo=rawhide -l nodejs-yarn | grep /usr/bin /usr/bin/nodejs-yarn /usr/bin/yarnpkg Also: $ repoquery --repo=rawhide -f /usr/bin/yarn So the "slot" is free now, at least on rawhide.
FEDORA-2020-766ce5adae has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-766ce5adae
nodejs-yarn-1.21.1-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-766ce5adae
nodejs-yarn-1.21.1-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.