ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandeepbaldawa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-1932) "brunch w" gives error with latest code from github
Date Mon, 15 Apr 2013 04:10:15 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631484#comment-13631484
] 

sandeepbaldawa commented on AMBARI-1932:
----------------------------------------

The log from "npm install -g brunch" is as below, hope it's not an issue.

npm install -g brunch
npm http GET https://registry.npmjs.org/brunch
npm http 304 https://registry.npmjs.org/brunch
npm http GET https://registry.npmjs.org/chokidar
npm http GET https://registry.npmjs.org/coffee-script
npm http GET https://registry.npmjs.org/argumentum
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/ncp
npm http GET https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/debug
npm http GET https://registry.npmjs.org/init-skeleton
npm http GET https://registry.npmjs.org/loggy
npm http 304 https://registry.npmjs.org/chokidar
npm http 304 https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/coffee-script
npm http 304 https://registry.npmjs.org/ncp
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/express
npm http 304 https://registry.npmjs.org/debug
npm http 304 https://registry.npmjs.org/init-skeleton
npm http 304 https://registry.npmjs.org/loggy
npm http 304 https://registry.npmjs.org/argumentum
npm http GET https://registry.npmjs.org/ansi-color
npm http GET https://registry.npmjs.org/growl
npm http GET https://registry.npmjs.org/date-utils
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/connect/2.7.5
npm http GET https://registry.npmjs.org/commander/0.6.1
npm http GET https://registry.npmjs.org/range-parser/0.0.4
npm http GET https://registry.npmjs.org/cookie/0.0.5
npm http GET https://registry.npmjs.org/buffer-crc32
npm http GET https://registry.npmjs.org/fresh/0.1.0
npm http GET https://registry.npmjs.org/methods/0.0.1
npm http GET https://registry.npmjs.org/send/0.1.0
npm http GET https://registry.npmjs.org/cookie-signature/1.0.0
npm http 304 https://registry.npmjs.org/growl
npm http 304 https://registry.npmjs.org/date-utils
npm http 304 https://registry.npmjs.org/connect/2.7.5
npm http 304 https://registry.npmjs.org/range-parser/0.0.4
npm http 304 https://registry.npmjs.org/commander/0.6.1
npm http 304 https://registry.npmjs.org/cookie/0.0.5
npm http 304 https://registry.npmjs.org/buffer-crc32
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/rimraf
npm http 304 https://registry.npmjs.org/ansi-color
npm http 304 https://registry.npmjs.org/fresh/0.1.0
npm http 304 https://registry.npmjs.org/send/0.1.0
npm http 304 https://registry.npmjs.org/methods/0.0.1
npm http 304 https://registry.npmjs.org/cookie-signature/1.0.0
npm WARN package.json methods@0.0.1 No README.md file found!
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/keypress
npm http GET https://registry.npmjs.org/mime/1.2.6
npm http GET https://registry.npmjs.org/qs/0.5.1
npm http GET https://registry.npmjs.org/formidable/1.0.11
npm http GET https://registry.npmjs.org/buffer-crc32/0.1.1
npm http GET https://registry.npmjs.org/bytes/0.2.0
npm http GET https://registry.npmjs.org/pause/0.0.1
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/buffer-crc32/0.1.1
npm http 304 https://registry.npmjs.org/keypress
npm http 304 https://registry.npmjs.org/bytes/0.2.0
npm http 304 https://registry.npmjs.org/mime/1.2.6
npm http 304 https://registry.npmjs.org/pause/0.0.1
npm http 304 https://registry.npmjs.org/qs/0.5.1
npm http 304 https://registry.npmjs.org/formidable/1.0.11
/usr/local/node-v0.10.2-linux-x64/bin/brunch -> /usr/local/node-v0.10.2-linux-x64/lib/node_modules/brunch/bin/brunch
brunch@1.6.3 /usr/local/node-v0.10.2-linux-x64/lib/node_modules/brunch
├── debug@0.7.2
├── ncp@0.4.2
├── chokidar@0.6.2
├── async@0.2.7
├── mkdirp@0.3.5
├── argumentum@0.6.0
├── coffee-script@1.6.2
├── loggy@0.1.0 (ansi-color@0.2.1, growl@1.7.0, date-utils@1.2.12)
├── init-skeleton@0.1.3 (rimraf@2.1.4, commander@1.1.1)
└── express@3.1.2 (methods@0.0.1, fresh@0.1.0, range-parser@0.0.4, cookie-signature@1.0.0,
buffer-crc32@0.2.1, cookie@0.0.5, commander@0.6.1, send@0.1.0, connect@2.7.5)
                
> "brunch w" gives error with latest code from github
> ---------------------------------------------------
>
>                 Key: AMBARI-1932
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1932
>             Project: Ambari
>          Issue Type: Bug
>         Environment: rhel 2.6 32 bit
> Latest code from Github
>            Reporter: sandeepbaldawa
>            Priority: Blocker
>
> 1. git clone git://git.apache.org/ambari.git
> 2. cd ambari/ambari-web
> 3. npm install -g brunch
> After doing the above steps, I run "brunch w" and get the below error
> >>brunch w
> 14 Apr 21:01:14 - error: { [Error: Cannot find module '/home/ambari-server/scratch/ambari/ambari-web/node_modules/javascript-brunch']
code: 'MODULE_NOT_FOUND' }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message