You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
So in add-remote-git.js, npm will git clone the URL you give it. When it does this, Git will want to use global templates (hooks/, description, etc) by default.
If those global templates happen to be symlinks to files unwritable by the current user, npm install will fail. See debug log.
This may be an uncommon setup, but it may be more common as of late--I got this error because I installed GitHub.app for Mac with user A, then attempted to npm install git://foo with user B. GitHub.app provides some global templates, and those templates are symlinks to files within /Applications/GitHub.app/Contents/Resources/git/share/git-core/templates/, of course, owned by user A.
I reported this problem to GitHub and, while this may be questionable app behavior, I could see similar instances of this problem cropping up on shared systems; possibly, read-only global hooks set by some fascist sysadmin. We determined the problem was with how npm install was cloning repos.
I have a fix; PR forthcoming.
The text was updated successfully, but these errors were encountered:
boneskull
pushed a commit
to boneskull/npm
that referenced
this issue
Aug 3, 2014
So in
add-remote-git.js
, npm willgit clone
the URL you give it. When it does this, Git will want to use global templates (hooks/
,description
, etc) by default.If those global templates happen to be symlinks to files unwritable by the current user,
npm install
will fail. See debug log.This may be an uncommon setup, but it may be more common as of late--I got this error because I installed GitHub.app for Mac with user A, then attempted to
npm install git://foo
with user B. GitHub.app provides some global templates, and those templates are symlinks to files within/Applications/GitHub.app/Contents/Resources/git/share/git-core/templates/
, of course, owned by user A.I reported this problem to GitHub and, while this may be questionable app behavior, I could see similar instances of this problem cropping up on shared systems; possibly, read-only global hooks set by some fascist sysadmin. We determined the problem was with how
npm install
was cloning repos.I have a fix; PR forthcoming.
The text was updated successfully, but these errors were encountered: