Created attachment 275991 [details] msgpack-0.1.9.ebuild (CC:ing python@ since they might be interested in this, sorry if I'm way off here) Attaching ebuild of the msgpack (de)serializer for python. Following the current name conventions (dev-libs/msgpack dev-ruby/msgpack). I got it to build for python 2.5,2.6,2.7 and 3.1 - but one test segfaults on all versions: test_obj.test_bad_hook I'll take a look at what's been changed upstream, perhaps there is a solution in HEAD. Also, I'm not very happy about "cd test; foo" in src_test() - but I don't know any other way of avoiding that PYTHONPATH issue.
Created attachment 276015 [details] msgpack-0.1.9.ebuild With some help from Arfrever, I was able to remove the "cd test". Additionally, Arfrever also noted that disabling the segfault test and running the suite on 3.1, 3.2 will show a rather bleak test result: FAILED (errors=14, failures=3)
DISTUTILS_SRC_TEST="nosetests" already adds "test? ( dev-python/nose )" to DEPEND. src_test() { python_execute_nosetests -P '$(ls -d build-${PYTHON_ABI}/lib.*)' -- -w test }
Created attachment 284361 [details] msgpack-0.1.10.ebuild New ebuild for msgpack 0.1.10. Note: python3 has issues running the test suite. I'm currently looking into it (talking to upstream)
Will you be proxying it?
Yes, I will proxy it - but I prefer keeping it out until the test suite is fixed on python 3.
If you mention proxy maintaining, CC apropriate herd :) Johan, i can take it as python@ and proxy-maint@ when you think it's ready.
After washing this through 2to3 and fiddling around with nosetests3 I have to draw the conclusion that the test suite isn't ready to run on python 3. We should therefore disable it. Let's wait a couple of days and see what upstream says about it. Track progress here: http://jira.msgpack.org/browse/MSGPACK-33
Created attachment 285031 [details] msgpack-0.1.10.ebuild Updated ebuild with minor fixes, all contributed by Arfrever (thanks for your valuable feedback!).
(In reply to comment #8) > Created attachment 285031 [details] > msgpack-0.1.10.ebuild > > Updated ebuild with minor fixes, all contributed by Arfrever (thanks for your > valuable feedback!). Oh, forgot to mention - we now skip tests on 3.*
There's actually a "test3" in their git repo, which now is added to MANIFEST.in. These tests pass perfectly (nosetests3 -w test3) on py 3.1, 3.2 - so when 0.1.11 is out I'll update the ebuild and we'll hopefully have a perfectly fine ebuild
(In reply to comment #10) > There's actually a "test3" in their git repo, which now is added to > MANIFEST.in. These tests pass perfectly (nosetests3 -w test3) on py 3.1, 3.2 - > so when 0.1.11 is out I'll update the ebuild and we'll hopefully have a > perfectly fine ebuild Ok, that's fine. Ping us when you are ready to maintain it in tree.
Any news here?
Sorry for my late response. Fellt out of my radar :( No 0.1.11 with python3 tests yet, lets get on with the show (read: release 0.1.10 with python 3 tests disabled)?
Seems fine to me.
Created attachment 297115 [details] msgpack-0.1.12.ebuild OMG msgpack 0.1.12 here. Includes python 3 fixes and removes setuptools dep. Got some help from Arfrever to solve pythonpath issues regarding nosetests. (note to nose users: nose defaults to -w . which will mess with your PYTHONPATH)
* Testing of dev-python/msgpack-0.1.12 with CPython 3.2... PYTHONPATH=build/lib.linux-x86_64-3.2 nosetests --verbosity=1 -P -w test /usr/bin/nosetests: '/usr/bin/nosetests-3.2' does not exist * ERROR: dev-python/msgpack-0.1.12 failed (test phase): Now that's a funny one, but most likely my fault :)
+ 28 Dec 2011; Patrick Lauer <patrick@gentoo.org> +metadata.xml, + +msgpack-0.1.12.ebuild: + Initial import for #370267, ebuild by Johan Bergstr�m (I wonder if my console mangled that?)
