summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorSergey Vlasov <sigprof@gmail.com>2024-03-10 22:20:04 +0300
committerFranz Pletz <fpletz@fnordicwalking.de>2024-07-23 22:13:25 +0200
commitb934fad58cec0b7923b33ea2e49ae022bef2cc8a (patch)
tree32c37d4ce2965b538f36ac476f38b338c3ba7df1 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentf20ebb120121e7cf3b549670a61691a92bb089b4 (diff)
i3: fix and reenable testsuite
The `checkPhase` script was stale and needed to be rewritten for the new version of i3 (paths are different now, and `complete-run.pl` now invokes `xvfb-run` internally). The code to check the log file for errors might be unneeded for the new version (`complete-run.pl` seems to return a non-zero exit code correctly on errors), but is left to catch any possible regressions in the test runner behavior. Also the `318-i3-dmenu-desktop.t` testcase was failing, because that testcase was creating a temporary Perl script intended to shadow the real `i3-msg` executable, but the `#!/usr/bin/env perl` shebang in that script did not work in the build environment; this problem was not really obvious, because `system('i3-msg', $cmd)` silently continued to search for the `i3-msg` executable further in `$PATH` and launched the real binary instead of the replacement script. The problematic shebang needed to be replaced manually, because `patchShebangs` handles only real shebangs on the first line of each executable file.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions