Date: Wed, 21 Sep 2016 18:08:39 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212886] security/gpgme update to 1.7 Message-ID: <bug-212886-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212886 Bug ID: 212886 Summary: security/gpgme update to 1.7 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: jhale@FreeBSD.org Reporter: groot@kde.org Flags: maintainer-feedback?(jhale@FreeBSD.org) Assignee: jhale@FreeBSD.org This is partly an update-PR, partly a request-for-consultation with kde@ . Today's release announcement of GPGMe++ reads (in part): I'm pleased to announce that the C++ bindings for GnuPG's GPGME library a= nd=20 the Qt Job API for GpgME++ (QGpgME) that was previously in Libkleo are no= w=20 part of the upstream GPGME repository and have been released today with=20 GPGME-1.7: kde@ has a gpgmepp port prepared for use, but that's based on the "old" gpe= mepp released by the KDE Community, as opposed to the new upstream. I was just a= bout to PR the kde@ port for it, but we should sit down perhaps for a minute to figure out who puts what where -- since released KDE code wants the "old" g= pgme and apparently there's file install and source-compatibility conflicts betw= een old and new. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212886-13>