Bug#931566: Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true")

[Christoph Berg <myon@debian.org>]

Package: apt
Version: 1.8.1
Severity: important

Hi,

I and #debian-devel in general were pretty surprised that our "buster"
systems couldn't properly "apt-get update" anymore today:

+ apt-get update
Get:1 http://mirror.hetzner.de/debian/packages buster InRelease [118 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [39.1 kB]
Get:3 http://ftp.de.debian.org/debian buster InRelease [118 kB]
Hit:4 http://apt.postgresql.org/pub/repos/apt buster-pgdg InRelease
Hit:5 http://atalia.postgresql.org/pub/repos/apt buster-pgdg-testing InRelease
Reading package lists...
E: Repository 'http://mirror.hetzner.de/debian/packages buster InRelease' changed its 'Suite' value from 'testing' to 'stable'
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'testing' to 'stable'
E: Repository 'http://ftp.de.debian.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'

For me, this killed the update process for the build chroots for
apt.postgresql.org.

I guess the same thing will happen once buster is turning oldstable,
breaking out all our stable installations out there. IMHO that's bad.

It might make sense to send a signal to people tracking suites, but if
sources.list is on a codename, it doesn't make any sense to break
systems that are totally fine.

Please consider setting Acquire::AllowReleaseInfoChange::Suite "true";

Or maybe silently do the change when running non-interactively.
Thanks.

Christoph

PS: Please document AllowReleaseInfoChange.