20
5
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?
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 – 2019-07-11T17:38:52.537
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 – 2019-07-15T02:45:20.100
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 – 2019-07-15T02:46:19.893
@music2myear, ordinarily, I'd agree with your close reason. In this case, though, the problem isn't unique to the OP. It's a standard process, documented by Debian. The OP just wasn't familiar with it. Even though the OP can't confirm what worked for them, the question and answers will be applicable to other users. – fixer1234 – 2019-07-16T08:04:55.500
@music2myear, I have unmarked the accepted answer. – geoff – 2019-07-16T12:14:13.463
@music2myear I wrote that answer, after I myself had the exact same problem, and the command I posted solved it for several of my machines. I just didn't mention it in the post. – Alex Stragies – 2020-01-07T17:38:52.957