The following packages cannot be authenticated
sktseer at gmail.com
Mon Dec 5 14:48:14 UTC 2011
On Fri, 02 Dec 2011 11:09:22 +0200, Marius Gedminas wrote:
> On Wed, Nov 30, 2011 at 08:53:41AM -0600, sktsee wrote:
>> That usually means that you need to run "sudo apt-get update" before
>> installing your package so that apt can authenticate the repo.
> Incidentally, why does it happen? An intermittent network connection
> that didn't let the previous apt-get update download the right
> Release.gpg? An archive update that coincided with your apt-get update,
> and so you downloaded a Packages.gz that is newer than your Release
>> The following link explains the process of how APT authenticates
>> repositories and checks package integrity.
> I see my question is also raised (but not answered) in that FAQ:
> } Another problem you may encounter if using testing or unstable is that
> } if you have not run apt-get update lately and apt-get install a
> package, } apt might complain that it cannot be authenticated (why does
> it do } this?). apt-get update will fix this.
I'm as clueless as to why this occurs as the person who wrote that
paragraph. But since that person is longtime Debian developer Joey Hess,
I don't feel so bad about my ignorance. :)
More information about the ubuntu-users