Hi, sparc. This is to notify you that you lost your keywords for >=net-new/liferea-1.4.18 due to lack of xulrunner 1.9 keywords. Feel free to add them back when xulrunner is working again. I'll leave 1.4.15 in the tree as long as it needs to be there.
Okay, we got a working xulrunner-1.9 again but we got another (well, minor) problem: net-news/liferea-1.4.24 hits a bug in sqlite, which makes it sigbus again. That bug is fixed in sqlite-3.6.13 which should arive on tuesday. Would it be possible to bump the sqlite dependency to >=3.6.13? Or would that conflict with your stble plans for .24?
It would be okay, if there were a sqlite-3.6.13 in the tree, but 3.6.12 appears to be the top.
There is now.
Okay, dep bumped on 2.4.28-r1. Keyword away.
Heck, you added sqlite for *all* architectures. It's not needed for amd64 or x86. Can you add a USE flag forced for sparc and disabled by default for the other archs ?
No. What's the point? A complicated dep on a ~arch package just to keep another ~arch package (supposedly with a ton of bugfixes) from being pulled in?
I'm not sure I follow you. Isn't the goal of an ebuild to be put in stable at one point or another ? Right now, trying an emerge -u world gives me an error because I unmasked liferea (tired of the oooold 1.2). What about this: >=dev-db/sqlite-3.3 sparc? ( >=dev-db/sqlite-3.6.13 ) Works just fine, I just tested it.
At the moment, no, the plans are not to have this ebuild go stable. It has to wait for webkit-gtk to go stable, which will be longer than for sqlite to go stable.
Fixed
