Bug#1003865: GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)

2023-11-27 Thread legvpnext167 (Hays)
also here the error occurs with all Linux installations that use apt-cacher-ng as apt proxy. As a workaround, it helps to deactivate the caching of the InRelease files so that they are always fetched directly. ## /etc/apt-cacher-ng/acng.conf DontCacheResolved: .*InRelease

Bug#1003865: GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)

2023-07-06 Thread Martin Schwenke
Adding more data... I have been seeing this on bookworm (both the machine running "apt update" and the machine running apt-cacher-ng): W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: The following signatures were invalid: BADSIG 0E98404D386FA1D9 Debian Archive Automatic

Bug#1003865: GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)

2022-06-12 Thread Diederik de Haas
On 19 Jan 2022 21:40:18 +0530 Pirate Praveen wrote: > On Wed, 19 Jan 2022 02:47:56 +0530 Pirate Praveen > wrote: > > >Based on the fact that autobuilding of unstable is still continuing and > > >there haven't been any reports of this issue on either #d-devel or > > >debian-devel@lists, it seems

Bug#1003865: GPG error: http://deb.debian.org/debian sid InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster)

2022-01-19 Thread Andreas Beckmann
On Wed, 19 Jan 2022 02:47:56 +0530 Pirate Praveen wrote: I have seen at least one forum posting on the same error when searching for it so its likely more common https://www.nixcraft.com/t/signatures-were-invalid-badsig-648acfd622f3d138-debian-archive-automatic-signing-key-10-buster/4025 May