Overview
Request 694846 superseded
- Reactivate test suite
- De-vendor python-future
- Add MIT to License: and %license due to vendored pypng, using
pypng-license.patch
- Remove macos and win32 platform support
- Add missing runtime dependency libxcb-glx0 and add several
runtime recommended dependencies
- Remove incorrect runtime dependencies
- Remove unused build dependencies
- Fix fdupes and permissions of examples
- Created by jayvdb
- In state superseded
- Supersedes 687992
- Superseded by 701734
@TheBlackCat, @alarrosa, @aplanas, @cyberiad, @czerw, @dirkmueller, @glaubitz, @mcepl, @mimi_vx, @pavlix, @posophe, @rjschwei, @scarabeus_iv, @sleep_walker, @tbechtold: review reminder
whats the issue with aarcht64 being excluded?
Small notes about aarch64 in previous SRs. It fails very badly. It might be possible to get a subset of the test suite working on aarch64 by selecting specific files. Im not sure it is worth it, as I expect it will then hit other arch-specific bugs, but if it is a really important arch for openSUSE I can explore it a bit more.
Also it was noted upstream at https://bitbucket.org/pyglet/pyglet/issues/225/unit-test-module-mediatest_procedural
There is one DSO loading fix merged upstream - I tried it and it didnt seem to make a difference.
Upstream has implied that we might try their beta release, or master.
I enabled build and test on aarch64 and it passed just fine: https://build.opensuse.org/package/show/home:Guillaume_G:branches:home:jayvdb:branches:devel:languages:python:numeric/python-pyglet
Nice. confusing but nice. I get the same results now. I'll resubmit with that as soon as the jobs are finished.
Request History
jayvdb created request
- Reactivate test suite
- De-vendor python-future
- Add MIT to License: and %license due to vendored pypng, using
pypng-license.patch
- Remove macos and win32 platform support
- Add missing runtime dependency libxcb-glx0 and add several
runtime recommended dependencies
- Remove incorrect runtime dependencies
- Remove unused build dependencies
- Fix fdupes and permissions of examples
You can still use xvfb-run and add to extensions that you need it with glx enabled and avoid most of the magic and additions of mesa/etc...
Also looking on the upstream I would just honestly say screw it and package the 1.4.0b1 from the september...
the glx and mesa aspect is not simplified by using xvfb-run - the hard part is the runtime deps, and due to dynamic linking in python that isnt automated (would be nice if we could, like pkgconfig voodoo). Using xvfb-run would maybe save a few lines, but then would mean starting and stopping Xvfb twice because python2 and python3 test invocations are forced to be separate. xvfb-run does nothing to assist with mesa or xcb build deps. This is the least of the problems with packaging pyglet.
1.4.0b1 is busted, at least in the test suite, but likely in the runtime library also. https://build.opensuse.org/package/show/home:jayvdb:branches:devel:languages:python:numeric/python-pyglet-1.4.0b I haven't put much effort into diagnosing it, or raising issues upstream against their beta, as they have enough problems yet to fix with their default branch, with issues that have been reported upstream, and https://build.opensuse.org/package/show/home:jayvdb:branches:devel:languages:python:numeric/python-pyglet-hg here, but my offline version of that is more advanced at getting into their interactive tests which is where everything really falls apart.
@TheBlackCat, @alarrosa, @aplanas, @cyberiad, @czerw, @dirkmueller, @glaubitz, @mcepl, @mimi_vx, @pavlix, @posophe, @rjschwei, @scarabeus_iv, @sleep_walker, @tbechtold: review reminder