Nate Bargmann wrote:
> * Joey Hess <[EMAIL PROTECTED]> [2006 Jan 03 23:29 -0600]:
>> Edward C. Jones wrote:
>> > I am getting the following message from synaptic:
>> >
>> > W: GPG error: http://ftp.us.debian.org unstable Release: The following
>> > signatures couldn't be verified because the publ
on Wed, Jan 04, 2006 at 12:25:15AM -0500, Joey Hess ([EMAIL PROTECTED]) wrote:
> Edward C. Jones wrote:
> > I am getting the following message from synaptic:
> >
> > W: GPG error: http://ftp.us.debian.org unstable Release: The following
> > signatures couldn't be verified because the public key i
"Edward C. Jones" <[EMAIL PROTECTED]> writes:
> 1. Use "su" to become root.
>
> 2. Run "apt-key list".
If you can use sudo later on, why not for this step too?
> 3. If key 4F368D5D is not present, run (as a single line) "wget
> http://ftp-master.debian.org/ziyi_key_2005.asc -O - | sudo apt-key a
* Joey Hess <[EMAIL PROTECTED]> [2006 Jan 03 23:29 -0600]:
> Edward C. Jones wrote:
> > I am getting the following message from synaptic:
> >
> > W: GPG error: http://ftp.us.debian.org unstable Release: The following
> > signatures couldn't be verified because the public key is not available:
>
[04/01/2006 -- 21:34u] Edward C. Jones:
> 6. Should I run "apt-key del 4F368D5D"?
I'd say no. That was what caused the problem to not go away. :)
Cheers,
Tom
--
"Es bückt sich der Mann, um durch das Tor in das Innere zu sehen."
---(Franz Kafka, Vor dem Gesetz)
I was getting the following message:
W: GPG error: http://ftp.us.debian.org unstable Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 010908312D230C5F
Here is worked for me:
1. Use "su" to become root.
2. Run "apt-key list".
3. If ke
[04/01/2006 -- 19:43u] Joey Hess:
> > That works fine here, and the new key is listed in apt-key list output,
> > but still, I get the GPG error when updating.
<...>
> > NO_PUBKEY F1D53D8C4F368D5D
>
> Key 4F368D5D is:
>
> pub 1024D/4F368D5D 2005-01-31 [expires: 2006-01-31]
> uid
Tom wrote:
> That works fine here, and the new key is listed in apt-key list output,
> but still, I get the GPG error when updating.
>
> I use ftp.de.debian.org as a mirror. I'd expect one key "to rule them
> all", but I could be very wrong, as usual. Is one key supposed to be
> valid for all arch
Joey Hess:
> > From what I have read, this is going to happen every January. What do
> > I do? Where in the Debian documentation is the procedure I need to use
> > documented?
>
> wget http://ftp-master.debian.org/ziyi_key_2006.asc -O - | sudo apt-key add -
That works fine here, and the new key i
Edward C. Jones wrote:
> I am getting the following message from synaptic:
>
> W: GPG error: http://ftp.us.debian.org unstable Release: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY 010908312D230C5F
>
> From what I have read, this is going
Edward C. Jones wrote:
I am getting the following message from synaptic:
W: GPG error: http://ftp.us.debian.org unstable Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 010908312D230C5F
From what I have read, this is going to happen
I am getting the following message from synaptic:
W: GPG error: http://ftp.us.debian.org unstable Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 010908312D230C5F
From what I have read, this is going to happen every January. What do I
12 matches
Mail list logo
