Joe, building LeoVue fails for me on Windows and Ubuntu

[Edward K. Ream]

Windows

See #735: Installing and running LeoVue

Ubuntu

I have, at one time or another this morning, done the following:

Reinstalled node.js

sudo apt install default-jdk

npm install -g dev-server

sudo npm install -g gyp
  # Seems to installed g...@0.5.0 ???
 
npm install appears to work, with warnings.

npm run dev fails as follows:

npm ERR! Linux 4.4.0-112-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "dev"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! leo-vue@1.6.4 dev: `node build/dev-server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the leo-vue@1.6.4 dev script 'node build/dev-server.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the leo-vue package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node build/dev-server.js

Joe (or anyone else), any help you could give would be appreciated.

I should be able to answer most questions about what I have just done because I did all the installs in separate consoles.

These consoles tell me everything except the order in which they were installed ;-) Hmm, maybe I should add a time stamp to the console prompts...

Edward

[Edward K. Ream]

On Monday, February 19, 2018 at 11:42:11 AM UTC-6, Edward K. Ream wrote:

It's troubling that the Ubuntu versions are so much lower than corresponding Windows versions.

Edward

[Jacob MacDonald]

Yes, I would suspect that ancient Node version first and foremost. The NodeJS site has a repository you can add for more up to date versions of their software.

--
You received this message because you are subscribed to the Google Groups "leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+...@googlegroups.com.
To post to this group, send email to leo-e...@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

[Kent Tenney]

Ubuntu main is too old, use the node repo
This is what I have:
curl -sL https://deb.nodesource.com/setup_6.x | bash -

which is a shortcut to add the node repo

after that

apt-get install nodejs

installs current version

--

You received this message because you are subscribed to the Google Groups "leo-editor" group.

To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscribe@googlegroups.com.

[Edward K. Ream]

On Monday, February 19, 2018 at 11:55:28 AM UTC-6, Kent Tenney wrote:

Ubuntu main is too old, use the node repo
This is what I have:
curl -sL https://deb.nodesource.com/setup_6.x | bash -

which is a shortcut to add the node repo

after that

apt-get install nodejs

installs current version

Thanks Jacob. Thanks Kent. I'll try again later today...

Edward

[Edward K. Ream]

On Monday, February 19, 2018 at 11:55:28 AM UTC-6, Kent Tenney wrote:

Ubuntu main is too old, use the node repo
This is what I have:
curl -sL https://deb.nodesource.com/setup_6.x | bash -

It turns out that the following is required (gnashes teeth):

curl -sL https://deb.nodesource.com/setup_6.x | sudo bash -

Edward

[Edward K. Ream]

On Monday, February 19, 2018 at 11:42:11 AM UTC-6, Edward K. Ream wrote:

> See #735: Installing and running LeoVue

Hurray! LeoVue now works properly for me on Ubuntu with Mozilla.  #735 presents a summary of what I did.

There are some fine points in #735.  When in doubt, I deleted the leovue folder, downloaded again with git clone, and reinstalled.

Edward

[Edward K. Ream]

On Monday, February 19, 2018 at 11:42:11 AM UTC-6, Edward K. Ream wrote:

I did all the installs in separate consoles. These consoles tell me everything except the order in which they were installed ;-) Hmm, maybe I should add a time stamp to the console prompts...

There's too much cruft in the approach.  Imo, it's better just to keep an accurate log of the commands I issued.

I ended up reinstalling the leovue folder four or five times. It would just add to the confusion if I kept lots of consoles around.

Edward

[Zoom.Quiet]

OT: Critical Linux filesystem permissions are being changed by latest
version · Issue #19883 · npm/npm
https://github.com/npm/npm/issues/19883

god bless NPM user

> --
> You received this message because you are subscribed to the Google Groups
> "leo-editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to leo-editor+...@googlegroups.com.

> To post to this group, send email to leo-e...@googlegroups.com.
> Visit this group at https://groups.google.com/group/leo-editor.
> For more options, visit https://groups.google.com/d/optout.

--
life is pathetic, go Pythonic! 人生苦短, Python当歌!
俺: http://zoomquiet.io
授: http://creativecommons.org/licenses/by-sa/2.5/cn/
怒: 冗余不做,日子甭过!备份不做,十恶不赦!
KM keep growing environment culture which promoting organization learning!

[Edward K. Ream]

On Fri, Feb 23, 2018 at 11:05 AM, Zoom.Quiet <zoom....@gmail.com> wrote:

OT: Critical Linux filesystem permissions are being changed by latest
version · Issue #19883 · npm/npm
    https://github.com/npm/npm/issues/19883

​Yikes! From the thread:

QQQ

1. Be a dev on one of the most critical pieces of on infrastructure of a widely used language.
2. Release new prerelease.
3. Do not use semantic versioning so it looks like a stable.
4. Advertise new build in emails and blog posts but don't mention it's a prerelease.
5. The update mechanism updates to next instead of latest for whatever reason
6. It bricks everyone's systems.
7. Users are reasonably upset.
8. Insult users for being upset.

It might be time for an expansion of the NPM team and a review of the current developers on it.

QQQ

Doesn't increase my confidence in node.js or its security.

Edward

[Joe Orr]

Sorry, was offline for a week. Still having problems?

I did a clean install on a new Ubuntu and no problems.

Also, it can be run with Docker (there is a Dockerfile now).

Joe

[Edward K. Ream]

On Wed, Feb 28, 2018 at 4:46 AM, Joe Orr <joe...@gmail.com> wrote:

Sorry, was offline for a week. Still having problems?

​I was able to build and run leovue on Ubuntu only.​

 

​The info item #735: Installing and running LeoVue contains detailed notes.

I have just updated the first comment in #735 to recap the present status.

Edward

[Joe Orr]

Oops.. thought I had removed xst4node and xmldom from package.json. Those require java, and that could be an issue for Windows.

I just removed those and tried an install on a new Windows installation and was able to get npm install to work with no problems.

The xslt4node and xmldom packages (which require java) are only needed for people who want to run the build-static script, which makes a set of javascriptless static pages. The xsl stylesheets which make the output are very simple but in the future they could be improved to e.g. support Jekyl templates so that Leo could be used for static site generation.

Joe

[Chris George]

I have been using Leo and Nikola to write, build and deploy a static site.

Nikola is written in python, so it was little more familiar to me than setting up a Ruby environment.

Chris

[Edward K. Ream]

On Wed, Feb 28, 2018 at 7:38 PM, Joe Orr <joe...@gmail.com> wrote:

Oops.. thought I had removed xst4node and xmldom from package.json. Those require java, and that could be an issue for Windows.

I just removed those and tried an install on a new Windows installation and was able to get npm install to work with no problems.

​Thanks!  I'll try a Windows build later today, updating #735 Installing and running LeoVue afterwards.

Edward

[Edward K. Ream]

On Thu, Mar 1, 2018 at 5:42 AM, Edward K. Ream <edre...@gmail.com> wrote:

I'll try a Windows build later today, updating #735 Installing and running LeoVue afterwards.

​A quick rebuild failed in new ways. I'll investigate when I can.

Edward