Re: The following packages cannot be authenticated
- From: sktsee <sktseer@xxxxxxxxx>
- Date: Mon, 5 Dec 2011 14:48:14 +0000 (UTC)
On Fri, 02 Dec 2011 11:09:22 +0200, Marius Gedminas wrote:
On Wed, Nov 30, 2011 at 08:53:41AM -0600, sktsee wrote:
[snip]
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
file?
The following link explains the process of how APT authenticates
repositories and checks package integrity.
http://wiki.debian.org/SecureApt
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. :)
--
sktsee
--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
- References:
- Re: The following packages cannot be authenticated
- From: Marius Gedminas
- Re: The following packages cannot be authenticated
- Prev by Date: Re: copying images and data to document?
- Next by Date: Re: What I do for a new machine?
- Previous by thread: Re: The following packages cannot be authenticated
- Next by thread: Re: The following packages cannot be authenticated
- Index(es):
Relevant Pages
|
