How to configure apt in Debian Buster after releaseReinstalling Debian Squeeze via APT after significant core package removalWhere are Debian packages hosted?How to configure apt-cacher for ftpapt-get requests installation media after installing Debian 7debian install package bittwistDebian XFCE “Session and Startup” doesn't see all applicationsDebian Scripting to remove the logging during apt-get installafter debian stretch install (RC3), apt signature issue(s)File .profile is not sourced on Debian Buster (testing)apt-get throws 400 URI failure when trying to download docker-ce

Did the First Order follow Poe to Jakku, or did they independently discover that the map fragment was there?

Why do the faithful have to say "And with your spirit " in Catholic Mass?

Is there an English equivalent for "Les carottes sont cuites", while keeping the vegetable reference?

Align by center of symbol

What do mathematicians mean when they say some conjecture can’t be proven using the current technology?

Draw a line nicely around notes

When to ask for constructive criticism?

Old short story where the future emperor of the galaxy is taken for a tour around Earth

What's the phrasal verb for carbonated drinks exploding out of the can after being shaken?

Too many spies!

What are the arguments for California’s nonpartisan blanket primaries?

Sending a photo of my bank account card to the future employer

Will it hurt my career to work as a graphic designer in a startup for beauty and skin care?

Is there a way to handmake alphabet pasta?

Why use null function instead of == [] to check for empty list in Haskell?

Adding a vertical line at the right end of the horizontal line in frac

Animal Shelter Management C++

Accidentally deleted python and yum is not working in centos7

Can both line and load go to same screw on a GFCI outlet?

What impact would a dragon the size of Asia have on the environment?

I do not have power to all my breakers

line break after the word "proof" in proof environment

When do sending stones recharge if they are in different time zones (or different planes)?

What is the technical explanation of the note "A♭" in a F7 chord in the key of C?



How to configure apt in Debian Buster after release


Reinstalling Debian Squeeze via APT after significant core package removalWhere are Debian packages hosted?How to configure apt-cacher for ftpapt-get requests installation media after installing Debian 7debian install package bittwistDebian XFCE “Session and Startup” doesn't see all applicationsDebian Scripting to remove the logging during apt-get installafter debian stretch install (RC3), apt signature issue(s)File .profile is not sourced on Debian Buster (testing)apt-get throws 400 URI failure when trying to download docker-ce






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








11















I currently run Debian Buster on my computer as testing.
Now that Buster has become stable, how should I update my system?



Specifically, how do I configure /etc/apt/sources.list?



Currently, it looks like this:



# deb cdrom:[Official Debian GNU/Linux Live 9.9.0 xfce 2019-04-27T10:47]/ stretch main
# deb cdrom:[Official Debian GNU/Linux Live 9.9.0 xfce 2019-04-27T10:47]/ stretch main

deb http://ftp.uk.debian.org/debian/ buster main
deb-src http://ftp.uk.debian.org/debian/ buster main
deb http://security.debian.org/debian-security/ buster/updates main
deb-src http://security.debian.org/debian-security/ buster/updates main

#stretch-updates, previously known as 'volatile'
deb http://ftp.uk.debian.org/debian/ buster-updates main
deb-src http://ftp.uk.debian.org/debian/ buster-updates main


And when I run sudo apt-get update I get this output:



Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB]
Get:3 http://ftp.uk.debian.org/debian buster InRelease [118 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://ftp.uk.debian.org/debian buster-updates InRelease [46.8 kB]
Get:6 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Reading package lists... Done
E: Repository 'http://security.debian.org/debian-security 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.
N: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://ftp.uk.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.
E: Repository 'http://ftp.uk.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.
E: Repository 'http://deb.debian.org/debian stretch Release' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.


Update:
I ran sudo apt update and had this dialog with the update manager:



geoff@geoff-debian:/etc/apt$ sudo apt update
Get:1 http://ftp.uk.debian.org/debian buster InRelease [118 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB]
E: Repository 'http://security.debian.org/debian-security 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
Get:3 http://ftp.uk.debian.org/debian buster-updates InRelease [46.8 kB]
Ign:4 http://deb.debian.org/debian stretch InRelease
Get:5 http://deb.debian.org/debian stretch Release [118 kB]
Get:6 http://security.debian.org/debian-security buster/updates/main Sources [1,688 B]
Get:7 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Get:8 http://security.debian.org/debian-security buster/updates/main amd64 Packages [1,448 B]
Get:9 http://security.debian.org/debian-security buster/updates/main Translation-en [1,364 B]
N: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://ftp.uk.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://ftp.uk.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
E: Repository 'http://deb.debian.org/debian stretch Release' changed its 'Suite' value from 'stable' to 'oldstable'
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
Fetched 171 kB in 1min 6s (2,594 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
159 packages can be upgraded. Run 'apt list --upgradable' to see them.
geoff@geoff-debian:/etc/apt$


Is this fine? I am particularly concerned with the old-stable message. Am I supposed to have this repository still?










share|improve this question
























  • Unfortunately, I cannot test the answers below, because I had to reinstall Debian for some other reasons. However, I accepted @alex-stragies answer, because it had the most votes.

    – geoff
    Jul 11 at 17:38












  • We want answers that work, not popular answers. Because you can no longer test solutions to this problem, and you were not able to find a solution, this question should be closed.

    – music2myear
    18 hours ago











  • I'm voting to close this question as off-topic because OP had to perform a work around and is not able to test solutions. The marked answer is the popular answer and cannot be verified in this situation.

    – music2myear
    18 hours ago

















11















I currently run Debian Buster on my computer as testing.
Now that Buster has become stable, how should I update my system?



Specifically, how do I configure /etc/apt/sources.list?



Currently, it looks like this:



# deb cdrom:[Official Debian GNU/Linux Live 9.9.0 xfce 2019-04-27T10:47]/ stretch main
# deb cdrom:[Official Debian GNU/Linux Live 9.9.0 xfce 2019-04-27T10:47]/ stretch main

deb http://ftp.uk.debian.org/debian/ buster main
deb-src http://ftp.uk.debian.org/debian/ buster main
deb http://security.debian.org/debian-security/ buster/updates main
deb-src http://security.debian.org/debian-security/ buster/updates main

#stretch-updates, previously known as 'volatile'
deb http://ftp.uk.debian.org/debian/ buster-updates main
deb-src http://ftp.uk.debian.org/debian/ buster-updates main


And when I run sudo apt-get update I get this output:



Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB]
Get:3 http://ftp.uk.debian.org/debian buster InRelease [118 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://ftp.uk.debian.org/debian buster-updates InRelease [46.8 kB]
Get:6 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Reading package lists... Done
E: Repository 'http://security.debian.org/debian-security 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.
N: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://ftp.uk.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.
E: Repository 'http://ftp.uk.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.
E: Repository 'http://deb.debian.org/debian stretch Release' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.


Update:
I ran sudo apt update and had this dialog with the update manager:



geoff@geoff-debian:/etc/apt$ sudo apt update
Get:1 http://ftp.uk.debian.org/debian buster InRelease [118 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB]
E: Repository 'http://security.debian.org/debian-security 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
Get:3 http://ftp.uk.debian.org/debian buster-updates InRelease [46.8 kB]
Ign:4 http://deb.debian.org/debian stretch InRelease
Get:5 http://deb.debian.org/debian stretch Release [118 kB]
Get:6 http://security.debian.org/debian-security buster/updates/main Sources [1,688 B]
Get:7 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Get:8 http://security.debian.org/debian-security buster/updates/main amd64 Packages [1,448 B]
Get:9 http://security.debian.org/debian-security buster/updates/main Translation-en [1,364 B]
N: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://ftp.uk.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://ftp.uk.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
E: Repository 'http://deb.debian.org/debian stretch Release' changed its 'Suite' value from 'stable' to 'oldstable'
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
Fetched 171 kB in 1min 6s (2,594 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
159 packages can be upgraded. Run 'apt list --upgradable' to see them.
geoff@geoff-debian:/etc/apt$


Is this fine? I am particularly concerned with the old-stable message. Am I supposed to have this repository still?










share|improve this question
























  • Unfortunately, I cannot test the answers below, because I had to reinstall Debian for some other reasons. However, I accepted @alex-stragies answer, because it had the most votes.

    – geoff
    Jul 11 at 17:38












  • We want answers that work, not popular answers. Because you can no longer test solutions to this problem, and you were not able to find a solution, this question should be closed.

    – music2myear
    18 hours ago











  • I'm voting to close this question as off-topic because OP had to perform a work around and is not able to test solutions. The marked answer is the popular answer and cannot be verified in this situation.

    – music2myear
    18 hours ago













11












11








11


3






I currently run Debian Buster on my computer as testing.
Now that Buster has become stable, how should I update my system?



Specifically, how do I configure /etc/apt/sources.list?



Currently, it looks like this:



# deb cdrom:[Official Debian GNU/Linux Live 9.9.0 xfce 2019-04-27T10:47]/ stretch main
# deb cdrom:[Official Debian GNU/Linux Live 9.9.0 xfce 2019-04-27T10:47]/ stretch main

deb http://ftp.uk.debian.org/debian/ buster main
deb-src http://ftp.uk.debian.org/debian/ buster main
deb http://security.debian.org/debian-security/ buster/updates main
deb-src http://security.debian.org/debian-security/ buster/updates main

#stretch-updates, previously known as 'volatile'
deb http://ftp.uk.debian.org/debian/ buster-updates main
deb-src http://ftp.uk.debian.org/debian/ buster-updates main


And when I run sudo apt-get update I get this output:



Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB]
Get:3 http://ftp.uk.debian.org/debian buster InRelease [118 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://ftp.uk.debian.org/debian buster-updates InRelease [46.8 kB]
Get:6 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Reading package lists... Done
E: Repository 'http://security.debian.org/debian-security 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.
N: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://ftp.uk.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.
E: Repository 'http://ftp.uk.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.
E: Repository 'http://deb.debian.org/debian stretch Release' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.


Update:
I ran sudo apt update and had this dialog with the update manager:



geoff@geoff-debian:/etc/apt$ sudo apt update
Get:1 http://ftp.uk.debian.org/debian buster InRelease [118 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB]
E: Repository 'http://security.debian.org/debian-security 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
Get:3 http://ftp.uk.debian.org/debian buster-updates InRelease [46.8 kB]
Ign:4 http://deb.debian.org/debian stretch InRelease
Get:5 http://deb.debian.org/debian stretch Release [118 kB]
Get:6 http://security.debian.org/debian-security buster/updates/main Sources [1,688 B]
Get:7 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Get:8 http://security.debian.org/debian-security buster/updates/main amd64 Packages [1,448 B]
Get:9 http://security.debian.org/debian-security buster/updates/main Translation-en [1,364 B]
N: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://ftp.uk.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://ftp.uk.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
E: Repository 'http://deb.debian.org/debian stretch Release' changed its 'Suite' value from 'stable' to 'oldstable'
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
Fetched 171 kB in 1min 6s (2,594 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
159 packages can be upgraded. Run 'apt list --upgradable' to see them.
geoff@geoff-debian:/etc/apt$


Is this fine? I am particularly concerned with the old-stable message. Am I supposed to have this repository still?










share|improve this question
















I currently run Debian Buster on my computer as testing.
Now that Buster has become stable, how should I update my system?



Specifically, how do I configure /etc/apt/sources.list?



Currently, it looks like this:



# deb cdrom:[Official Debian GNU/Linux Live 9.9.0 xfce 2019-04-27T10:47]/ stretch main
# deb cdrom:[Official Debian GNU/Linux Live 9.9.0 xfce 2019-04-27T10:47]/ stretch main

deb http://ftp.uk.debian.org/debian/ buster main
deb-src http://ftp.uk.debian.org/debian/ buster main
deb http://security.debian.org/debian-security/ buster/updates main
deb-src http://security.debian.org/debian-security/ buster/updates main

#stretch-updates, previously known as 'volatile'
deb http://ftp.uk.debian.org/debian/ buster-updates main
deb-src http://ftp.uk.debian.org/debian/ buster-updates main


And when I run sudo apt-get update I get this output:



Ign:1 http://deb.debian.org/debian stretch InRelease
Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB]
Get:3 http://ftp.uk.debian.org/debian buster InRelease [118 kB]
Get:4 http://deb.debian.org/debian stretch Release [118 kB]
Get:5 http://ftp.uk.debian.org/debian buster-updates InRelease [46.8 kB]
Get:6 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Reading package lists... Done
E: Repository 'http://security.debian.org/debian-security 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.
N: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://ftp.uk.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.
E: Repository 'http://ftp.uk.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.
E: Repository 'http://deb.debian.org/debian stretch Release' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.


Update:
I ran sudo apt update and had this dialog with the update manager:



geoff@geoff-debian:/etc/apt$ sudo apt update
Get:1 http://ftp.uk.debian.org/debian buster InRelease [118 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB]
E: Repository 'http://security.debian.org/debian-security 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
Get:3 http://ftp.uk.debian.org/debian buster-updates InRelease [46.8 kB]
Ign:4 http://deb.debian.org/debian stretch InRelease
Get:5 http://deb.debian.org/debian stretch Release [118 kB]
Get:6 http://security.debian.org/debian-security buster/updates/main Sources [1,688 B]
Get:7 http://deb.debian.org/debian stretch Release.gpg [2,434 B]
Get:8 http://security.debian.org/debian-security buster/updates/main amd64 Packages [1,448 B]
Get:9 http://security.debian.org/debian-security buster/updates/main Translation-en [1,364 B]
N: Repository 'http://ftp.uk.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0'
E: Repository 'http://ftp.uk.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://ftp.uk.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
E: Repository 'http://deb.debian.org/debian stretch Release' changed its 'Suite' value from 'stable' to 'oldstable'
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
Fetched 171 kB in 1min 6s (2,594 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
159 packages can be upgraded. Run 'apt list --upgradable' to see them.
geoff@geoff-debian:/etc/apt$


Is this fine? I am particularly concerned with the old-stable message. Am I supposed to have this repository still?







debian






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 7 at 10:40







geoff

















asked Jul 7 at 10:14









geoffgeoff

581 silver badge5 bronze badges




581 silver badge5 bronze badges












  • Unfortunately, I cannot test the answers below, because I had to reinstall Debian for some other reasons. However, I accepted @alex-stragies answer, because it had the most votes.

    – geoff
    Jul 11 at 17:38












  • We want answers that work, not popular answers. Because you can no longer test solutions to this problem, and you were not able to find a solution, this question should be closed.

    – music2myear
    18 hours ago











  • I'm voting to close this question as off-topic because OP had to perform a work around and is not able to test solutions. The marked answer is the popular answer and cannot be verified in this situation.

    – music2myear
    18 hours ago

















  • Unfortunately, I cannot test the answers below, because I had to reinstall Debian for some other reasons. However, I accepted @alex-stragies answer, because it had the most votes.

    – geoff
    Jul 11 at 17:38












  • We want answers that work, not popular answers. Because you can no longer test solutions to this problem, and you were not able to find a solution, this question should be closed.

    – music2myear
    18 hours ago











  • I'm voting to close this question as off-topic because OP had to perform a work around and is not able to test solutions. The marked answer is the popular answer and cannot be verified in this situation.

    – music2myear
    18 hours ago
















Unfortunately, I cannot test the answers below, because I had to reinstall Debian for some other reasons. However, I accepted @alex-stragies answer, because it had the most votes.

– geoff
Jul 11 at 17:38






Unfortunately, I cannot test the answers below, because I had to reinstall Debian for some other reasons. However, I accepted @alex-stragies answer, because it had the most votes.

– geoff
Jul 11 at 17:38














We want answers that work, not popular answers. Because you can no longer test solutions to this problem, and you were not able to find a solution, this question should be closed.

– music2myear
18 hours ago





We want answers that work, not popular answers. Because you can no longer test solutions to this problem, and you were not able to find a solution, this question should be closed.

– music2myear
18 hours ago













I'm voting to close this question as off-topic because OP had to perform a work around and is not able to test solutions. The marked answer is the popular answer and cannot be verified in this situation.

– music2myear
18 hours ago





I'm voting to close this question as off-topic because OP had to perform a work around and is not able to test solutions. The marked answer is the popular answer and cannot be verified in this situation.

– music2myear
18 hours ago










4 Answers
4






active

oldest

votes


















24














tl;dr : run once apt-get update --allow-releaseinfo-change



What happens here, is that the local apt database remembered your package-sources "release-information" to be "busterAsTesting", and when updating now "busterAsStable" is returned.



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.






share|improve this answer
































    2














    1. open synaptic

    2. in menu select settings-->repositories

    3. in tabs uncheck everything

    4. close the tabs and let it make the update

    5. open again the repositories dialog and check everything you want

    6. close the tabs and update again and it is OK





    share|improve this answer

























    • This worked for me!

      – user1059517
      Jul 8 at 20:39



















    1














    I suggest using




    apt update --allow-releaseinfo-change




    This was because apt-get update --allow-releaseinfo-change did not work for me.



    I cant comment on the accepted answer above. So if all else fails, use my answer.






    share|improve this answer






























      0














      Run apt update and accept changes (type y each time when asked). It will made all required changes.






      share|improve this answer








      New contributor



      Volodymyr Bodenchuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



















      • The OP says to have already done apt update. This is not going to change anything to the situation, an edit of /etc/apt/sources.list seems to be necessary here.

        – Ale
        Jul 11 at 12:05













      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "3"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1456989%2fhow-to-configure-apt-in-debian-buster-after-release%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      24














      tl;dr : run once apt-get update --allow-releaseinfo-change



      What happens here, is that the local apt database remembered your package-sources "release-information" to be "busterAsTesting", and when updating now "busterAsStable" is returned.



      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.






      share|improve this answer





























        24














        tl;dr : run once apt-get update --allow-releaseinfo-change



        What happens here, is that the local apt database remembered your package-sources "release-information" to be "busterAsTesting", and when updating now "busterAsStable" is returned.



        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.






        share|improve this answer



























          24












          24








          24







          tl;dr : run once apt-get update --allow-releaseinfo-change



          What happens here, is that the local apt database remembered your package-sources "release-information" to be "busterAsTesting", and when updating now "busterAsStable" is returned.



          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.






          share|improve this answer















          tl;dr : run once apt-get update --allow-releaseinfo-change



          What happens here, is that the local apt database remembered your package-sources "release-information" to be "busterAsTesting", and when updating now "busterAsStable" is returned.



          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.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jul 8 at 13:15

























          answered Jul 7 at 11:21









          Alex StragiesAlex Stragies

          9787 silver badges16 bronze badges




          9787 silver badges16 bronze badges























              2














              1. open synaptic

              2. in menu select settings-->repositories

              3. in tabs uncheck everything

              4. close the tabs and let it make the update

              5. open again the repositories dialog and check everything you want

              6. close the tabs and update again and it is OK





              share|improve this answer

























              • This worked for me!

                – user1059517
                Jul 8 at 20:39
















              2














              1. open synaptic

              2. in menu select settings-->repositories

              3. in tabs uncheck everything

              4. close the tabs and let it make the update

              5. open again the repositories dialog and check everything you want

              6. close the tabs and update again and it is OK





              share|improve this answer

























              • This worked for me!

                – user1059517
                Jul 8 at 20:39














              2












              2








              2







              1. open synaptic

              2. in menu select settings-->repositories

              3. in tabs uncheck everything

              4. close the tabs and let it make the update

              5. open again the repositories dialog and check everything you want

              6. close the tabs and update again and it is OK





              share|improve this answer















              1. open synaptic

              2. in menu select settings-->repositories

              3. in tabs uncheck everything

              4. close the tabs and let it make the update

              5. open again the repositories dialog and check everything you want

              6. close the tabs and update again and it is OK






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jul 8 at 1:26









              gamer0

              5515 silver badges20 bronze badges




              5515 silver badges20 bronze badges










              answered Jul 7 at 15:03









              user1059517user1059517

              311 bronze badge




              311 bronze badge












              • This worked for me!

                – user1059517
                Jul 8 at 20:39


















              • This worked for me!

                – user1059517
                Jul 8 at 20:39

















              This worked for me!

              – user1059517
              Jul 8 at 20:39






              This worked for me!

              – user1059517
              Jul 8 at 20:39












              1














              I suggest using




              apt update --allow-releaseinfo-change




              This was because apt-get update --allow-releaseinfo-change did not work for me.



              I cant comment on the accepted answer above. So if all else fails, use my answer.






              share|improve this answer



























                1














                I suggest using




                apt update --allow-releaseinfo-change




                This was because apt-get update --allow-releaseinfo-change did not work for me.



                I cant comment on the accepted answer above. So if all else fails, use my answer.






                share|improve this answer

























                  1












                  1








                  1







                  I suggest using




                  apt update --allow-releaseinfo-change




                  This was because apt-get update --allow-releaseinfo-change did not work for me.



                  I cant comment on the accepted answer above. So if all else fails, use my answer.






                  share|improve this answer













                  I suggest using




                  apt update --allow-releaseinfo-change




                  This was because apt-get update --allow-releaseinfo-change did not work for me.



                  I cant comment on the accepted answer above. So if all else fails, use my answer.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jul 11 at 11:20









                  Leon185Leon185

                  113 bronze badges




                  113 bronze badges





















                      0














                      Run apt update and accept changes (type y each time when asked). It will made all required changes.






                      share|improve this answer








                      New contributor



                      Volodymyr Bodenchuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.



















                      • The OP says to have already done apt update. This is not going to change anything to the situation, an edit of /etc/apt/sources.list seems to be necessary here.

                        – Ale
                        Jul 11 at 12:05















                      0














                      Run apt update and accept changes (type y each time when asked). It will made all required changes.






                      share|improve this answer








                      New contributor



                      Volodymyr Bodenchuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.



















                      • The OP says to have already done apt update. This is not going to change anything to the situation, an edit of /etc/apt/sources.list seems to be necessary here.

                        – Ale
                        Jul 11 at 12:05













                      0












                      0








                      0







                      Run apt update and accept changes (type y each time when asked). It will made all required changes.






                      share|improve this answer








                      New contributor



                      Volodymyr Bodenchuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.









                      Run apt update and accept changes (type y each time when asked). It will made all required changes.







                      share|improve this answer








                      New contributor



                      Volodymyr Bodenchuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.








                      share|improve this answer



                      share|improve this answer






                      New contributor



                      Volodymyr Bodenchuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.








                      answered Jul 9 at 17:49









                      Volodymyr BodenchukVolodymyr Bodenchuk

                      91 bronze badge




                      91 bronze badge




                      New contributor



                      Volodymyr Bodenchuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.




                      New contributor




                      Volodymyr Bodenchuk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.














                      • The OP says to have already done apt update. This is not going to change anything to the situation, an edit of /etc/apt/sources.list seems to be necessary here.

                        – Ale
                        Jul 11 at 12:05

















                      • The OP says to have already done apt update. This is not going to change anything to the situation, an edit of /etc/apt/sources.list seems to be necessary here.

                        – Ale
                        Jul 11 at 12:05
















                      The OP says to have already done apt update. This is not going to change anything to the situation, an edit of /etc/apt/sources.list seems to be necessary here.

                      – Ale
                      Jul 11 at 12:05





                      The OP says to have already done apt update. This is not going to change anything to the situation, an edit of /etc/apt/sources.list seems to be necessary here.

                      – Ale
                      Jul 11 at 12:05

















                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1456989%2fhow-to-configure-apt-in-debian-buster-after-release%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown