Sorry for the zero-day bug, but I'd like to track this as this new version will be required for KDE. Specifically, we will require the C++/Qt bindings have moved to app-crypt/gpgme-1.7.0 from kde-apps/gpgmepp.
Beware of https://lists.gnupg.org/pipermail/gnupg-devel/2016-September/031648.html that should be patched for a bump at least
(In reply to Kristian Fiskerstrand from comment #1) > Beware of > https://lists.gnupg.org/pipermail/gnupg-devel/2016-September/031648.html > that should be patched for a bump at least (the fixes are already in upstream git)
Added, disabled failing tests, python disabled as is in bad shape, qt doc is disabled as it is not installed.
(In reply to Alon Bar-Lev from comment #3) > Added, disabled failing tests, python disabled as is in bad shape, qt doc is > disabled as it is not installed. https://lists.gnupg.org/pipermail/gnupg-devel/2016-September/031667.html
app-crypt/gpgme-1.7.0 installs /usr/lib64/libqgpgme.so which collides with: kde-apps/gpgmepp:4 kde-apps/kdepimlibs:4 So conditional blockers are needed. There is no collision with kde-apps/gpgmepp:5.
And qt5 USE flag should be temporarily masked until any package starts to need app-crypt/gpgme[qt5].
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #5) > app-crypt/gpgme-1.7.0 installs /usr/lib64/libqgpgme.so which collides with: > kde-apps/gpgmepp:4 > kde-apps/kdepimlibs:4 > So conditional blockers are needed. > > There is no collision with kde-apps/gpgmepp:5. Done. (In reply to Arfrever Frehtes Taifersar Arahesis from comment #6) > And qt5 USE flag should be temporarily masked until any package starts to > need app-crypt/gpgme[qt5]. Done, please unmask when ready.