Bug 2059360

Summary: yarnpkg for fedora 35 installs binary '/usr/bin/%{fc_name}'
Product: [Fedora] Fedora Reporter: martin.kuehl
Component: yarnpkgAssignee: Zuzana Svetlikova <zsvetlik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: epel-packagers-sig, ngompa13, zsvetlik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 16:48:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description martin.kuehl 2022-02-28 21:35:02 UTC
Description of problem:
the current yarnpkg rpm installs a binary at the path '/usr/bin/%{fc_name}'

this is also visible at:
https://packages.fedoraproject.org/pkgs/yarnpkg/yarnpkg/fedora-35.html#files

Version-Release number of selected component (if applicable):
yarnpkg-1.22.10-3.fc35

How reproducible:
always

Steps to Reproduce:
1. dnf repoquery --list yarnpkg | grep /usr/bin

or look at https://packages.fedoraproject.org/pkgs/yarnpkg/yarnpkg/fedora-35.html#files

Actual results:
/usr/bin/%{fc_name}
/usr/bin/yarn
/usr/bin/yarnpkg

Expected results:
judging by the package for fedora 36:
/usr/bin/nodejs-yarn
/usr/bin/yarn
/usr/bin/yarnpkg

Additional info:
if i remember correctly that's rpm spec template syntax so there might be some stray escaping or something?
it's also apparently fixed for f36 so backporting that package would be just fine.

Comment 1 Neal Gompa 2022-03-01 17:11:49 UTC
This should be fixed with https://src.fedoraproject.org/rpms/yarnpkg/c/7769ea91f435e808a8b5991157a3cf2d0b880b89

Comment 2 Ben Cotton 2022-11-29 17:58:39 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 '35'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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.

Comment 3 Ben Cotton 2022-12-13 16:48:00 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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.