| Summary: | yarn - A fast, reliable, and secure dependency management for nodejs/npm | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | New RPM package request | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | chb0, lovaren, marja11 |
| Version: | Cauldron | Keywords: | PATCH |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://yarnpkg.com | ||
| Whiteboard: | |||
| Source RPM: | yarn | CVE: | |
| Status comment: | |||
| Attachments: |
Proposal spec file
New proposal spec file New working proposal spec file New proposal spec file for the latest version |
||
|
Description
Kristoffer Grundström
2018-12-18 01:48:38 CET
Assigning this package request to all packagers collectively. On a voluntary basis, one of them might, if there are no license or other legal issues, want to integrate it to the distribution and maintain it for bug and security fixes. Keywords:
(none) =>
PATCH Created attachment 11883 [details]
New working proposal spec file
I have now managed to build yarn from this spec file.
Anyone able to push it to Cauldron before Mageia 8 is released?
Attachment 11197 is obsolete:
0 =>
1 However, when building with rpmbuild -ba I got this: pcregrep: line 53397 of file $USER/rpmbuild/BUILDROOT/yarn-1.22.5-1.mga7.x86_64/usr/share/yarn/lib/cli.js is too long for the internal buffer pcregrep: check the --buffer-size option pcregrep: line 53397 of file $USER/rpmbuild/BUILDROOT/yarn-1.22.5-1.mga7.x86_64/usr/share/yarn/lib/cli.js is too long for the internal buffer pcregrep: check the --buffer-size option Created attachment 12706 [details]
New proposal spec file for the latest version
I just built the latest official version of Yarn and here's my spec file.
If you need the src.rpm I'd be happy to add it to.
Attachment 11883 is obsolete:
0 =>
1 I don't know if it's an issue specific for Mageia, but yarn update fails due to not having the proper permissions. A patch to fix this would be nice as well. Hi. I just discovered this report. I have imported a yarnpkg package into MGA9, some time ago. Status:
NEW =>
RESOLVED |