CCing arches (amd64 hppa ppc ppc64 sparc x86 x86-fbsd) due 11 Sep 2008. # ChangeLog for net-im/psi # Copyright 2002-2008 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/net-im/psi/ChangeLog,v 1.142 2008/08/11 17:52:44 yngwin Exp $ 11 Aug 2008; Ben de Groot <yngwin@gentoo.org> psi-0.11.ebuild: Fix split qt4 deps wrt bug 217161.
Arches, please test and mark stable =net-im/psi-0.12 !
!!! All ebuilds that could satisfy "=app-crypt/qca-2*" have been masked. !!! One of the following masked packages is required to complete your request: - app-crypt/qca-2.0.1-r1 (masked by: ~amd64 keyword) - app-crypt/qca-2.0.0-r2 (masked by: ~amd64 keyword) which is not so long in the tree: *qca-2.0.1-r1 (06 Sep 2008)
app-crypt/qca-2.0.0-r2 should be fine.
ppc stable
Stable for HPPA. (In reply to comment #4) > ppc stable ppc picked app-crypt/qca-gnupg-2.0.0_beta3 which has only just hit the tree. Please avoid that version. To be clear about what needs to be stabilised: =net-im/psi-0.12 =app-crypt/qca-2.0.0-r2 =app-crypt/qca-gnupg-2.0.0_beta2 =app-crypt/qca-ossl-2.0.0_beta3
ppc64 stable
amd64 stable
Sparc stable for all four of them.
x86 stable, closing
Very funny. app-crypt/qca-2.0.0-r2 is blocking <app-crypt/qca-1.0-r3 but only app-crypt/qca-1.0-r2 is stable. You should mark app-crypt/qca-1.0-r3 stable as well - because after emerging qca-2 (and unmerging the blocked qca-1.0-r2) an "emerge -pDuvN" world wants to emerge version 1.0-r2 again. So qca-1 seems to be needed by some other application. Strange enough a "revdep-rebuild -- -pv" doesn't show any qca-dependency being missing...
I also have the same problem for emerge -D world. The -r3 version has to be made stable as well.
equery d =app-crypt/qca-1.0-r2 [ Searching for packages depending on =app-crypt/qca-1.0-r2... ] app-crypt/qca-tls-1.0-r3 (>=app-crypt/qca-1.0) kde-base/kdenetwork-3.5.9 (=app-crypt/qca-1.0*)
qca-1 problem addressed in bug #238000 and fixed.