On Saturday 04 March 2017 14:59:51 Alan McKinnon wrote:
> On 04/03/2017 14:33, Peter Humphrey wrote:
> > On Saturday 04 Mar 2017 12:42:38 Alan McKinnon wrote:
> >> On 04/03/2017 11:45, Peter Humphrey wrote:
> >>> Greetings.
> >>>
> >>> This is a KDE ~amd64 box, which still depends on kde-apps/kdepimlibs:4
> >>> for many things. I've been running happily on =app-crypt/gpgme-1.5.5,
> >>> but today portage wants to upgrade to =app-crypt/gpgme-1.8.0-r2. But
> >>> that version can't be installed while kdepimlibs:4 is still around, as
> >>> I see from the ebuild:
> >>>
> >>> [...]
> >>> RDEPEND="${COMMON_DEPEND}
> >>>
> >>> cxx? (
> >>>
> >>> !kde-apps/gpgmepp
> >>> !kde-apps/kdepimlibs:4
> >>>
> >>> )"
> >>>
> >>> [...]
> >>>
> >>> Is it even possible to satisfy that condition?
> >>
> >> No, but you can mask app-crypt/gpgme-1.8.0-r2 and stay on 1.5/1.6
> >
> > Yes, I've done that, but why has such silliness been allowed out?
>
> Maybe that combination never got tested? It's a ~arch package, so you
> get to be a field tester when you use it :-)Not anymore it isn't, see https://packages.gentoo.org/packages/app-crypt/gpgme. The bug referenced in the other gpgme thread [0] is the corresponding stabilisation bug. I'm surprised the plasma profile wasn't modified to deal with this. After all, it already takes care of various other blockers. [0] https://bugs.gentoo.org/show_bug.cgi?id=611470 -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
signature.asc
Description: This is a digitally signed message part.
