Re: PSA: 'apt-get update' new-Debian-release error fix
On 8/14/21, The Wanderer wrote: > On 2021-08-14 at 19:06, Greg Wooledge wrote: > >> On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote: >> >>> I had enough trouble with this at the last Debian release, >> >> ... but not this time, right? > > Yes, this time; in fact... > >>> For anyone who uses 'apt-get update' - and, I suspect, any other tool >>> than 'apt' itself - to update the list of available packages from the >>> new release, you're at least moderately likely to see the update attempt >>> fail with error messages like the following: >>> >>> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' >>> > changed its 'Codename' value from 'buster' to 'bullseye' >> >> You copied this from the NewInBuster wiki most likely. > > ...nope, I copied it from a terminal on my computer, where it had just > been output on my initial 'apt-get update' attempt. > >> That's where I put it, when I ran into this issue two years ago, and >> documented it there. It's even the same mirror that I use (which is >> no longer the default, hence it standing out). >> >> The issue did not happen this time around. Instead of getting an >> "E:" line (error), you only get a bunch of N: (warning) lines. >> >> You're trying to solve a problem that doesn't actually exist any >> more. > > I would love for that to have been the case, but my experience does not > reflect it being so. > > Maybe somehow I'm running an older apt-get version than what has the > fix(es)? But as far as I know that's shipped in the 'apt' package, and I > have that at version 2.2.4, which is what's currently in both stable and > testing (unsurprising given that they should currently be nearly > identical). Stuff's not totally caught up or something. I've encountered the following a couple of times. The latest was while playing along with a recent Debian-User Docker thread: https://packages.debian.org/search?keywords=docker That packages page says buster is stable and bullseye is still testing. That's possibly (likely?) not the only place still showing similar, too. Yesterday I debootstrap'ed in anticipation of new and not so stable. Only a couple font packages failed as no longer available, and the rest were already hoarded locally here. My previous experience had been that a LOT of packages are not available because Developers haven't brought them up to speed. Examples there would be something like GIMP and Inkscape. This morning there were a lot of upgrades and incidental deletions that were more as expected. Things are slowly rolling along and catching up to speed, I guess. :) OR not.. Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
Re: PSA: 'apt-get update' new-Debian-release error fix
The Wanderer wrote: ... > I had enough trouble with this at the last Debian release, and came > close enough to having trouble with it again this time, that I want to > make sure the solution is available and findable for anyone else who may > need it. ... considering i use only testing in my apt sources list and do not reference bullseye or bookworm directly this is precisely the reason why i use testing and follow it. i don't care about specific version names. having to figure this out is a PITA. definitely a BUG IMO. yet another place where security has made things worse for people who don't need it. i don't know if apt has been fixed or not to honor the don't remove packages from the cache flag i have set, but the last time i ran it ages ago it cleared things out i didn't want it to remove so i won't run it again. i always use apt-get. songbird
Re: PSA: 'apt-get update' new-Debian-release error fix
On Sun, Aug 15, 2021 at 04:40:31PM +0300, ellanios82 wrote: > > - bewildered , am getting stuff like this : > > > GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY F942E0D4E1C726CD > > > . > > what to try please ?? An MX Linux support forum, perhaps? This isn't one.
Re: PSA: 'apt-get update' new-Debian-release error fix
- bewildered , am getting stuff like this : GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F942E0D4E1C726CD . what to try please ?? thanks .
Re: PSA: 'apt-get update' new-Debian-release error fix
On 8/15/21 4:08 AM, Greg Wooledge wrote: Why not simply "apt update"? : i have myself muddled : am getting "NO_PUBKEY" - what to try, please ? thank you regards .
Re: PSA: 'apt-get update' new-Debian-release error fix
On Sat, 14 Aug 2021 20:02:51 -0400 The Wanderer wrote: Hello The, >As do I. It may be possible that this is what makes the difference. I'm almost certain that is the root of it. I recall having to do this at the previous Debian release. I forgot that I'm now using a new machine built after the last release. So glad about your reminder. I would have figured the solution out (I did last time, despite the cryptic info in the man pages), but you saved me a few moments of mild panic. Thank you. -- Regards _ / ) "The blindingly obvious is never immediately apparent" / _)rad "Is it only me that has a working delete key?" I'm spending all my money and it's going up my nose Teenage Depression - Eddie & The Hot Rods pgpEtJCKK4K6k.pgp Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On 2021-08-14 9:08 p.m., Greg Wooledge wrote: > On Sat, Aug 14, 2021 at 08:52:19PM -0400, Polyna-Maude Racicot-Summerside > wrote: >> I got a series of line saying N and one saying E: >> >> N: Repository 'http://security.debian.org buster/updates InRelease' >> changed its 'Suite' value from 'stable' to 'oldstable' >> N: Repository 'http://security.debian.org stretch/updates InRelease' >> changed its 'Suite' value from 'oldstable' to 'oldoldstable' >> E: Repository 'http://deb.debian.org/debian testing InRelease' changed >> its 'Codename' value from 'bullseye' to 'bookworm' > > Fascinating. > >> Will be fixed in a dirty way (remove the offending non needed repository) > > Why not simply "apt update"? > I did apt update when I finally "catched" that it was apt-get update that didn't allow interactive questions. So doing *apt update* fixed it (saying Y helped too). > Also, um... if you weren't planning to track bookworm-as-testing, you > really should've removed that testing line before the bullseye release. > That what I said when I talked about dirty way, removing *testing* but *apt update* worked. -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development OpenPGP_signature Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On Sat, Aug 14, 2021 at 08:52:19PM -0400, Polyna-Maude Racicot-Summerside wrote: > I got a series of line saying N and one saying E: > > N: Repository 'http://security.debian.org buster/updates InRelease' > changed its 'Suite' value from 'stable' to 'oldstable' > N: Repository 'http://security.debian.org stretch/updates InRelease' > changed its 'Suite' value from 'oldstable' to 'oldoldstable' > E: Repository 'http://deb.debian.org/debian testing InRelease' changed > its 'Codename' value from 'bullseye' to 'bookworm' Fascinating. > Will be fixed in a dirty way (remove the offending non needed repository) Why not simply "apt update"? Also, um... if you weren't planning to track bookworm-as-testing, you really should've removed that testing line before the bullseye release.
Re: PSA: 'apt-get update' new-Debian-release error fix
On 2021-08-14 7:45 p.m., The Wanderer wrote: > On 2021-08-14 at 19:41, Greg Wooledge wrote: > >> On Sat, Aug 14, 2021 at 07:26:44PM -0400, The Wanderer wrote: > >>> The warnings I'd be OK with; I might even be OK with the errors, >>> except for the fact that they point not to anything with useful >>> information but to a place which doesn't actually tell you anything >>> helpful. >> >> Yeah, the DD who replied with "If you run it interactive, you get >> asked directly" clearly had no idea > > If I remember that exchange correctly, that seems to have been a case of > confusion about which front-end was being used. If you run 'apt' > interactively rather than for scripting purposes, I understand that you > *do* get asked directly; if you run 'apt-get', however, you don't. > Using *apt update* instead of *apt-get update* solved my problem (without changing my sources.list files). >> In any case, it sounds like your machines have some unique setup >> that's triggering the symptoms in cases where other people won't >> experience them. For now, I'm going to assume that the problem is >> unique to you, unless/until someone else reports it. > > I'd be glad of that, but given the number of other people reporting the > problem in that collection of bug reports, don't expect it to be the > case; that was part of what led me to report the solution here in the > form of a PSA, rather than bringing it up in some other way or just not > mentioning it at all. > >> Also, the fact that people apparently can't manage to find the >> NewInBuster page that describes the symptom and its workaround (not >> even with Google?) is sad. > > I didn't even look this time, since I'd had to look so hard last time > and found nothing anyway. I just ran 'reportbug apt', filtered the list > of bugs for mention of 'secure', and looked at the first bug report - > out of, IIRC, three or four - whose title seemed relevant. > -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development OpenPGP_signature Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On 2021-08-14 7:06 p.m., Greg Wooledge wrote: > On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote: >> I had enough trouble with this at the last Debian release, > > ... but not this time, right? > >> For anyone who uses 'apt-get update' - and, I suspect, any other tool >> than 'apt' itself - to update the list of available packages from the >> new release, you're at least moderately likely to see the update attempt >> fail with error messages like the following: >> >>> E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed >>> its 'Codename' value from 'buster' to 'bullseye' > > You copied this from the NewInBuster wiki most likely. That's where I > put it, when I ran into this issue two years ago, and documented it > there. It's even the same mirror that I use (which is no longer the > default, hence it standing out). > > The issue did not happen this time around. Instead of getting an "E:" > line (error), you only get a bunch of N: (warning) lines. > > You're trying to solve a problem that doesn't actually exist any more. > Running Buster and having a the bullseye repository on my system (source one only). I kept source package repository for stretch, buster, bullseye and testing. Seem to be testing changed from bullseye to bookwork that is complaining. I got a series of line saying N and one saying E: N: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable' N: Repository 'http://security.debian.org stretch/updates InRelease' changed its 'Suite' value from 'oldstable' to 'oldoldstable' E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 'Codename' value from 'bullseye' to 'bookworm' 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.debian.org/debian bullseye InRelease' changed its 'Version' value from '' to '11.0' N: Repository 'http://ftp.debian.org/debian bullseye InRelease' changed its 'Suite' value from 'testing' to 'stable' N: Repository 'http://ftp.debian.org/debian bullseye-updates InRelease' changed its 'Version' value from '' to '11-updates' N: Repository 'http://ftp.debian.org/debian bullseye-updates InRelease' changed its 'Suite' value from 'testing-updates' to 'stable-updates' N: Repository 'https://www.deb-multimedia.org buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable' N: Repository 'http://ftp.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable' N: Repository 'http://ftp.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates' N: Repository 'http://ftp.debian.org/debian stretch-updates InRelease' changed its 'Suite' value from 'oldstable-updates' to 'oldoldstable-updates' N: Repository 'http://ftp.debian.org/debian stretch Release' changed its 'Suite' value from 'oldstable' to 'oldoldstable' Will be fixed in a dirty way (remove the offending non needed repository) -- Polyna-Maude R.-Summerside -Be smart, Be wise, Support opensource development OpenPGP_signature Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On 15-08-2021 10:02, The Wanderer wrote: > On 2021-08-14 at 19:49, Brad Rogers wrote: > >> On Sat, 14 Aug 2021 19:28:32 -0400 Greg Wooledge >> wrote: >> >> Hello Greg, >> >>> It will be interesting to see if anyone else reports the same >>> problem you're seeing. >> >> I experienced it here. >> >> I usually use Synaptic to perform updates. Synaptic put up the >> warning message about the codename change, but I could find no way to >> explicitly accept the changes in Synaptic. As The Wanderer >> suggested, I ran 'apt update' from a command line and followed the >> prompts. >> >> I will add that my sources lists refer only to 'testing', and do not >> use version codenames at all. > > As do I. It may be possible that this is what makes the difference. I always use distribution and never versioning, but have never experienced this problem. Cheers! Harry -- `Unthinking respect for authority is the greatest enemy of truth'. -- Albert Einstein
Re: PSA: 'apt-get update' new-Debian-release error fix
On 2021-08-14 at 19:49, Brad Rogers wrote: > On Sat, 14 Aug 2021 19:28:32 -0400 Greg Wooledge > wrote: > > Hello Greg, > >> It will be interesting to see if anyone else reports the same >> problem you're seeing. > > I experienced it here. > > I usually use Synaptic to perform updates. Synaptic put up the > warning message about the codename change, but I could find no way to > explicitly accept the changes in Synaptic. As The Wanderer > suggested, I ran 'apt update' from a command line and followed the > prompts. > > I will add that my sources lists refer only to 'testing', and do not > use version codenames at all. As do I. It may be possible that this is what makes the difference. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On Sat, 14 Aug 2021 19:28:32 -0400 Greg Wooledge wrote: Hello Greg, >It will be interesting to see if anyone else reports the same problem >you're seeing. I experienced it here. I usually use Synaptic to perform updates. Synaptic put up the warning message about the codename change, but I could find no way to explicitly accept the changes in Synaptic. As The Wanderer suggested, I ran 'apt update' from a command line and followed the prompts. I will add that my sources lists refer only to 'testing', and do not use version codenames at all. -- Regards _ / ) "The blindingly obvious is never immediately apparent" / _)rad "Is it only me that has a working delete key?" But they didn't tell him the first two didn't count Tin Soldiers - Stiff Little Fingers pgpRWfEt8GZ6y.pgp Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On 2021-08-14 at 19:41, Greg Wooledge wrote: > On Sat, Aug 14, 2021 at 07:26:44PM -0400, The Wanderer wrote: >> The warnings I'd be OK with; I might even be OK with the errors, >> except for the fact that they point not to anything with useful >> information but to a place which doesn't actually tell you anything >> helpful. > > Yeah, the DD who replied with "If you run it interactive, you get > asked directly" clearly had no idea If I remember that exchange correctly, that seems to have been a case of confusion about which front-end was being used. If you run 'apt' interactively rather than for scripting purposes, I understand that you *do* get asked directly; if you run 'apt-get', however, you don't. > In any case, it sounds like your machines have some unique setup > that's triggering the symptoms in cases where other people won't > experience them. For now, I'm going to assume that the problem is > unique to you, unless/until someone else reports it. I'd be glad of that, but given the number of other people reporting the problem in that collection of bug reports, don't expect it to be the case; that was part of what led me to report the solution here in the form of a PSA, rather than bringing it up in some other way or just not mentioning it at all. > Also, the fact that people apparently can't manage to find the > NewInBuster page that describes the symptom and its workaround (not > even with Google?) is sad. I didn't even look this time, since I'd had to look so hard last time and found nothing anyway. I just ran 'reportbug apt', filtered the list of bugs for mention of 'secure', and looked at the first bug report - out of, IIRC, three or four - whose title seemed relevant. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On Sat, Aug 14, 2021 at 07:26:44PM -0400, The Wanderer wrote: > See bug #879786, and the various bugs that have been merged into it > (listed near the very bottom, IIRC). Man, some people have the most *bizarre* setups. And then when someone points it out, they act all confused. :-/ Most of the separate instances in that bug report have something wrong with them, like trying to use testing/updates for security after the URL changed, or using Ubuntu repositories, so it's a bit hard to see what's actually happening. > The warnings I'd be OK with; I might even be OK with the errors, except > for the fact that they point not to anything with useful information but > to a place which doesn't actually tell you anything helpful. Yeah, the DD who replied with "If you run it interactive, you get asked directly" clearly had no idea In any case, it sounds like your machines have some unique setup that's triggering the symptoms in cases where other people won't experience them. For now, I'm going to assume that the problem is unique to you, unless/until someone else reports it. Also, the fact that people apparently can't manage to find the NewInBuster page that describes the symptom and its workaround (not even with Google?) is sad.
Re: PSA: 'apt-get update' new-Debian-release error fix
On Sat, Aug 14, 2021 at 07:12:30PM -0400, The Wanderer wrote: > Maybe somehow I'm running an older apt-get version than what has the > fix(es)? But as far as I know that's shipped in the 'apt' package, and I > have that at version 2.2.4, which is what's currently in both stable and > testing (unsurprising given that they should currently be nearly identical). apt version 2.2.4 here. It will be interesting to see if anyone else reports the same problem you're seeing. And, I suppose, to see whether I experience the same problem myself when I do a straight buster-to-bullseye upgrade with no testing in the middle.
Re: PSA: 'apt-get update' new-Debian-release error fix
On 2021-08-14 at 19:15, Greg Wooledge wrote: > On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote: > >> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed >> > its 'Codename' value from 'buster' to 'bullseye' >> > N: This must be accepted explicitly before updates for this repository can >> > be applied. See apt-secure(8) manpage for details. >> >> If you used the label 'buster' instead of 'stable' in your sources.list, >> you may see complaints about a change in the 'Suite' value instead. > > Hmm... after reading your message again, I think we're talking about > two separate problems that have very similar symptoms. > > I've never actually *heard* of your problem before, nor have I seen it. See bug #879786, and the various bugs that have been merged into it (listed near the very bottom, IIRC). > In all cases, whenever I've had a machine that ran *only* stable > releases, this symptom has never happened to me. All > stable-to-stable release upgrades have gone smoothly for me, at least > as far as the "apt-get update" step goes. I'm not sure what you're > doing differently, or why it's not working properly for you. Some of the discussion in the bug report seems to imply that this is only expected to happen if you have a repository which has some aspect which isn't properly configured as trusted on your system. I'm guessing that the exact details of how I access the same repositories which would normally be considered trusted makes them not be so. > What *I* saw (and put on the wiki), was that a machine which ran > buster *as testing* (i.e. was upgraded from stretch to testing, prior > to buster's release) ran into the problem you describe, except that > it said the suite name changed from "testing" to "stable". That sounds like the situation I'm in; I typically dist-upgrade against testing once a day during the weeks after a new release, and then about once a week after that, till it's time to repeat the cycle with the next release. I've been running testing (specified by that name in sources.list) for... long enough that I don't actually remember when I started; it was probably over a decade ago. That said, I *did* somewhat-recently (around the end of June, I think) install a new machine to the same specifications as the old one - using, IIRC, the then-release-candidate installer version - and immediately switch it to target testing, using the same sources.list as on the previous machine. I never ran this '--allow-releaseinfo-change' on the new machine, although I had done it on the old; maybe somehow there's a flag involved other than just the release info itself being different, which hadn't been set previously on this new machine? > When I upgraded my buster-to-testing-to-bullseye machine today, I did > not see this same problem. I got a bunch of warnings, and I > *thought* I was seeing the same problem as last time, but it turns > out I didn't actually have to run "apt update". The "apt-get update" > had worked in the first place. The warnings I'd be OK with; I might even be OK with the errors, except for the fact that they point not to anything with useful information but to a place which doesn't actually tell you anything helpful. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote: > > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed > > its 'Codename' value from 'buster' to 'bullseye' > > N: This must be accepted explicitly before updates for this repository can > > be applied. See apt-secure(8) manpage for details. > > If you used the label 'buster' instead of 'stable' in your sources.list, > you may see complaints about a change in the 'Suite' value instead. Hmm... after reading your message again, I think we're talking about two separate problems that have very similar symptoms. I've never actually *heard* of your problem before, nor have I seen it. In all cases, whenever I've had a machine that ran *only* stable releases, this symptom has never happened to me. All stable-to-stable release upgrades have gone smoothly for me, at least as far as the "apt-get update" step goes. I'm not sure what you're doing differently, or why it's not working properly for you. What *I* saw (and put on the wiki), was that a machine which ran buster *as testing* (i.e. was upgraded from stretch to testing, prior to buster's release) ran into the problem you describe, except that it said the suite name changed from "testing" to "stable". When I upgraded my buster-to-testing-to-bullseye machine today, I did not see this same problem. I got a bunch of warnings, and I *thought* I was seeing the same problem as last time, but it turns out I didn't actually have to run "apt update". The "apt-get update" had worked in the first place.
Re: PSA: 'apt-get update' new-Debian-release error fix
On 2021-08-14 at 19:06, Greg Wooledge wrote: > On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote: > >> I had enough trouble with this at the last Debian release, > > ... but not this time, right? Yes, this time; in fact... >> For anyone who uses 'apt-get update' - and, I suspect, any other tool >> than 'apt' itself - to update the list of available packages from the >> new release, you're at least moderately likely to see the update attempt >> fail with error messages like the following: >> >> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed >> > its 'Codename' value from 'buster' to 'bullseye' > > You copied this from the NewInBuster wiki most likely. ...nope, I copied it from a terminal on my computer, where it had just been output on my initial 'apt-get update' attempt. > That's where I put it, when I ran into this issue two years ago, and > documented it there. It's even the same mirror that I use (which is > no longer the default, hence it standing out). > > The issue did not happen this time around. Instead of getting an > "E:" line (error), you only get a bunch of N: (warning) lines. > > You're trying to solve a problem that doesn't actually exist any > more. I would love for that to have been the case, but my experience does not reflect it being so. Maybe somehow I'm running an older apt-get version than what has the fix(es)? But as far as I know that's shipped in the 'apt' package, and I have that at version 2.2.4, which is what's currently in both stable and testing (unsurprising given that they should currently be nearly identical). -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: PSA: 'apt-get update' new-Debian-release error fix
On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote: > I had enough trouble with this at the last Debian release, ... but not this time, right? > For anyone who uses 'apt-get update' - and, I suspect, any other tool > than 'apt' itself - to update the list of available packages from the > new release, you're at least moderately likely to see the update attempt > fail with error messages like the following: > > > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed > > its 'Codename' value from 'buster' to 'bullseye' You copied this from the NewInBuster wiki most likely. That's where I put it, when I ran into this issue two years ago, and documented it there. It's even the same mirror that I use (which is no longer the default, hence it standing out). The issue did not happen this time around. Instead of getting an "E:" line (error), you only get a bunch of N: (warning) lines. You're trying to solve a problem that doesn't actually exist any more.
PSA: 'apt-get update' new-Debian-release error fix
I had enough trouble with this at the last Debian release, and came close enough to having trouble with it again this time, that I want to make sure the solution is available and findable for anyone else who may need it. For anyone who uses 'apt-get update' - and, I suspect, any other tool than 'apt' itself - to update the list of available packages from the new release, you're at least moderately likely to see the update attempt fail with error messages like the following: > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed its > 'Codename' value from 'buster' to 'bullseye' > N: This must be accepted explicitly before updates for this repository can be > applied. See apt-secure(8) manpage for details. If you used the label 'buster' instead of 'stable' in your sources.list, you may see complaints about a change in the 'Suite' value instead. The error message directs you to the apt-secure(8) man page. This man page does document the reason why this error happens (although not in a very clear or discoverable fashion), but provides no hint about how to explicitly accept the change and allow the update to proceed. That is apparently because the fancy new 'apt' front-end will detect this situation and prompt you to accept the change interactively, but none of the others necessarily will. The actual solution will depend on which apt front-end you're using. For the front-end which is also called 'apt', a simple 'apt update' will apparently be enough; it will apparently prompt you to accept the change interactively, and if you do so, will proceed accordingly. For the 'apt-get' front-end, the necessary solution is to run the command 'apt-get update --allow-releaseinfo-change'. For other front-ends (aptitude, synaptic, others?), there are probably commands which can make it possible to get past this, but I don't know what any of them are. There have been bug reports about this misdirecting documentation, and the lack of any usefully-discoverable pointer to the actual solution, dating back as far as 2017; the bug has been acknowledged, possible solutions have been proposed, but nothing has apparently actually made it into the release as of yet. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
