Bug #39556
Updated by Nathan Cutler almost 5 years ago
Environment: openSUSE 15.1 with Python 3 only ("python-base" RPM is not installed) When I run "./run-make-check.sh" on tip of nautilus (v14.2.1), it fails with the following message: <pre> > ceph-dashboard@0.0.0 env_build /home/smithfarm/src/ceph/smithfarm/ceph/src/pybind/mgr/dashboard/frontend > cp src/environments/environment.tpl.ts src/environments/environment.prod.ts && cp src/environments/environment.tpl.ts src/environments/environment.ts && node ./environment.build.js CC examples/nvme/nvme_manage/nvme_manage.o Environment variables have been set LINK examples/nvme/nvme_manage/nvme_manage As a forewarning, we are moving the CLI npm package to "@angular/cli" with the next release, which will only support Node 6.9 and greater. This package will be officially deprecated shortly after. To disable this warning use "ng set --global warnings.packageDeprecation=false". CC examples/nvme/arbitration/arbitration.o You have to be inside an angular-cli project in order to use the build command. npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! ceph-dashboard@0.0.0 build: `npm run env_build && ng build "--progress=false"` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the ceph-dashboard@0.0.0 build 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-01T08_34_25_369Z-debug.log make[3]: *** [src/pybind/mgr/dashboard/CMakeFiles/mgr-dashboard-frontend-build.dir/build.make:2944: ../src/pybind/mgr/dashboard/frontend/dist] Error 1 </pre> And, in a perhaps related development, in a different environment (openSUSE Leap 15.1 with both Python 2 and Python 3 installed When installed), when I run make-dist install-deps.sh on tip of master branch, I get: <pre> 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 </pre>