Summary: | broken dev-libs/redland breaks soprano, kdelibs and packages using nepomuk (in this order) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nikoli <nikoli> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dragonheart, esigra, MolbOrg, sayusi.ando |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 331761 | ||
Bug Blocks: |
Description
Nikoli
2010-05-07 11:59:53 UTC
Similar issue - but in this case mysql (and not rasqal) causing breakage in redland (and thus in soprano and thus in kdelibs) http://forums.gentoo.org/viewtopic-t-815507-highlight-.html As a solution: emerge -1 redland emerge -1 soprano emerge -1 kdelibs We should really add it to FAQ... >emerge -1 kdelibs
it is not enough, at least nepomuk package is broken too.
Yeah, probably, anyway... CC-ing people maintaining our troublemakers - rasqal and redland. Summing it up for you: dev-libs/redland is fragile - it links to multiple shared libs that are quite frequently SOVERSION bumped (like libmysqlclient or rasqal). Updating ABI-incompatible redland dependency obviously breaks redland which as a consequence breaks (in this order): - dev-libs/soprano (rebuilding soprano won't help, it will actually *break* soprano as soprano buildsystem will detect redland deps as broken and will refuse to build certain required component - redland storage backend for soprano) - kde-base/kdelibs (due to mentioned soprano components not built, but they are needed for KDE semantic desktop - libnepomuk) - any KDE4 application that needs libnepomuk from kdelibs (kde-base/gwenview, kmail, kde-base/nepomuk and many many others) What can be done to redland to prevent this breaking domino effect? yes, soname changes often... nothing unusual (In reply to comment #4) > - dev-libs/soprano (rebuilding soprano won't help, it will actually *break* > soprano as soprano buildsystem will detect redland deps as broken and will > refuse to build certain required component - redland storage backend for > soprano) then the configure should bail out on soprano if the required deps are not met > What can be done to redland to prevent this breaking domino effect? see previous comment *** Bug 319299 has been marked as a duplicate of this bug. *** (In reply to comment #3) > >emerge -1 kdelibs > > it is not enough, at least nepomuk package is broken too. > if it can help, for 4.4.4 and 4.3.3 .... i solved by unmerging all kde-base packages 1) emerge -C $(qlist -IC kde-base) 2) emerge kde-meta eventually a dup of #307673 however the nepomuk installing only man pages is still a bug. I'll probably inject some code into kdelibs' CMakeList.txt that will make it bail out on missing nepomuk deps (when nepomuk enabled). This should be fixed in 2.4.4 with following patch (soprano, like Samuli suggested) diff -ru ../soprano-2.4.4/cmake/modules/FindRedland.cmake ./cmake/modules/FindRedland.cmake --- ../soprano-2.4.4/cmake/modules/FindRedland.cmake 2009-12-18 15:33:44.000000000 +0100 +++ ./cmake/modules/FindRedland.cmake 2010-07-06 03:25:55.421484970 +0200 @@ -108,7 +108,7 @@ if(NOT "${_TEST_EXITCODE}" EQUAL 0) set(_REDLAND_VERSION_OK) message(STATUS "${_OUTPUT}") - message(STATUS "Redland with broken NEEDED section detected, disabling") + message(SEND_ERROR "Broken Redland detected, rebuild it now. If problem persists, report bug at bugs.gentoo.org.") endif(NOT "${_TEST_EXITCODE}" EQUAL 0) endif(_REDLAND_STORAGE_LIBS) Since this is the only place when any linking/dlopening is being performed at build system level, it should fix this soprano[redland] vs not_actually_building_redland_storage inconsistency. Thank you for this tip ! :) (In reply to comment #1) > Similar issue - but in this case mysql (and not rasqal) causing breakage in > redland (and thus in soprano and thus in kdelibs) > > http://forums.gentoo.org/viewtopic-t-815507-highlight-.html > > As a solution: > emerge -1 redland > emerge -1 soprano > emerge -1 kdelibs > (In reply to comment #10) > This should be fixed in 2.4.4 with following patch (soprano, like Samuli > suggested) > So can we close the bug? (In reply to comment #12) > (In reply to comment #10) > > This should be fixed in 2.4.4 with following patch (soprano, like Samuli > > suggested) > > > > So can we close the bug? > I did not get past this with the latest portage dependencies. I came here and figured out that I needed to rebuild redland. That solved my problem. Still seems portage should catch this dependency better? Maybe? It does, if you use portage-2.2_rc. Otherwise it's unfortunately user's responsibility to run revdep-rebuild occasionally. (In reply to comment #14) > It does, if you use portage-2.2_rc. Otherwise it's unfortunately user's > responsibility to run revdep-rebuild occasionally. > So resolving then. I had the same issues, when starting kmail i got a segfault regarding soprano but i've fixed it in a different way. Watching logs i could see that virtuoso was shutted down but then it couldn't restart (and that showed the segfault in logs) because of a problem of soprano while calling the function "Soprano::VirtuosoController::writeConfigFile" that actually did not create the config file and let virtuoso down. I tried upgrading with latest ~amd64 libsoprano (2.6.0) and the problem seems solved. |