Closed
Bug 1343896
Opened 8 years ago
Closed 8 years ago
Fix yarn install breakage
Categories
(Conduit :: General, defect)
Conduit
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: davidwalsh, Assigned: davidwalsh)
Details
Attachments
(1 file)
Bunch of people just got hit with this:
https://github.com/yarnpkg/yarn/issues/2816
yarn started shipping starting with 7.7-alpine, which is preventing our own custom yarn install from running. Error is:
npm info linkStuff yarn@0.20.3
/usr/local/bin/yarnpkg -> /usr/local/lib/node_modules/yarn/bin/yarn.js
npm ERR! Linux 4.4.0-62-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "yarn@0.20.3"
npm ERR! node v7.7.0
npm ERR! npm v4.1.2
npm ERR! path /usr/local/bin/yarn
npm ERR! code EEXIST
npm ERR! Refusing to delete /usr/local/bin/yarn: node_modules/npm/bin/npm-cli.js symlink target is not controlled by npm /usr/local
npm ERR! File exists: /usr/local/bin/yarn
npm ERR! Move it away, and try again.
npm ERR! Please include the following file with any support request:
npm ERR! /npm-debug.log
ERROR: Service 'yarn' failed to build: The command '/bin/sh -c npm install -g yarn@0.20.3' returned a non-zero code: 1
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → dwalsh
Comment hidden (mozreview-request) |
Comment 2•8 years ago
|
||
mozreview-review |
Comment on attachment 8842898 [details]
autoland-ui: Update Node version to prevent yarn breakage (Bug 1343896).
https://reviewboard.mozilla.org/r/116638/#review118404
Ship it!
Attachment #8842898 -
Flags: review?(mars) → review+
Comment 3•8 years ago
|
||
mozreview-review |
Comment on attachment 8842898 [details]
autoland-ui: Update Node version to prevent yarn breakage (Bug 1343896).
https://reviewboard.mozilla.org/r/116638/#review118408
rs
Attachment #8842898 -
Flags: review+
Pushed by mcote@mozilla.com:
https://hg.mozilla.org/automation/conduit/rev/0c5ceb083096
autoland-ui: Update Node version to prevent yarn breakage . r=mars,mcote
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•