distributions: Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata
I am getting this:
1- When trying to install from https://rpm.nodesource.com/setup_12.x
https://rpm.nodesource.com/pub_12.x/el/7/x86_64/nodejs-12.22.7-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata
Trying other mirror.
Error downloading packages:
2:nodejs-12.22.7-1nodesource.x86_64: [Errno 256] No more mirrors to try.
2- When trying to install from https://rpm.nodesource.com/setup_14.x
https://rpm.nodesource.com/pub_14.x/el/7/x86_64/nodejs-14.18.1-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata
Trying other mirror.
Error downloading packages:
2:nodejs-14.18.1-1nodesource.x86_64: [Errno 256] No more mirrors to try.
This was working yesterday.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 55
- Comments: 56 (3 by maintainers)
Commits related to this issue
- fix: docker build issue https://github.com/nodesource/distributions/issues/1290 — committed to qlik-oss/qmfe-actions by nilzona 3 years ago
- fix: docker build issue https://github.com/nodesource/distributions/issues/1290 — committed to qlik-oss/qmfe-actions by nilzona 3 years ago
- fix: docker build issue (#53) https://github.com/nodesource/distributions/issues/1290 — committed to qlik-oss/qmfe-actions by nilzona 3 years ago
- Remove nodejs RPM workaround since nodesource/distributions#1290 is fixed — committed to zrhoffman/trafficcontrol by zrhoffman 2 years ago
- Rocky Linux 8 support (#6535) * Base centos:8-based Dockerfiles on rockylinux:8 * Support Rocky Linux 8, drop CentOS 8 support, retain CentOS 7 support * Import all RPM-GPG-KEY-prefixed keys in... — committed to apache/trafficcontrol by zrhoffman 2 years ago
- Rocky Linux 8 support (#6535) * Base centos:8-based Dockerfiles on rockylinux:8 * Support Rocky Linux 8, drop CentOS 8 support, retain CentOS 7 support * Import all RPM-GPG-KEY-prefixed keys in /et... — committed to apache/trafficcontrol by zrhoffman 2 years ago
- Rocky Linux 8 support (#6535) * Base centos:8-based Dockerfiles on rockylinux:8 * Support Rocky Linux 8, drop CentOS 8 support, retain CentOS 7 support * Import all RPM-GPG-KEY-prefixed keys in /et... — committed to mikeV02/trafficcontrol by zrhoffman 2 years ago
- Updated node_init.sh per https://github.com/nodesource/distributions/issues/1290#issuecomment-960310860 — committed to opedani/webapp-opedani by KageKowalski 2 years ago
same issue
https://rpm.nodesource.com/pub_12.x/el/7/x86_64/nodejs-12.22.7-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata
Error downloading packages: 2:nodejs-12.22.7-1nodesource.x86_64: [Errno 256] No more mirrors to try.
AWS Linux us-east-1 and us-east-2
seems to affect every node version i try
Edit: replacing
sudo yum install nodejs -ywithsudo yum install nodejs-12.22.6-1nodesource -yseems to fix for now, looks like it’s an issue with latest release, if your using a different version, just look at what it’s trying to install and replace the version number in this command with one minor before the one you’re tryingsudo yum install nodejs-[[VERSION]]-1nodesource -yAnother workaround like said above, I have followed and installed Node 14 using, and it worked smooth. Thanks.
This issue appears to be back for nodejs16
Please note that as soon as we detected the issue, we took action to correct it, however, Akamai has shown that its spreading is not even across regions (what makes it a bit unreliable).
Apologies for the inconvenience.
This should be fixed now or in the next few minutes.
Just adding another workaround. We do not want to user 12.22.6 has the .7 patch was a security vulnerability.
So until this is resolved we are able to download the RPM file via:
Then installing it via:
same here:
Thank you for reporting this issue, we are working to fix it.
We’re seeing this as resolved. Our hosts are able to successfully download and install the package using the command we had previously.
Still experiencing it here
Still having the same issue in AWS
This is happening to us. One year since the last one, could be cert related?
https://rpm.nodesource.com/pub_14.x/el/7/x86_64/nodejs-14.21.0-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata
We are also having issues. Are there alternative mirrors that we can use in the meantime?
Confirming that this is still a problem on CentOS 7 trying to install latest 16.x from repository in https://rpm.nodesource.com/pub_16.x/el/7x86_64/.
Happens even after removing
/var/cache/yumand doingyum clean allPerhaps a problem inrepodata?Excerpt of output from
yum install nodejs:workaround confirmed.
Can confirm that the fix from @keepevets worked: Replacing:
with
got our AWS workers auto-scaling again. Thanks!
We get the same error in our AWS code build running in us-east-1.
For us 12 and 14 are working now reproducible from eu-west-1. Thank you!
We’re still facing this in our
us-east-1region:@igsu our CircleCI builds are still running into this problem. Can you confirm it was indeed fixed?
Hey - we are still running in this issue with: yum install -y nodejs
do we need to change the command?
Another workaround is to download and install it directly using the RPM URL:
For people who want to install nodejs 16.x for centos 7
wget https://nodejs.org/dist/v16.15.0/node-v16.15.0-linux-x64.tar.xz
xz -d node-v16.15.0-linux-x64.tar.xz
tar xvf node-v16.15.0-linux-x64.tar
mv node-v16.15.0-linux-x64 /usr/local/nodejs
vi /etc/profile
add line
export PATH=$PATH:‘/usr/local/nodejs/bin’
source /etc/profile node -v npm -v
I got this error again today, My debugging is in morning RUN yum install -y nodejs was installing nodejs-14.20.1 and now same command is installing nodejs-14.20.0 on hard coding version RUN yum install nodejs-14.20.1 -y it is proceeding
For me the manually way works.
Confirmed that this is still not working for me in us-east-1 region:
Akamai is still serving different rpms depending on the edge-node, one hits.
e.g. France (working)
but Ireland (not working)
For nodejs-14.18.1-1nodesource.x86_64.rpm also Germany (where nodejs-12.22.7-1nodesource.x86_64.rpm fails) is working. But Ireland… 😞
Can’t you “just” issue
https://developer.akamai.com/api/core_features/fast_purge/v3.htmlwith either all rpm-urls or worst case for the whole cpcode?It seems like Akamai’s CDN service has not yet fully propagated the modified files. This is most likely the reason that some people are experiencing issues while others are not. I’m not sure how long it will take for this to complete, but there is likely a way to manually expire the cache for the broken files if this does not resolve after a while.
I too am assuming that it’s related to an issue within the
repodatadirectory (I.E. the file’s checksum does not match.)How long do you believe this will get fixed in AWS servers?
@igsu still having the same problem, are there any updates?
As a workaround I used following command
Having this same issue, sometime in the past few hours, running from AWS Codebuild, in this case:
https://rpm.nodesource.com/pub_12.x/el/7/x86_64/nodejs-12.22.7-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadataInteresting that this is happening exactly 1 year from #1126 …is it some sort of package signing certificate expiration thing?