Hello community,

here is the log from the commit of package python3-simplejson for 
openSUSE:Factory checked in at 2013-08-01 16:02:17
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python3-simplejson (Old)
 and      /work/SRC/openSUSE:Factory/.python3-simplejson.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python3-simplejson"

Changes:
--------
--- /work/SRC/openSUSE:Factory/python3-simplejson/python3-simplejson.changes    
2013-06-21 19:09:02.000000000 +0200
+++ 
/work/SRC/openSUSE:Factory/.python3-simplejson.new/python3-simplejson.changes   
    2013-08-01 16:02:19.000000000 +0200
@@ -1,0 +2,5 @@
+Thu Aug  1 09:11:12 UTC 2013 - [email protected]
+
+- No need to run 2to3 anymore, fixes testsuite
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ python3-simplejson.spec ++++++
--- /var/tmp/diff_new_pack.om3sLn/_old  2013-08-01 16:02:19.000000000 +0200
+++ /var/tmp/diff_new_pack.om3sLn/_new  2013-08-01 16:02:19.000000000 +0200
@@ -26,9 +26,8 @@
 Source:         
http://pypi.python.org/packages/source/s/simplejson/simplejson-%{version}.tar.gz
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 BuildRequires:  python3 >= 3.3
-BuildRequires:  python3-2to3
 BuildRequires:  python3-devel
-BuildRequires:  python3-distribute
+BuildRequires:  python3-setuptools
 Requires:       python3-coverage
 Requires:       python3-nose
 
@@ -42,15 +41,13 @@
 %setup -q -n simplejson-%{version}
 
 %build
-2to3 -w -n ./
 CFLAGS="%{optflags} -fno-strict-aliasing" python3 setup.py build
 
 %install
 python3 setup.py install --prefix=%{_prefix} --root=%{buildroot}
 
-#NOTE(saschpe): Recursion error, check back:
-#%%check
-#python3 setup.py test
+%check
+python3 setup.py test
 
 %files
 %defattr(-,root,root)

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

Reply via email to