Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
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) <ftpmaster@debian.org>
164 views
Skip to first unread message
Pirate Praveen
Jan 28, 2022, 10:20:04 AM1/28/22
to
Control: reassign -1 apt-cacher-ng
On Wed, 19 Jan 2022 21:49:33 +0100 Andreas Beckmann <an...@debian.org> wrote:
> On Wed, 19 Jan 2022 02:47:56 +0530 Pirate Praveen
> <pra...@onenetbeyond.org> 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 be related to apt-cacher-ng (though I tried with apt-cacher-ng disabled without fixing this issue).
>
> When I encounter similar errors from time to time (once a year or so) I
> consider them as "caching artefacts" and fix them by having apt
> "reinitialize" the corresponding package source: first comment the line
> in sources.list (or rename the snippet in sources.list.d to *.list.off),
> run apt-get update (or whatever you like instead) to "forget" the
> source, enable it again, apt-get update again and the error is gone.
>
> Actually I cannot remember having ever seen that as a piuparts failure
> (and that does a lot of apt-get update), only once in a while on my main
> machine which has everything from oldoldstable to experimental with 4
> foreign architectures available ...
I have seen this on another sid chroot. So I had to remove
/var/lib/apt/* inside the chroot and debrepo/dists directory in
apt-cacher-ng's cache directory. I'm not sure if it can be fixed in
apt-cacher-ng.
> Andreas
>
>
On Wed, 19 Jan 2022 21:49:33 +0100 Andreas Beckmann <an...@debian.org> wrote:
> On Wed, 19 Jan 2022 02:47:56 +0530 Pirate Praveen
> <pra...@onenetbeyond.org> 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 be related to apt-cacher-ng (though I tried with apt-cacher-ng disabled without fixing this issue).
>
> When I encounter similar errors from time to time (once a year or so) I
> consider them as "caching artefacts" and fix them by having apt
> "reinitialize" the corresponding package source: first comment the line
> in sources.list (or rename the snippet in sources.list.d to *.list.off),
> run apt-get update (or whatever you like instead) to "forget" the
> source, enable it again, apt-get update again and the error is gone.
>
> Actually I cannot remember having ever seen that as a piuparts failure
> (and that does a lot of apt-get update), only once in a while on my main
> machine which has everything from oldoldstable to experimental with 4
> foreign architectures available ...
I have seen this on another sid chroot. So I had to remove
/var/lib/apt/* inside the chroot and debrepo/dists directory in
apt-cacher-ng's cache directory. I'm not sure if it can be fixed in
apt-cacher-ng.
> Andreas
>
>
Pirate Praveen
Feb 11, 2022, 5:10:04 AM2/11/22
to
Control: severity -1 important
Control: reopen -1
On Fri, 28 Jan 2022 20:45:00 +0530 Pirate Praveen
<pra...@onenetbeyond.org> wrote:
>
> I have seen this on another sid chroot. So I had to remove
> /var/lib/apt/* inside the chroot and debrepo/dists directory in
> apt-cacher-ng's cache directory. I'm not sure if it can be fixed in
> apt-cacher-ng.
This seems to be happening very often, I had to fix this manually today
as well. Wondering if something needs to be done at apt-cacher-ng side
to invalidate the cached version?
Control: reopen -1
On Fri, 28 Jan 2022 20:45:00 +0530 Pirate Praveen
<pra...@onenetbeyond.org> wrote:
>
> I have seen this on another sid chroot. So I had to remove
> /var/lib/apt/* inside the chroot and debrepo/dists directory in
> apt-cacher-ng's cache directory. I'm not sure if it can be fixed in
> apt-cacher-ng.
as well. Wondering if something needs to be done at apt-cacher-ng side
to invalidate the cached version?
Diederik de Haas
Jun 12, 2022, 7:20:03 AM6/12/22
to
On 19 Jan 2022 21:40:18 +0530 Pirate Praveen <pra...@onenetbeyond.org> wrote:
> On Wed, 19 Jan 2022 02:47:56 +0530 Pirate Praveen
> <pra...@onenetbeyond.org> 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 unlikely that there's a general issue
> > >here, rather than something more local to your environment.
caused by apt-cacher-ng.
I don't know why it popped up now as usually/normally it works.
# debootstrap --arch arm64 sid /home/diederik/tmp/debootstrap/sysbase-sid-arm64 http://<acng-machine>:3142/deb.debian.org/debian
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
E: Invalid Release signature (key id 648ACFD622F3D138)
# debootstrap --arch arm64 sid /home/diederik/tmp/debootstrap/sysbase-sid-arm64 http://deb.debian.org/debian
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id A7236886F3CCCAAD148A27F80E98404D386FA1D9)
Interestingly enough, this only happens when specifying 'sid':
# debootstrap --arch arm64 testing /home/diederik/tmp/debootstrap/sysbase-bookworm-arm64 http://<acng-machine>:3142/deb.debian.org/debian
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id A7236886F3CCCAAD148A27F80E98404D386FA1D9)
> sudo rm -rf /var/lib/apt/*
>
> fixed the issue (sharing in case someone someone searches for the same
> error)
Do you do that on the host machine or on the machine running apt-cacher-ng?
I have a device running acng in my LAN which all (other) devices use,
but I also have one running on my main PC when repeatedly building images.
> On Wed, 19 Jan 2022 02:47:56 +0530 Pirate Praveen
> <pra...@onenetbeyond.org> 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 unlikely that there's a general issue
> > >here, rather than something more local to your environment.
> >
> > May be related to apt-cacher-ng (though I tried with apt-cacher-ng
> > disabled without fixing this issue).
>
I'm having/seeing this issue for ~1 week now and it very much looks like it is
> > May be related to apt-cacher-ng (though I tried with apt-cacher-ng
> > disabled without fixing this issue).
>
caused by apt-cacher-ng.
I don't know why it popped up now as usually/normally it works.
# debootstrap --arch arm64 sid /home/diederik/tmp/debootstrap/sysbase-sid-arm64 http://<acng-machine>:3142/deb.debian.org/debian
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
E: Invalid Release signature (key id 648ACFD622F3D138)
# debootstrap --arch arm64 sid /home/diederik/tmp/debootstrap/sysbase-sid-arm64 http://deb.debian.org/debian
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id A7236886F3CCCAAD148A27F80E98404D386FA1D9)
Interestingly enough, this only happens when specifying 'sid':
# debootstrap --arch arm64 testing /home/diederik/tmp/debootstrap/sysbase-bookworm-arm64 http://<acng-machine>:3142/deb.debian.org/debian
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id A7236886F3CCCAAD148A27F80E98404D386FA1D9)
> sudo rm -rf /var/lib/apt/*
>
> fixed the issue (sharing in case someone someone searches for the same
> error)
Do you do that on the host machine or on the machine running apt-cacher-ng?
I have a device running acng in my LAN which all (other) devices use,
but I also have one running on my main PC when repeatedly building images.
Martin Schwenke
Jul 6, 2023, 6:50:04 PM7/6/23
to
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 Signing Key (11/bullseye) <ftpm...@debian.org>
E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.
On Fri, 28 Jan 2022 20:45:00 +0530 Pirate Praveen
<pra...@onenetbeyond.org> wrote:
> I have seen this on another sid chroot. So I had to remove
> /var/lib/apt/* inside the chroot and debrepo/dists directory in
> apt-cacher-ng's cache directory. I'm not sure if it can be fixed in
> apt-cacher-ng.
The above workaround has fixed it for me... for now.
peace & happiness,
martin
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 Signing Key (11/bullseye) <ftpm...@debian.org>
E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.
On Fri, 28 Jan 2022 20:45:00 +0530 Pirate Praveen
<pra...@onenetbeyond.org> wrote:
> I have seen this on another sid chroot. So I had to remove
> /var/lib/apt/* inside the chroot and debrepo/dists directory in
> apt-cacher-ng's cache directory. I'm not sure if it can be fixed in
> apt-cacher-ng.
peace & happiness,
martin
legvpnext167 (Hays)
Nov 27, 2023, 3:10:05 AM11/27/23
to
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.
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
##################
##################
Regards
Klaus
0 new messages