Public bug reported: Binary package hint: apt-cacher-ng
Using Ubuntu Hardy AMD64 server. Package is apt-cacher-ng 0.1.9-1 apt-cacher-ng runs as proxy (server) for several hosts (clients) which do a daily apt-get update. Entries in sources.list are as follows: deb http://apt-proxy:9999/de.archive.ubuntu.com/ubuntu/ hardy main restricted universe multiverse deb-src http://apt-proxy:9999/de.archive.ubuntu.com/ubuntu/ hardy main restricted universe multiverse deb http://apt-proxy:9999/de.archive.ubuntu.com/ubuntu/ hardy-updates main restricted universe multiverse deb-src http://apt-proxy:9999/de.archive.ubuntu.com/ubuntu/ hardy-updates main restricted universe multiverse deb http://apt-proxy:9999/security.ubuntu.com/ubuntu hardy-security main restricted universe multiverse deb-src http://apt-proxy:9999/security.ubuntu.com/ubuntu hardy-security main restricted universe multiverse This works well for some days. What happens: From one day to the next, apt-get update fails on the clients with this error message: ... OK http://apt-proxy hardy Release Hole:6 http://apt-proxy hardy-updates Release [58,5kB] Fehl http://apt-proxy hardy-updates Release OK http://apt-proxy hardy-security Release ... W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used.GPG error: http://apt-proxy hardy-updates Release: Die folgenden Signaturen waren ungültig: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <[EMAIL PROTECTED]> ... The Release on the server is actual, but it isn't transferred to the clients. The only way to force it is to clear the actual Release-files on the server(!) _for_each_client_, and then to re-run apt-get update on the client. The server gets the files again from the mirror, and transferres them to this client. md5sum shows that the files are identical now. For all other clients, the error remains. I have to proceed to clear the Release-files on the server for each client. With about 20 clients, this is highly uncomfortable. Corresponding log entries in /var/log/apt-cacher-ng/apt-cacher.log (no entries in *.err) of example client 172.16.2.5 failure: 1225121155|O|560|::ffff:172.16.2.5|de.archive.ubuntu.com/ubuntu/dists/hardy-updates/Release.gpg 1225121155|I|361|::ffff:172.16.2.5|de.archive.ubuntu.com/ubuntu/dists/hardy-updates/Release.gpg 1225121155|O|423|::ffff:172.16.2.5|de.archive.ubuntu.com/ubuntu/dists/hardy-updates/Release 1225121155|I|371|::ffff:172.16.2.5|de.archive.ubuntu.com/ubuntu/dists/hardy-updates/Release after clear: 1225121351|O|561|::ffff:172.16.2.5|de.archive.ubuntu.com/ubuntu/dists/hardy-updates/Release.gpg 1225121351|I|505|::ffff:172.16.2.5|de.archive.ubuntu.com/ubuntu/dists/hardy-updates/Release.gpg 1225121351|O|58903|::ffff:172.16.2.5|de.archive.ubuntu.com/ubuntu/dists/hardy-updates/Release 1225121351|I|58851|::ffff:172.16.2.5|de.archive.ubuntu.com/ubuntu/dists/hardy-updates/Release ** Affects: apt-cacher-ng (Ubuntu) Importance: Undecided Status: New -- apt-cacher-ng problems with Release[.gpg] https://bugs.launchpad.net/bugs/289874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
