Overview
Request 701734 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 694846
- Superseded by 702074
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
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
Use of Arial in test suite now also solved.
Why not to make arch-specific failing tests covered by
%ifarchdirectives? Otherwise, I would say we are there? @scarabeus?A few are arch specific, but they are bugs, and I am often turning the bcond on to retry them to try to workaround them. For that reason, bconds are better , as multiple sets of commands can be switched on together , rather than needing to edit the ifarch multiple times for each set of commands.
We are not quite ready - s390x is giving ImportError: Library "freetype" not found. That wasnt visible earlier, and builds were blocked. Tomorrow I'll re-disable the relevant test module which causes that so s390x is green again.