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: Sun, 01 Apr 2007 08:06:31 -0400 [thread overview]
Message-ID: <001301c77456$2ff36c00$6405a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <Pine.BSF.4.64.0703312349220.67631@server2.shellworld.net>
I don't think you need to add the exclude line. (I thought that was only to prevent upgrading the kernel to one that isn't modified for speakup.)
I haven't had to worry about any other keys yet.
Al
----- Original Message -----
From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, April 01, 2007 12:52 AM
Subject: Re: small warning messages on fedora core 6 kernel installation
> Hi, yes that fixed the issue on the gpg keys. Now that yum can download
> speakupmodified kernels sense I followed the directions on the main
> speakupmodified.org page do I still need to add the exclude line to
> /etc/yum.conf and what key do I import for the rest of the packages I
> download? I am also getting the message sqlite cache needs updating
> what does this mean and how do I fix it? When yum updates kernels will
> it remove the old one or will I need to do this after it is updated?On
> Sat, 31 Mar 2007, Albert E. Sten-Clanton wrote:
>
> > 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
> > >
> > >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> 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
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Nick Gawronski
` Albert E. Sten-Clanton
` Nick Gawronski
` Albert E. Sten-Clanton [this message]
` 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='001301c77456$2ff36c00$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).