Refusing to install avconv as a dependency of itself

[Doug-Wyman]

npm ERR! Linux 3.10.65-5-pine64-longsleep
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "avconv"
npm ERR! node v7.0.0-pre
npm ERR! npm  v3.9.0
npm ERR! code ENOSELF

npm ERR! Refusing to install avconv as a dependency of itself
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/code/GitHub/avconv/npm-debug.log

npm-debug.txt

[Doug-Wyman]

Installing on a pine64 running Debian. Installed node then npm then tried installing avconv.
I may have worked on my first computer in 1962 but am still a dummy wrt Linux Debian or the little RISC processors

[mattiafianco]

I have the same problem, the terminal tells me "Refusing to install avconv as a dependency of itself"
The Parrot AR Drone is connected with the wifi but it does not work.

[kenany]

@Doug-Wyman Try renaming the /mnt/code/GitHub/avconv/ directory to something which does not share a name with one of your dependencies (in this case, anything but "avconv"). Also ensure that the "name" attribute of your package.json is not set to "avconv".

[Doug-Wyman]

@kenany Thank you. changing the name in package.json overcame that error. After moving the files to the Pine64 to fix a chown error, all went without an error but avconv is not installed.

I guess the warning is true: └── avconv@3.0.2 extraneous

npm WARN You are using a pre-release version of node and things may not work as expected

[Doug-Wyman]

See previous

[kenany]

@Doug-Wyman

Seeing

└── avconv@3.0.2 extraneous

in your npm ls or npm install output should indicate that avconv is installed. The "extraneous" part is only indicating that the module is not defined as a dependency in your package.json, so npm considers it extraneous.

[Doug-Wyman]

@kenany Thank you very much. avconv still didn't install but that could be caused by any number of things. I ended up with a pre-release node (don't know how) and need to replace it with a release version for ARM 64 processor. That plus it being a Pine64 and new release OS which may be buggy. Ah the fun of experimentation and learning when retired and 73 years old.

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.