Hello community,
here is the log from the commit of package python-pycryptodome for
openSUSE:Factory checked in at 2019-05-25 13:17:05
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-pycryptodome (Old)
and /work/SRC/openSUSE:Factory/.python-pycryptodome.new.5148 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-pycryptodome"
Sat May 25 13:17:05 2019 rev:10 rq:705218 version:3.8.1
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-pycryptodome/python-pycryptodome.changes
2019-05-20 10:25:01.005982636 +0200
+++
/work/SRC/openSUSE:Factory/.python-pycryptodome.new.5148/python-pycryptodome.changes
2019-05-25 13:17:10.188404943 +0200
@@ -1,0 +2,6 @@
+Fri May 24 11:36:30 UTC 2019 - Martin Liška <mli...@suse.cz>
+
+- Use -fno-strict-aliasing in order to bypass:
+ https://github.com/Legrandin/pycryptodome/issues/291.
+
+-------------------------------------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-pycryptodome.spec ++++++
--- /var/tmp/diff_new_pack.e3JoQU/_old 2019-05-25 13:17:11.300404529 +0200
+++ /var/tmp/diff_new_pack.e3JoQU/_new 2019-05-25 13:17:11.300404529 +0200
@@ -84,7 +84,9 @@
%setup -q -n pycryptodome-%{version}
%build
-export CFLAGS="%{optflags}"
+# Use -fno-strict-aliasing in order to bypass:
+# https://github.com/Legrandin/pycryptodome/issues/291
+export CFLAGS="%{optflags} -fno-strict-aliasing"
%python_build
%install
