Control: forcemerge 879786 -1 On Sun, May 19, 2019 at 11:37:57PM +0200, Thorsten Glaser wrote: > Package: apt > Version: 1.8.0 > Severity: normal > > (but ought to be release-critical, see last paragraph) > > > E: Repository 'http://debs.tarent.de buster InRelease' changed its 'Suite' > value from 'buster' to 'testing' > N: This must be accepted explicitly before updates for this repository can be > applied. See apt-secure(8) manpage for details. > > Sure, but the apt-secure(8) manpage is 8 screen pages, and while > I eventually (took me some time) found the right section, it does > not document *how* one would accept this change: > > INFORMATION CHANGES > A Release file contains beside the checksums for the files in the > repository also general information about the repository like the > origin, codename or version number of the release. > > This information is shown in various places so a repository owner > should always ensure correctness. Further more user configuration like > apt_preferences(5) can depend and make use of this information. Since > version 1.5 the user must therefore explicitly confirm changes to > signal that the user is sufficiently prepared e.g. for the new major > release of the distribution shipped in the repository (as e.g. > indicated by the codename). > > Nothing in here shows the correct way, so people will duckduckgo for > answers and likely find things like “sudo chmod 777 somefile” on > ask*buntu, or something… > > … for the record, I *believe* that adding --allow-releaseinfo-change > to apt-get update is right, but this appears only in the apt-get(8) > manpage, not in apt(8) which some people believe is the new tool, and > especially not in apt-secure(8) where the user is directed to. > > As such, this is a rather severe documentation bug that I believe > ought to be fixed before buster.
Merging this into the other bug -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
