Debian Codegraph @

debian/patches/

9 patches in series

  1. disable-multithreaded-test.patch
    One of the tests uses Python's multiprocessing, which on some machines causes FTBFS due to problematic permissions on /dev/shm, resulting in: PermissionError: [Errno 13] Permission denied This patch disables this test to allow building at the minor expense of this missing test.
    Author
    Sascha Steinbiss <[email protected]>
    Forwarded
    not-needed
  2. perl-shebang.patch
    Author
    Sascha Steinbiss <[email protected]>
    Forwarded
    not-needed
  3. samtools1.10
    Author
    Michael R. Crusoe <[email protected]>
    Forwarded
    https://github.com/sanger-pathogens/iva/pull/110
  4. disable-ram-test.patch
    KMC needs a lot of memory (multi-gigabyte) and fails hard when that memory cannot be allocated, which can cause builds to fail when tests are crashing because of that on low-spec buildds. Let's disable these tests for now.
    Author
    Sascha Steinbiss <[email protected]>
    Forwarded
    not-needed
    Last update
    2020-02-09
  5. python3.12.patch
    Author
    Andreas Tille <[email protected]>
    Forwarded
    https://github.com/sanger-pathogens/iva/pull/110
    Debian bug
    https://bugs.debian.org/1061804
    Last update
    2024-02-01
  6. check-test-data-and-altdir.patch
    iva/test_run_data is no longer bundled inside the Debian iva package. It's provided via a symlink (usr/lib/python3/dist-packages/iva/test_run_data -> usr/share/doc/iva/examples) from the separate iva-examples package, which is only a Suggests, not a Depends, of iva. This makes Tester check the data directory exists and is non-empty before doing anything else, printing a clear warning. It also accepts an explicit alternative directory, wired up in scripts/iva as --test_data_dir, and drops the dependency on iva.egg_extract (no longer needed once we have a plain absolute path).
    Author
    Andreas Tille <[email protected]>
    Forwarded
    not-needed
    Last update
    2026-07-08
  7. fix_python3.14_forkserver.patch
    Python 3.14 changed the default multiprocessing start method on Linux from "fork" to "forkserver". This patch prevents reimporting and re-executing the entire script from scratch
    Author
    Andreas Tille <[email protected]>
    Forwarded
    https://github.com/sanger-pathogens/iva/issues/111
    Debian bug
    https://bugs.debian.org/1141283
    Last update
    2026-07-08
  8. fork-context-workaround.patch
    Python 3.14 made "forkserver" the default multiprocessing start method on Linux. There is a known CPython regression (https://github.com/python/cpython/issues/144503, present in at least 3.14.3/3.13.12) in forkserver's daemon bootstrap that can surface as "ConnectionResetError: [Errno 104] Connection reset by peer" during the initial authentication handshake, unrelated to anything this script does. This script only uses multiprocessing.Process for two short-lived, trivial parallel calls to pyfastaq.tasks.to_fasta() and has no threading concerns that would make "fork" unsafe, so request the "fork" context explicitly for these two Process objects rather than relying on the (currently broken in some 3.14 point releases) forkserver default. This is a workaround for an upstream Python bug, not a long-term design choice; it can be dropped once the relevant Python versions in Debian carry the fix for cpython#144503.
    Author
    Andreas Tille <[email protected]>
    Forwarded
    https://github.com/sanger-pathogens/iva/issues/111
    Bug
    https://github.com/python/cpython/issues/144503
    Last update
    2026-07-08
dir..
file check-test-data-and-altdir.patch
file disable-multithreaded-test.patch
file disable-ram-test.patch
file fix_python3.14_forkserver.patch
file fork-context-workaround.patch
file perl-shebang.patch
file python3.12.patch
file samtools1.10
file series
file syntax-warning.patch