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: Fedora 8 update dependency problem
Date: Wed, 12 Dec 2007 12:33:55 -0500 [thread overview]
Message-ID: <003d01c83ce5$2be8bef0$6405a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <20071212155357.GT14302@rednote.net>
Thanks, Janina. Looks like I got my updates.
Al
----- Original Message -----
From: "Janina Sajka" <janina@rednote.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Wednesday, December 12, 2007 10:53 AM
Subject: Re: Fedora 8 update dependency problem
> This is correct. FF3 conflicts with devhelp and yelp. You need to remove
> those:
>
> rpm -e --nodeps --allmatches yelp devhelp
>
> before you can install FF3.
>
> This is documented in our Yum Quick Tips file, but should now probably
> be made more prominent as FF3 has moved from alpha to beta, and will
> likely be released early in 2008.
>
> Janina
>
> Albert E. Sten-Clanton writes:
> > 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
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> --
>
> Janina Sajka, Phone: +1.202.595.7777; sip:janina@a11y.org
> Partner, Capital Accessibility LLC http://CapitalAccessibility.Com
>
> Marketing the Owasys 22C talking screenless cell phone in the U.S. and Canada
> Learn more at http://ScreenlessPhone.Com
>
> Chair, Open Accessibility janina@a11y.org
> Linux Foundation http://a11y.org
>
> _______________________________________________
> 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.503 / Virus Database: 269.17.1/1182 - Release Date: 12/12/2007 11:29 AM
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Albert E. Sten-Clanton
` Janina Sajka
` Albert E. Sten-Clanton [this message]
` 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='003d01c83ce5$2be8bef0$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).