TL;DR:
$ sudo apt-get update --allow-releaseinfo-change
Debian acaba de liberar bullseye. En mi caso particular utilizo
testing, lo cual no me afecta mucho aparte de que se
termina el período de freezing.
Lo que me tomó por sorpresa fué que al actualizar los repositorios obtuviera el siguiente mensaje:
$ sudo apt-get update
Get:1 http://deb.debian.org/debian testing InRelease [81.6 kB]
Get:2 http://security.debian.org/debian-security testing-security InRelease [35.6 kB]
Get:3 http://deb.debian.org/debian testing-updates InRelease [36.8 kB]
Hit:4 https://download.virtualbox.org/virtualbox/debian buster InRelease
Reading package lists... Done
E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 'Codename' value from 'bullseye' to 'bookworm'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E: Repository 'http://security.debian.org/debian-security testing-security InRelease' changed its 'Codename' value from 'bullseye-security' to 'bookworm-security'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E: Repository 'http://deb.debian.org/debian testing-updates InRelease' changed its 'Codename' value from 'bullseye-updates' to 'bookworm-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Leyendo la página del manual de apt-secure, se indica que
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).
Pero por otro lado no hay indicación de como hacer esto.
El tip se encuentra en las Release Notes for Debian 11 (bullseye):
Users of apt-secure may find issues when using
aptitudeorapt-get. For apt-get, you can useapt-get update --allow-releaseinfo-change.
Confirmando en la página del manual de apt-get:
–allow-releaseinfo-change Allow the update command to continue downloading data from a repository which changed its information of the release contained in the repository indicating e.g a new major release. APT will fail at the update command for such repositories until the change is confirmed to ensure the user is prepared for the change
Por lo que, luego de haber entendido todo lo anterior, ejecutamos:
$ sudo apt-get update --allow-releaseinfo-change
(Luego de esta actualización no es necesario volver a utilizar el parámetro
--allow-releaseinfo-change.)
Realmente no recordaba este paso, aunque creo que es entendible ya que debe realizarse solo una vez cada dos años… Espero recordar este post para 2024 cuando se libere bookworm :)