Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 271250 - [gnome overlay] epiphany-2.26.2 does not merge properly due to xulrunner-1.9.1 (sandbox violation)
Summary: [gnome overlay] epiphany-2.26.2 does not merge properly due to xulrunner-1.9....
Status: RESOLVED DUPLICATE of bug 263585
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-26 01:08 UTC by Brian Johnson
Modified: 2009-05-26 20:31 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Johnson 2009-05-26 01:08:00 UTC
With xulrunner-1.9.1, a sandbox violation will occur when emerging epiphany-2.26.2

Reproducible: Always

Steps to Reproduce:
This will only happen when/if xulrunner-1.9.1 (currently beta) is installed. The ebuild itself adds predictions for xulrunner-1.9 but not xulrunner-1.9.1



This can be fixed by changing the following lines in the epiphany-2.26.2 ebuild:

        addpredict /usr/$(get_libdir)/xulrunner-1.9/components/xpti.dat
        addpredict /usr/$(get_libdir)/xulrunner-1.9/components/xpti.dat.tmp
        addpredict /usr/$(get_libdir)/xulrunner-1.9/components/compreg.dat.tmp

to

src_configure() {
        addpredict /usr/$(get_libdir)/xulrunner-1.9.1/components/xpti.dat
        addpredict /usr/$(get_libdir)/xulrunner-1.9.1/components/xpti.dat.tmp
        addpredict /usr/$(get_libdir)/xulrunner-1.9.1/components/compreg.dat.tmp
Comment 1 Brian Johnson 2009-05-26 01:10:32 UTC
Bugs #263585 #265700 are likely duplicates of this. A more robust solution is needed in the ebuilds for epiphany to handle multiple versions of xulrunner.
Comment 2 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-05-26 06:30:46 UTC

*** This bug has been marked as a duplicate of bug 263585 ***