Hi, Jeremy,

Because Bullseye was released over the weekend, we've seen the following message for the last two days (i.e. on Saturday night and Sunday night) when cron runs at night.  Is there anything that we need to do in order to ensure that Buster updates continue to be downloaded and installed on our appliances?

CRON-APT RUN [/etc/cron-apt/config]: Mon Aug 16 00:10:01 UTC 2021
CRON-APT SLEEP: 924, Mon Aug 16 00:25:25 UTC 2021
CRON-APT ACTION: 0-update
CRON-APT LINE: /usr/bin/apt-get -o quiet=1 update -o quiet=2
E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'

Replies (6)

Output Error: changed its 'Suite' value from 'stable' to 'oldst

Reply 1

I changed bootstrap_ap and insert :
apt-get --allow-releaseinfo-change update

Test It.

Run one of the commands in my previous post

Reply 3

If you use the '--allow-releaseinfo-change update' switch with apt/apt-get update, or run apt/apt-get interactively (and answer 'y' when asked) that should resolve the issue.

I.e. Either run:

apt-get update --allow-releaseinfo-change update

Or run this interactively (and answer 'y' if/when asked):

apt update

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

Reply 4

I am getting this in my turnkey core server.  What file do I make the above change to inorder for the daily security updates cron job not fail.

Hi Gary

Reply 5

As banana hinted in their comment, if you run:

apt-get --allow-releaseinfo-change update

Then that should fix the error message. To double check by re-running the apt update, i.e.:

apt update

All Fixed

Reply 6

Hi,

That seems to have done the trick.  Thank you so much!