amber 0.13 init on Ubuntu derivative

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

amber 0.13 init on Ubuntu derivative

Hannes Hirzel
Hello

I am installing Amber 0.13.0-pre on an Ubuntu derivative.  The

    amber init

command does not run completely. Thus the legacy and the Helios IDE do not open.

Do you have suggestions please how to fix this?

Thank you in advance

Hannes

----------------------------------------------------------------------------------------------------------
Installation activities log
----------------------------------------------------------------------------------------------------------

(Note: previous amber is 0.12.4, no de-installation)

sudo npm -g install amber-cli@~0.13.0
npm install -g requirejs

mkdir amber13test3
cd amber13test3
amber init

...... snip....


codemirror#3.24.0 bower_components/codemirror

bootstrap2.3.2#2.3.2 bower_components/bootstrap2.3.2
└── jquery#2.0.3

showdown#0.3.1 bower_components/showdown
npm install exec error:
{ [Error: Command failed: npm http GET https://registry.npmjs.org/grunt
npm http GET https://registry.npmjs.org/grunt-contrib-clean
npm http GET https://registry.npmjs.org/grunt-execute
npm http GET https://registry.npmjs.org/amber-dev
npm http 304 https://registry.npmjs.org/grunt
npm http 304 https://registry.npmjs.org/grunt-contrib-clean
npm ERR! Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
npm ERR!  { [Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds']
npm ERR!   errno: 3,
npm ERR!   code: 'EACCES',
npm ERR!   path: '/home/hhzl/tmp/npm-5184-idT59yds' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 3.8.0-34-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /home/hhzl/Documents/ambertest3
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! path /home/hhzl/tmp/npm-5184-idT59yds
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
npm http 304 https://registry.npmjs.org/grunt-execute
npm http 304 https://registry.npmjs.org/amber-dev
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/hhzl/Documents/ambertest3/npm-debug.log
npm ERR! not ok code 0
] killed: false, code: 3, signal: null }
hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest3 $


----------------------------------------------------------------------------------------------------------
Another attempt  -- run amber init with administrator priviledge
Installation activities log
----------------------------------------------------------------------------------------------------------



mkdir ambertest4
cd ambertest4
sudo amber init

....
Writing Gruntfile.js...OK
Writing README.md...OK
Writing app.build.js...OK
Writing .gitignore...OK
Writing index.html...OK
Writing local.amd.json...OK
Writing src/Ambertest4.js...OK
Writing src/Ambertest4.st...OK
Writing src/Ambertest4-Tests.js...OK
Writing src/Ambertest4-Tests.st...OK
Writing LICENSE-MIT...OK
Writing package.json...OK

Initialized from template "grunt-init-amber".
You need to have these installed globally via npm: amber-cli_; _grunt-cli_;
_bower. Now, install project dependencies with bower install, tool
dependencies with npm install and optionally, recompile with grunt. If you
are running amber init, these three tasks are going to be performed for you
now. Afterwards, start the development server with amber serve. Your
application is then accessible via http://localhost:4000/

Done, without errors.
bower install exec error:
{ [Error: Command failed: bower ESUDO         Cannot be run with sudo

Additional error details:
Since bower is a user command, there is no need to execute it with
superuser permissions.
If you're having permission errors when using bower without sudo,
please spend a few minutes learning more about how your system should
work and make any necessary repairs.

http://www.joyent.com/blog/installing-node-and-npm
https://gist.github.com/isaacs/579814

You can however run a command with sudo using --allow-root option
] killed: false, code: 1, signal: null }
hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest4 $

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: amber 0.13 init on Ubuntu derivative

sebastianconcept
you shouldn’t do 
`sudo npm  …`

read here:





On Sep 7, 2014, at 7:53 PM, H. Hirzel <[hidden email]> wrote:

Hello

I am installing Amber 0.13.0-pre on an Ubuntu derivative.  The

   amber init

command does not run completely. Thus the legacy and the Helios IDE do not open.

Do you have suggestions please how to fix this?

Thank you in advance

Hannes

----------------------------------------------------------------------------------------------------------
Installation activities log
----------------------------------------------------------------------------------------------------------

(Note: previous amber is 0.12.4, no de-installation)

sudo npm -g install amber-cli@~0.13.0
npm install -g requirejs

mkdir amber13test3
cd amber13test3
amber init

...... snip....


codemirror#3.24.0 bower_components/codemirror

bootstrap2.3.2#2.3.2 bower_components/bootstrap2.3.2
└── jquery#2.0.3

showdown#0.3.1 bower_components/showdown
npm install exec error:
{ [Error: Command failed: npm http GET https://registry.npmjs.org/grunt
npm http GET https://registry.npmjs.org/grunt-contrib-clean
npm http GET https://registry.npmjs.org/grunt-execute
npm http GET https://registry.npmjs.org/amber-dev
npm http 304 https://registry.npmjs.org/grunt
npm http 304 https://registry.npmjs.org/grunt-contrib-clean
npm ERR! Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
npm ERR!  { [Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds']
npm ERR!   errno: 3,
npm ERR!   code: 'EACCES',
npm ERR!   path: '/home/hhzl/tmp/npm-5184-idT59yds' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 3.8.0-34-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! cwd /home/hhzl/Documents/ambertest3
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! path /home/hhzl/tmp/npm-5184-idT59yds
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
npm http 304 https://registry.npmjs.org/grunt-execute
npm http 304 https://registry.npmjs.org/amber-dev
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/hhzl/Documents/ambertest3/npm-debug.log
npm ERR! not ok code 0
] killed: false, code: 3, signal: null }
hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest3 $


----------------------------------------------------------------------------------------------------------
Another attempt  -- run amber init with administrator priviledge
Installation activities log
----------------------------------------------------------------------------------------------------------



mkdir ambertest4
cd ambertest4
sudo amber init

....
Writing Gruntfile.js...OK
Writing README.md...OK
Writing app.build.js...OK
Writing .gitignore...OK
Writing index.html...OK
Writing local.amd.json...OK
Writing src/Ambertest4.js...OK
Writing src/Ambertest4.st...OK
Writing src/Ambertest4-Tests.js...OK
Writing src/Ambertest4-Tests.st...OK
Writing LICENSE-MIT...OK
Writing package.json...OK

Initialized from template "grunt-init-amber".
You need to have these installed globally via npm: amber-cli_; _grunt-cli_;
_bower. Now, install project dependencies with bower install, tool
dependencies with npm install and optionally, recompile with grunt. If you
are running amber init, these three tasks are going to be performed for you
now. Afterwards, start the development server with amber serve. Your
application is then accessible via http://localhost:4000/

Done, without errors.
bower install exec error:
{ [Error: Command failed: bower ESUDO         Cannot be run with sudo

Additional error details:
Since bower is a user command, there is no need to execute it with
superuser permissions.
If you're having permission errors when using bower without sudo,
please spend a few minutes learning more about how your system should
work and make any necessary repairs.

http://www.joyent.com/blog/installing-node-and-npm
https://gist.github.com/isaacs/579814

You can however run a command with sudo using --allow-root option
] killed: false, code: 1, signal: null }
hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest4 $

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: amber 0.13 init on Ubuntu derivative

Herby Vojčík
In reply to this post by Hannes Hirzel
Well, occasionally npm has outages, so it may be that http request fails.

OTOH, this seems like real access right problem on your side. Did you chech that /home/hhzl/tmp which was common cause of all problems? Did you have write access there? It may be you ran something with sudo before so it has root as an owner.


"H. Hirzel" <[hidden email]>napísal/a:

>Hello
>
>I am installing Amber 0.13.0-pre on an Ubuntu derivative.  The
>
>    amber init
>
>command does not run completely. Thus the legacy and the Helios IDE do not open.
>
>Do you have suggestions please how to fix this?
>
>Thank you in advance
>
>Hannes
>
>----------------------------------------------------------------------------------------------------------
>Installation activities log
>----------------------------------------------------------------------------------------------------------
>
>(Note: previous amber is 0.12.4, no de-installation)
>
>sudo npm -g install amber-cli@~0.13.0
>npm install -g requirejs
>
>mkdir amber13test3
>cd amber13test3
>amber init
>
>...... snip....
>
>
>codemirror#3.24.0 bower_components/codemirror
>
>bootstrap2.3.2#2.3.2 bower_components/bootstrap2.3.2
>└── jquery#2.0.3
>
>showdown#0.3.1 bower_components/showdown
>npm install exec error:
>{ [Error: Command failed: npm http GET https://registry.npmjs.org/grunt
>npm http GET https://registry.npmjs.org/grunt-contrib-clean
>npm http GET https://registry.npmjs.org/grunt-execute
>npm http GET https://registry.npmjs.org/amber-dev
>npm http 304 https://registry.npmjs.org/grunt
>npm http 304 https://registry.npmjs.org/grunt-contrib-clean
>npm ERR! Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
>npm ERR!  { [Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds']
>npm ERR!   errno: 3,
>npm ERR!   code: 'EACCES',
>npm ERR!   path: '/home/hhzl/tmp/npm-5184-idT59yds' }
>npm ERR!
>npm ERR! Please try running this command again as root/Administrator.
>
>npm ERR! System Linux 3.8.0-34-generic
>npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
>npm ERR! cwd /home/hhzl/Documents/ambertest3
>npm ERR! node -v v0.10.22
>npm ERR! npm -v 1.3.14
>npm ERR! path /home/hhzl/tmp/npm-5184-idT59yds
>npm ERR! code EACCES
>npm ERR! errno 3
>npm ERR! stack Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
>npm http 304 https://registry.npmjs.org/grunt-execute
>npm http 304 https://registry.npmjs.org/amber-dev
>npm ERR!
>npm ERR! Additional logging details can be found in:
>npm ERR!     /home/hhzl/Documents/ambertest3/npm-debug.log
>npm ERR! not ok code 0
>] killed: false, code: 3, signal: null }
>hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest3 $
>
>
>----------------------------------------------------------------------------------------------------------
>Another attempt  -- run amber init with administrator priviledge
>Installation activities log
>----------------------------------------------------------------------------------------------------------
>
>
>
>mkdir ambertest4
>cd ambertest4
>sudo amber init
>
>....
>Writing Gruntfile.js...OK
>Writing README.md...OK
>Writing app.build.js...OK
>Writing .gitignore...OK
>Writing index.html...OK
>Writing local.amd.json...OK
>Writing src/Ambertest4.js...OK
>Writing src/Ambertest4.st...OK
>Writing src/Ambertest4-Tests.js...OK
>Writing src/Ambertest4-Tests.st...OK
>Writing LICENSE-MIT...OK
>Writing package.json...OK
>
>Initialized from template "grunt-init-amber".
>You need to have these installed globally via npm: amber-cli_; _grunt-cli_;
>_bower. Now, install project dependencies with bower install, tool
>dependencies with npm install and optionally, recompile with grunt. If you
>are running amber init, these three tasks are going to be performed for you
>now. Afterwards, start the development server with amber serve. Your
>application is then accessible via http://localhost:4000/
>
>Done, without errors.
>bower install exec error:
>{ [Error: Command failed: bower ESUDO         Cannot be run with sudo
>
>Additional error details:
>Since bower is a user command, there is no need to execute it with
>superuser permissions.
>If you're having permission errors when using bower without sudo,
>please spend a few minutes learning more about how your system should
>work and make any necessary repairs.
>
>http://www.joyent.com/blog/installing-node-and-npm
>https://gist.github.com/isaacs/579814
>
>You can however run a command with sudo using --allow-root option
>] killed: false, code: 1, signal: null }
>hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest4 $
>
>--
>You received this message because you are subscribed to the Google Groups "amber-lang" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
>For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: amber 0.13 init on Ubuntu derivative

Hannes Hirzel
Thank you Herby, the issue is no fixed.

On 9/8/14, Herby Vojčík <[hidden email]> wrote:
> Well, occasionally npm has outages, so it may be that http request fails.
>
> OTOH, this seems like real access right problem on your side. Did you chech
> that /home/hhzl/tmp which was common cause of all problems?

No

> Did you have
> write access there? It may be you ran something with sudo before so it has
> root as an owner.
>

The tmp directory was owned by the  'root' user. Changing the owner to
the current user fixed the issue.


I  then had node.js in a local
    /home/user/bin
directory for the user and added the path to the .profile.

   PATH="$HOME/bin:/home/user/bin/node-v0.10.31-linux-x86/bin:$PATH"

Then I did not have to use sudo for amber.

The history of commands

sudo apt-get install git

npm -g install amber-cli@~0.13.0
npm -g install bower
npm -g install grunt-cli
npm -g install requirejs
cd Documents/
mkdir ambertest13
cd ambertest13
amber init
amber serve
point browser to localhost:4000

>
> "H. Hirzel" <[hidden email]>napísal/a:
>
>>Hello
>>
>>I am installing Amber 0.13.0-pre on an Ubuntu derivative.  The
>>
>>    amber init
>>
>>command does not run completely. Thus the legacy and the Helios IDE do not
>> open.
>>
>>Do you have suggestions please how to fix this?
>>
>>Thank you in advance
>>
>>Hannes
>>
>>----------------------------------------------------------------------------------------------------------
>>Installation activities log
>>----------------------------------------------------------------------------------------------------------
>>
>>(Note: previous amber is 0.12.4, no de-installation)
>>
>>sudo npm -g install amber-cli@~0.13.0
>>npm install -g requirejs
>>
>>mkdir amber13test3
>>cd amber13test3
>>amber init
>>
>>...... snip....
>>
>>
>>codemirror#3.24.0 bower_components/codemirror
>>
>>bootstrap2.3.2#2.3.2 bower_components/bootstrap2.3.2
>>└── jquery#2.0.3
>>
>>showdown#0.3.1 bower_components/showdown
>>npm install exec error:
>>{ [Error: Command failed: npm http GET https://registry.npmjs.org/grunt
>>npm http GET https://registry.npmjs.org/grunt-contrib-clean
>>npm http GET https://registry.npmjs.org/grunt-execute
>>npm http GET https://registry.npmjs.org/amber-dev
>>npm http 304 https://registry.npmjs.org/grunt
>>npm http 304 https://registry.npmjs.org/grunt-contrib-clean
>>npm ERR! Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
>>npm ERR!  { [Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds']
>>npm ERR!   errno: 3,
>>npm ERR!   code: 'EACCES',
>>npm ERR!   path: '/home/hhzl/tmp/npm-5184-idT59yds' }
>>npm ERR!
>>npm ERR! Please try running this command again as root/Administrator.
>>
>>npm ERR! System Linux 3.8.0-34-generic
>>npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
>>npm ERR! cwd /home/hhzl/Documents/ambertest3
>>npm ERR! node -v v0.10.22
>>npm ERR! npm -v 1.3.14
>>npm ERR! path /home/hhzl/tmp/npm-5184-idT59yds
>>npm ERR! code EACCES
>>npm ERR! errno 3
>>npm ERR! stack Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
>>npm http 304 https://registry.npmjs.org/grunt-execute
>>npm http 304 https://registry.npmjs.org/amber-dev
>>npm ERR!
>>npm ERR! Additional logging details can be found in:
>>npm ERR!     /home/hhzl/Documents/ambertest3/npm-debug.log
>>npm ERR! not ok code 0
>>] killed: false, code: 3, signal: null }
>>hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest3 $
>>
>>
>>----------------------------------------------------------------------------------------------------------
>>Another attempt  -- run amber init with administrator priviledge
>>Installation activities log
>>----------------------------------------------------------------------------------------------------------
>>
>>
>>
>>mkdir ambertest4
>>cd ambertest4
>>sudo amber init
>>
>>....
>>Writing Gruntfile.js...OK
>>Writing README.md...OK
>>Writing app.build.js...OK
>>Writing .gitignore...OK
>>Writing index.html...OK
>>Writing local.amd.json...OK
>>Writing src/Ambertest4.js...OK
>>Writing src/Ambertest4.st...OK
>>Writing src/Ambertest4-Tests.js...OK
>>Writing src/Ambertest4-Tests.st...OK
>>Writing LICENSE-MIT...OK
>>Writing package.json...OK
>>
>>Initialized from template "grunt-init-amber".
>>You need to have these installed globally via npm: amber-cli_;
>> _grunt-cli_;
>>_bower. Now, install project dependencies with bower install, tool
>>dependencies with npm install and optionally, recompile with grunt. If you
>>are running amber init, these three tasks are going to be performed for
>> you
>>now. Afterwards, start the development server with amber serve. Your
>>application is then accessible via http://localhost:4000/
>>
>>Done, without errors.
>>bower install exec error:
>>{ [Error: Command failed: bower ESUDO         Cannot be run with sudo
>>
>>Additional error details:
>>Since bower is a user command, there is no need to execute it with
>>superuser permissions.
>>If you're having permission errors when using bower without sudo,
>>please spend a few minutes learning more about how your system should
>>work and make any necessary repairs.
>>
>>http://www.joyent.com/blog/installing-node-and-npm
>>https://gist.github.com/isaacs/579814
>>
>>You can however run a command with sudo using --allow-root option
>>] killed: false, code: 1, signal: null }
>>hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest4 $
>>
>>--
>>You received this message because you are subscribed to the Google Groups
>> "amber-lang" group.
>>To unsubscribe from this group and stop receiving emails from it, send an
>> email to [hidden email].
>>For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "amber-lang" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> For more options, visit https://groups.google.com/d/optout.
>

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: amber 0.13 init on Ubuntu derivative

Hannes Hirzel
Sorry for the typo. The issue is NOW fixed.

On 9/8/14, H. Hirzel <[hidden email]> wrote:

> Thank you Herby, the issue is no fixed.
>
> On 9/8/14, Herby Vojčík <[hidden email]> wrote:
>> Well, occasionally npm has outages, so it may be that http request fails.
>>
>> OTOH, this seems like real access right problem on your side. Did you
>> chech
>> that /home/hhzl/tmp which was common cause of all problems?
>
> No
>
>> Did you have
>> write access there? It may be you ran something with sudo before so it
>> has
>> root as an owner.
>>
>
> The tmp directory was owned by the  'root' user. Changing the owner to
> the current user fixed the issue.
>
>
> I  then had node.js in a local
>     /home/user/bin
> directory for the user and added the path to the .profile.
>
>    PATH="$HOME/bin:/home/user/bin/node-v0.10.31-linux-x86/bin:$PATH"
>
> Then I did not have to use sudo for amber.
>
> The history of commands
>
> sudo apt-get install git
>
> npm -g install amber-cli@~0.13.0
> npm -g install bower
> npm -g install grunt-cli
> npm -g install requirejs
> cd Documents/
> mkdir ambertest13
> cd ambertest13
> amber init
> amber serve
> point browser to localhost:4000
>
>>
>> "H. Hirzel" <[hidden email]>napísal/a:
>>
>>>Hello
>>>
>>>I am installing Amber 0.13.0-pre on an Ubuntu derivative.  The
>>>
>>>    amber init
>>>
>>>command does not run completely. Thus the legacy and the Helios IDE do
>>> not
>>> open.
>>>
>>>Do you have suggestions please how to fix this?
>>>
>>>Thank you in advance
>>>
>>>Hannes
>>>
>>>----------------------------------------------------------------------------------------------------------
>>>Installation activities log
>>>----------------------------------------------------------------------------------------------------------
>>>
>>>(Note: previous amber is 0.12.4, no de-installation)
>>>
>>>sudo npm -g install amber-cli@~0.13.0
>>>npm install -g requirejs
>>>
>>>mkdir amber13test3
>>>cd amber13test3
>>>amber init
>>>
>>>...... snip....
>>>
>>>
>>>codemirror#3.24.0 bower_components/codemirror
>>>
>>>bootstrap2.3.2#2.3.2 bower_components/bootstrap2.3.2
>>>└── jquery#2.0.3
>>>
>>>showdown#0.3.1 bower_components/showdown
>>>npm install exec error:
>>>{ [Error: Command failed: npm http GET https://registry.npmjs.org/grunt
>>>npm http GET https://registry.npmjs.org/grunt-contrib-clean
>>>npm http GET https://registry.npmjs.org/grunt-execute
>>>npm http GET https://registry.npmjs.org/amber-dev
>>>npm http 304 https://registry.npmjs.org/grunt
>>>npm http 304 https://registry.npmjs.org/grunt-contrib-clean
>>>npm ERR! Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
>>>npm ERR!  { [Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds']
>>>npm ERR!   errno: 3,
>>>npm ERR!   code: 'EACCES',
>>>npm ERR!   path: '/home/hhzl/tmp/npm-5184-idT59yds' }
>>>npm ERR!
>>>npm ERR! Please try running this command again as root/Administrator.
>>>
>>>npm ERR! System Linux 3.8.0-34-generic
>>>npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install"
>>>npm ERR! cwd /home/hhzl/Documents/ambertest3
>>>npm ERR! node -v v0.10.22
>>>npm ERR! npm -v 1.3.14
>>>npm ERR! path /home/hhzl/tmp/npm-5184-idT59yds
>>>npm ERR! code EACCES
>>>npm ERR! errno 3
>>>npm ERR! stack Error: EACCES, mkdir '/home/hhzl/tmp/npm-5184-idT59yds'
>>>npm http 304 https://registry.npmjs.org/grunt-execute
>>>npm http 304 https://registry.npmjs.org/amber-dev
>>>npm ERR!
>>>npm ERR! Additional logging details can be found in:
>>>npm ERR!     /home/hhzl/Documents/ambertest3/npm-debug.log
>>>npm ERR! not ok code 0
>>>] killed: false, code: 3, signal: null }
>>>hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest3 $
>>>
>>>
>>>----------------------------------------------------------------------------------------------------------
>>>Another attempt  -- run amber init with administrator priviledge
>>>Installation activities log
>>>----------------------------------------------------------------------------------------------------------
>>>
>>>
>>>
>>>mkdir ambertest4
>>>cd ambertest4
>>>sudo amber init
>>>
>>>....
>>>Writing Gruntfile.js...OK
>>>Writing README.md...OK
>>>Writing app.build.js...OK
>>>Writing .gitignore...OK
>>>Writing index.html...OK
>>>Writing local.amd.json...OK
>>>Writing src/Ambertest4.js...OK
>>>Writing src/Ambertest4.st...OK
>>>Writing src/Ambertest4-Tests.js...OK
>>>Writing src/Ambertest4-Tests.st...OK
>>>Writing LICENSE-MIT...OK
>>>Writing package.json...OK
>>>
>>>Initialized from template "grunt-init-amber".
>>>You need to have these installed globally via npm: amber-cli_;
>>> _grunt-cli_;
>>>_bower. Now, install project dependencies with bower install, tool
>>>dependencies with npm install and optionally, recompile with grunt. If
>>> you
>>>are running amber init, these three tasks are going to be performed for
>>> you
>>>now. Afterwards, start the development server with amber serve. Your
>>>application is then accessible via http://localhost:4000/
>>>
>>>Done, without errors.
>>>bower install exec error:
>>>{ [Error: Command failed: bower ESUDO         Cannot be run with sudo
>>>
>>>Additional error details:
>>>Since bower is a user command, there is no need to execute it with
>>>superuser permissions.
>>>If you're having permission errors when using bower without sudo,
>>>please spend a few minutes learning more about how your system should
>>>work and make any necessary repairs.
>>>
>>>http://www.joyent.com/blog/installing-node-and-npm
>>>https://gist.github.com/isaacs/579814
>>>
>>>You can however run a command with sudo using --allow-root option
>>>] killed: false, code: 1, signal: null }
>>>hhzl@hhzl-Latitude-E6400 ~/Documents/ambertest4 $
>>>
>>>--
>>>You received this message because you are subscribed to the Google Groups
>>> "amber-lang" group.
>>>To unsubscribe from this group and stop receiving emails from it, send an
>>> email to [hidden email].
>>>For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "amber-lang" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [hidden email].
>> For more options, visit https://groups.google.com/d/optout.
>>
>

--
You received this message because you are subscribed to the Google Groups "amber-lang" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.