Hello community,

here is the log from the commit of package lalmetaio for openSUSE:Factory 
checked in at 2020-12-03 18:41:49
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/lalmetaio (Old)
 and      /work/SRC/openSUSE:Factory/.lalmetaio.new.5913 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "lalmetaio"

Thu Dec  3 18:41:49 2020 rev:3 rq:849353 version:1.6.1

Changes:
--------
--- /work/SRC/openSUSE:Factory/lalmetaio/lalmetaio.changes      2020-10-30 
11:50:09.229839421 +0100
+++ /work/SRC/openSUSE:Factory/.lalmetaio.new.5913/lalmetaio.changes    
2020-12-03 18:43:11.066193808 +0100
@@ -1,0 +2,10 @@
+Thu Nov 19 09:20:15 UTC 2020 - Atri Bhattacharya <[email protected]>
+
+- Disable builds for 32-bit archs where lal is not supported.
+
+-------------------------------------------------------------------
+Fri Nov  6 14:59:22 UTC 2020 - Stefan BrĂ¼ns <[email protected]>
+
+- Build without octave bindings on Leap 15.x, requires SWIG 4.0
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ lalmetaio.spec ++++++
--- /var/tmp/diff_new_pack.ZqO6Cc/_old  2020-12-03 18:43:11.678194616 +0100
+++ /var/tmp/diff_new_pack.ZqO6Cc/_new  2020-12-03 18:43:11.678194616 +0100
@@ -17,7 +17,11 @@
 
 
 %define shlib lib%{name}8
+%if 0%{?suse_version} >= 1550
 %bcond_without octave
+%else
+%bcond_with    octave
+%endif
 Name:           lalmetaio
 Version:        1.6.1
 Release:        0
@@ -50,6 +54,7 @@
 # /SECTION
 Requires:       python-lal >= 6.21.0
 Requires:       python-numpy
+ExcludeArch:    %{ix86}
 
 %python_subpackages
 
_______________________________________________
openSUSE Commits mailing list -- [email protected]
To unsubscribe, email [email protected]
List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette
List Archives: 
https://lists.opensuse.org/archives/list/[email protected]

Reply via email to