On Sat, Sep 7, 2019 at 4:45 PM Sven Joachim <svenj...@gmx.de> wrote: > So the file looks like this: > > ,---- > | Origin: Debian > | Label: Debian-Security > | Suite: stable > | Version: 10 > | Codename: buster > | Date: Fri, 06 Sep 2019 11:51:20 UTC > | Valid-Until: Fri, 13 Sep 2019 11:51:20 UTC > | Acquire-By-Hash: yes > | Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el > s390x > | Components: updates/main updates/contrib updates/non-free > | Description: Debian 10 - Security Updates > `---- > > Which is definitely wrong for buster-updates, this is how an InRelease > file from the security repository starts. > > It's hard to tell how this happened (file system corruption perhaps), > but if you proceed with the update it should be corrected. > Run "apt-get update --allow-releaseinfo-change" to do so.
Ok thanks for pointing that out apt-get update --allow-releaseinfo-change did the trick. But I want to understand what was wrong in previous file and what did you noticed that should have been there which was not there in my file. ---------------------- Thanks and Regards Tapas