Your message dated Mon, 16 Aug 2021 06:57:25 +0100 with message-id <9f24f3b7e8779b2b85105833ab6680914a645cb1.camel@adam-barratt.org.uk> and subject line Re: Bug#992225: Suite value change for buster package list causes apt-get update failures has caused the Debian Bug report #992225, regarding Suite value change for buster package list causes apt-get update failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 992225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992225 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Suite value change for buster package list causes apt-get update failures
- From: Kamal Ramchandani <kamal.ramchandani@robinhood.com>
- Date: Sun, 15 Aug 2021 22:40:51 -0700
- Message-id: <[🔎] CAPVFGxCX60dvvHRY1MM3z+JhMzcmUiD907NtbrXg1gLMSdHqFw@mail.gmail.com>
Package: apt
Version: 1.8.2.2
It seems that the for buster package list, the 'Suite' value was changed from 'stable' to 'oldstable' on Sat, 14 Aug 2021
Reference - http://ftp.debian.org/debian/dists/buster/InRelease
This is breaking apt-get update across hundreds of services that we use.
Error logs as follows
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
One option for us is to use the --allow-releaseinfo-change flag. But, doing so across all services is disruptive and a time consuming effort.
I wanted to check if this can be resolved on the debian side by maintaining backwards compatibility in the package list.
--- End Message ---
--- Begin Message ---
- To: Kamal Ramchandani <kamal.ramchandani@robinhood.com>, 992225-done@bugs.debian.org
- Subject: Re: Bug#992225: Suite value change for buster package list causes apt-get update failures
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Mon, 16 Aug 2021 06:57:25 +0100
- Message-id: <9f24f3b7e8779b2b85105833ab6680914a645cb1.camel@adam-barratt.org.uk>
- In-reply-to: <[🔎] CAPVFGxCX60dvvHRY1MM3z+JhMzcmUiD907NtbrXg1gLMSdHqFw@mail.gmail.com>
- References: <[🔎] CAPVFGxCX60dvvHRY1MM3z+JhMzcmUiD907NtbrXg1gLMSdHqFw@mail.gmail.com>
Version: 1.8.2.3 On Sun, 2021-08-15 at 22:40 -0700, Kamal Ramchandani wrote: > Package: apt > Version: 1.8.2.2 > > It seems that the for buster package list, the 'Suite' value was > changed from 'stable' to 'oldstable' on Sat, 14 Aug 2021 > Reference - http://ftp.debian.org/debian/dists/buster/InRelease Yes, there was a release, so stable is now "bullseye" and buster is oldstable. > This is breaking apt-get update across hundreds of services that we > use. > > Error logs as follows > E: Repository 'http://security.debian.org/debian-security > buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable' > E: Repository 'http://deb.debian.org/debian buster InRelease' changed > its 'Suite' value from 'stable' to 'oldstable' > E: Repository 'http://deb.debian.org/debian buster-updates InRelease' > changed its 'Suite' value from 'stable-updates' to 'oldstable- > updates' > This implies that the systems in question are not up-to-date - apt 1.8.2.3 has been in buster since June (as part of the 10.10 point release, and downgrades that error to an informational notice. I'm marking this bug as resolved in that version on that basis. > One option for us is to use the --allow-releaseinfo-change flag. But, > doing so across all services is disruptive and a time consuming > effort. > > I wanted to check if this can be resolved on the debian side by > maintaining backwards compatibility in the package list. This isn't a question of backward compatibility. buster is no longer stable, it would be wrong for the repository metadata to claim that it is. If you ensure that all your systems are up-to-date, this should not be an issue. Regards, Adam
--- End Message ---