BADSIG while using apt-proxy

[Kevin Otte]

Binary package hint: apt

I am using an apt-proxy at home and updates are failing with a BADSIG error.

root@mystic:~# apt-get update
...
Fetched 27.6kB in 7s (3711B/s)
Reading package lists... Done
W: GPG error: http://reliant dapper-security Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <email address hidden>
W: You may want to run apt-get update to correct these problems

root@mystic:~# cat /etc/apt/sources.list
deb http://reliant:9999/ubuntu/ dapper main restricted universe multiverse
deb http://reliant:9999/ubuntu/ dapper-updates main restricted universe multiverse
deb http://reliant:9999/ubuntu-security dapper-security main restricted universe multiverse

deb http://reliant.nivex.lan/debs/ dapper custom

deb http://kubuntu.org/packages/amarok-14 dapper main

This may be related to bug 33505, but I filed seperately as I am not using the http_proxy directives.

All the best,
Kevin

[Kevin Otte (nivex)]

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

[Simon Law (sfllaw)]

That sounds like a pretty good theory. Cache coherency is probably
at the heart of this bug.

[Wayne Scott (wsc9tt)]

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.