On Wed, 19 Jan 2022 02:47:56 +0530 Pirate Praveen
<prav...@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 ...
Andreas
