Hello When I run aptitude update I get, amongst the successful update reports, the following error messages:
W: There is no public key available for the following key IDs: 1397BC53640DB551 W: Failed to fetch http://http.debian.net/debian/dists/jessie-backports/main/i18n/Translation-enIndex: Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. E: Couldn't rebuild package cache I'm not sure if the warning about the key and the second warning are related or not, I've got my doubts. My sources.list looks like this: # # deb cdrom:[Debian GNU/Linux wheezy-DI-a1 _Wheezy_ - Official Snapshot amd64 NETINST Binary-1 20120512-00:39]/ wheezy main # deb cdrom:[Debian GNU/Linux wheezy-DI-a1 _Wheezy_ - Official Snapshot amd64 NETINST Binary-1 20120512-00:39]/ wheezy main deb http://ftp.jp.debian.org/debian/ jessie main contrib non-free deb-src http://ftp.jp.debian.org/debian/ jessie main contrib non-free deb http://security.debian.org/ jessie/updates main contrib non-free deb-src http://security.debian.org/ jessie/updates main contrib non-free deb http://ftp.jp.debian.org/debian/ jessie-updates main contrib non-free deb http://www.deb-multimedia.org jessie main non-free and files in sources.list.d add the following: deb http://dl.google.com/linux/talkplugin/deb/ stable main deb http://http.debian.net/debian/ jessie-backports main I'm located in Japan, hence my (long-standing) use of the Japan Debian mirror ftp.jp.debian.org for the mainstream stuff, but I came late to the party of automatic mirror selection, hence my more-recently-added jessie-backports using http.debian.net. Which seems to be having some sort of problem... I imagine jessie-backports is available on ftp.jp.debian.org, but rather than camouflage the problem I'd like to understand and solve it. Googling around the missing key ID, most of the solutions are for Ubuntu and mention PPAs which are not a Debian thing. I am not sure where to go to find the public key with that key ID, for the first warning, and I really don't know how to interpret the second, if it is not caused by the first (instinctively, I suspect not). Any idea what is causing the warnings I consistently get on aptitude update, and can anyone confirm that the errors that follow those warnings are caused by the warnings and not indicative of something ELSE being wrong? Thanks Mark