Bug#931566: Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true")
Re: Paul Wise 2019-09-02 <[🔎] 68737fa6fe19d3c2a71beadefbe69c661dd4d271.camel@debian.org>
> I recently had a similar issue with the backports repos:
>
> E: Repository 'https://incoming.debian.org/debian-buildd buildd-stretch-backports-sloppy InRelease' changed its default priority for apt_preferences(5) from 500 to 100.
> E: Repository 'https://cdn-aws.deb.debian.org/debian stretch-backports-sloppy InRelease' changed its default priority for apt_preferences(5) from 500 to 100.
>
> This was because those suites got a couple of settings added to their
> Release files in the apt repository:
>
> NotAutomatic: yes
> ButAutomaticUpgrades: yes
I think this is an example of something that this mechanism *should*
catch, especially if the change would have gone the other way round.
But the pain caused by testing->stable and oldstable->stable is still
much more prevalent than the legitimate cases. If we don't find a
solution that can tell these apart in a robust way, we should disable
the whole thing in stable.
Christoph
Reply to: