On Sun, 7 Jul 2019 16:41:27 +0200 Francesco Poli wrote: [...] > I am looking forward to seeing this fix implemented.
Hello again! After more than two years, this bug is still unfixed in aptitude... # cat /etc/apt/sources.list deb http://deb.debian.org/debian testing main deb http://deb.debian.org/debian unstable main deb http://deb.debian.org/debian-security testing-security main # aptitude update && aptitude --purge-unused safe-upgrade Get: 1 http://deb.debian.org/debian testing InRelease [81.6 kB] Get: 2 http://deb.debian.org/debian unstable InRelease [165 kB] Get: 3 http://deb.debian.org/debian-security testing-security InRelease [35.6 kB] Fetched 282 kB in 8s (36.6 kB/s) E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 'Codename' value from 'bullseye' to 'bookworm' E: Repository 'http://deb.debian.org/debian-security testing-security InRelease' changed its 'Codename' value from 'bullseye-security' to 'bookworm-security' E: Failed to download some files W: Failed to fetch http://deb.debian.org/debian/dists/testing/InRelease: W: Failed to fetch http://deb.debian.org/debian-security/dists/testing-security/InRelease: E: Some index files failed to download. They have been ignored, or old ones used instead. Once again, I had to work around the bug by using 'apt update': # apt update Get:1 http://deb.debian.org/debian testing InRelease [81.6 kB] Hit:2 http://deb.debian.org/debian unstable InRelease Get:3 http://deb.debian.org/debian-security testing-security InRelease [35.6 kB] 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. Do you want to accept these changes and continue updating from this repository? [y/N] y E: Repository 'http://deb.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. Do you want to accept these changes and continue updating from this repository? [y/N] y Reading package lists... Done Building dependency tree... Done Reading state information... Done 4 packages can be upgraded. Run 'apt list --upgradable' to see them. At that point, I was able to resume my usual upgrade routine with: # aptitude update && aptitude --purge-unused safe-upgrade Are there any plans to fix this bug in aptitude once and for all? Please -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpKIcA1v7Ihn.pgp
Description: PGP signature
_______________________________________________ Aptitude-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel
