public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: speakup@braille.uwo.ca
Subject: debian testing problem
Date: Mon, 23 Jan 2006 13:44:27 -0700	[thread overview]
Message-ID: <20060123204427.GA11560@localhost.localdomain> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all.

I'm running debian testing, and whenever I run apt-get update, I see
this at the end:

W: There are no public key available for the following key IDs:
F1D53D8C4F368D5D
W: There are no public key available for the following key IDs:
F1D53D8C4F368D5D
W: GPG error: http://security.debian.org testing/updates Release: The
following signatures couldn't be verified because the public key is
not available: NO_PUBKEY F1D53D8C4F368D5D
W: You may want to run apt-get update to correct these problems

I've ran apt-get update 4 times over the last 4 weeks, and the problem
isn't being corrected. My understanding is that /etc/apt/trusted.gpg
contains the key ring that apt-get uses, but I don't know if it's a
good idea to mess with that key ring manually, since it might create
more issues.

Any suggestions would be much appreciated. Thanks in advance as well.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD1UAr7s9z/XlyUyARAq6vAJ95foRflGNpirCCqi4Bf6dv3B0iVgCgz1u8
431ktOTwteN9VG/EFJhq8GU=
=6AoV
-----END PGP SIGNATURE-----


             reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gregory Nowak [this message]
 ` Charles Hallenbeck
   ` Gregory Nowak
     ` Charles Hallenbeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060123204427.GA11560@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).