Bug#958120: apt-secure man page does not give promised information
Package: apt
Version: 2.0.2
Severity: normal
When an InRelease file changes, apt-get update gives the following error:
E: Repository 'http://approx.local:9999/debian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
The apt-secure man page describes _why_ this happens, but gives
absolutely no clue about how to fix it. While different front ends may
have different ways to do this, the apt-secure man page should at the
very least point explicitly to the --allow-releaseinfo-change option of
the apt-get man page, so the user can follow the error message to a
solution, without resorting to guessing or googling.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable'), (200, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages apt depends on:
ii adduser 3.118
ii debian-archive-keyring 2019.1
ii gpgv 2.2.20-1
ii libapt-pkg6.0 2.0.2
ii libc6 2.30-4
ii libgcc-s1 10-20200411-1
ii libgnutls30 3.6.13-2
ii libseccomp2 2.4.3-1+b1
ii libstdc++6 10-20200411-1
ii libsystemd0 238-5
Versions of packages apt recommends:
ii ca-certificates 20190110
Versions of packages apt suggests:
pn apt-doc <none>
ii aptitude 0.8.12-3
ii dpkg-dev 1.19.7
ii gnupg 2.2.20-1
ii powermgmt-base 1.36
ii synaptic 0.90+nmu1
-- no debconf information
Reply to: