public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Albert E. Sten-Clanton" <albert.e.sten_clanton@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: small warning messages on fedora core 6 kernel installation
Date: Sat, 31 Mar 2007 22:16:28 -0500	[thread overview]
Message-ID: <003501c7740c$23ea5da0$6405a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <Pine.LNX.4.64.0703311907100.4064@CHIHUAHUAD1.gateway.2wire.net>

Maybe this command will help with the key problem:

rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-speakupmodified

Be sure to do all caps with the

RPM-GPG-KEY

part of it.  

Al
----- Original Message ----- 
From: "Nick Gawronski" <nick@nickgawronski.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, March 31, 2007 7:09 PM
Subject: small warning messages on fedora core 6 kernel installation


> Hi, I remember reading some messages about this issue.  This is the
> message I get when installing some package and the package does install I
> would like to get this gpg key issue resolved.  Here is the error. This
> happens with all kernel packages not just the one I am pasting the output
> from.  warning: kernel-doc-2.6.20-1.2933.fc6spk.noarch.rpm: Header V3 DSA
> signature: NOKEY, key ID 4bfffd75
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.23/740 - Release Date: 3/30/2007 1:15 PM
> 
>


  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Nick Gawronski
 ` Albert E. Sten-Clanton [this message]
   ` Nick Gawronski
     ` Albert E. Sten-Clanton
   ` Janina Sajka
 ` Janina Sajka

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='003501c7740c$23ea5da0$6405a8c0@ALBERTLC7SN0ZA' \
    --to=albert.e.sten_clanton@verizon.net \
    --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).