Summary: | net-news/liferea fails to compile with net-libs/xulrunner-1.9 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nirbheek Chauhan (RETIRED) <nirbheek> |
Component: | [OLD] GNOME | Assignee: | Daniel Gryniewicz (RETIRED) <dang> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | desintegr, gentoo, graaff, ikelos, jobbara.artalmatlan, maxbritov, pacho, sebasmagri, theli.ua |
Priority: | High | ||
Version: | 2007.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 213296 | ||
Attachments: | this ebuild fix issue for me |
Description
Nirbheek Chauhan (RETIRED)
2008-03-14 09:53:07 UTC
Reassigning to correct maintainer per reporters request This is a known issue; upstream hasn't ported to xulrunner 1.9 yet. This one will have to wait for them, I believe. If it starts to be a problem (ie, xulrunner 1.9 is in the tree), I'll see about doing the port myself. Ubuntu is already applying: http://patches.ubuntu.com/l/liferea/extracted/xul1.9.code.dpatch http://patches.ubuntu.com/l/liferea/extracted/xul1.9.dpatch Maybe they could help Created attachment 146588 [details]
this ebuild fix issue for me
Current ebuild doesn't disable gecko module if xulrunner enabled.
I have been fix ebuild for myself, please look.
That's unrelated to this bug. Please open a new bug for it. liferea-1.4.13 tried to build against xulrunner-1.9 if both 1.8 and 1.9 were installed. This was due to a check for using (tree-cleaned) www-client/mozilla as a gecko backend which gave a false positive with xulrunner-1.9 liferea-1.4.14 reordered the logic completely (bug #217003), and the problem is now gone since gecko is explicitly disabled when xulrunner is enabled. Hence www-client/mozilla is never checked for, and there is no false positive. Just FYI that bug #217003 was two birds with one stone ;) I'd like to leave this open for xulrunner 1.9 support. I can confirm this error on liferea-1.4.13 on amd64. But 1.4.15 compiles good and runs without errors... Should it be stabilized for amd64? is there any other limitant? (In reply to comment #8) > I can confirm this error on liferea-1.4.13 on amd64. But 1.4.15 compiles good > and runs without errors... Should it be stabilized for amd64? is there any > other limitant? > (In reply to comment #8) > I can confirm this error on liferea-1.4.13 on amd64. But 1.4.15 compiles good > and runs without errors... Should it be stabilized for amd64? is there any > other limitant? > According to this changelog. 1.4.16 fixes this bug. "What's New in 1.4.16 Stable Release: · Fixed wrong language code of Czech translation. (reported by Martin Picek) · Fixes SF #1920860: crash after memory corruption when parsing feed with invalid encoding (reported by mumrel) · Build support for XulRunner 1.9 (patch from Alexander Sack) · Significant speed improvement for the cache conversion necessary when upgrading from 1.4.9. Fixes 100% CPU during startup problem. · Fixes comment removal bug. · Drops all comments from cache to cleanup stale comments. · Changes DB schema to better handle comments during item and subscription deletion. This makes the cache version incompatible to 1.4.15! " 1.4.15 is going stable (bug #228357) It will use only xulrunner 1.8. The plan is to put in 1.4.16 using only xulrunner 1.9 (and maybe optionally webkit, if I can get it to work well enough). It will go stable with xulrunner 1.9 some time in july. 1.4.16b and 1.4.17 build against xulrunner 1.9 |