Stabilize: dev-libs/libassuan-2.0.0 app-crypt/dirmngr-1.1.0_rc1 app-crypt/gnupg-2.0.15 app-crypt/gpgme-1.3.0 app-crypt/gpa-0.9.1_pre20100416 Packages must be stabilized at the same time. Some packages don't have any stable versions on some architectures, so don't stabilize these packages on these architectures.
ppc
amd64 done
libassuan-2.0.0 breaks kde-base/kleopatra in all versions in tree, while I have some untested patch backported from KDE trunk (and applied in kde overlay), I'm not sure how to proceed yet. Anyway it wasn't very nice of you to stabilize all those packages without checking whether it's really safe.
Just FYI, kleopatra issue will be fixed in next KDE release (4.4.4) which is about to be stabilized soon.
(In reply to comment #3) > Anyway it wasn't very nice of you to stabilize all those packages without > checking whether it's really safe. I had installed all reverse dependencies of libassuan. If build system of a package doesn't fail when accepted version of libassuan isn't found, then a problem might have been missed.
x86 stable
Stable for HPPA.
arm stable
ppc64 done (despite 3 tests failing in gnupg, will investigate with 2.0.16 release)
alpha/ia64/s390/sh/sparc stable, closing