Bug 221240 - Updating Galeon to 2.0.3-4.fc6.1 is missing a dependency
Updating Galeon to 2.0.3-4.fc6.1 is missing a dependency
Product: Fedora
Classification: Fedora
Component: galeon (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Denis Leroy
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-01-03 01:32 EST by Callum Macdonald
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-03 14:15:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Callum Macdonald 2007-01-03 01:32:51 EST
Description of problem:
When running yum update to update galeon to version 2.0.3-4.fc6.1, it says it's
missing a dependency (gecko-libs v1.8.0.9 I think). I assumed the dependency was
yet to be updated, so I held off for a few days, but it's been like that for a
week or so now.

Additional info:
I haven't tried disabling other repos to see if that makes a difference. I also
have a few other Mozilla based browsers installed, and have upgraded Firefox to
2.0 using the development repo, so it might be related to that.
Comment 1 Denis Leroy 2007-01-03 14:11:40 EST
Right, the update matches that of firefox (with which galeon is compiled). What
version of firefox have you installed ? :

> rpm -q --whatprovides gecko-libs
> rpm -q firefox --provides | grep gecko
gecko-libs =

Is your yum setup correctly for fedora core updates ? Or maybe are you using a
problematic mirror ?
Comment 2 Denis Leroy 2007-01-03 14:15:23 EST
Argh, didn't read your post correctly. Yes, you'll need to install galeon from
rawhide as well. I think Remi Collet (http://remi.collet.free.fr/) maintains his
own yum repo with firefox 2.0 and compatible RPMs including galeon if that's any

Closing this as 'not a bug'.

Note You need to log in before you can comment on or make changes to this bug.