Bug 684461 - FTBFS - conflicts with xulrunner-devel
Summary: FTBFS - conflicts with xulrunner-devel
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: librsvg2
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthias Clasen
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-12 18:47 UTC by Zenon Panoussis
Modified: 2017-12-06 10:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:20:16 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Zenon Panoussis 2011-03-12 18:47:27 UTC
Building the 2.26.0-5.el6 SRPM breaks:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -DXP_UNIX -I/usr/include/xulrunner-sdk-1.9.2 -DBINDIR=\"/usr/bin/\" -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -MT moz-plugin.lo -MD -MP -MF .deps/moz-plugin.Tpo -c moz-plugin.c  -fPIC -DPIC -o .libs/moz-plugin.o
moz-plugin.c:42:19: error: npupp.h: No such file or directory

moz-plugin.c also includes npapi.h. Completely different versions of npapi.h are provided by qt3-devel and by xulrunner-devel. libsvgr2 picks npapi.h from xulrunner-devel if it can find it; otherwise it takes the one from qt3-devel.

npupp.h comes with qt3-devel but conflicts with npapi.h from xulrunner-devel.

Solution: BuildConflicts: xulrunner-devel

However, the mozilla plugin is deleted during install anyway, so the whole exercise of making it build is useless. 

Better solution: 

--- librsvg2.spec.orig	2010-05-27 17:01:06.000000000 +0200
+++ librsvg2.spec	2011-03-12 19:43:11.921562851 +0100
@@ -76,7 +76,7 @@
 	--enable-gtk-theme \
 	--enable-gnome-vfs \
 	--with-croco \
-
+	--disable-mozilla-plugin
 make


See also bug #617309.

Comment 2 RHEL Program Management 2011-03-12 19:17:36 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Zenon Panoussis 2011-03-13 02:34:00 UTC
The bot says "This request was evaluated ... for inclusion in the current release", but the bug is filed against 6.1, which is not the current release. That's a bug in the bot: it does not read or does not respect the "Version" field.

Comment 5 Akemi Yagi 2014-02-04 09:04:31 UTC
Still seen in RHEL 6.5 (bug 1059984).

Comment 7 Jan Kurik 2017-12-06 10:20:16 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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