Red Hat Bugzilla – Bug 206745
Liferea requires a specific Firefox
Last modified: 2007-11-30 17:11:43 EST
Description of problem:
A run of "yum update" ends with an error:
Error: Missing Dependency: firefox = 220.127.116.11 is needed by package liferea
Version-Release number of selected component (if applicable):
Always reproducible with "rpm -q --whatrequires", but an actual
failure only happens when rebuilds are in progress.
Steps to Reproduce:
1. Run yum
Error (see above)
This is obviously nothing a simple rebuild won't fix, but I would think
that there's no need to be so specific about the version of Firefox
that Liferea needs. Please feel free to close as NOTABUG, with explanation
why a specific version of Firefox is needed.
[root@lembas zaitcev]# rpm -q --provides firefox | grep firefox
firefox = 18.104.22.168-9
So maybe it was an automatically generated dependancy that tripped Liferea.
Here's one e-mail from today:
From: Louis Garcia <email@example.com>
Subject: Apps that depend on firefox
Date: Fri, 15 Sep 2006 16:07:51 -0400
When firefox was updated to 22.214.171.124 the apps that depend on gecko were
not rebuild. Apps like epiphany and yelp and will not run now.
It should be clear, because Liferea renders HTML. Right? There remains
a mystery, however. When I look at what libraries /usr/bin/liferea-bin
loads, there's nothing from Firefox. Maybe Gecko is linked statically
or we use some built-in in reality... Either way, I'd like someone who
knows how it works to investigate if the precise dependency is needed.
Yeah, this has already been rebuilt earlier today, the extras packages just
haven't been pushed out yet.
The reason for a specific firefox:
You still haven't mentioned why this requrement exists.
Since no dynamic libraries are used, there's no runtime dependency.
The dependency could be just on firefox, or even on gnome-moz-remote.
*** Bug 206770 has been marked as a duplicate of this bug. ***
Pete, the reason for the strict dependency is given in comment 3,
see the ticket at SF. The background is explained there. You are mistaken
about the runtime deps. There are dependencies on firefox libs in Liferea's
"Mozilla" rendering plugin (this could be moved into a sub-package, though).
With recent releases of Liferea, the Firefox home directory path is hardcoded
into the binary, which is an upstream decision.
Sorry. I felt that I was missing something, so didn't reopen the bug.