Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reusable Vagrant Box for Builds #779

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

naftulikay
Copy link

@naftulikay naftulikay commented Jul 1, 2017

Because portability is king™.

WARNING

This is currently broken, due in part to some weird errors I get during building:

npm install
[vagrant@devel vagrant]$ npm install
[email protected] /vagrant
└── (empty)

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! Linux 3.10.0-514.el7.x86_64
npm ERR! argv "/usr/local/node-6.11.0/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! path /vagrant/node_modules/npm/node_modules/node-gyp/node_modules/semver/bin/semver
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod

npm ERR! enoent ENOENT: no such file or directory, chmod '/vagrant/node_modules/npm/node_modules/node-gyp/node_modules/semver/bin/semver'
npm ERR! enoent ENOENT: no such file or directory, chmod '/vagrant/node_modules/npm/node_modules/node-gyp/node_modules/semver/bin/semver'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR!     /vagrant/npm-debug.log
npm ERR! code 1
gulp build
[vagrant@devel vagrant]$ gulp build
module.js:471
    throw err;
    ^

Error: Cannot find module 'cordova-lib'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/vagrant/gulps/mobile.js:3:45)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)

Here is my npm-debug.log: npm-debug.log.zip

Not sure why it's not building. I would like to build the Electron app and package it for various Linux distributions.

Because portability is king™.
@wwebfor
Copy link
Member

wwebfor commented Jul 3, 2017

Hi, awesome job, but would it be possible to push it to dev branch instead? Also the Electron app is here now https://github.com/Laverna/laverna-desktop

@naftulikay
Copy link
Author

I can rebase on dev branch, but can you please update your documentation to point to Laverna Desktop as a separate repository? I honestly don't know what is what anymore, I've had quite a hard time getting this together.

@naftulikay
Copy link
Author

Additionally, there are no releases listed on Laverna Desktop in that repository so it appears I'm still on my own to get things building in a predictable way. I'm happy to contribute and help, but I'm very confused as to how this project is organized.

@wwebfor
Copy link
Member

wwebfor commented Jul 5, 2017

Sorry for confusion and late response. Long story short, on Laverna/laverna-desktop we keep just Electron related stuff. On Laverna/laverna we keep the core app. Instructions how to build laverna-desktop: https://github.com/Laverna/laverna-desktop#development

@naftulikay
Copy link
Author

@wwebfor should I contribute this work to that other repository?

@wwebfor
Copy link
Member

wwebfor commented Jul 7, 2017

@naftulikay yes, if possible.

@naftulikay
Copy link
Author

I will be submitting a pull request soon to Laverna Desktop. I am trying to build Laverna locally first so I can test that the package actually works over there.

@naftulikay
Copy link
Author

FWIW this project does not build on either Node 6 (stable) or Node 8 (latest) within this Vagrant box. We can merge this pull request, but until the issues are resolved, this won't change anything.

Attached are logs for both versions of Node.

npm-debug.log.gz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants