Add a smoke-test for xvfb-run, and make it pass on armhf again
-
d/tests: Add an autopkgtest to verify basic functionality of xvfb-run
xvfb-run is frequently used in other packages' automated tests, so any regressions that affect it are likely to cause numerous test failures. Having Xvfb's own test fail provides a way to narrow down the reason for failure.
-
d/rules: Check basic functionality of xvfb-run at build-time
Not all architectures have autopkgtest coverage, so detecting regressions at build-time is sometimes the best we can do.
-
d/control, d/rules.flags: Disable libunwind on armhf
libunwind 1.7.x regressed on armhf in a way that causes Xvfb to segfault during startup, and displaying better backtraces on a crash doesn't seem like key functionality for Xvfb.
The last commit can be reverted (if desired) after libunwind is fixed, but the first two will continue to be desirable.