buster InRelease changed its 'Suite' value from 'stable' to 'oldstable'

[evenSosaAkido]

Hi I'm getting an issue when running curl -sL https://deb.nodesource.com/setup_12.x | bash - from a dockerfile

Step 13/34 : RUN curl -sL https://deb.nodesource.com/setup_12.x | bash -
 ---> Running in 57cecb99a0c6

## Installing the NodeSource Node.js 12.x repo...


## Populating apt-get cache...

+ apt-get update
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:2 http://deb.debian.org/debian buster InRelease [122 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
Get:5 https://dl.yarnpkg.com/debian stable/main amd64 Packages [10.1 kB]
Get:6 https://dl.yarnpkg.com/debian stable/main all Packages [10.1 kB]
Reading package lists...
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
Error executing command, exiting

I read you need to just accept the changes but the way the script is set I think we cannot answer any questions. Do you know any workarounds for this?

[feline-fanatic]

I'm running into the same issue. I think --allow-releaseinfo-change needs to be added to the apt-get update command.

[flgraveline]

Running into the same issue in my DockerFile using nodesource/setup_8.x.

I'm using a temporary dirty fix to see if it solves the issue, basically appending the flag after the apt-get in the script :thinking:

curl -sL https://deb.nodesource.com/setup_8.x | sed "s/exec_cmd 'apt-get update'/exec_cmd 'apt-get --allow-releaseinfo-change update'/" | bash -

(change the setup_8.x to your desired version)

[evenSosaAkido]

Running into the same issue in my DockerFile using nodesource/setup_8.x.

I'm using a temporary dirty fix to see if it solves the issue, basically appending the flag after the apt-get in the script 🤔

curl -sL https://deb.nodesource.com/setup_8.x | sed "s/exec_cmd 'apt-get update'/exec_cmd 'apt-get --allow-releaseinfo-change update'/" | bash -

@flgraveline did that work for you? I wasn't able to make sed work that way

[flgraveline]

@flgraveline did that work for you? I wasn't able to make sed work that way

@evenSosaAkido

Seemed to have done the trick for me, it replaces each exec_cmd 'apt-get update' with exec_cmd 'apt-get --allow-releaseinfo-change update'.

Note that I'm using the setup_8.x though, not sure if it's exactly the same for setup_12.x.

You can play with it without actually executing anything in a terminal to see which outputs it gives :

curl -sL https://deb.nodesource.com/setup_12.x | sed "s/exec_cmd 'apt-get update'/exec_cmd 'apt-get --allow-releaseinfo-change update'/"

[evenSosaAkido]

@flgraveline tried to play around with my own script using your logic but didn't do the replacement for some reason. But I just gave it a shot with the actual setup_12.x and it worked perfectly, thanks a lot!

[LightnerDev]

I ran curl -sL https://deb.nodesource.com/setup_8.x | sed "s/exec_cmd 'apt-get update'/exec_cmd 'apt-get --allow-releaseinfo-change update'/" | bash - which gave an output of

## Installing the NodeSource Node.js 14.x repo...
## Populating apt-get cache...
+ apt-get --allow-releaseinfo-change update
Reading package lists... Done
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
Error executing command, exiting

[JinShil]

Debian 11 Bullseye was released: https://www.debian.org/News/2021/20210814 See also https://www.debian.org/releases/ for the "stable", "oldstable", etc... naming conventions.

[LightnerDev]

Since I was on Linux, I found an alternative: NodeJS For Linux Debian In the URL you can change the 14.x to any version (16.6 doesn't work, you use 16.x)

[JesusPaz]

This issue is resolved with our new repository. More information can be found here.

[alibajelan]

just change dns to 8.8.8.8 , 4.4.4.4 this worked for me