Re: Apt-update errors

2016-04-18 Thread Himanshu Shekhar
On Apr 18, 2016 2:53 PM, "Eric" wrote: > > Hello, > > Did you try "apt-get clean" to clean the cache ? > May be it can fix the issue. > > I tried, didn't work. I deleted all files in /var/lib/apt/lists referring to solution at this link : http://serverfault.com/questions/368669/debian-ubuntu-is-i

Apt-update errors

2016-04-17 Thread Himanshu Shekhar
Everything was working fine yesterday. When I ran "apt-get update" today morning, I got a lot or errors : "hash sum mismatch" and many more. Here's the output for apt update: Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease > > Hit:2 http://dl.google.com/linux/chrome/deb stable Release

Re: apt-update errors

2006-04-20 Thread Björn Gustafsson
Rob Blomquist wrote: W: GPG error: http://ftp.debian-unofficial.org sarge Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5642BC86823D007 http://www.debian-unofficial.org/faq.html And I guess the same applies to the other ones. I

Re: apt-update errors

2006-04-19 Thread Christopher Nelson
On Thu, Apr 20, 2006 at 09:52:25PM +, Rob Blomquist wrote: > W: GPG error: http://ftp.debian-unofficial.org sarge Release: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY D5642BC86823D007 > W: GPG error: ftp://ftp.tuke.sk sarge-backports Re

apt-update errors

2006-04-19 Thread Rob Blomquist
W: GPG error: http://ftp.debian-unofficial.org sarge Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5642BC86823D007 W: GPG error: ftp://ftp.tuke.sk sarge-backports Release: The following signatures couldn't be verified because the publi