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: Fedora 8 update dependency problem
Date: Wed, 12 Dec 2007 09:34:25 -0500	[thread overview]
Message-ID: <000a01c83ccc$18f4f200$6405a8c0@ALBERTLC7SN0ZA> (raw)

Greetings!  

In case I'd screwed something up, I reinstalled Fedora 8 this morning from the 11 December DVD image.  I selected everything.  The rpm --import and gpg key commands seem to have worked fine.  When I used yum update, though, I got the following output:

Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package firefox-devel.i386 0:3.0-0.b2pre_2007121015.fc8 set to be updated
---> Package firefox.i386 0:3.0-0.b2pre_2007121015.fc8 set to be updated
--> Processing Dependency: libgtkembedmoz.so for package: yelp
--> Processing Dependency: libgtkembedmoz.so for package: devhelp
--> Processing Dependency: libxpcom_core.so for package: yelp
--> Finished Dependency Resolution
Error: Missing Dependency: libgtkembedmoz.so is needed by package devhelp
Error: Missing Dependency: libgtkembedmoz.so is needed by package yelp
Error: Missing Dependency: libxpcom_core.so is needed by package yelp
\x1a
I've had this problem with Fedora 7 as well as 8.  Along with any screw-ups I might have made, I'd hoped this would get fixed by the full install this morning.  Yelp is what I want to do at the moment!  Can anybody tell me where to find the missing dependencies, or how else to deal with this?  Thanks!

Al



             reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Albert E. Sten-Clanton [this message]
 ` Janina Sajka
   ` Albert E. Sten-Clanton
 ` 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='000a01c83ccc$18f4f200$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).