Debian Patches
Status for nipype/1.12.0-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| deb_skip_doctest_pybids | Skip doctest pybids | Yaroslav Halchenko | no | 2018-12-18 | ||
| deb_disable_google_online_snippets | disable Google online snippets | Yaroslav Halchenko | no | 2014-10-14 | ||
| python3.patch | Force usage of Python3 | Andreas Tille <tille@debian.org> | no | 2020-02-20 | ||
| sphinx.patch | Get sphinx doc somehow building | Andreas Tille <tille@debian.org> | no | 2020-02-20 | ||
| fix-transpose.patch | Declare a,b in tests as np arrays explicitly | Nilesh Patra <nilesh@debian.org> | no | 2022-05-02 | ||
| reproducible-build.patch | Make build reproducible This patch replaces local file links with remote url in the sphinx generated documentation. Also disables printing object id in the generated doc. |
Mohammed Bilal <mdbilal@disroot.org> | not-needed | 2022-08-22 | ||
| fix-privacy-breaches.patch | fix privacy breaches caused by autoloaded links. There are a bunch of links landing in the html documentation which end up automatically loaded upon mere reading of the local-only document. This concerns images, scripts and stylesheets, among other things. These are problematic for two reasons: * they break when offline, or when the remote resource disappears; * they reveal the remote resource someone is reading the documentation at a given time. . Note that there are still some leftover links which still need to be addressed, but I failed to identify where they stem from (basically this concerns a bunch of scripts which are loaded from cloudflare, and also some TeX html-ized resources). |
Étienne Mollier <emollier@debian.org> | not-needed | 2023-08-18 | ||
| stabilize-makefiles.patch | stabilise the makefile implementation. This change fixes possible build issues when targets are executed in an unexpected order. |
Étienne Mollier <emollier@debian.org> | no | debian | 2025-12-20 | |
| nipype-conftest-cleanup.patch | conftest: start each pytest session with a pristine doctest data dir All doctests run in a single shared directory, <tmp>/nipype tmp/data, which pytest_configure only populates if it does not exist yet, and which is not removed at the end of the session (pytest_unconfigure removes just NIPYPE_TMPDIR). Doctests create entries in that directory, so a second pytest run on the same machine fails: - nipype.interfaces.io.ExportFile: os.mkdir("output_folder") raises FileExistsError - nipype.interfaces.base.traits_extension.Directory: the expected TraitError for the not yet existing 'relative_dir' is not raised This shows up when the test suite runs more than once in the same environment, e.g. during the build and again in autopkgtest, or once per Python version. . Recreate the data dir in the controller process at session start and remove it at session end. xdist workers reuse the controller's copy. |
Andreas Tille <tille@debian.org> | yes | 2026-11-05 |