-
Notifications
You must be signed in to change notification settings - Fork 336
npm instlal fails with "is not a valid repository name" (debian unstable) #458
Comments
I see the same failure if I manually try git clone git clone git@github.com:github:ssbc/scuttlebot The problem appears to be the ":github:" part of that, which is just invalid AFAIK |
Note that I'm doing exactly what the ssb handbook says to do. |
I think this is because you are using an old version of npm (v1.4.21) and node (v4.8.1). Github links are only available in npm v2 and higher. Try updating to the latest versions and see what happens. Also you could try installing a standalone version from https://github.com/ssbc/patchwork/releases which won't require you upgrading your node installation. @ahdinosaur we should probably add a note to the handbook about checking your node/npm version. |
Matt McKegg wrote:
I think this is because you are using an old version of npm (v1.4.21) and node
(v4.8.1). Github links are only available in npm v2 and higher.
Well, these being the versions in currently all versions of Debian,
it's fairly likely a user following the installation instations will be
using these now and probably for the next 2+ years. So perhaps the
instructions need to state the minimum version.
…--
see shy jo
|
hey, i think this can be closed: |
@joeyh wrote:
On Debian, just install
|
joey@darkstar:
/tmp>git clone https://github.com/ssbc/patchwork/tmp>cd patchwork/Cloning into 'patchwork'...
remote: Counting objects: 14020, done.
remote: Total 14020 (delta 0), reused 0 (delta 0), pack-reused 14020
Receiving objects: 100% (14020/14020), 14.40 MiB | 159.00 KiB/s, done.
Resolving deltas: 100% (9414/9414), done.
joey@darkstar:
joey@darkstar:~/tmp/patchwork>npm install
npm WARN package.json ssb-patchwork@3.2.2 No repository field.
npm WARN package.json ssb-patchwork@3.2.2 license should be a valid SPDX license expression
npm ERR! git clone git@github.com:github:mmckegg/pull-scroll Cloning into bare repository '/home/joey/.npm/_git-remotes/git-github-com-github-mmckegg-pull-scroll-7f8e0a77'...
npm ERR! git clone git@github.com:github:mmckegg/pull-scroll fatal: remote error:
npm ERR! git clone git@github.com:github:mmckegg/pull-scroll is not a valid repository name
npm ERR! git clone git@github.com:github:mmckegg/pull-scroll Email support@github.com for help
npm ERR! notarget No compatible version found: pull-scroll@'github:mmckegg/pull-scroll#0fddc085fc82cfce9f3ccfd4096fce99843a1e51'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.0.0","0.0.1","0.0.2","0.0.3","0.1.0","0.2.0","0.2.1","0.2.2","0.3.0","0.3.2","0.3.3","0.3.4","1.0.0","1.0.1","1.0.2","1.0.3"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! System Linux 4.9.0-2-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/joey/tmp/patchwork
npm ERR! node -v v4.8.1
npm ERR! npm -v 1.4.21
npm ERR! code ETARGET
npm ERR! git clone git@github.com:github:ssbc/scuttlebot Cloning into bare repository '/home/joey/.npm/_git-remotes/git-github-com-github-ssbc-scuttlebot-abcbb3a9'...
npm ERR! git clone git@github.com:github:ssbc/scuttlebot fatal: remote error:
npm ERR! git clone git@github.com:github:ssbc/scuttlebot is not a valid repository name
npm ERR! git clone git@github.com:github:ssbc/scuttlebot Email support@github.com for help
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/joey/tmp/patchwork/npm-debug.log
npm ERR! not ok code 0
The text was updated successfully, but these errors were encountered: