quassel currently depends on qca-ossl, which is blocked in >=qca-2.1, it only supports (needs?) qca when built without qt5 support(?). SERVER_RDEPEND=" qt5? ( dev-qt/qtscript:5 postgres? ( dev-qt/qtsql:5[postgres] ) !postgres? ( dev-qt/qtsql:5[sqlite] dev-db/sqlite:3[threadsafe(+),-secure-delete] ) ) !qt5? ( dev-qt/qtscript:4 crypt? ( app-crypt/qca:2 app-crypt/qca-ossl ) postgres? ( dev-qt/qtsql:4[postgres] ) !postgres? ( dev-qt/qtsql:4[sqlite] dev-db/sqlite:3[threadsafe(+),-secure-delete] ) )
You can use qt5 build as workarround/ CMakeLists.txt: > # While QCA2 seems to support Qt5, it is not actually co-installable or distinguishable from the Qt4 version... > # In order to avoid linking against the Qt4 version (which is probably the one installed), disable this for now > #find_package(QCA2 QUIET) > #set_package_properties(QCA2 PROPERTIES TYPE RECOMMENDED > # URL "https://projects.kde.org/projects/kdesupport/qca" > # DESCRIPTION "Qt Cryptographic Architecture" > # PURPOSE "Required for encryption support" > #)
Thanks for reporting. This is fixed in cvs now. Please sync. + + 29 Jan 2015; Johannes Huber <johu@gentoo.org> quassel-0.10.0-r1.ebuild, + quassel-0.10.1.ebuild, quassel-0.11.0.ebuild, quassel-0.9.2.ebuild, + quassel-0.9.3.ebuild, quassel-9999.ebuild: + Adjust dependencies to handle merged plugins in >=app-crypt/qca-2.1, bug + #537994. +