Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
install-coqide-bytecode | Fix installation of coqide on bytecode architectures =================================================================== |
Ralf Treinen <treinen@debian.org> | no | |||
remove-heavy-tests.patch | Remove heavyweight tests Remove tests that use too much RAM or time to run on a buildd. (The MIPS buildd is frequently the culprit, as MIPS lacks an OCaml native compiler.) |
Benjamin Barenblat <bbaren@debian.org>, | not-needed | |||
remove-tests-that-need-coqlib.patch | Disable tests which require -coqlib to be set A number of tests (mostly for coq_makefile) assume that Coq is installed when the test runs. This isn't true in an sbuild environment, though, so disable those tests. |
Benjamin Barenblat <bbaren@debian.org> | not-needed | 2019-08-11 | ||
avoid-usr-bin-env.patch | Avoid invoking /usr/bin/env Per Debian Python policy [1], use `/usr/bin/python3` rather than `/usr/bin/env python` to refer to the system Python (3) interpreter. [1] https://www.debian.org/doc/packaging-manuals/python-policy/python.html#interpreter_loc |
Benjamin Barenblat <bbaren@debian.org> | not-needed | 2019-08-11 | ||
python-scripts-libraries.patch | Differentiate between Python scripts and libraries Eliminate the .py extension from executable Python scripts. |
Benjamin Barenblat <bbaren@debian.org> | not-needed | 2019-08-11 | ||
skip-dot-pc.patch | Ignore .pc directory when building | Benjamin Barenblat <bbaren@debian.org> | yes | 2019-08-11 | ||
remove-bytecode-failing-tests.patch | Disable tests which require ocamlopt Disable unit tests. They require ocamlopt, which isn't available on all Debian architectures, and Gaƫtan Gilbert says that "they don't test much yet" anyway. Also disable .vio tests, as they run afoul of https://github.com/coq/coq/issues/9141. |
Benjamin Barenblat <bbaren@debian.org> | not-needed | 2019-08-11 | ||
testsuite-bytecode | Fix export of byte architecture flag to test-suite. =================================================================== |
Hugo Herbelin <Hugo.Herbelin@inria.fr> | no |