[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1033487: apt: apt-get says "This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details." but apt-secure(8) doesn't tell where or how to accept it



Package: apt
Version: 2.6.0
Control: found -1 1.8.2.3

"apt-get update" says:

E: Repository 'https://debian.ethz.ch/debian experimental InRelease' changed its 'Codename' value from 'experimental' to 'rc-buggy'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

But apt-secure(8) does not explain how to actually accept it:

  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).

IMHO either the message from apt-get or at least the apt-secure(8) man
page should explain,

a) that (only) "apt update" (and neither apt-get nor aptitude) provides
   an interactive prompt to accept that change, and

b) that apt-get can accept that change via the
   --allow-releaseinfo-change option. (And yeah, aptitude lacks that
   option as of now.)

Had a user nearly going nuts because of not finding out how to fix this
due to not being mentioned in the message nor in the referenced man
page. (He didn't look into the apt-get man page as that one wasn't
referenced.)

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'testing-security'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages apt depends on:
ii  adduser                    3.132
ii  base-passwd                3.6.1
ii  debian-archive-keyring     2023.2
ii  gpgv                       2.2.40-1
ii  gpgv1                      1.4.23-1.1+b1
ii  libapt-pkg6.0              2.6.0
ii  libc6                      2.36-8
ii  libelogind0 [libsystemd0]  246.10-1debian1
ii  libgcc-s1                  12.2.0-14
ii  libgnutls30                3.7.9-1
ii  libseccomp2                2.5.4-1+b3
ii  libstdc++6                 12.2.0-14

Versions of packages apt recommends:
ii  ca-certificates  20230311

Versions of packages apt suggests:
ii  apt-doc         2.6.0
ii  aptitude        0.8.13-5+abe+test1+bug1032654
ii  dpkg-dev        1.21.21
ii  gnupg           2.2.40-1
ii  gnupg1          1.4.23-1.1+b1
ii  gnupg2          2.2.40-1
ii  powermgmt-base  1.37
ii  wajig           4.0.3

-- no debconf information


Reply to: