1 1
guidol

[Info] check/start manually "apt update" because of buster-repository value changes

Recommended Posts

because of some value changes for buster updates via apt (or buster going stable)

N: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Version' value from '' to '10'
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] Y

N: Repository 'http://cdn-fastly.deb.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://cdn-fastly.deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] Y


E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'testing-updates' to 'stable-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] Y

you should accept the changes to get new package-lists.

 

If you only do (like me) a apt update in a update-script - the script will  throw an error (because of the missing acceptance) and didnt load the new package-list :(

 

A apt update -y will do the trick in the script or you have to start it once manually and accept with Y

 

 

 

Share this post


Link to post
Share on other sites

@Igor while compiling images I do see this messages.

Do you know if the compiling-script accept the new values as the E: could mean error.

 

Cant fix this via manually do a "apt update -y" or "apt upgrade -y" because this doesnt work to the apt commands in the compile-script :(


 


Get:4 http://security.debian.org buster/updates InRelease [39.1 kB]
Err:5 http://apt.armbian.com buster InRelease
  Connection failed [IP: 127.0.0.1 3142]
Reading package lists...
E: Repository 'http://httpredir.debian.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'
E: Repository 'http://httpredir.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'testing-updates' to 'stable-updates'
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'testing' to 'stable'


Get:7 http://apt.armbian.com buster/buster-utils armhf Packages [3,108 B]
Reading package lists...
E: Repository 'http://httpredir.debian.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'
E: Repository 'http://httpredir.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'testing-updates' to 'stable-updates'
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'testing' to 'stable'

 

Share this post


Link to post
Share on other sites
3 hours ago, guidol said:

Do you know if the compiling-script accept the new values as the E: could mean error.

 

I don't thing this is error and its anyway outside out domain. Debian repository label changed from testing to stable ... Perhaps this is technically an error, but IMO its not. 

 

Our sources definition looks correct: https://github.com/armbian/build/blob/master/lib/general.sh#L128-L149 We don't use label stable/testing but codename. 

Share this post


Link to post
Share on other sites

https://www.reddit.com/r/debian/comments/ca3se6/for_people_who_gets_this_error_inrelease_changed/

If someone get it as well then the solution is relative simple.

Run "apt-get --allow-releaseinfo-change update" and you should be ready to use Buster

 

https://superuser.com/questions/1456989/how-to-configure-apt-in-debian-buster-after-release

This results in the error, and the indication, that you need to "allow the change of the release version information".

Luckily, apt-get has an option for that, aptly named allow-releaseinfo-change

When running apt-get with this option, it notices -as without- the version discrepancy (the N:-lines), but now accepts it as told to do, and then updates the local database.

apt-get --allow-releaseinfo-change update

 

Share this post


Link to post
Share on other sites
On 7/10/2019 at 8:18 PM, Igor said:

 

I don't thing this is error and its anyway outside out domain. Debian repository label changed from testing to stable ... Perhaps this is technically an error, but IMO its not. 

 

but I am afraid of:

 

E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value

from 'testing-updates' to 'stable-updates'
N: This must be accepted explicitly before updates for this repository can be applied.

See apt-secure(8) manpage for details.
 

 

Share this post


Link to post
Share on other sites
 
but I am afraid of:
 
E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value
from 'testing-updates' to 'stable-updates'
N: This must be accepted explicitly before updates for this repository can be applied.
See apt-secure(8) manpage for details.
 
 


This issue resolved itself with a new rootfs during build.


Sent from my iPad using Tapatalk

Share this post


Link to post
Share on other sites
1 1