Re: [solved?] Can't Upgrade to Buster
On Sun, Jul 07, 2019 at 12:05:30PM -0500, Mark Allums wrote: > On 7/7/19 9:42 AM, Brad Rogers wrote: > >On Sun, 7 Jul 2019 08:44:52 -0500 > >Mark Allums wrote: > > > >Hello Mark, > > >>I am not exactly sure why you are concerned about "mixed repos". > > > >Personally, I'm not. However, the nature of your questions indicated to > >me that you aren't entirely at home fiddling with this stuff. I stress; > >to me. It also seems I may have come to the wrong conclusion about your > >capabilities in this area. My apologies. > > No problem. I am experienced, but I don't subscribe to all the > mailing lists. I'm no guru. > > > > >Having a mixture of stable and testing under certain circumstances can > >be a recipe for disaster. Check the list archives; there are quite a > >few examples of people getting into a mess when mixing repos in this way. > > > > Generally updates to discrete packages and sets of packages are > okay. I am careful about system packages. E.g., I would update VLC > or LibreOffice, but not systemd. Take into account that one of those might want to pull in a new libc (the installer will make a lot of noise then :-) That's where the real fun starts... Cheers -- t signature.asc Description: Digital signature
Re: [solved?] Can't Upgrade to Buster
On 7/7/19 9:42 AM, Brad Rogers wrote: On Sun, 7 Jul 2019 08:44:52 -0500 Mark Allums wrote: Hello Mark, I am not exactly sure why you are concerned about "mixed repos". Personally, I'm not. However, the nature of your questions indicated to me that you aren't entirely at home fiddling with this stuff. I stress; to me. It also seems I may have come to the wrong conclusion about your capabilities in this area. My apologies. No problem. I am experienced, but I don't subscribe to all the mailing lists. I'm no guru. Having a mixture of stable and testing under certain circumstances can be a recipe for disaster. Check the list archives; there are quite a few examples of people getting into a mess when mixing repos in this way. Generally updates to discrete packages and sets of packages are okay. I am careful about system packages. E.g., I would update VLC or LibreOffice, but not systemd. Thanks for all your help. Mark
Re: [solved?] Can't Upgrade to Buster
On Sun, 7 Jul 2019 08:44:52 -0500
Mark Allums wrote:
Hello Mark,
{snip explanation of synaptic behaviour}
I was already aware of synaptic's behaviour, I use it myself quite a
bit, but thanks for the explanation. It's as well to get it on list so
others can be informed. I always try to remember that for every person
that asks a question there may be ten (or more) people who are too shy
to do so, but equally keen for an answer.
>I am not exactly sure why you are concerned about "mixed repos".
Personally, I'm not. However, the nature of your questions indicated to
me that you aren't entirely at home fiddling with this stuff. I stress;
to me. It also seems I may have come to the wrong conclusion about your
capabilities in this area. My apologies.
Having a mixture of stable and testing under certain circumstances can
be a recipe for disaster. Check the list archives; there are quite a
few examples of people getting into a mess when mixing repos in this way.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Hey there, Mr Average, you don't exist, you never did
Persons Unknown - Poison Girls
pgpoTe_6j9rhq.pgp
Description: OpenPGP digital signature
Re: [solved?] Can't Upgrade to Buster
On 7/7/19 8:19 AM, Brad Rogers wrote: On Sun, 7 Jul 2019 07:30:51 -0500 Mark Allums wrote: Hello Mark, enabling bullseye in sources.list and running apt update seems to have Why add bullseye (testing)? Your talk thus far has been about buster (stable). It seems to me that you have mixed repos in your sources.list. I was running buster (testing) before release. Synaptic seemed to want testing. It seemed intuitive to give it what it wanted. I don't intend to run testing for a while. I will soon comment out the bullseye line in sources.list and see what happens. But FYI, it is OK to have both stable and testing enabled when using exclusively using Synaptic. As long as you don't install massive amounts of packages from both. And as long as you don't use apt-get/apt or aptitude CLI. You can tell Synaptic to prefer whichever repository you want. By default, it prefers "highest". But you can tell it it "stable" or "testing", and it will abide by your choice. In a few months, I will reenable bullseye and move to it. I am not exactly sure why you are concerned about "mixed repos". Mark
Re: [solved?] Can't Upgrade to Buster
On Sun, 7 Jul 2019 07:30:51 -0500 Mark Allums wrote: Hello Mark, >enabling bullseye in sources.list and running apt update seems to have Why add bullseye (testing)? Your talk thus far has been about buster (stable). It seems to me that you have mixed repos in your sources.list. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" A friend of a friend he got beaten I Predict A Riot - Kaiser Chiefs pgp7CztO8tw0I.pgp Description: OpenPGP digital signature
Re: [solved?] Can't Upgrade to Buster
On 7/7/19 6:59 AM, wrote: root@martha:~# apt-get update Get:1 http://deb.debian.org/debian buster InRelease [118 kB] Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB] Get:3 http://security.debian.org buster/updates InRelease [31.1 kB] Get:4 http://deb.debian.org/debian buster-updates InRelease [46.8 kB] Hit:5 http://packages.microsoft.com/repos/vscode stable InRelease Hit:6 https://repo.skype.com/deb stable InRelease Hit:7 https://packages.microsoft.com/debian/9/prod stretch InRelease Hit:8 http://deb.debian.org/debian sid InReleaseHit:9 http://deb.debian.org/debian experimental InRelease Ign:10 http://repo.vivaldi.com/stable/deb stable InRelease Hit:11 http://repo.vivaldi.com/stable/deb stable Release Ign:12 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 InRelease Hit:14 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 Release Reading package lists... Done N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0' E: Repository 'http://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. 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. 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. E: Repository 'http://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. For Buster its best to use apt update - then just answer y to accept the change in repo status to stable or However if you want to use apt-get still, perform this command: # apt-get --allow-releaseinfo-change update > Running synaptic, I get: > E: The value 'testing' is invalid for APT::Default-Release as such a > release is not available in the sources > E: _cache->open() failed, please report. Well, I don't know what an official proper solution would be, but enabling bullseye in sources.list and running apt update seems to have done it. At least Synaptic runs without error, now. Mark
Apt vs Apt-get (Was: Can't Upgrade to Buster}
On 7/7/19 4:29 AM, Mark Allums wrote: > I never heard of the difference between apt-get and apt (no -get). Is > this new? I found this article that explains the differences between apt and apt-get. https://itsfoss.com/apt-vs-apt-get-difference/ The Debian Wiki has a section on apt as well. https://wiki.debian.org/DebianPackageManagement#Apt Apt exists to simplify usage of apt-get, by consolidating the most used options across the different "apt-get" and "apt-cache" commands into a single interface. IE instead of having to remember that you use "apt-cache search" instead of "apt-get search" you can just use "apt search". "apt-get dist-upgrade" becomes "apt full-upgrade". Things like that Apt also has a few new commands such as "apt list" which can be used in some nifty ways such as: $ apt list --upgradable To see which packages can be upgraded $ apt list --installed To see which packages are installed $ apt list foo To see which packages match the criteria $ apt list | grep foo To pipe the results of apt list into grep, to do some grep magic. Apt-get and Apt-cache still work, and there are still specific functions that they do that apt itself doesn't, but for day-to-day tasks apt works very well, and in many ways works easier and better than apt-get and apt-cache. Cheers. -Matt signature.asc Description: OpenPGP digital signature
Re: Can't Upgrade to Buster
On Sun, 7 Jul 2019 08:18:57 -0400 songbird wrote: Hello songbird, > some of us run testing on purpose. OP is running Buster. He says so in the subject and body of his message. The advice was for the OP. What you and I run isn't relevant. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" What do you call that noise, that you put on? This Is Pop - XTC pgpIQNzy_czyL.pgp Description: OpenPGP digital signature
Re: Can't Upgrade to Buster
john doe wrote: ... > Don't you have 'testing' in your '/etc/apt/sources.list'? yes. > If so, try to change it to 'stable'. no. some of us run testing on purpose. songbird
Re: Can't Upgrade to Buster
On Sun, 7 Jul 2019 06:08:27 -0500 Mark Allums wrote: Hello Mark, >root@martha:~# apt-secure >-bash: apt-secure: command not found > > >What do I do? apt-secure, despite appearances, isn't a command. What you do is, as indicated Dekks, #apt update, and accept changes. This will put things straight correct version number [10] and code name). Once done, you can simply carry on as before. I don't recall having to do this before, so it may be a (comparatively) new requirement. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" An old custom to sell your daughter Hong Kong Garden - Siouxsie & The Banshees pgp3AB_2ZFqz3.pgp Description: OpenPGP digital signature
Re: Can't Upgrade to Buster
On 7/7/2019 6:15 AM, Dekks Herton wrote: Mark Allums writes: I've been running Buster in Testing happily for months. So technically, I'm already upgraded. However, root@martha:~# apt-get update Get:1 http://deb.debian.org/debian buster InRelease [118 kB] Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB] Get:3 http://security.debian.org buster/updates InRelease [31.1 kB] Get:4 http://deb.debian.org/debian buster-updates InRelease [46.8 kB] Hit:5 http://packages.microsoft.com/repos/vscode stable InRelease Hit:6 https://repo.skype.com/deb stable InRelease Hit:7 https://packages.microsoft.com/debian/9/prod stretch InRelease Hit:8 http://deb.debian.org/debian sid InRelease Hit:9 http://deb.debian.org/debian experimental InRelease Ign:10 http://repo.vivaldi.com/stable/deb stable InRelease Hit:11 http://repo.vivaldi.com/stable/deb stable Release Ign:12 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 InRelease Hit:14 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 Release Reading package lists... Done N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0' E: Repository 'http://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. 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. 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. E: Repository 'http://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. root@martha:~# apt-secure -bash: apt-secure: command not found What do I do? For Buster its best to use apt update - then just answer y to accept the change in repo status to stable I never heard of the difference between apt-get and apt (no -get). Is this new? Mark
Re: Can't Upgrade to Buster
On Sun, 7 Jul 2019 06:38:56 -0500 Mark Allums wrote: Hello Mark, >has surfaced. Running synaptic, I get: >E: The value 'testing' is invalid for APT::Default-Release as such a >release is not available in the sources >E: _cache->open() failed, please report. Didn't happen here and I often use synaptic. >Apropos: Is Bullseye up yet? Seems to be. Nothing updatable yet, though. But in a few days time I expect to see a trickle, which will turn into a torrent, and then settle down once everything recovers from the dam sluices being reopened. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Drums quite good, bass is too loud, and I can't hear the words Sound Of The Suburbs - Members pgpAubQ9aiII4.pgp Description: OpenPGP digital signature
Re: Can't Upgrade to Buster
On 2019-07-07 06:41 -0500, Mark Allums wrote: > Thank you. I never heard of Apt as opposed to apt-get. Is this new? It's been there since apt 1.0, released in April 2014. Cheers, Sven
Re: Can't Upgrade to Buster
On 7/7/2019 6:37 AM, Matthew Crews wrote: On 7/7/19 4:15 AM, Dekks Herton wrote: Mark Allums writes: I've been running Buster in Testing happily for months. So technically, I'm already upgraded. However, **snip** What do I do? For Buster its best to use apt update - then just answer y to accept the change in repo status to stable Indeed, apt is the preferred tool instead of apt-get. However if you want to use apt-get still, perform this command: # apt-get --allow-releaseinfo-change update -Matt Thank you. I never heard of Apt as opposed to apt-get. Is this new? Mark
Re: Can't Upgrade to Buster
On 7/7/19 6:15 AM, Dekks Herton wrote: Mark Allums writes: I've been running Buster in Testing happily for months. So technically, I'm already upgraded. However, root@martha:~# apt-get update Get:1 http://deb.debian.org/debian buster InRelease [118 kB] Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB] Get:3 http://security.debian.org buster/updates InRelease [31.1 kB] Get:4 http://deb.debian.org/debian buster-updates InRelease [46.8 kB] Hit:5 http://packages.microsoft.com/repos/vscode stable InRelease Hit:6 https://repo.skype.com/deb stable InRelease Hit:7 https://packages.microsoft.com/debian/9/prod stretch InRelease Hit:8 http://deb.debian.org/debian sid InRelease Hit:9 http://deb.debian.org/debian experimental InRelease Ign:10 http://repo.vivaldi.com/stable/deb stable InRelease Hit:11 http://repo.vivaldi.com/stable/deb stable Release Ign:12 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 InRelease Hit:14 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 Release Reading package lists... Done N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0' E: Repository 'http://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. 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. 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. E: Repository 'http://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. root@martha:~# apt-secure -bash: apt-secure: command not found What do I do? For Buster its best to use apt update - then just answer y to accept the change in repo status to stable This worked. Was there an alternate solution? However, a new problem has surfaced. Running synaptic, I get: E: The value 'testing' is invalid for APT::Default-Release as such a release is not available in the sources E: _cache->open() failed, please report. and it closes. Apropos: Is Bullseye up yet? Mark
Re: Can't Upgrade to Buster
On 7/7/19 4:15 AM, Dekks Herton wrote: > Mark Allums writes: > >> I've been running Buster in Testing happily for months. So technically, I'm >> already upgraded. However, **snip** >> What do I do? > > For Buster its best to use apt update - then just answer y to accept the > change in repo status to stable > Indeed, apt is the preferred tool instead of apt-get. However if you want to use apt-get still, perform this command: # apt-get --allow-releaseinfo-change update -Matt signature.asc Description: OpenPGP digital signature
Re: Can't Upgrade to Buster
On 7/7/19 6:08 AM, Mark Allums wrote: I've been running Buster in Testing happily for months. So technically, I'm already upgraded. However, root@martha:~# apt-get update Get:1 http://deb.debian.org/debian buster InRelease [118 kB] Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB] Get:3 http://security.debian.org buster/updates InRelease [31.1 kB] Get:4 http://deb.debian.org/debian buster-updates InRelease [46.8 kB] Hit:5 http://packages.microsoft.com/repos/vscode stable InRelease Hit:6 https://repo.skype.com/deb stable InRelease Hit:7 https://packages.microsoft.com/debian/9/prod stretch InRelease Hit:8 http://deb.debian.org/debian sid InRelease Hit:9 http://deb.debian.org/debian experimental InRelease Ign:10 http://repo.vivaldi.com/stable/deb stable InRelease Hit:11 http://repo.vivaldi.com/stable/deb stable Release Ign:12 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 InRelease Hit:14 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 Release Reading package lists... Done N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0' E: Repository 'http://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. 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. 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. E: Repository 'http://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. root@martha:~# apt-secure -bash: apt-secure: command not found What do I do? Mark To go along with this, here's my /etc/apt/sources.list. I have a few third-party sources in /etc/apt/sources.list.d. deb http://deb.debian.org/debian/ buster non-free contrib main deb http://security.debian.org/debian-security/ buster/updates non-free contrib main deb http://security.debian.org/ buster/updates contrib non-free main deb http://deb.debian.org/debian/ buster-updates non-free contrib main #deb http://deb.debian.org/debian/ bullseye non-free contrib main #deb http://security.debian.org/debian-security/ bullseye/updates non-free contrib main #deb http://security.debian.org/ bullseye/updates contrib non-free main #deb http://deb.debian.org/debian/ bullseye-updates non-free contrib main deb http://deb.debian.org/debian/ sid non-free contrib main deb http://deb.debian.org/debian/ experimental main contrib non-free Mark
Re: Can't Upgrade to Buster
On 7/7/2019 1:08 PM, Mark Allums wrote: > I've been running Buster in Testing happily for months. So technically, > I'm already upgraded. However, > >> root@martha:~# apt-get update >> Get:1 http://deb.debian.org/debian buster InRelease [118 kB] >> Get:2 http://security.debian.org/debian-security buster/updates >> InRelease [31.1 kB] >> Get:3 http://security.debian.org buster/updates InRelease [31.1 >> kB] Get:4 http://deb.debian.org/debian buster-updates >> InRelease [46.8 kB] Hit:5 >> http://packages.microsoft.com/repos/vscode stable >> InRelease Hit:6 https://repo.skype.com/deb stable >> InRelease Hit:7 >> https://packages.microsoft.com/debian/9/prod stretch >> InRelease Hit:8 http://deb.debian.org/debian sid >> InRelease Hit:9 http://deb.debian.org/debian >> experimental InRelease >> Ign:10 http://repo.vivaldi.com/stable/deb stable InRelease >> Hit:11 http://repo.vivaldi.com/stable/deb stable Release >> Ign:12 >> http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 >> InRelease >> Hit:14 >> http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 >> Release >> Reading package lists... Done >> N: Repository 'http://deb.debian.org/debian buster InRelease' changed >> its 'Version' value from '' to '10.0' >> E: Repository 'http://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. >> 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. >> 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. >> E: Repository 'http://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. > > root@martha:~# apt-secure > -bash: apt-secure: command not found > > > What do I do? > Don't you have 'testing' in your '/etc/apt/sources.list'? If so, try to change it to 'stable'. -- John Doe
Re: Can't Upgrade to Buster
Mark Allums writes: > I've been running Buster in Testing happily for months. So technically, I'm > already upgraded. However, > >> root@martha:~# apt-get update >> Get:1 http://deb.debian.org/debian buster InRelease [118 kB] >> Get:2 http://security.debian.org/debian-security buster/updates InRelease >> [31.1 kB] >> Get:3 http://security.debian.org buster/updates InRelease [31.1 kB] >> Get:4 http://deb.debian.org/debian buster-updates InRelease [46.8 >> kB] Hit:5 http://packages.microsoft.com/repos/vscode stable >> InRelease Hit:6 https://repo.skype.com/deb stable InRelease Hit:7 >> https://packages.microsoft.com/debian/9/prod stretch InRelease Hit:8 >> http://deb.debian.org/debian sid InRelease Hit:9 >> http://deb.debian.org/debian experimental InRelease >> Ign:10 http://repo.vivaldi.com/stable/deb stable InRelease >> Hit:11 http://repo.vivaldi.com/stable/deb stable Release >> Ign:12 >> http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 >> InRelease >> Hit:14 >> http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 >> Release >> Reading package lists... Done >> N: Repository 'http://deb.debian.org/debian buster InRelease' changed its >> 'Version' value from '' to '10.0' >> E: Repository 'http://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. >> 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. >> 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. >> E: Repository 'http://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. > > root@martha:~# apt-secure > -bash: apt-secure: command not found > > > What do I do? For Buster its best to use apt update - then just answer y to accept the change in repo status to stable -- Regards. PGP Fingerprint: 3DF8 311C 4740 B5BC 3867 72DF 1050 452F 9BCE BA00
Can't Upgrade to Buster
I've been running Buster in Testing happily for months. So technically, I'm already upgraded. However, root@martha:~# apt-get update Get:1 http://deb.debian.org/debian buster InRelease [118 kB] Get:2 http://security.debian.org/debian-security buster/updates InRelease [31.1 kB] Get:3 http://security.debian.org buster/updates InRelease [31.1 kB] Get:4 http://deb.debian.org/debian buster-updates InRelease [46.8 kB] Hit:5 http://packages.microsoft.com/repos/vscode stable InRelease Hit:6 https://repo.skype.com/deb stable InRelease Hit:7 https://packages.microsoft.com/debian/9/prod stretch InRelease Hit:8 http://deb.debian.org/debian sid InRelease Hit:9 http://deb.debian.org/debian experimental InRelease Ign:10 http://repo.vivaldi.com/stable/deb stable InRelease Hit:11 http://repo.vivaldi.com/stable/deb stable Release Ign:12 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 InRelease Hit:14 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_9.0 Release Reading package lists... Done N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '' to '10.0' E: Repository 'http://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. 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. 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. E: Repository 'http://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. root@martha:~# apt-secure -bash: apt-secure: command not found What do I do? Mark
