Hello community,

here is the log from the commit of package libqca-qt5 for openSUSE:Factory 
checked in at 2017-10-23 16:19:17
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libqca-qt5 (Old)
 and      /work/SRC/openSUSE:Factory/.libqca-qt5.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libqca-qt5"

Mon Oct 23 16:19:17 2017 rev:7 rq:532956 version:2.1.3

Changes:
--------
--- /work/SRC/openSUSE:Factory/libqca-qt5/libqca-qt5.changes    2017-10-07 
17:46:12.879043370 +0200
+++ /work/SRC/openSUSE:Factory/.libqca-qt5.new/libqca-qt5.changes       
2017-10-23 16:19:18.684120183 +0200
@@ -1,0 +2,7 @@
+Mon Oct  9 11:32:54 UTC 2017 - [email protected]
+
+- Hardcode certstore path on Tumbleweed, in order to avoid
+  BuildRequires: ca-certificates, which will create a conflict,
+  because it requires openssl-1_1_0 (bsc#1055310)
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ libqca-qt5.spec ++++++
--- /var/tmp/diff_new_pack.6Mz2H8/_old  2017-10-23 16:19:19.304091157 +0200
+++ /var/tmp/diff_new_pack.6Mz2H8/_new  2017-10-23 16:19:19.304091157 +0200
@@ -36,7 +36,6 @@
 Source99:       libqca-qt5-rpmlintrc
 # PATCH-FIX-OPENSUSE ansi.diff -- rh#1182200. drop ansi flags in order to 
compile with latest gcrypt
 Patch0:         ansi.diff
-BuildRequires:  ca-certificates
 BuildRequires:  cmake >= 2.8.12
 BuildRequires:  cyrus-sasl-devel
 BuildRequires:  gpg2
@@ -47,6 +46,7 @@
 %if 0%{?suse_version} >= 1330
 BuildRequires:  libopenssl-1_0_0-devel
 %else
+BuildRequires:  ca-certificates
 BuildRequires:  openssl-devel
 %endif
 %if %{with pkcs11}
@@ -107,6 +107,7 @@
       -DWITH_botan_PLUGIN=OFF \
       -DQCA_BINARY_INSTALL_DIR:PATH="%{_bindir}" \
       -DQCA_MAN_INSTALL_DIR:PATH="%{_mandir}" \
+      -Dqca_CERTSTORE="/etc/ssl/ca-bundle.pem" \
       -DQCA_SUFFIX=qt5
 make %{?_smp_mflags}
 


Reply via email to