RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 805408 - unresolved dependency for xulrunner
Summary: unresolved dependency for xulrunner
Keywords:
Status: CLOSED DUPLICATE of bug 797779
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libproxy
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Skala
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-21 08:27 UTC by Tomas Pelka
Modified: 2014-11-09 22:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-26 10:19:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tomas Pelka 2012-03-21 08:27:49 UTC 
Description of problem:
In case you have no libproxy-mozjs package on your system xulrunner instalation will fail on unresolved dependency.

It requires libmozjs.so()(64bit).

xulrunner-1.9.2.24-2.el6_1.1 provided this.
xulrunner-10.0.3-1.el6_2 does not. 

Version-Release number of selected component (if applicable):
xulrunner-10.0.3-1.el6_2

How reproducible:
100%

Steps to Reproduce:
1. remove libproxy-mozjs
2. update xulrunner to 10
3.
  
Actual results:
It requires libmozjs.so()(64bit).

Expected results:
libmozjs.so should be in required packages for xulrunner

Additional info:
Comment 1 John W. Lockhart 2012-03-21 17:38:52 UTC 
To be more specific, libproxy-mozjs requires libmozjs.so()(64bit).  xulrunner-1.9 provides libmozjs, but xulrunner-10 does not provide libmozjs.

If libproxy-mozjs is present with an old xulrunner, the update to xulrunner-10 will fail because xulrunner-10 no longer provides libmozjs.

If you did not have libproxy-mozjs installed before updating to xulrunner-10, the missing libmozjs in 10 will prevent libproxy-mozjs from being installed.

Note that libproxy-mozjs comes from libproxy.src.rpm.

Expected result:
  libmozjs should be provided by something -- either xulrunner (which used to provide it), or something else.  If libproxy-mozjs is no longer intended to be available, something needs to Obsolete it, or libproxy needs to be updated.
Comment 2 RHEL Program Management 2012-03-26 09:40:05 UTC 
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.
Comment 3 Jan Horak 2012-03-26 09:44:52 UTC 
We can fix that issue just by rebuilding libproxy against xulrunner 10 and changing:
%define gecko_version 1.9.2
to:
%define gecko_version 10.0

I've changed the component to libproxy.
Comment 4 Jan Horak 2012-03-26 10:19:43 UTC 

*** This bug has been marked as a duplicate of bug 797779 ***
Note You need to log in before you can comment on or make changes to this bug.