Project

General

Profile

Actions

Bug #39556

closed

npm problem causes "make-dist" to fail when directory contains colon character

Added by Nathan Cutler about 5 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific, octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Environment: openSUSE Leap 15.1, Tumbleweed, Python 2+3 and Python 3 only

tl;dr - when the directory path contains a colon (':') character, make-dist fails in the npm phase with the error messages shown below. When the directory does not contain a colon, the bug does not manifest and the npm phase succeeds.

When I run make-dist on tip of master branch, I get:

Collecting nodeenv
Installing collected packages: nodeenv
Successfully installed nodeenv-1.3.3
 * Install prebuilt node (10.13.0) ..... done.
 * Appending data to /tmp/tmp.PRGQz8NIRr/bin/activate
 * Appending data to /tmp/tmp.PRGQz8NIRr/bin/activate.fish

> fsevents@1.2.4 install /home/smithfarm/obs/filesystems:ceph:octopus:upstream/ceph/tmp.gs6pfXbgP2/src/pybind/mgr/dashboard/frontend/node_modules/fsevents
> node install

> node-sass@4.11.0 install /home/smithfarm/obs/filesystems:ceph:octopus:upstream/ceph/tmp.gs6pfXbgP2/src/pybind/mgr/dashboard/frontend/node_modules/node-sass
> node scripts/install.js

Cached binary found at /home/smithfarm/.npm/node-sass/4.11.0/linux-x64-64_binding.node

> node-sass@4.11.0 postinstall /home/smithfarm/obs/filesystems:ceph:octopus:upstream/ceph/tmp.gs6pfXbgP2/src/pybind/mgr/dashboard/frontend/node_modules/node-sass
> node scripts/build.js

Binary found at /home/smithfarm/obs/filesystems:ceph:octopus:upstream/ceph/tmp.gs6pfXbgP2/src/pybind/mgr/dashboard/frontend/node_modules/node-sass/vendor/linux-x64-64/binding.node
Testing binary
Binary is fine

> fsevents@1.2.7 install /home/smithfarm/obs/filesystems:ceph:octopus:upstream/ceph/tmp.gs6pfXbgP2/src/pybind/mgr/dashboard/frontend/node_modules/@compodoc/compodoc/node_modules/fsevents
> node install

> @compodoc/compodoc@1.1.9 postinstall /home/smithfarm/obs/filesystems:ceph:octopus:upstream/ceph/tmp.gs6pfXbgP2/src/pybind/mgr/dashboard/frontend/node_modules/@compodoc/compodoc
> opencollective postinstall

sh: opencollective: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! @compodoc/compodoc@1.1.9 postinstall: `opencollective postinstall`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @compodoc/compodoc@1.1.9 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/smithfarm/.npm/_logs/2019-05-01T11_31_10_328Z-debug.log

This only happens if the directory path contains a colon (':') character.


Related issues 3 (0 open3 closed)

Copied to Ceph - Backport #50356: nautilus: npm problem causes "make-dist" to fail when directory contains colon characterResolvedNathan CutlerActions
Copied to Ceph - Backport #50357: octopus: npm problem causes "make-dist" to fail when directory contains colon characterResolvedNathan CutlerActions
Copied to Ceph - Backport #50358: pacific: npm problem causes "make-dist" to fail when directory contains colon characterResolvedNathan CutlerActions
Actions

Also available in: Atom PDF