search

nodesource / distributions

NodeSource Node.js Binary Distributions
https://nodesource.com
MIT License
13.51k stars 3.07k forks source link

[ERROR] Node.js 20 on debian Bullseye Installation fails due to checksum error #1576

Closed RebelSoftware closed 1 year ago

RebelSoftware commented 1 year ago

When installing Node into docker container an error is received to say that there is a hash failure

#0 23.91 E: Failed to fetch https://deb.nodesource.com/node_20.x/dists/bullseye/main/binary-amd64/Packages.gz  File has unexpected size (777 != 776). Mirror sync in progress? [IP: 23.217.103.89 443]
#0 23.91    Hashes of expected file:
#0 23.91     - Filesize:776 [weak]
#0 23.91     - SHA256:b8ca63ac4fbe9dad6950b850a9258db453c68c7b1c60f25457b9709684154e47
#0 23.91     - SHA1:35c0928a4089a3064e90b1c3cd0eb3f90d96983f [weak]
#0 23.91     - MD5Sum:333f082eb4c6371f533f47acb4774153 [weak]
#0 23.91    Release file created at: Tue, 16 May 2023 15:52:17 +0000

Distribution Information:

Node Version:

To Reproduce Steps to reproduce the behavior: Use installation process

RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash - \
         && apt-get install -y nodejs \
         && npm install --global yarn

Expected behavior Node npm and yarn to install into image

cfuhrman commented 1 year ago

Something similar is happening under Ubuntu 22.04 as well:

`curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash -

E: Failed to fetch https://deb.nodesource.com/node_20.x/dists/jammy/main/binary-amd64/Packages.gz File has unexpected size (777 != 776). Mirror sync in progress? [IP: 2600:1409:12::6850:5973 443] Hashes of expected file:

Please let me know if you need any additional information.

jaromanda commented 1 year ago

Can confirm this is also an issue with arm64

E: Failed to fetch https://deb.nodesource.com/node_20.x/dists/bullseye/main/binary-arm64/Packages.gz  File has unexpected size (773 != 776). Mirror sync in progress? [IP: 2403:5800:100:29::7bfd:9553 443]
   Hashes of expected file:
    - Filesize:776 [weak]
    - SHA256:d7dda878d1a32b5e984eed67f9ce219e91cc688889476a0074ddb2453d72374e
    - SHA1:662c4bc9770a1705f1f19146074fe35f8affa637 [weak]
    - MD5Sum:d3abd4a681e37794d14d09ad3c72c6f0 [weak]
   Release file created at: Tue, 16 May 2023 15:52:17 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

and armhf (not able to copy the output for that)

Not sure if it's significant, but the "sums" in node_20.x/dists/bullseye/Release do not match node_20.x/dists/bullseye/InRelease

paulzakin commented 1 year ago

Can confirm I get the bug on arm64

#0 63.49 E: Failed to fetch https://deb.nodesource.com/node_20.x/dists/bullseye/main/binary-arm64/Packages.gz  File has unexpected size (773 != 776). Mirror sync in progress? [IP: 23.220.246.8 443]
#0 63.49    Hashes of expected file:
#0 63.49     - Filesize:776 [weak]
#0 63.49     - SHA256:d7dda878d1a32b5e984eed67f9ce219e91cc688889476a0074ddb2453d72374e
#0 63.49     - SHA1:662c4bc9770a1705f1f19146074fe35f8affa637 [weak]
#0 63.49     - MD5Sum:d3abd4a681e37794d14d09ad3c72c6f0 [weak]
#0 63.49    Release file created at: Tue, 16 May 2023 15:52:17 +0000
#0 63.49 E: Some index files failed to download. They have been ignored, or old ones used instead.
#0 63.50 Error executing command, exiting
omerinero commented 1 year ago

I'm facing the same problem on Debian (12) Bookworm

Err:19 https://deb.nodesource.com/node_20.x bookworm/main amd64 Packages
  File has unexpected size (777 != 776). Mirror sync in progress? [IP: 2a02:26f0:3900::211:c533 443]
  Hashes of expected file:
   - Filesize:776 [weak]
   - SHA256:b8ca63ac4fbe9dad6950b850a9258db453c68c7b1c60f25457b9709684154e47
   - SHA1:35c0928a4089a3064e90b1c3cd0eb3f90d96983f [weak]
   - MD5Sum:333f082eb4c6371f533f47acb4774153 [weak]
  Release file created at: Tue, 16 May 2023 15:52:18 +0000
LaurensRietveld commented 1 year ago

Interestingly, this doesn't always happen. On one device (host with ubuntu 20.04) the following fails with the mentioned error message, where on other device (host with ubuntu 22.04) things work fine.

riosje commented 1 year ago

Hi guys we've received some reports about this, I'm checking into this.

RebelSoftware commented 1 year ago

Interestingly, this doesn't always happen. On one device (host with ubuntu 20.04) the following fails with the mentioned error message, where on other device (host with ubuntu 22.04) things work fine.

I think that this is probably a configuration thing. I'd say the system that does not fail is not using the weak file size test, however I haven't been able to discover how to disable the filesize test or even where its implemented :(

The hash tests are more robust.

My guess is the file was edited after hashes were generated.

iwebroot commented 1 year ago

Hello, Same issue. OS : Debian Bullseye Architecture : amd64

E: Failed to fetch https://deb.nodesource.com/node_20.x/dists/bullseye/main/binary-amd64/Packages.gz  File has unexpected size (776 != 777). Mirror sync in progress? [IP: 2a02:26f0:9100:16::6011:cedb 443]
   Hashes of expected file:
    - Filesize:777 [weak]
    - SHA256:d3f27ebc448d5904f92e83ab311460dbe7f3b1cd301b96e3272ad46f36bedcc5
    - SHA1:d5734eed42a52b07875d413076e72bfc9baf940e [weak]
    - MD5Sum:59e22e9983ba2434a056d4bfeb073938 [weak]
   Release file created at: Thu, 08 Jun 2023 21:03:26 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
Error executing command, exiting
LaurensRietveld commented 1 year ago

Interestingly, this doesn't always happen. On one device (host with ubuntu 20.04) the following fails with the mentioned error message, where on other device (host with ubuntu 22.04) things work fine.

I think that this is probably a configuration thing. I'd say the system that does not fail is not using the weak file size test, however I haven't been able to discover how to disable the filesize test or even where its implemented :(

The hash tests are more robust.

My guess is the file was edited after hashes were generated.

This merely being a (apt?) configuration thing would be strange, given that the MWE uses exactly the same docker image on both devices. (i.e., the configuration inside the docker containers will be exactly the same) That being said, I have no clue why my snippet fails on some devices and succeeds on others

virusproj3ct commented 1 year ago

With this Dockerfile : 

FROM ubuntu:22.04
RUN apt update
RUN apt -y install apt-utils curl jq
RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash -

I've got the same error when I try to build this image on gitlab CI (without any specific configuration)

Step 4/19 : RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash -
 ---> Running in 2a49b933c937
## Installing the NodeSource Node.js 20.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Reading package lists...
## Installing packages required for setup: lsb-release gnupg...
+ apt-get install -y lsb-release gnupg > /dev/null 2>&1
## Confirming "jammy" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_20.x/dists/jammy/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null
## Creating apt sources list file for the NodeSource Node.js 20.x repo...
+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x jammy main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x jammy main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Get:4 https://deb.nodesource.com/node_20.x jammy InRelease [4563 B]
Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:6 https://deb.nodesource.com/node_20.x jammy/main amd64 Packages [776 B]
Err:6 https://deb.nodesource.com/node_20.x jammy/main amd64 Packages
  File has unexpected size (777 != 776). Mirror sync in progress? xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  Hashes of expected file:
   - Filesize:776 [weak]
   - SHA256:b8ca63ac4fbe9dad6950b850a9258db453c68c7b1c60f25457b9709684154e47
   - SHA1:35c0928a4089a3064e90b1c3cd0eb3f90d96983f [weak]
   - MD5Sum:333f082eb4c6371f533f47acb4774153 [weak]
  Release file created at: Tue, 16 May 2023 15:52:19 +0000
Fetched 4563 B in 0s (13.6 kB/s)
Reading package lists...
riosje commented 1 year ago

Hi guys I'm still not able to re-produce this issue so far.

I've purged the cache on the CDN side.

if you access this URL: https://deb.nodesource.com/node_20.x/dists/jammy/main/binary-amd64/Packages the hashes should match with the following one

Size: 30251110
SHA256: 0b32cf05748042caf520d66da41f57bcb7daf715ec2c0a384e02cb6154166af3
SHA1: 36e5878b2c55db12068a1cd93aad00713b2127ae
MD5sum: 560e8346a3499162a1cf004a95bf58c1

Also I've validated the checksum of the stored package and it matchs with the served by our CDN. With this I can be sure there is not corrupted or modified files after the release.

560e8346a3499162a1cf004a95bf58c1  nodejs_20.3.0-1nodesource1_amd64.deb

Please run the following commands and try installing it again.

ap-get clean
apt-update
Zenexer commented 1 year ago

Still not fixed, sadly. InRelease and Release are the broken files, not Packages.

Zenexer commented 1 year ago 
root@e504f25facc0:/# curl -s https://deb.nodesource.com/node_20.x/dists/bullseye/InRelease | grep -e '^Date: ' -e 'main/binary-arm64/Packages\.gz$'
Date: Tue, 16 May 2023 15:52:17 UTC
 d3abd4a681e37794d14d09ad3c72c6f0 776 main/binary-arm64/Packages.gz
 662c4bc9770a1705f1f19146074fe35f8affa637 776 main/binary-arm64/Packages.gz
 d7dda878d1a32b5e984eed67f9ce219e91cc688889476a0074ddb2453d72374e 776 main/binary-arm64/Packages.gz
root@e504f25facc0:/# curl -o Packages.gz https://deb.nodesource.com/node_20.x/dists/bullseye/main/binary-arm64/Packages.gz
root@e504f25facc0:/# curl -so Packages.gz https://deb.nodesource.com/node_20.x/dists/bullseye/main/binary-arm64/Packages.gz
root@e504f25facc0:/# md5sum Packages.gz
dbbb789f45dedfeb0516871e3e3db2c0  Packages.gz
root@e504f25facc0:/# shasum Packages.gz
b3761928b4797f0e8744160c9c0ade1f5d7be8dc  Packages.gz
root@e504f25facc0:/# sha256sum Packages.gz
bcf96163cb941453a04209b1d12b6404589835ee6a283cc0db7620d3524350ad  Packages.gz
Zenexer commented 1 year ago

Oh, I figured it out. It's HTTPS vs. HTTP. HTTP works fine, whereas HTTPS returns the wrong values.

Zenexer commented 1 year ago 
root@e504f25facc0:/# curl -s https://deb.nodesource.com/node_20.x/dists/jammy/InRelease -vo /dev/null |& grep -i '^< last-modified: '
< last-modified: Tue, 16 May 2023 15:52:19 GMT
root@e504f25facc0:/# curl -s http://deb.nodesource.com/node_20.x/dists/jammy/InRelease -vo /dev/null |& grep -i '^< last-modified: '
< Last-Modified: Thu, 08 Jun 2023 21:03:28 GMT
riosje commented 1 year ago

ok, that was useful. would you mind to try it again in some mins over HTTPS? thank you

Zenexer commented 1 year ago

Can confirm that it's working now. Thanks!

iwebroot commented 1 year ago

OS : Debian 11 Architecture : amd64

Thanks, it's work now. 👍

omerinero commented 1 year ago

working for me! Thank you

Debian 12

dacorsa commented 1 year ago

now it's working, thanks for fix it !!!

Blockzilla101 commented 1 year ago

i am still having this issue installing on a raspberry pi

Zenexer commented 1 year ago

The issue has indeed returned:

% curl -s https://deb.nodesource.com/node_20.x/dists/jammy/main/binary-arm64/Packages.gz\?v=1 | wc -c
     776
% curl -s http://deb.nodesource.com/node_20.x/dists/jammy/main/binary-arm64/Packages.gz\?v=1 | wc -c
     773
Zenexer commented 1 year ago

This time it looks like the InRelease and Release files are fine, but Packages.gz is out-of-date on HTTPS. The issue has flipped.

riosje commented 1 year ago

I guys, sorry about this issue again, I've forced again the cache purge. I'll rise a ticket with our CDN vendor.

Zenexer commented 1 year ago

Much appreciated! Let me know if there's any additional debugging info I can provide.

In the meantime, anyone experiencing this issue can probably work around it by using HTTP instead of HTTPS. This isn't ideal, but the packages are still signed, so it should at least ensure package integrity.

RebelSoftware commented 1 year ago

I was able to successfully build the docker image. The CDN issue of serving stale files is a common one, we used to have it all the time when I was dealing with CDN's :(

I am going to be interstate for the next week so won't be able to retry any builds so cant help check the consistency of the solution.

Thanks @riosje for attending to this.

ryanbrownellbounteous commented 1 year ago

I had a brief moment of success yesterday with HTTP instead of HTTPS but it appears that this work around is no longer functional.

I did discover yesterday that docker upgraded the image for php:8.1-cli to Debian bookworm from bullseye, I switched back to bullseye by changing the image to be php:8.1-cli-bullseye.

Yesterday, the combination of HTTP and bullseye seemed to fix the pipeline issues we were encountering long enough to complete a build and deployment.

This success was however short-lived and we are back to pipelines no longer functioning because setup_14.x errors out with the following:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libnode72 : Conflicts: nodejs-legacy
 nodejs : Conflicts: npm
E: Unable to correct problems, you have held broken packages.

Seeing as how the setup_14.x instructions do not exist in the readme, I gather this is no longer supported?

Zenexer commented 1 year ago

Node 14.x reached EOL in April: https://nodejs.dev/en/about/releases/ I would assume it's not supported. Although you shouldn't, I'm sure you can get it working if you resolve the dependency problems, but that's a separate issue--it's not related to the HTTP/HTTPS staleness issue.

riosje commented 1 year ago

Hi guys this issue has been solved so far, it any of you still experiencing this?

jaromanda commented 1 year ago

Looks like it's working everywhere I need (arm64 bullseye, amd64 bullseye, amd64 bookworm, armhf bullseye) :D

Daniere-Mathieu commented 1 year ago

i still got the error with 18 , i got this on raspberry pi

pi@raspberrypi:~/pronto $ sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Get:3 https://deb.nodesource.com/node_18.x bullseye InRelease [4,586 B]
Get:4 https://deb.nodesource.com/node_18.x bullseye/main armhf Packages [786 B]
Err:4 https://deb.nodesource.com/node_18.x bullseye/main armhf Packages
  File has unexpected size (784 != 786). Mirror sync in progress? [IP: 2a02:26f0:b80:5::210:950e 443]
  Hashes of expected file:
   - Filesize:786 [weak]
   - SHA256:494b5f500c74fec4c17e3e453a376ee6bf1a58174f612b214a861a0cb5b61dec
   - SHA1:807d6ad97af66ff09611cf0f93186abddd8502c6 [weak]
   - MD5Sum:a3b3d6e03986d71fedcd168ee692af4a [weak]
  Release file created at: Thu, 13 Apr 2023 14:12:02 +0000
Fetched 4,586 B in 1s (6,396 B/s)
Reading package lists... Done
E: Failed to fetch https://deb.nodesource.com/node_18.x/dists/bullseye/main/binary-armhf/Packages.gz  File has unexpected size (784 != 786). Mirror sync in progress? [IP: 2a02:26f0:b80:5::210:950e 443]
   Hashes of expected file:
    - Filesize:786 [weak]
    - SHA256:494b5f500c74fec4c17e3e453a376ee6bf1a58174f612b214a861a0cb5b61dec
    - SHA1:807d6ad97af66ff09611cf0f93186abddd8502c6 [weak]
    - MD5Sum:a3b3d6e03986d71fedcd168ee692af4a [weak]
   Release file created at: Thu, 13 Apr 2023 14:12:02 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
jaromanda commented 1 year ago

Was fixed for 20.3.0

Broken again for 20.3.1

NicBeans commented 1 year ago

I am having a similar issue trying to install Nodejs onto a raspberry pi. OS: Debian GNU/Linux 11 (bullseye) aarch64 Ive tried installing v14(LTS), v17, v18, v19, and v20. File has unexpected size (786 != 785). Mirror sync in progress?

jamesshaw1987 commented 1 year ago

Ubuntu 22.04:


$ apt-get update
[...]
Get:7 http://deb.nodesource.com/node_16.x jammy/main amd64 Packages [776 B]
Err:7 http://deb.nodesource.com/node_16.x jammy/main amd64 Packages
  File has unexpected size (775 != 776). Mirror sync in progress? [IP: xxx.xxx.xxx.xxx]
  Hashes of expected file:
   - Filesize:776 [weak]
   - SHA256:e5d3c880cdb1ec15f193329e5a3abe68056c59f6026144de4d4b52fcce2131e6
   - SHA1:87f1583949354fe006bc0137a84d8cfe90b0229d [weak]
   - MD5Sum:c881892f3a46cc943e7ff44162cbee62 [weak]
  Release file created at: Wed, 19 Apr 2023 16:10:36 +0000
Reading package lists... Done
W: http://deb.nodesource.com/node_16.x/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
E: Failed to fetch http://deb.nodesource.com/node_16.x/dists/jammy/main/binary-amd64/Packages.gz  File has unexpected size (775 != 776). Mirror sync in progress? [IP: xxx.xxx.xxx.xxx]
   Hashes of expected file:
    - Filesize:776 [weak]
    - SHA256:e5d3c880cdb1ec15f193329e5a3abe68056c59f6026144de4d4b52fcce2131e6
    - SHA1:87f1583949354fe006bc0137a84d8cfe90b0229d [weak]
    - MD5Sum:c881892f3a46cc943e7ff44162cbee62 [weak]
   Release file created at: Wed, 19 Apr 2023 16:10:36 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.```
SiroAusili commented 1 year ago

Same issue on Ubuntu 22.04 and Docker (Docksal):

Err:12 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages
5.737   File has unexpected size (775 != 776). Mirror sync in progress? [IP: xxx.xx.xxx.xxx]
5.737   Hashes of expected file:
5.737    - Filesize:776 [weak]
5.737    - SHA256:e5d3c880cdb1ec15f193329e5a3abe68056c59f6026144de4d4b52fcce2131e6
5.737    - SHA1:87f1583949354fe006bc0137a84d8cfe90b0229d [weak]
5.737    - MD5Sum:c881892f3a46cc943e7ff44162cbee62 [weak]
5.737   Release file created at: Wed, 19 Apr 2023 16:10:35 +0000

8 hours ago it was working

elalecs commented 1 year ago

Same issue with node_18.x and node_20.x

#0 7.398 E: Failed to fetch https://deb.nodesource.com/node_18.x/dists/jammy/main/binary-arm64/Packages.gz  File has unexpected size (778 != 776). Mirror sync in progress? [IP: 23.203.60.10 443]
#0 7.398    Hashes of expected file:
#0 7.398     - Filesize:776 [weak]
#0 7.398     - SHA256:4cdc71073957aaffbea511d99669cc4fa98b752eab966068a023558555e0ab92
#0 7.398     - SHA1:0b9c08bd020fac9bc1d05b3008fe7aeee3d1a182 [weak]
#0 7.398     - MD5Sum:fc5eace817a48e2a439589628112ec00 [weak]
#0 7.398    Release file created at: Thu, 13 Apr 2023 14:12:05 +0000

yesterday was working great

rdsun0301 commented 1 year ago

^ Same issue, was working a few hours ago.

E: Failed to fetch https://deb.nodesource.com/node_16.x/dists/focal/main/binary-amd64/Packages.gz  File has unexpected size (775 != 776). Mirror sync in progress? [IP: xx.xxx.xxx.xxx 443]
--
312 | Hashes of expected file:
313 | - Filesize:776 [weak]
314 | - SHA256:e5d3c880cdb1ec15f193329e5a3abe68056c59f6026144de4d4b52fcce2131e6
315 | - SHA1:87f1583949354fe006bc0137a84d8cfe90b0229d [weak]
316 | - MD5Sum:c881892f3a46cc943e7ff44162cbee62 [weak]
317 | Release file created at: Wed, 19 Apr 2023 16:10:36 +0000
tersmitten commented 1 year ago

Same here:

    virtualbox-iso:     "stderr_lines": [
    virtualbox-iso:         "E: Failed to fetch https://deb.nodesource.com/node_16.x/dists/focal/main/binary-amd64/Packages.gz  File has unexpected size (776 != 775). Mirror sync in progress? [IP: 23.48.23.35 443]",
    virtualbox-iso:         "   Hashes of expected file:",
    virtualbox-iso:         "    - Filesize:775 [weak]",
    virtualbox-iso:         "    - SHA256:0c6d8382f60bbb4bcc24ce922521673cd749c7530b2128b8dffb3e11297d1a15",
    virtualbox-iso:         "    - SHA1:1e1b1951e616fb84373ee32a26944b356a83149d [weak]",
    virtualbox-iso:         "    - MD5Sum:fdee69ee72123acebf6c975c753f6182 [weak]",
    virtualbox-iso:         "   Release file created at: Wed, 21 Jun 2023 21:26:29 +0000",
    virtualbox-iso:         "E: Some index files failed to download. They have been ignored, or old ones used instead."
    virtualbox-iso:     ],
MatthewEdwards commented 1 year ago

Also seeing the above, same error and hashes

jaytaph commented 1 year ago

same here.. http works, https does not

peter-manton commented 1 year ago

Same issue on Debian 10

JohnXLivingston commented 1 year ago

Same issue on Debian bullseye, and node 16 LTS:

Réception de :5 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages [775 B]
Err :5 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages
  Le fichier a une taille incohérente (776 != 775). Le miroir est peut-être en cours de mise à jour ? [IP : 2a02:26f0:9400::215:22bb 443]
  Hashes of expected file:
   - Filesize:775 [weak]
   - SHA256:0c6d8382f60bbb4bcc24ce922521673cd749c7530b2128b8dffb3e11297d1a15
   - SHA1:1e1b1951e616fb84373ee32a26944b356a83149d [weak]
   - MD5Sum:fdee69ee72123acebf6c975c753f6182 [weak]
  Release file created at: Wed, 21 Jun 2023 21:26:27 +0000
Zenexer commented 1 year ago

@riosje, could you reopen this?

JesusPaz commented 1 year ago

I did several cache purges yesterday. I will contact our CDN provider.

jfrej commented 1 year ago

FYI, I'm indirectly affected by this through Playwright which uses nodesource in its Dockerfile: https://github.com/microsoft/playwright/blob/main/utils/docker/Dockerfile.focal#L12 (Edit: permalink)

npwolf commented 1 year ago

Still affected:

E: Failed to fetch https://deb.nodesource.com/node_16.x/dists/focal/main/binary-amd64/Packages.gz  File has unexpected size (775!= 776). Mirror sync in progress? [IP: 23.220.206.29 443]
   Hashes of expected file:
    - Filesize:776 [weak]
    - SHA256:e5d3c880cdb1ec15f193329e5a3abe68056c59f6026144de4d4b52fcce2131e6
    - SHA1:87f1583949354fe006bc0137a84d8cfe90b0229d [weak]
    - MD5Sum:c881892f3a46cc943e7ff44162cbee62 [weak]
   Release file created at: Wed, 19 Apr 2023 16:10:36 +0000
david-d-h commented 1 year ago

+1

kuabhish commented 1 year ago

Can confirm that it's working now. Thanks!

I am trying to download node - 16. in ubuntu. getting same error.

shadinaif commented 1 year ago

node 16 on ubuntu 20.04, not working, same error

Francoois commented 1 year ago

Same with node 18 on Ubuntu 22 Jammy

E: Impossible de récupérer https://deb.nodesource.com/node_18.x/dists/jammy/main/binary-amd64/Packages.gz  Somme de contrôle de hachage incohére
nte
   Hashes of expected file:
    - Filesize:776 [weak]
    - SHA256:50d8328c928ddd7d3e92a24eaa86582ee700af234efb9be7a5409faca804bdfc
    - SHA1:534fbff39c1182a33ea11c96c3e6b48b4ad7b894 [weak]
    - MD5Sum:367c3d8e7064ca14220fc48b0076bff8 [weak]
   Hashes of received file:
    - SHA256:e920b3bfb51a057ea1957faec3fea2af197a6f6dbfad0bdaf7074c71c1b57595
    - SHA1:e1406d386ef26768a3a5c15d2000b54aa23faf37 [weak]
    - MD5Sum:ec62e16cd333a4c82438580259a719e9 [weak]
    - Filesize:776 [weak]
   Last modification reported: Wed, 21 Jun 2023 21:41:57 +0000
   Release file created at: Thu, 13 Apr 2023 14:12:05 +0000

Works with HTTP Réception de :6 http://deb.nodesource.com/node_18.x jammy/main amd64 Packages [776 B]