[Bug 49132] Re: BADSIG while using apt-proxy

2010-06-30 Thread Wayne Scott
*** This bug is a duplicate of bug 24061 *** https://bugs.launchpad.net/bugs/24061 I see this as well when using apt-cacher-ng, and found I had to 'rm /var/lib/apt/lists/*' to get things working again. -- BADSIG while using apt-proxy https://bugs.launchpad.net/bugs/49132 You received this bu

[Bug 49132] Re: BADSIG while using apt-proxy

2010-02-16 Thread Rolf Leggewie
*** This bug is a duplicate of bug 24061 *** https://bugs.launchpad.net/bugs/24061 ** This bug has been marked a duplicate of bug 24061 GPG error with apt-get (BADSIG 40976EAF437D05B5) -- BADSIG while using apt-proxy https://bugs.launchpad.net/bugs/49132 You received this bug notification

[Bug 49132] Re: BADSIG while using apt-proxy

2006-08-23 Thread Simon Law
That sounds like a pretty good theory. Cache coherency is probably at the heart of this bug. ** Changed in: apt (Ubuntu) Importance: Untriaged => Low Status: Unconfirmed => Confirmed -- BADSIG while using apt-proxy https://launchpad.net/bugs/49132 -- ubuntu-bugs mailing list ubuntu-

[Bug 49132] Re: BADSIG while using apt-proxy

2006-06-15 Thread Kevin Otte
This now seems to be an intermittent problem. I just did an update and it went off without a hitch. My theory is that the Release.gpg file is getting out of sync with whatever it is signing due to the timeouts on the cache. -- Kevin -- BADSIG while using apt-proxy https://launchpad.net/bugs/49