Package: apt Version: 2.6.1 (amd64) Severity: normal First I want to say that my system is nothing special. I don't have any fancy settings and most things are at default.
A few days ago I ran 'apt update' and it said something like this (error #1, This is not the only error. Please keep reading.): "File has unexpected size (32 != 1104). Mirror sync in progress?" Someone has the same error here https://askubuntu.com/questions/1147254/apt-update-fails-at-chrome-stable-main-file-has-unexpected-size-1103-1104 Normally this is not a problem because you can wait until the server works again. So I waited until the next day and tried again. But I got another error which looks like this (error #2): user1@user1-laptop1:/media/user1/SMO-STICK$ sudo apt update Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB] Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://download.virtualbox.org/virtualbox/debian bookworm InRelease E: Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Label' value from 'Debian' to 'Debian-Security' N: Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Version' value from '12-updates' to '12' N: Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Suite' value from 'stable-updates' to 'stable-security' E: Repository 'http://security.debian.org/debian-security bookworm-security InRelease' changed its 'Codename' value from 'bookworm-updates' 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] However if you look into waybackmachine you can see that these tags (Label, Version, ...) never changed. This error didn't go away even after waiting multiple days. I suppose that error #2 is a result of error #1. Error #1 seems to have changed the tags to wrong values. Someone had the same problem in 2022 here https://lists.debian.org/debian-user/2022/12/msg00412.html This person also has the issue with the debian-security repository. It seems to be a rare issue (bug). So the actual bug is that apt wants me to confirm changed tags which actually never changed. I now confirmed the message with 'y' and everything seems to work. I am only reporting this so it will get fixed and other users won't experience it. Best regards Stefan
