Hello community, here is the log from the commit of package gpgme for openSUSE:Factory checked in at 2016-10-20 23:06:27 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/gpgme (Old) and /work/SRC/openSUSE:Factory/.gpgme.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "gpgme" Changes: -------- --- /work/SRC/openSUSE:Factory/gpgme/gpgme.changes 2016-10-18 10:08:48.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.gpgme.new/gpgme.changes 2016-10-20 23:06:27.000000000 +0200 @@ -1,0 +2,32 @@ +Thu Oct 20 06:40:43 UTC 2016 - [email protected] + +- Trim and update descriptions + +------------------------------------------------------------------- +Tue Oct 18 20:38:59 UTC 2016 - [email protected] + +- New upstream release 1.7.1 + * Fixed problems with the new language bindings. + * New helper function gpgme_addrspec_from_uid. + * Use option --exit-on-status-write-error with newer gpg versions. + * qt: Missed API from the Qt Binding inclusion has + been added again. + * qt: abstractimportjob.h is now installed to that + ImportJobs can be used again. + * qt: Fixed spelling error in API (startReceive). + * Interface changes relative to the 1.7.0 release: + gpgme_addrspec_from_uid NEW. + qt: WksPublishJob::startRecieve RENAMED to ::startReceive. + qt: MultiDeleteJob NEW. + qt: AbstractImportJob NEW. + qt: SpecialJob NEW. + cpp: Signature::key(bool, bool) NEW. + cpp: UserID::addrSpecFromString(const char*) NEW. + cpp: UserID::addrSpec() NEW. +- Drop conflict (handled on kdepimlibs4 side) +- Drop upstreamed patches: + * gpgme-1.7.0-nonvoid-returns.patch + * gpgme-1.7.0-cpp-qt-Include-config.h.patch + * gpgme-1.7.0-python-Include-config.h.patch + +------------------------------------------------------------------- Old: ---- gpgme-1.7.0-cpp-qt-Include-config.h.patch gpgme-1.7.0-nonvoid-returns.patch gpgme-1.7.0-python-Include-config.h.patch gpgme-1.7.0.tar.bz2 gpgme-1.7.0.tar.bz2.sig New: ---- gpgme-1.7.1.tar.bz2 gpgme-1.7.1.tar.bz2.sig ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ gpgme.spec ++++++ --- /var/tmp/diff_new_pack.b6zGuH/_old 2016-10-20 23:06:28.000000000 +0200 +++ /var/tmp/diff_new_pack.b6zGuH/_new 2016-10-20 23:06:28.000000000 +0200 @@ -21,9 +21,9 @@ %define with_python3 0 %define with_qt 1 Name: gpgme -Version: 1.7.0 +Version: 1.7.1 Release: 0 -Summary: A Library Designed to Give Applications Easy Access to GnuPG +Summary: Programmatic library interface to GnuPG License: LGPL-2.1+ and GPL-3.0+ Group: Productivity/Security Url: http://www.gnupg.org/related_software/gpgme/ @@ -33,9 +33,6 @@ Source3: gpgme.keyring # used to have a fixed timestamp Source99: %{name}.changes -Patch0: gpgme-1.7.0-nonvoid-returns.patch -Patch1: gpgme-1.7.0-cpp-qt-Include-config.h.patch -Patch2: gpgme-1.7.0-python-Include-config.h.patch # for gpgme-1.7.0-python-Include-config.h.patch BuildRequires: automake >= 1.14 # @@ -64,41 +61,23 @@ %description GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +management. It uses GnuPG as its back-end. %package -n libgpgme11 -Summary: A Library Designed to give Applications easy Access to GnuPG +Summary: Programmatic library interface to GnuPG Group: Development/Libraries/C and C++ Requires: gpg2 %description -n libgpgme11 GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Who Should use GPGME? - -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +management. It uses GnuPG as its back-end. %package -n libgpgme-devel -Summary: A Library Designed to give Applications easy Access to GnuPG +Summary: Development files for GPGME, a C library for accessing GnuPG Group: Development/Libraries/C and C++ Requires: glibc-devel Requires: libgpg-error-devel @@ -109,170 +88,101 @@ %description -n libgpgme-devel GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Who Should use GPGME? +management. -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +This subpackage contains the headers needed for building applications +making use of libgpgme. %if 0%{with_cpp} %package -n libgpgmepp6 -Summary: A Library Designed to give C++ Applications easy Access to GnuPG +Summary: Programmatic C++ library interface to GnuPG Group: Development/Libraries/C and C++ Requires: gpg2 %description -n libgpgmepp6 GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Who Should use GPGME? - -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +management. This package contains the C++ bindings. %package -n libgpgmepp-devel -Summary: A Library Designed to give C++ Applications easy Access to GnuPG +Summary: Development files for libgpgmepp, a C++ library for accessing GnuPG Group: Development/Libraries/C and C++ Requires: glibc-devel Requires: libgpg-error-devel Requires: libgpgme-devel = %{version} Requires: libgpgmepp6 = %{version} -# GPGME++ originated from kdepimlibs, then became independent -# It's impossible to build kdepimlibs4 with GpGME++ 1.7: therefore, conflict. -Conflicts: kdepimlibs4-devel %requires_ge libassuan-devel %description -n libgpgmepp-devel GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Who Should use GPGME? - -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +management. -This package contains the bindings to use the library in C++ applications. +This subpackage contains the headers needed for building applications +making use of libgpgmepp. %endif # with_cpp %if 0%{with_python2} %package -n python-pyme -Summary: Access GnuPG from Python 2 made easy +Summary: Python 2 bindings for GPGME, a library for accessing GnuPG Group: Development/Libraries/Python %description -n python-pyme GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Who Should use GPGME? - -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +management. This package contains the bindings to use the library from Python 2 applications. %endif # with_python2 %if 0%{with_python3} %package -n python3-pyme -Summary: Access GnuPG from Python 3 made easy +Summary: Python 3 bindings for GPGME, a library for accessing GnuPG Group: Development/Libraries/Python %description -n python3-pyme GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Who Should use GPGME? - -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +management. This package contains the bindings to use the library from Python 3 applications. %endif # with_python3 %if 0%{with_qt} -%package -n libqgpgme6 -Summary: A Library Designed to give Qt Applications easy Access to GnuPG +%package -n libqgpgme7 +Summary: Programmatic Qt library interface to GnuPG Group: Development/Libraries/C and C++ Requires: gpg2 -%description -n libqgpgme6 +%description -n libqgpgme7 GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Who Should use GPGME? - -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +management. This package contains the Qt bindings. %package -n libqgpgme-devel -Summary: A Library Designed to give C++ Qt Applications easy Access to GnuPG +Summary: Development files for libqgpgme, a Qt library for accessing GnuPG Group: Development/Libraries/C and C++ Requires: libgpgme-devel = %{version} Requires: libgpgmepp-devel = %{version} -Requires: libqgpgme6 = %{version} +Requires: libqgpgme7 = %{version} %description -n libqgpgme-devel GnuPG Made Easy (GPGME) is a library designed to make access to GnuPG -easier for applications. It provides a high-level Crypto API for +easier for applications. It provides a high-level crypto API for encryption, decryption, signing, signature verification, and key -management. Currently it uses GnuPG as its back-end, but the API is not -restricted to this engine. - -Who Should use GPGME? - -Because the direct use of GnuPG from an application can be a -complicated programming task, it is suggested that all software should -try to use GPGME instead. This way bug fixes or improvements can be -done at a central place and every application benefits from this. -Authors of MUAs should especially consider using GPGME. Creating a set -of standard widgets for common key selection tasks is even planned. +management. This package contains the bindings to use the library in Qt C++ applications. @@ -280,9 +190,6 @@ %prep %setup -q -%patch0 -p1 -%patch1 -p1 -%patch2 -p1 %build # for gpgme-1.7.0-python-Include-config.h.patch @@ -340,8 +247,8 @@ %endif # with_cpp %if 0%{with_qt} -%post -n libqgpgme6 -p /sbin/ldconfig -%postun -n libqgpgme6 -p /sbin/ldconfig +%post -n libqgpgme7 -p /sbin/ldconfig +%postun -n libqgpgme7 -p /sbin/ldconfig %endif # with_qt %post @@ -401,7 +308,7 @@ %endif # with_python3 %if 0%{with_qt} -%files -n libqgpgme6 +%files -n libqgpgme7 %defattr(-,root,root) %{_libdir}/libqgpgme.so.* ++++++ baselibs.conf ++++++ --- /var/tmp/diff_new_pack.b6zGuH/_old 2016-10-20 23:06:28.000000000 +0200 +++ /var/tmp/diff_new_pack.b6zGuH/_new 2016-10-20 23:06:28.000000000 +0200 @@ -1,3 +1,3 @@ libgpgme11 libgpgmepp6 -libqgpgme6 +libqgpgme7 ++++++ gpgme-1.7.0.tar.bz2 -> gpgme-1.7.1.tar.bz2 ++++++ ++++ 4792 lines of diff (skipped)
