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
vagrant@ubuntu2204 ~ % nvm install node
Downloading and installing node v20.8.0...
Downloading https://nodejs.org/dist/v20.8.0/node-v20.8.0-linux-x64.tar.xz...
######################################################################################################################################### 100.0%
Computing checksum with sha256sum
Checksums matched!
tar: bin/corepack: Cannot create symlink to ‘../lib/node_modules/corepack/dist/corepack.js’: Protocol error
tar: bin/npx: Cannot create symlink to ‘../lib/node_modules/npm/bin/npx-cli.js’: Protocol error
tar: bin/npm: Cannot create symlink to ‘../lib/node_modules/npm/bin/npm-cli.js’: Protocol error
tar: Exiting with failure status due to previous errors
Now using node v20.8.0
Installing npm...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 3755 100 3755 0 0 10344 0 --:--:-- --:--:-- --:--:-- 61557
failed to get tarball url for npm/0.2.19
vagrant@ubuntu2204 ~ % rm -rf ~/.nvm ~/.npm
vagrant@ubuntu2204 ~ % curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15916 100 15916 0 0 119k 0 --:--:-- --:--:-- --:--:-- 119k
=> Downloading nvm from git to '/home/vagrant/.nvm'
=> Cloning into '/home/vagrant/.nvm'...
remote: Enumerating objects: 360, done.
remote: Counting objects: 100% (360/360), done.
remote: Compressing objects: 100% (306/306), done.
remote: Total 360 (delta 41), reused 162 (delta 28), pack-reused 0
Receiving objects: 100% (360/360), 220.24 KiB | 1.49 MiB/s, done.
Resolving deltas: 100% (41/41), done.
* (HEAD detached at FETCH_HEAD)
master
=> Compressing and cleaning up git repository
=> nvm source string already in /home/vagrant/.bashrc
=> bash_completion source string already in /home/vagrant/.bashrc
=> Close and reopen your terminal to start using nvm or run the following to use it now:
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion
vagrant@ubuntu2204 ~ % nvm install node
Downloading and installing node v20.8.0...
Downloading https://nodejs.org/dist/v20.8.0/node-v20.8.0-linux-x64.tar.xz...
######################################################################################################################################### 100.0%
Computing checksum with sha256sum
Checksums matched!
tar: bin/corepack: Cannot create symlink to ‘../lib/node_modules/corepack/dist/corepack.js’: Protocol error
tar: bin/npx: Cannot create symlink to ‘../lib/node_modules/npm/bin/npx-cli.js’: Protocol error
tar: bin/npm: Cannot create symlink to ‘../lib/node_modules/npm/bin/npm-cli.js’: Protocol error
tar: Exiting with failure status due to previous errors
Installing npm...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 3755 100 3755 0 0 9610 0 --:--:-- --:--:-- --:--:-- 9610
failed to get tarball url for **npm/0.2.19**
What happened?
Looks like it failed to get tarball url for npm/0.2.19 I'm not sure why it would leave me in this state without npm.
What did you expect to happen?
I'd expect nvm to install npm version 20.0.8? I'm not sure where it's even getting 0.2.19 from. Is their another place that I can delete the reference to 0.2.19 from??
Is there anything in any of your profile files that modifies the PATH?
Short answer is no.
If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?
vagrant@ubuntu2204 ~ % curl -I --compressed -v https://nodejs.org/dist/
* Trying 104.20.22.46:443...
* Connected to nodejs.org (104.20.22.46) port 443 (#0)* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=*.nodejs.org
* start date: Feb 3 00:00:00 2023 GMT
* expire date: Mar 5 23:59:59 2024 GMT
* subjectAltName: host "nodejs.org" matched cert's "nodejs.org"* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA* SSL certificate verify ok.* Using HTTP2, server supports multiplexing* Connection state changed (HTTP/2 confirmed)* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0* TLSv1.2 (OUT), TLS header, Supplemental data (23):* TLSv1.2 (OUT), TLS header, Supplemental data (23):* TLSv1.2 (OUT), TLS header, Supplemental data (23):* Using Stream ID: 1 (easy handle 0x564e8fc6be90)* TLSv1.2 (OUT), TLS header, Supplemental data (23):> HEAD /dist/ HTTP/2> Host: nodejs.org> user-agent: curl/7.81.0> accept: */*> accept-encoding: deflate, gzip, br, zstd>* TLSv1.2 (IN), TLS header, Supplemental data (23):* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):* old SSL session ID is stale, removing* TLSv1.2 (IN), TLS header, Supplemental data (23):* TLSv1.2 (OUT), TLS header, Supplemental data (23):* TLSv1.2 (IN), TLS header, Supplemental data (23):* TLSv1.2 (IN), TLS header, Supplemental data (23):< HTTP/2 200HTTP/2 200< date: Sun, 01 Oct 2023 20:32:25 GMTdate: Sun, 01 Oct 2023 20:32:25 GMT< content-type: text/htmlcontent-type: text/html< cache-control: public, max-age=3600, s-maxage=14400cache-control: public, max-age=3600, s-maxage=14400< last-modified: Sun, 01 Oct 2023 17:55:11 GMTlast-modified: Sun, 01 Oct 2023 17:55:11 GMT< cf-cache-status: HITcf-cache-status: HIT< age: 9143age: 9143< vary: Accept-Encodingvary: Accept-Encoding< strict-transport-security: max-age=31536000; includeSubDomains; preloadstrict-transport-security: max-age=31536000; includeSubDomains; preload< x-content-type-options: nosniffx-content-type-options: nosniff< server: cloudflareserver: cloudflare< cf-ray: 80f779902ec910e5-ORDcf-ray: 80f779902ec910e5-ORD< content-encoding: brcontent-encoding: br<* Connection #0 to host nodejs.org left intactvagrant@ubuntu2204 ~ %
The text was updated successfully, but these errors were encountered:
varnem2
changed the title
npm tarball url
npm tarball url failure
Oct 2, 2023
Operating system and version:
Vagrant Box:
generic/ubuntu2204 (virtualbox, 4.3.2)
Using a generic zsh shell
nvm debug
output:nvm ls
output:How did you install
nvm
?What steps did you perform?
What happened?
Looks like it failed to get tarball url for npm/0.2.19 I'm not sure why it would leave me in this state without npm.
What did you expect to happen?
I'd expect nvm to install npm version 20.0.8? I'm not sure where it's even getting 0.2.19 from. Is their another place that I can delete the reference to 0.2.19 from??
Is there anything in any of your profile files that modifies the
PATH
?Short answer is no.
If you are having installation issues, or getting "N/A", what does
curl -I --compressed -v https://nodejs.org/dist/
print out?The text was updated successfully, but these errors were encountered: