search

jitsi / jitsi-meet

Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
https://jitsi.org/meet
Apache License 2.0
22.94k stars 6.69k forks source link

Building after fresh checkout fails! #1726

Closed ctel closed 7 years ago

ctel commented 7 years ago

I have trouble "installing" jitsi-meet sources after successful checkout (version 152427e on master) into a clean directory. The development system runs on Ubuntu 16.04 LTS (within VirtualBox), npm (Version 3.5.2-0ubuntu4), nodejs-legacy (Version 4.2.6~dfsg-1ubuntu4.1). Everything has been installed as instructed here. Errors occour during the execution of npm install It seems that the webpack dependencies (is referenced multiple times as dependency) could not be fetched! Additionally I encountered several deprecation (easy-fix?) warnings during npm install (see below). This issue might be related to https://github.com/jitsi/jitsi-meet/issues/1718 Maybe this (stripped) log sheds light on the problem (I also stripped the loading bars for better readablity; [...] means I omitted a part to shorten this text):

npm WARN deprecated jssha@1.5.0: jsSHA versions < v2.0.0 will no longer receive features npm WARN deprecated strophe@1.2.4: This package is no longer maintained; use 'strophe.js' instead. WARN engine skatejs@0.13.17: wanted: {"node":">=0.12.x","npm":"2.x.x"} (current: {"node":"4.2.6","npm":"3.5.npm WARN deprecated minimatch@3.0.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated bower@1.7.7: ..psst! While Bower is maintained, we recommend Yarn and Webpack for *new* front-end projects! Yarn's advantage is security and reliability, and Webpack's is support for both CommonJS and AMD projects. Currently there's no migration path, but please help to create it: https://github.com/bower/bower/issues/2467 npm WARN deprecated ignore@2.2.19: several bugs fixed in v3.2.1 npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. npm WARN deprecated node-uuid@1.4.8: Use uuid module instead npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@1.0.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree. npm WARN deprecated node-uuid@1.4.7: Use uuid module instead [...] WARN engine loader-runner@2.3.0: wanted: {"node":">=4.3.0 <5.0.0 || >=5.10"} (current: {"node":"4.2.6","npm":"3.5.2"}) [...] ├─┬ @ atlassian/aui@6.0.6 [...] │ ├── UNMET DEPENDENCY eslint@2.1.0 [...] ├─┬ babel-preset-es2015@6.24.1 [...] │ ├── babel-plugin-transform-es2015-modules-amd@6.24.1 npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.2 npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.2 npm WARN eslint-plugin-mocha@2.0.0 requires a peer of eslint@^2.0.0 but none was installed. npm ERR! Linux 4.4.0-83-generic npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" npm ERR! node v4.2.6 npm ERR! npm v3.5.2 npm ERR! path ../acorn/bin/acorn npm ERR! code EROFS npm ERR! errno -30 npm ERR! syscall symlink npm ERR! rofs EROFS: read-only file system, symlink '../acorn/bin/acorn' -> '/media/sf_share/jitsi/jitsi-meet/node_modules/.bin/acorn' npm ERR! rofs This is most likely not a problem with npm itself npm ERR! rofs and is related to the file system being read-only. npm ERR! rofs npm ERR! rofs Often virtualized file systems, or other file systems npm ERR! rofs that don't support symlinks, give this error. │ │ └── babel-plugin-transform-strict-mode@6.24.1 [...] ├── UNMET PEER DEPENDENCY eslint@>=2.0.0 [...] ├── UNMET PEER DEPENDENCY webpack@2 [...] ├─┬ webpack-dev-server@2.4.5 [...] │ ├── UNMET PEER DEPENDENCY webpack@^1.0.0 || ^2.0.0 || ^3.0.0 [...] npm ERR! Linux 4.4.0-83-generic npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" npm ERR! node v4.2.6 npm ERR! npm v3.5.2 npm ERR! path npm-debug.log.1641229291 npm ERR! code ETXTBSY npm ERR! errno -26 npm ERR! syscall rename [...]

Is there an easy solution for my problem or is this a mayor problem? Should I try another version? Which one is considered stable enough to include latest fixes?

cyberbandya007 commented 7 years ago

@ctel, I don't believe jitsi-meet supports 16.04 LTS yet. Please try to build on ubuntu 14.04 and let us know how you find out.

cyberbandya007 commented 7 years ago

@ctel, you also need to upgrade your node and npm versions to make it work on ubuntu 14.04. 'npm install' fails on legacy nodejs. Try with latest stable version.

lyubomir commented 7 years ago 
npm ERR! path ../acorn/bin/acorn
npm ERR! code EROFS
npm ERR! errno -30
npm ERR! syscall symlink
npm ERR! rofs EROFS: read-only file system, symlink '../acorn/bin/acorn' -> '/media/sf_share/jitsi/jitsi-meet/node_modules/.bin/acorn'
npm ERR! rofs This is most likely not a problem with npm itself
npm ERR! rofs and is related to the file system being read-only.
npm ERR! rofs
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

Is there anything special about the file system as mentioned in the above?

ctel commented 7 years ago

Yup that problem is probably not jitsi related: I checked out jitsi-meet within a host-shared folder of VirtualBox. The filesystem is writable, but symbolic links cannot be created. Strangely ubuntu reports that the filesystem not being writable, but creating folders and files work just fine, so the problem was unnoticed before. So this portion of the problem can be ignored... Thus I again cloned the repository and executed npm install at a safe location within my virtual user home, and the errors vanished. Only some warnings are still thrown (Skipping failed optional dependency /chokidar/fsevents: [...]), but I think thats okay? make still fails, but I will open another issue for that.