Hello community,

here is the log from the commit of package python3-pip for openSUSE:Factory 
checked in at 2014-02-18 14:46:29
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python3-pip (Old)
 and      /work/SRC/openSUSE:Factory/.python3-pip.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python3-pip"

Changes:
--------
--- /work/SRC/openSUSE:Factory/python3-pip/python3-pip.changes  2014-01-23 
15:55:10.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.python3-pip.new/python3-pip.changes     
2014-02-18 14:46:30.000000000 +0100
@@ -1,0 +2,6 @@
+Fri Feb 14 14:06:19 UTC 2014 - [email protected]
+
+- disable test dependencies for SLE 12
+- break build cycle when python 3.4 starts requiring python3-pip
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ python3-pip.spec ++++++
--- /var/tmp/diff_new_pack.1ZHK5G/_old  2014-02-18 14:46:30.000000000 +0100
+++ /var/tmp/diff_new_pack.1ZHK5G/_new  2014-02-18 14:46:30.000000000 +0100
@@ -31,11 +31,18 @@
 %endif
 BuildRequires:  python3-devel
 BuildRequires:  python3-setuptools
-# Test requirements:
+
+# prevent build cycle with python3 requirement
+#!BuildIgnore:  python3-pip
+
+# Test requirements (not on SLE12)
+%if 0%{?suse_version} != 1315
 BuildRequires:  python3-mock
 BuildRequires:  python3-pytest
 BuildRequires:  python3-scripttest >= 1.3
 BuildRequires:  python3-virtualenv >= 1.1.0
+%endif
+
 Requires:       python3-setuptools
 Requires(post): update-alternatives
 Requires(postun): update-alternatives
@@ -60,7 +67,9 @@
 ln -s %{_bindir}/pip%{py3_ver} %{buildroot}%{_bindir}/pip
 
 %check
+%if 0%{?suse_version} != 1315
 python3 setup.py test
+%endif
 
 %pre
 # Since /usr/bin/pip became ghosted to be used with update-alternatives, we 
have to get rid

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to