debspawn 0.6.5 on fennel at 2024-10-18 06:44:30 UTC-0700 gpgv: Signature made Sat 31 Aug 2024 04:27:49 AM PDT gpgv: using RSA key 8F6DE104377F3B11E741748731F3144544A1741A gpgv: issuer "tchet@debian.org" gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for /var/lib/lkspark/workspaces/d0ebde8e-dcdc-4b00-96bd-87435da4cdb6/multiqc_1.21+dfsg-2.dsc: no acceptable signature found dpkg-source: info: extracting multiqc in multiqc-1.21+dfsg dpkg-source: info: unpacking multiqc_1.21+dfsg.orig.tar.xz dpkg-source: info: unpacking multiqc_1.21+dfsg.orig-debian-tests-data.tar.xz dpkg-source: info: unpacking multiqc_1.21+dfsg-2.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying removeHighcharts.patch ╔═══════════════════════╗ ║ Package build ║ ╚═══════════════════════╝ Package: multiqc Version: 1.21+dfsg-2 Distribution: landing Architecture: amd64 Free space in workspace: 63.1GiB ┌───────────────────────────────────────┐ │ Preparing container for build │ └───────────────────────────────────────┘ Get:1 https://repo.pureos.net/pureos landing InRelease [9625 B] Get:2 https://repo.pureos.net/pureos landing/main all Packages [3883 kB] Get:3 https://repo.pureos.net/pureos landing/main amd64 Packages [4392 kB] Fetched 8284 kB in 1s (6959 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following packages will be upgraded: gpgv 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/218 kB of archives. After this operation, 1024 B disk space will be freed. debconf: delaying package configuration, since apt-utils is not installed (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 13780 files and directories currently installed.) Preparing to unpack .../gpgv_2.2.44-1_amd64.deb ... Unpacking gpgv (2.2.44-1) over (2.2.43-8+b1) ... Setting up gpgv (2.2.44-1) ... Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.10). dpkg-dev is already the newest version (1.21.22pureos1). fakeroot is already the newest version (1.36-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ┌───────────────────────────────────────────────┐ │ Installing package build-dependencies │ └───────────────────────────────────────────────┘ Note, using directory './' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: autoconf automake autopoint autotools-dev blt bsdextrautils debhelper dh-autoreconf dh-python dh-strip-nondeterminism dwz file fontconfig-config fonts-dejavu-core fonts-dejavu-mono fonts-lyx gettext gettext-base groff-base intltool-debian libarchive-zip-perl libblas3 libbrotli1 libdebhelper-perl libdeflate0 libelf1t64 libfile-stripnondeterminism-perl libfontconfig1 libfreetype6 libfribidi0 libgfortran5 libglib2.0-0t64 libgraphite2-3 libgssapi-krb5-2 libharfbuzz0b libicu72 libimagequant0 libjbig0 libjpeg62-turbo libjs-jquery libjs-jquery-ui libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblapack3 liblbfgsb0 liblcms2-2 liblerc4 libmagic-mgc libmagic1t64 libncursesw6 libnsl2 libopenjp2-7 libpipeline1 libpng16-16t64 libpython3-stdlib libpython3.12-stdlib libqhull-r8.0 libraqm0 libreadline8t64 libsharpyuv0 libsqlite3-0 libtcl8.6 libtiff6 libtirpc-common libtirpc3t64 libtk8.6 libtool libuchardet0 libwebp7 libwebpdemux2 libwebpmux3 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 libxft2 libxml2 libxrender1 libxslt1.1 libxss1 libyaml-0-2 m4 man-db media-types netbase po-debconf python-matplotlib-data python3 python3-all python3-appdirs python3-attr python3-autocommand python3-brotli python3-certifi python3-chardet python3-charset-normalizer python3-click python3-colorama python3-coloredlogs python3-colormath python3-contourpy python3-cycler python3-dateutil python3-decorator python3-fastjsonschema python3-fonttools python3-fs python3-humanfriendly python3-humanize python3-idna python3-importlib-metadata python3-inflect python3-jaraco.context python3-jaraco.functools python3-jinja2 python3-jsonschema python3-jsonschema-specifications python3-jupyter-core python3-kiwisolver python3-lxml python3-lz4 python3-lzstring python3-markdown python3-markdown-it python3-markupsafe python3-matplotlib python3-mdurl python3-more-itertools python3-mpmath python3-nbformat python3-networkx python3-numpy python3-packaging python3-pil python3-pil.imagetk python3-pkg-resources python3-platformdirs python3-plotly python3-pyaml-env python3-pygments python3-pyparsing python3-referencing python3-requests python3-rich python3-rich-click python3-rpds-py python3-scipy python3-setuptools python3-six python3-spectra python3-sympy python3-tenacity python3-tk python3-traitlets python3-typeguard python3-typing-extensions python3-tz python3-ufolib2 python3-urllib3 python3-yaml python3-zipp python3.12 python3.12-tk python3.13-tk readline-common sensible-utils tk8.6-blt2.5 unicode-data x11-common 0 upgraded, 173 newly installed, 0 to remove and 0 not upgraded. Need to get 2812 kB/108 MB of archives. After this operation, 493 MB of additional disk space will be used. Get:1 https://repo.pureos.net/pureos landing/main all python3-colormath all 3.0.0-4 [34.7 kB] Get:2 https://repo.pureos.net/pureos landing/main all python3-lzstring all 1.0.4-3 [5544 B] Get:3 https://repo.pureos.net/pureos landing/main all python3-plotly all 5.20.0+dfsg-1 [2726 kB] Get:4 https://repo.pureos.net/pureos landing/main all python3-pyaml-env all 1.2.1-2 [9032 B] Get:5 https://repo.pureos.net/pureos landing/main all python3-rich-click all 1.6.0-1 [20.8 kB] Get:6 https://repo.pureos.net/pureos landing/main all python3-spectra all 0.0.11-4 [16.5 kB] Fetched 2812 kB in 0s (13.7 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package media-types. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 13779 files and directories currently installed.) Preparing to unpack .../000-media-types_10.1.0_all.deb ... Unpacking media-types (10.1.0) ... Selecting previously unselected package netbase. Preparing to unpack .../001-netbase_6.4_all.deb ... Unpacking netbase (6.4) ... Selecting previously unselected package libncursesw6:amd64. Preparing to unpack .../002-libncursesw6_6.5-2_amd64.deb ... Unpacking libncursesw6:amd64 (6.5-2) ... Selecting previously unselected package libkrb5support0:amd64. Preparing to unpack .../003-libkrb5support0_1.21.3-3_amd64.deb ... Unpacking libkrb5support0:amd64 (1.21.3-3) ... Selecting previously unselected package libk5crypto3:amd64. Preparing to unpack .../004-libk5crypto3_1.21.3-3_amd64.deb ... Unpacking libk5crypto3:amd64 (1.21.3-3) ... Selecting previously unselected package libkeyutils1:amd64. Preparing to unpack .../005-libkeyutils1_1.6.3-3_amd64.deb ... Unpacking libkeyutils1:amd64 (1.6.3-3) ... Selecting previously unselected package libkrb5-3:amd64. Preparing to unpack .../006-libkrb5-3_1.21.3-3_amd64.deb ... Unpacking libkrb5-3:amd64 (1.21.3-3) ... Selecting previously unselected package libgssapi-krb5-2:amd64. Preparing to unpack .../007-libgssapi-krb5-2_1.21.3-3_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.21.3-3) ... Selecting previously unselected package libtirpc-common. Preparing to unpack .../008-libtirpc-common_1.3.4+ds-1.3_all.deb ... Unpacking libtirpc-common (1.3.4+ds-1.3) ... Selecting previously unselected package libtirpc3t64:amd64. Preparing to unpack .../009-libtirpc3t64_1.3.4+ds-1.3_amd64.deb ... Adding 'diversion of /lib/x86_64-linux-gnu/libtirpc.so.3 to /lib/x86_64-linux-gnu/libtirpc.so.3.usr-is-merged by libtirpc3t64' Adding 'diversion of /lib/x86_64-linux-gnu/libtirpc.so.3.0.0 to /lib/x86_64-linux-gnu/libtirpc.so.3.0.0.usr-is-merged by libtirpc3t64' Unpacking libtirpc3t64:amd64 (1.3.4+ds-1.3) ... Selecting previously unselected package libnsl2:amd64. Preparing to unpack .../010-libnsl2_1.3.0-3+b2_amd64.deb ... Unpacking libnsl2:amd64 (1.3.0-3+b2) ... Selecting previously unselected package readline-common. Preparing to unpack .../011-readline-common_8.2-5_all.deb ... Unpacking readline-common (8.2-5) ... Selecting previously unselected package libreadline8t64:amd64. Preparing to unpack .../012-libreadline8t64_8.2-5_amd64.deb ... Adding 'diversion of /lib/x86_64-linux-gnu/libhistory.so.8 to /lib/x86_64-linux-gnu/libhistory.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/x86_64-linux-gnu/libhistory.so.8.2 to /lib/x86_64-linux-gnu/libhistory.so.8.2.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/x86_64-linux-gnu/libreadline.so.8 to /lib/x86_64-linux-gnu/libreadline.so.8.usr-is-merged by libreadline8t64' Adding 'diversion of /lib/x86_64-linux-gnu/libreadline.so.8.2 to /lib/x86_64-linux-gnu/libreadline.so.8.2.usr-is-merged by libreadline8t64' Unpacking libreadline8t64:amd64 (8.2-5) ... Selecting previously unselected package libsqlite3-0:amd64. Preparing to unpack .../013-libsqlite3-0_3.46.0-1_amd64.deb ... Unpacking libsqlite3-0:amd64 (3.46.0-1) ... Selecting previously unselected package libpython3.12-stdlib:amd64. Preparing to unpack .../014-libpython3.12-stdlib_3.12.6-1_amd64.deb ... Unpacking libpython3.12-stdlib:amd64 (3.12.6-1) ... Selecting previously unselected package python3.12. Preparing to unpack .../015-python3.12_3.12.6-1_amd64.deb ... Unpacking python3.12 (3.12.6-1) ... Selecting previously unselected package libpython3-stdlib:amd64. Preparing to unpack .../016-libpython3-stdlib_3.12.6-1_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.12.6-1) ... Selecting previously unselected package python3. Preparing to unpack .../017-python3_3.12.6-1_amd64.deb ... Unpacking python3 (3.12.6-1) ... Selecting previously unselected package sensible-utils. Preparing to unpack .../018-sensible-utils_0.0.24_all.deb ... Unpacking sensible-utils (0.0.24) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../019-libmagic-mgc_1%3a5.45-3_amd64.deb ... Unpacking libmagic-mgc (1:5.45-3) ... Selecting previously unselected package libmagic1t64:amd64. Preparing to unpack .../020-libmagic1t64_1%3a5.45-3_amd64.deb ... Unpacking libmagic1t64:amd64 (1:5.45-3) ... Selecting previously unselected package file. Preparing to unpack .../021-file_1%3a5.45-3_amd64.deb ... Unpacking file (1:5.45-3) ... Selecting previously unselected package gettext-base. Preparing to unpack .../022-gettext-base_0.22.5-2_amd64.deb ... Unpacking gettext-base (0.22.5-2) ... Selecting previously unselected package libuchardet0:amd64. Preparing to unpack .../023-libuchardet0_0.0.8-1+b1_amd64.deb ... Unpacking libuchardet0:amd64 (0.0.8-1+b1) ... Selecting previously unselected package groff-base. Preparing to unpack .../024-groff-base_1.23.0-5_amd64.deb ... Unpacking groff-base (1.23.0-5) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../025-bsdextrautils_2.40.2-9_amd64.deb ... Unpacking bsdextrautils (2.40.2-9) ... Selecting previously unselected package libpipeline1:amd64. Preparing to unpack .../026-libpipeline1_1.5.8-1_amd64.deb ... Unpacking libpipeline1:amd64 (1.5.8-1) ... Selecting previously unselected package man-db. Preparing to unpack .../027-man-db_2.13.0-1_amd64.deb ... Unpacking man-db (2.13.0-1) ... Selecting previously unselected package m4. Preparing to unpack .../028-m4_1.4.19-4_amd64.deb ... Unpacking m4 (1.4.19-4) ... Selecting previously unselected package autoconf. Preparing to unpack .../029-autoconf_2.72-3_all.deb ... Unpacking autoconf (2.72-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../030-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../031-automake_1%3a1.16.5-1.3_all.deb ... Unpacking automake (1:1.16.5-1.3) ... Selecting previously unselected package autopoint. Preparing to unpack .../032-autopoint_0.22.5-2_all.deb ... Unpacking autopoint (0.22.5-2) ... Selecting previously unselected package libtcl8.6:amd64. Preparing to unpack .../033-libtcl8.6_8.6.15+dfsg-2_amd64.deb ... Unpacking libtcl8.6:amd64 (8.6.15+dfsg-2) ... Selecting previously unselected package libbrotli1:amd64. Preparing to unpack .../034-libbrotli1_1.1.0-2+b4_amd64.deb ... Unpacking libbrotli1:amd64 (1.1.0-2+b4) ... Selecting previously unselected package libpng16-16t64:amd64. Preparing to unpack .../035-libpng16-16t64_1.6.44-2_amd64.deb ... Unpacking libpng16-16t64:amd64 (1.6.44-2) ... Selecting previously unselected package libfreetype6:amd64. Preparing to unpack .../036-libfreetype6_2.13.3+dfsg-1_amd64.deb ... Unpacking libfreetype6:amd64 (2.13.3+dfsg-1) ... Selecting previously unselected package fonts-dejavu-mono. Preparing to unpack .../037-fonts-dejavu-mono_2.37-8_all.deb ... Unpacking fonts-dejavu-mono (2.37-8) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../038-fonts-dejavu-core_2.37-8_all.deb ... Unpacking fonts-dejavu-core (2.37-8) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../039-fontconfig-config_2.15.0-1.1_amd64.deb ... Unpacking fontconfig-config (2.15.0-1.1) ... Selecting previously unselected package libfontconfig1:amd64. Preparing to unpack .../040-libfontconfig1_2.15.0-1.1_amd64.deb ... Unpacking libfontconfig1:amd64 (2.15.0-1.1) ... Selecting previously unselected package libxau6:amd64. Preparing to unpack .../041-libxau6_1%3a1.0.9-1+b1_amd64.deb ... Unpacking libxau6:amd64 (1:1.0.9-1+b1) ... Selecting previously unselected package libxdmcp6:amd64. Preparing to unpack .../042-libxdmcp6_1%3a1.1.2-3+b1_amd64.deb ... Unpacking libxdmcp6:amd64 (1:1.1.2-3+b1) ... Selecting previously unselected package libxcb1:amd64. Preparing to unpack .../043-libxcb1_1.17.0-2_amd64.deb ... Unpacking libxcb1:amd64 (1.17.0-2) ... Selecting previously unselected package libx11-data. Preparing to unpack .../044-libx11-data_2%3a1.8.7-1_all.deb ... Unpacking libx11-data (2:1.8.7-1) ... Selecting previously unselected package libx11-6:amd64. Preparing to unpack .../045-libx11-6_2%3a1.8.7-1+b1_amd64.deb ... Unpacking libx11-6:amd64 (2:1.8.7-1+b1) ... Selecting previously unselected package libxrender1:amd64. Preparing to unpack .../046-libxrender1_1%3a0.9.10-1.1+b1_amd64.deb ... Unpacking libxrender1:amd64 (1:0.9.10-1.1+b1) ... Selecting previously unselected package libxft2:amd64. Preparing to unpack .../047-libxft2_2.3.6-1+b1_amd64.deb ... Unpacking libxft2:amd64 (2.3.6-1+b1) ... Selecting previously unselected package libxext6:amd64. Preparing to unpack .../048-libxext6_2%3a1.3.4-1+b2_amd64.deb ... Unpacking libxext6:amd64 (2:1.3.4-1+b2) ... Selecting previously unselected package x11-common. Preparing to unpack .../049-x11-common_1%3a7.7+23.1_all.deb ... Unpacking x11-common (1:7.7+23.1) ... Selecting previously unselected package libxss1:amd64. Preparing to unpack .../050-libxss1_1%3a1.2.3-1+b1_amd64.deb ... Unpacking libxss1:amd64 (1:1.2.3-1+b1) ... Selecting previously unselected package libtk8.6:amd64. Preparing to unpack .../051-libtk8.6_8.6.15-1_amd64.deb ... Unpacking libtk8.6:amd64 (8.6.15-1) ... Selecting previously unselected package tk8.6-blt2.5. Preparing to unpack .../052-tk8.6-blt2.5_2.5.3+dfsg-7_amd64.deb ... Unpacking tk8.6-blt2.5 (2.5.3+dfsg-7) ... Selecting previously unselected package blt. Preparing to unpack .../053-blt_2.5.3+dfsg-7_amd64.deb ... Unpacking blt (2.5.3+dfsg-7) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../054-libdebhelper-perl_13.20_all.deb ... Unpacking libdebhelper-perl (13.20) ... Selecting previously unselected package libtool. Preparing to unpack .../055-libtool_2.4.7-7_all.deb ... Unpacking libtool (2.4.7-7) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../056-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../057-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../058-libfile-stripnondeterminism-perl_1.14.0-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.14.0-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../059-dh-strip-nondeterminism_1.14.0-1_all.deb ... Unpacking dh-strip-nondeterminism (1.14.0-1) ... Selecting previously unselected package libelf1t64:amd64. Preparing to unpack .../060-libelf1t64_0.191-2_amd64.deb ... Unpacking libelf1t64:amd64 (0.191-2) ... Selecting previously unselected package dwz. Preparing to unpack .../061-dwz_0.15-1+b1_amd64.deb ... Unpacking dwz (0.15-1+b1) ... Selecting previously unselected package libicu72:amd64. Preparing to unpack .../062-libicu72_72.1-5_amd64.deb ... Unpacking libicu72:amd64 (72.1-5) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../063-libxml2_2.12.7+dfsg+really2.9.14-0.1_amd64.deb ... Unpacking libxml2:amd64 (2.12.7+dfsg+really2.9.14-0.1) ... Selecting previously unselected package gettext. Preparing to unpack .../064-gettext_0.22.5-2_amd64.deb ... Unpacking gettext (0.22.5-2) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../065-intltool-debian_0.35.0+20060710.6_all.deb ... Unpacking intltool-debian (0.35.0+20060710.6) ... Selecting previously unselected package po-debconf. Preparing to unpack .../066-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../067-debhelper_13.20_all.deb ... Unpacking debhelper (13.20) ... Selecting previously unselected package python3-autocommand. Preparing to unpack .../068-python3-autocommand_2.2.2-3_all.deb ... Unpacking python3-autocommand (2.2.2-3) ... Selecting previously unselected package python3-more-itertools. Preparing to unpack .../069-python3-more-itertools_10.5.0-1_all.deb ... Unpacking python3-more-itertools (10.5.0-1) ... Selecting previously unselected package python3-typing-extensions. Preparing to unpack .../070-python3-typing-extensions_4.12.2-2_all.deb ... Unpacking python3-typing-extensions (4.12.2-2) ... Selecting previously unselected package python3-zipp. Preparing to unpack .../071-python3-zipp_3.20.2-1_all.deb ... Unpacking python3-zipp (3.20.2-1) ... Selecting previously unselected package python3-importlib-metadata. Preparing to unpack .../072-python3-importlib-metadata_8.5.0-1_all.deb ... Unpacking python3-importlib-metadata (8.5.0-1) ... Selecting previously unselected package python3-typeguard. Preparing to unpack .../073-python3-typeguard_4.3.0-1_all.deb ... Unpacking python3-typeguard (4.3.0-1) ... Selecting previously unselected package python3-inflect. Preparing to unpack .../074-python3-inflect_7.3.1-2_all.deb ... Unpacking python3-inflect (7.3.1-2) ... Selecting previously unselected package python3-jaraco.context. Preparing to unpack .../075-python3-jaraco.context_6.0.0-1_all.deb ... Unpacking python3-jaraco.context (6.0.0-1) ... Selecting previously unselected package python3-jaraco.functools. Preparing to unpack .../076-python3-jaraco.functools_4.1.0-1_all.deb ... Unpacking python3-jaraco.functools (4.1.0-1) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../077-python3-pkg-resources_74.1.2-2_all.deb ... Unpacking python3-pkg-resources (74.1.2-2) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../078-python3-setuptools_74.1.2-2_all.deb ... Unpacking python3-setuptools (74.1.2-2) ... Selecting previously unselected package dh-python. Preparing to unpack .../079-dh-python_6.20240824_all.deb ... Unpacking dh-python (6.20240824) ... Selecting previously unselected package fonts-lyx. Preparing to unpack .../080-fonts-lyx_2.4.2.1-1_all.deb ... Unpacking fonts-lyx (2.4.2.1-1) ... Selecting previously unselected package libblas3:amd64. Preparing to unpack .../081-libblas3_3.12.0-3_amd64.deb ... Unpacking libblas3:amd64 (3.12.0-3) ... Selecting previously unselected package libdeflate0:amd64. Preparing to unpack .../082-libdeflate0_1.22-1_amd64.deb ... Unpacking libdeflate0:amd64 (1.22-1) ... Selecting previously unselected package libfribidi0:amd64. Preparing to unpack .../083-libfribidi0_1.0.15-1_amd64.deb ... Unpacking libfribidi0:amd64 (1.0.15-1) ... Selecting previously unselected package libgfortran5:amd64. Preparing to unpack .../084-libgfortran5_14.2.0-6_amd64.deb ... Unpacking libgfortran5:amd64 (14.2.0-6) ... Selecting previously unselected package libglib2.0-0t64:amd64. Preparing to unpack .../085-libglib2.0-0t64_2.82.1-1_amd64.deb ... Unpacking libglib2.0-0t64:amd64 (2.82.1-1) ... Selecting previously unselected package libgraphite2-3:amd64. Preparing to unpack .../086-libgraphite2-3_1.3.14-2_amd64.deb ... Unpacking libgraphite2-3:amd64 (1.3.14-2) ... Selecting previously unselected package libharfbuzz0b:amd64. Preparing to unpack .../087-libharfbuzz0b_9.0.0-1_amd64.deb ... Unpacking libharfbuzz0b:amd64 (9.0.0-1) ... Selecting previously unselected package libimagequant0:amd64. Preparing to unpack .../088-libimagequant0_2.18.0-1+b1_amd64.deb ... Unpacking libimagequant0:amd64 (2.18.0-1+b1) ... Selecting previously unselected package libjbig0:amd64. Preparing to unpack .../089-libjbig0_2.1-6.1+b1_amd64.deb ... Unpacking libjbig0:amd64 (2.1-6.1+b1) ... Selecting previously unselected package libjpeg62-turbo:amd64. Preparing to unpack .../090-libjpeg62-turbo_1%3a2.1.5-3_amd64.deb ... Unpacking libjpeg62-turbo:amd64 (1:2.1.5-3) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../091-libjs-jquery_3.6.1+dfsg+~3.5.14-1_all.deb ... Unpacking libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Selecting previously unselected package libjs-jquery-ui. Preparing to unpack .../092-libjs-jquery-ui_1.13.2+dfsg-1_all.deb ... Unpacking libjs-jquery-ui (1.13.2+dfsg-1) ... Selecting previously unselected package liblapack3:amd64. Preparing to unpack .../093-liblapack3_3.12.0-3_amd64.deb ... Unpacking liblapack3:amd64 (3.12.0-3) ... Selecting previously unselected package liblbfgsb0:amd64. Preparing to unpack .../094-liblbfgsb0_3.0+dfsg.4-1+b1_amd64.deb ... Unpacking liblbfgsb0:amd64 (3.0+dfsg.4-1+b1) ... Selecting previously unselected package liblcms2-2:amd64. Preparing to unpack .../095-liblcms2-2_2.14-2+b1_amd64.deb ... Unpacking liblcms2-2:amd64 (2.14-2+b1) ... Selecting previously unselected package liblerc4:amd64. Preparing to unpack .../096-liblerc4_4.0.0+ds-4+b1_amd64.deb ... Unpacking liblerc4:amd64 (4.0.0+ds-4+b1) ... Selecting previously unselected package libopenjp2-7:amd64. Preparing to unpack .../097-libopenjp2-7_2.5.0-2+b3_amd64.deb ... Unpacking libopenjp2-7:amd64 (2.5.0-2+b3) ... Selecting previously unselected package libqhull-r8.0:amd64. Preparing to unpack .../098-libqhull-r8.0_2020.2-6+b1_amd64.deb ... Unpacking libqhull-r8.0:amd64 (2020.2-6+b1) ... Selecting previously unselected package libraqm0:amd64. Preparing to unpack .../099-libraqm0_0.10.1-1+b1_amd64.deb ... Unpacking libraqm0:amd64 (0.10.1-1+b1) ... Selecting previously unselected package libsharpyuv0:amd64. Preparing to unpack .../100-libsharpyuv0_1.4.0-0.1_amd64.deb ... Unpacking libsharpyuv0:amd64 (1.4.0-0.1) ... Selecting previously unselected package libwebp7:amd64. Preparing to unpack .../101-libwebp7_1.4.0-0.1_amd64.deb ... Unpacking libwebp7:amd64 (1.4.0-0.1) ... Selecting previously unselected package libtiff6:amd64. Preparing to unpack .../102-libtiff6_4.5.1+git230720-5_amd64.deb ... Unpacking libtiff6:amd64 (4.5.1+git230720-5) ... Selecting previously unselected package libwebpdemux2:amd64. Preparing to unpack .../103-libwebpdemux2_1.4.0-0.1_amd64.deb ... Unpacking libwebpdemux2:amd64 (1.4.0-0.1) ... Selecting previously unselected package libwebpmux3:amd64. Preparing to unpack .../104-libwebpmux3_1.4.0-0.1_amd64.deb ... Unpacking libwebpmux3:amd64 (1.4.0-0.1) ... Selecting previously unselected package libxslt1.1:amd64. Preparing to unpack .../105-libxslt1.1_1.1.35-1.1_amd64.deb ... Unpacking libxslt1.1:amd64 (1.1.35-1.1) ... Selecting previously unselected package libyaml-0-2:amd64. Preparing to unpack .../106-libyaml-0-2_0.2.5-1+b1_amd64.deb ... Unpacking libyaml-0-2:amd64 (0.2.5-1+b1) ... Selecting previously unselected package python-matplotlib-data. Preparing to unpack .../107-python-matplotlib-data_3.8.3-3_all.deb ... Unpacking python-matplotlib-data (3.8.3-3) ... Selecting previously unselected package python3-all. Preparing to unpack .../108-python3-all_3.12.6-1_amd64.deb ... Unpacking python3-all (3.12.6-1) ... Selecting previously unselected package python3-appdirs. Preparing to unpack .../109-python3-appdirs_1.4.4-4_all.deb ... Unpacking python3-appdirs (1.4.4-4) ... Selecting previously unselected package python3-attr. Preparing to unpack .../110-python3-attr_23.2.0-2_all.deb ... Unpacking python3-attr (23.2.0-2) ... Selecting previously unselected package python3-brotli. Preparing to unpack .../111-python3-brotli_1.1.0-2+b4_amd64.deb ... Unpacking python3-brotli (1.1.0-2+b4) ... Selecting previously unselected package python3-certifi. Preparing to unpack .../112-python3-certifi_2024.8.30+dfsg-1_all.deb ... Unpacking python3-certifi (2024.8.30+dfsg-1) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../113-python3-chardet_5.2.0+dfsg-1_all.deb ... Unpacking python3-chardet (5.2.0+dfsg-1) ... Selecting previously unselected package python3-charset-normalizer. Preparing to unpack .../114-python3-charset-normalizer_3.3.2-4_amd64.deb ... Unpacking python3-charset-normalizer (3.3.2-4) ... Selecting previously unselected package python3-colorama. Preparing to unpack .../115-python3-colorama_0.4.6-4_all.deb ... Unpacking python3-colorama (0.4.6-4) ... Selecting previously unselected package python3-click. Preparing to unpack .../116-python3-click_8.1.7-2_all.deb ... Unpacking python3-click (8.1.7-2) ... Selecting previously unselected package python3-humanfriendly. Preparing to unpack .../117-python3-humanfriendly_10.0-6_all.deb ... Unpacking python3-humanfriendly (10.0-6) ... Selecting previously unselected package python3-coloredlogs. Preparing to unpack .../118-python3-coloredlogs_15.0.1-1_all.deb ... Unpacking python3-coloredlogs (15.0.1-1) ... Selecting previously unselected package python3-networkx. Preparing to unpack .../119-python3-networkx_3.2.1-4_all.deb ... Unpacking python3-networkx (3.2.1-4) ... Selecting previously unselected package python3-numpy. Preparing to unpack .../120-python3-numpy_1%3a1.26.4+ds-11_amd64.deb ... Unpacking python3-numpy (1:1.26.4+ds-11) ... Selecting previously unselected package python3-colormath. Preparing to unpack .../121-python3-colormath_3.0.0-4_all.deb ... Unpacking python3-colormath (3.0.0-4) ... Selecting previously unselected package python3-contourpy. Preparing to unpack .../122-python3-contourpy_1.3.0-2_amd64.deb ... Unpacking python3-contourpy (1.3.0-2) ... Selecting previously unselected package python3-cycler. Preparing to unpack .../123-python3-cycler_0.12.1-1_all.deb ... Unpacking python3-cycler (0.12.1-1) ... Selecting previously unselected package python3-dateutil. Preparing to unpack .../124-python3-dateutil_2.9.0-3_all.deb ... Unpacking python3-dateutil (2.9.0-3) ... Selecting previously unselected package python3-decorator. Preparing to unpack .../125-python3-decorator_5.1.1-5_all.deb ... Unpacking python3-decorator (5.1.1-5) ... Selecting previously unselected package python3-fastjsonschema. Preparing to unpack .../126-python3-fastjsonschema_2.20.0-1_all.deb ... Unpacking python3-fastjsonschema (2.20.0-1) ... Selecting previously unselected package python3-scipy. Preparing to unpack .../127-python3-scipy_1.13.1-5_amd64.deb ... Unpacking python3-scipy (1.13.1-5) ... Selecting previously unselected package python3-ufolib2. Preparing to unpack .../128-python3-ufolib2_0.16.0+dfsg1-1_all.deb ... Unpacking python3-ufolib2 (0.16.0+dfsg1-1) ... Selecting previously unselected package python3-mpmath. Preparing to unpack .../129-python3-mpmath_1.3.0-1_all.deb ... Unpacking python3-mpmath (1.3.0-1) ... Selecting previously unselected package python3-sympy. Preparing to unpack .../130-python3-sympy_1.13.2-1_all.deb ... Unpacking python3-sympy (1.13.2-1) ... Selecting previously unselected package python3-tz. Preparing to unpack .../131-python3-tz_2024.1-2_all.deb ... Unpacking python3-tz (2024.1-2) ... Selecting previously unselected package python3-six. Preparing to unpack .../132-python3-six_1.16.0-7_all.deb ... Unpacking python3-six (1.16.0-7) ... Selecting previously unselected package python3-fs. Preparing to unpack .../133-python3-fs_2.4.16-4_all.deb ... Unpacking python3-fs (2.4.16-4) ... Selecting previously unselected package python3-lxml:amd64. Preparing to unpack .../134-python3-lxml_5.3.0-1_amd64.deb ... Unpacking python3-lxml:amd64 (5.3.0-1) ... Selecting previously unselected package python3-lz4. Preparing to unpack .../135-python3-lz4_4.0.2+dfsg-1+b4_amd64.deb ... Unpacking python3-lz4 (4.0.2+dfsg-1+b4) ... Selecting previously unselected package unicode-data. Preparing to unpack .../136-unicode-data_15.1.0-1_all.deb ... Unpacking unicode-data (15.1.0-1) ... Selecting previously unselected package python3-fonttools. Preparing to unpack .../137-python3-fonttools_4.46.0-1+b1_amd64.deb ... Unpacking python3-fonttools (4.46.0-1+b1) ... Selecting previously unselected package python3-humanize. Preparing to unpack .../138-python3-humanize_4.11.0-1_all.deb ... Unpacking python3-humanize (4.11.0-1) ... Selecting previously unselected package python3-idna. Preparing to unpack .../139-python3-idna_3.8-2_all.deb ... Unpacking python3-idna (3.8-2) ... Selecting previously unselected package python3-markupsafe. Preparing to unpack .../140-python3-markupsafe_2.1.5-1+b1_amd64.deb ... Unpacking python3-markupsafe (2.1.5-1+b1) ... Selecting previously unselected package python3-jinja2. Preparing to unpack .../141-python3-jinja2_3.1.3-1_all.deb ... Unpacking python3-jinja2 (3.1.3-1) ... Selecting previously unselected package python3-rpds-py. Preparing to unpack .../142-python3-rpds-py_0.12.0-3+b1_amd64.deb ... Unpacking python3-rpds-py (0.12.0-3+b1) ... Selecting previously unselected package python3-referencing. Preparing to unpack .../143-python3-referencing_0.35.1-1_all.deb ... Unpacking python3-referencing (0.35.1-1) ... Selecting previously unselected package python3-jsonschema-specifications. Preparing to unpack .../144-python3-jsonschema-specifications_2023.12.1-2_all.deb ... Unpacking python3-jsonschema-specifications (2023.12.1-2) ... Selecting previously unselected package python3-jsonschema. Preparing to unpack .../145-python3-jsonschema_4.19.2-5_all.deb ... Unpacking python3-jsonschema (4.19.2-5) ... Selecting previously unselected package python3-platformdirs. Preparing to unpack .../146-python3-platformdirs_4.3.6-1_all.deb ... Unpacking python3-platformdirs (4.3.6-1) ... Selecting previously unselected package python3-traitlets. Preparing to unpack .../147-python3-traitlets_5.14.3+really5.14.3-1_all.deb ... Unpacking python3-traitlets (5.14.3+really5.14.3-1) ... Selecting previously unselected package python3-jupyter-core. Preparing to unpack .../148-python3-jupyter-core_5.7.2-4_all.deb ... Unpacking python3-jupyter-core (5.7.2-4) ... Selecting previously unselected package python3-kiwisolver. Preparing to unpack .../149-python3-kiwisolver_1.4.7-2_amd64.deb ... Unpacking python3-kiwisolver (1.4.7-2) ... Selecting previously unselected package python3-lzstring. Preparing to unpack .../150-python3-lzstring_1.0.4-3_all.deb ... Unpacking python3-lzstring (1.0.4-3) ... Selecting previously unselected package python3-markdown. Preparing to unpack .../151-python3-markdown_3.7-1_all.deb ... Unpacking python3-markdown (3.7-1) ... Selecting previously unselected package python3-mdurl. Preparing to unpack .../152-python3-mdurl_0.1.2-1_all.deb ... Unpacking python3-mdurl (0.1.2-1) ... Selecting previously unselected package python3-markdown-it. Preparing to unpack .../153-python3-markdown-it_3.0.0-2_all.deb ... Unpacking python3-markdown-it (3.0.0-2) ... Selecting previously unselected package python3-pil:amd64. Preparing to unpack .../154-python3-pil_10.4.0-1_amd64.deb ... Unpacking python3-pil:amd64 (10.4.0-1) ... Selecting previously unselected package python3.12-tk. Preparing to unpack .../155-python3.12-tk_3.12.6-1_amd64.deb ... Unpacking python3.12-tk (3.12.6-1) ... Selecting previously unselected package python3.13-tk. Preparing to unpack .../156-python3.13-tk_3.13.0-1_amd64.deb ... Unpacking python3.13-tk (3.13.0-1) ... Selecting previously unselected package python3-tk:amd64. Preparing to unpack .../157-python3-tk_3.12.6-1_amd64.deb ... Unpacking python3-tk:amd64 (3.12.6-1) ... Selecting previously unselected package python3-pil.imagetk:amd64. Preparing to unpack .../158-python3-pil.imagetk_10.4.0-1_amd64.deb ... Unpacking python3-pil.imagetk:amd64 (10.4.0-1) ... Selecting previously unselected package python3-pyparsing. Preparing to unpack .../159-python3-pyparsing_3.1.2-1_all.deb ... Unpacking python3-pyparsing (3.1.2-1) ... Selecting previously unselected package python3-packaging. Preparing to unpack .../160-python3-packaging_24.1-1_all.deb ... Unpacking python3-packaging (24.1-1) ... Selecting previously unselected package python3-matplotlib. Preparing to unpack .../161-python3-matplotlib_3.8.3-3_amd64.deb ... Unpacking python3-matplotlib (3.8.3-3) ... Selecting previously unselected package python3-nbformat. Preparing to unpack .../162-python3-nbformat_5.9.1-1_all.deb ... Unpacking python3-nbformat (5.9.1-1) ... Selecting previously unselected package python3-urllib3. Preparing to unpack .../163-python3-urllib3_2.0.7-2_all.deb ... Unpacking python3-urllib3 (2.0.7-2) ... Selecting previously unselected package python3-requests. Preparing to unpack .../164-python3-requests_2.32.3+dfsg-1_all.deb ... Unpacking python3-requests (2.32.3+dfsg-1) ... Selecting previously unselected package python3-tenacity. Preparing to unpack .../165-python3-tenacity_8.4.2+really8.4.1-1_all.deb ... Unpacking python3-tenacity (8.4.2+really8.4.1-1) ... Selecting previously unselected package python3-plotly. Preparing to unpack .../166-python3-plotly_5.20.0+dfsg-1_all.deb ... Unpacking python3-plotly (5.20.0+dfsg-1) ... Selecting previously unselected package python3-yaml. Preparing to unpack .../167-python3-yaml_6.0.2-1_amd64.deb ... Unpacking python3-yaml (6.0.2-1) ... Selecting previously unselected package python3-pyaml-env. Preparing to unpack .../168-python3-pyaml-env_1.2.1-2_all.deb ... Unpacking python3-pyaml-env (1.2.1-2) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../169-python3-pygments_2.18.0+dfsg-1_all.deb ... Unpacking python3-pygments (2.18.0+dfsg-1) ... Selecting previously unselected package python3-rich. Preparing to unpack .../170-python3-rich_13.7.1-1_all.deb ... Unpacking python3-rich (13.7.1-1) ... Selecting previously unselected package python3-rich-click. Preparing to unpack .../171-python3-rich-click_1.6.0-1_all.deb ... Unpacking python3-rich-click (1.6.0-1) ... Selecting previously unselected package python3-spectra. Preparing to unpack .../172-python3-spectra_0.0.11-4_all.deb ... Unpacking python3-spectra (0.0.11-4) ... Setting up media-types (10.1.0) ... Setting up libpipeline1:amd64 (1.5.8-1) ... Setting up libgraphite2-3:amd64 (1.3.14-2) ... Setting up liblcms2-2:amd64 (2.14-2+b1) ... Setting up libsharpyuv0:amd64 (1.4.0-0.1) ... Setting up libxau6:amd64 (1:1.0.9-1+b1) ... Setting up libxdmcp6:amd64 (1:1.1.2-3+b1) ... Setting up libkeyutils1:amd64 (1.6.3-3) ... Setting up libxcb1:amd64 (1.17.0-2) ... Setting up libicu72:amd64 (72.1-5) ... Setting up liblerc4:amd64 (4.0.0+ds-4+b1) ... Setting up bsdextrautils (2.40.2-9) ... Setting up libmagic-mgc (1:5.45-3) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libyaml-0-2:amd64 (0.2.5-1+b1) ... Setting up libtirpc-common (1.3.4+ds-1.3) ... Setting up fonts-lyx (2.4.2.1-1) ... Setting up libdebhelper-perl (13.20) ... Setting up libbrotli1:amd64 (1.1.0-2+b4) ... Setting up libsqlite3-0:amd64 (3.46.0-1) ... Setting up libmagic1t64:amd64 (1:5.45-3) ... Setting up x11-common (1:7.7+23.1) ... invoke-rc.d: could not determine current runlevel invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block. Setting up libdeflate0:amd64 (1.22-1) ... Setting up gettext-base (0.22.5-2) ... Setting up m4 (1.4.19-4) ... Setting up libqhull-r8.0:amd64 (2020.2-6+b1) ... Setting up file (1:5.45-3) ... Setting up libjbig0:amd64 (2.1-6.1+b1) ... Setting up libelf1t64:amd64 (0.191-2) ... Setting up libkrb5support0:amd64 (1.21.3-3) ... Setting up unicode-data (15.1.0-1) ... Setting up autotools-dev (20220109.1) ... Setting up libglib2.0-0t64:amd64 (2.82.1-1) ... No schema files found: doing nothing. Setting up libblas3:amd64 (3.12.0-3) ... update-alternatives: using /usr/lib/x86_64-linux-gnu/blas/libblas.so.3 to provide /usr/lib/x86_64-linux-gnu/libblas.so.3 (libblas.so.3-x86_64-linux-gnu) in auto mode Setting up libjpeg62-turbo:amd64 (1:2.1.5-3) ... Setting up libx11-data (2:1.8.7-1) ... Setting up libfribidi0:amd64 (1.0.15-1) ... Setting up libimagequant0:amd64 (2.18.0-1+b1) ... Setting up fonts-dejavu-mono (2.37-8) ... Setting up libpng16-16t64:amd64 (1.6.44-2) ... Setting up libtcl8.6:amd64 (8.6.15+dfsg-2) ... Setting up autopoint (0.22.5-2) ... Setting up fonts-dejavu-core (2.37-8) ... Setting up libncursesw6:amd64 (6.5-2) ... Setting up libk5crypto3:amd64 (1.21.3-3) ... Setting up libgfortran5:amd64 (14.2.0-6) ... Setting up autoconf (2.72-3) ... Setting up libwebp7:amd64 (1.4.0-0.1) ... Setting up dwz (0.15-1+b1) ... Setting up sensible-utils (0.0.24) ... Setting up libtiff6:amd64 (4.5.1+git230720-5) ... Setting up libuchardet0:amd64 (0.0.8-1+b1) ... Setting up libopenjp2-7:amd64 (2.5.0-2+b3) ... Setting up libx11-6:amd64 (2:1.8.7-1+b1) ... Setting up netbase (6.4) ... Setting up libkrb5-3:amd64 (1.21.3-3) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up python-matplotlib-data (3.8.3-3) ... Setting up libwebpmux3:amd64 (1.4.0-0.1) ... Setting up readline-common (8.2-5) ... Setting up libxml2:amd64 (2.12.7+dfsg+really2.9.14-0.1) ... Setting up automake (1:1.16.5-1.3) ... update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode Setting up libfile-stripnondeterminism-perl (1.14.0-1) ... Setting up liblapack3:amd64 (3.12.0-3) ... update-alternatives: using /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3 to provide /usr/lib/x86_64-linux-gnu/liblapack.so.3 (liblapack.so.3-x86_64-linux-gnu) in auto mode Setting up gettext (0.22.5-2) ... Setting up libxrender1:amd64 (1:0.9.10-1.1+b1) ... Setting up libtool (2.4.7-7) ... Setting up fontconfig-config (2.15.0-1.1) ... Setting up libwebpdemux2:amd64 (1.4.0-0.1) ... Setting up libxext6:amd64 (2:1.3.4-1+b2) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up dh-autoreconf (20) ... Setting up libjs-jquery-ui (1.13.2+dfsg-1) ... Setting up libfreetype6:amd64 (2.13.3+dfsg-1) ... Setting up libgssapi-krb5-2:amd64 (1.21.3-3) ... Setting up libreadline8t64:amd64 (8.2-5) ... Setting up dh-strip-nondeterminism (1.14.0-1) ... Setting up groff-base (1.23.0-5) ... Setting up libxslt1.1:amd64 (1.1.35-1.1) ... Setting up libharfbuzz0b:amd64 (9.0.0-1) ... Setting up libxss1:amd64 (1:1.2.3-1+b1) ... Setting up libfontconfig1:amd64 (2.15.0-1.1) ... Setting up liblbfgsb0:amd64 (3.0+dfsg.4-1+b1) ... Setting up libxft2:amd64 (2.3.6-1+b1) ... Setting up libtirpc3t64:amd64 (1.3.4+ds-1.3) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up libtk8.6:amd64 (8.6.15-1) ... Setting up python3.12-tk (3.12.6-1) ... Setting up man-db (2.13.0-1) ... Building database of manual pages ... Setting up python3.13-tk (3.13.0-1) ... Setting up libraqm0:amd64 (0.10.1-1+b1) ... Setting up libnsl2:amd64 (1.3.0-3+b2) ... Setting up tk8.6-blt2.5 (2.5.3+dfsg-7) ... Setting up libpython3.12-stdlib:amd64 (3.12.6-1) ... Setting up blt (2.5.3+dfsg-7) ... Setting up python3.12 (3.12.6-1) ... Setting up debhelper (13.20) ... Setting up libpython3-stdlib:amd64 (3.12.6-1) ... Setting up python3 (3.12.6-1) ... Setting up python3-zipp (3.20.2-1) ... Setting up python3-autocommand (2.2.2-3) ... Setting up python3-markupsafe (2.1.5-1+b1) ... Setting up python3-platformdirs (4.3.6-1) ... Setting up python3-tz (2024.1-2) ... Setting up python3-six (1.16.0-7) ... Setting up python3-pil:amd64 (10.4.0-1) ... Setting up python3-decorator (5.1.1-5) ... Setting up python3-jinja2 (3.1.3-1) ... Setting up python3-packaging (24.1-1) ... Setting up python3-pyparsing (3.1.2-1) ... Setting up python3-humanfriendly (10.0-6) ... Setting up python3-certifi (2024.8.30+dfsg-1) ... Setting up python3-brotli (1.1.0-2+b4) ... Setting up python3-mdurl (0.1.2-1) ... Setting up python3-cycler (0.12.1-1) ... Setting up python3-kiwisolver (1.4.7-2) ... Setting up python3-idna (3.8-2) ... Setting up python3-markdown (3.7-1) ... Setting up python3-typing-extensions (4.12.2-2) ... Setting up python3-urllib3 (2.0.7-2) ... Setting up python3-markdown-it (3.0.0-2) ... Setting up python3-rpds-py (0.12.0-3+b1) ... Setting up python3-fastjsonschema (2.20.0-1) ... Setting up python3-lxml:amd64 (5.3.0-1) ... Setting up python3-traitlets (5.14.3+really5.14.3-1) ... Setting up python3-dateutil (2.9.0-3) ... Setting up python3-mpmath (1.3.0-1) ... Setting up python3-lzstring (1.0.4-3) ... Setting up python3-coloredlogs (15.0.1-1) ... Setting up python3-appdirs (1.4.4-4) ... Setting up python3-jupyter-core (5.7.2-4) ... Setting up python3-more-itertools (10.5.0-1) ... Setting up python3-sympy (1.13.2-1) ... Setting up python3-attr (23.2.0-2) ... Setting up python3-importlib-metadata (8.5.0-1) ... Setting up python3-jaraco.functools (4.1.0-1) ... Setting up python3-jaraco.context (6.0.0-1) ... Setting up python3-colorama (0.4.6-4) ... Setting up python3-lz4 (4.0.2+dfsg-1+b4) ... Setting up python3-charset-normalizer (3.3.2-4) ... Setting up python3-tenacity (8.4.2+really8.4.1-1) ... Setting up python3-typeguard (4.3.0-1) ... Setting up python3-all (3.12.6-1) ... Setting up python3-yaml (6.0.2-1) ... Setting up python3-tk:amd64 (3.12.6-1) ... Setting up python3-click (8.1.7-2) ... Setting up python3-inflect (7.3.1-2) ... Setting up python3-pyaml-env (1.2.1-2) ... /usr/lib/python3/dist-packages/pyaml_env/parse_config.py:58: SyntaxWarning: invalid escape sequence '\w' type_tag_pattern = re.compile(f'({type_tag}\w+\s)') Setting up python3-pil.imagetk:amd64 (10.4.0-1) ... Setting up python3-referencing (0.35.1-1) ... Setting up python3-pkg-resources (74.1.2-2) ... Setting up python3-setuptools (74.1.2-2) ... Setting up python3-networkx (3.2.1-4) ... Setting up python3-fs (2.4.16-4) ... Setting up python3-pygments (2.18.0+dfsg-1) ... Setting up python3-chardet (5.2.0+dfsg-1) ... Setting up python3-requests (2.32.3+dfsg-1) ... Setting up python3-numpy (1:1.26.4+ds-11) ... Setting up python3-colormath (3.0.0-4) ... /usr/lib/python3/dist-packages/colormath/chromatic_adaptation.py:85: SyntaxWarning: invalid escape sequence '\*' logger.debug(" \* Applying adaptation matrix: %s", adaptation) /usr/lib/python3/dist-packages/colormath/color_appearance_models.py:684: SyntaxWarning: invalid escape sequence '\s' """ /usr/lib/python3/dist-packages/colormath/color_appearance_models.py:788: SyntaxWarning: invalid escape sequence '\s' """ /usr/lib/python3/dist-packages/colormath/color_conversions.py:40: SyntaxWarning: invalid escape sequence '\*' logger.debug(" \* Applying RGB conversion matrix: %s->%s", /usr/lib/python3/dist-packages/colormath/color_conversions.py:488: SyntaxWarning: invalid escape sequence '\-' logger.debug(" \- Target RGB space: %s", target_rgb) /usr/lib/python3/dist-packages/colormath/color_conversions.py:490: SyntaxWarning: invalid escape sequence '\-' logger.debug(" \- Target native illuminant: %s", target_illum) /usr/lib/python3/dist-packages/colormath/color_conversions.py:491: SyntaxWarning: invalid escape sequence '\-' logger.debug(" \- XYZ color's illuminant: %s", cobj.illuminant) /usr/lib/python3/dist-packages/colormath/color_conversions.py:497: SyntaxWarning: invalid escape sequence '\*' logger.debug(" \* Applying transformation from %s to %s ", /usr/lib/python3/dist-packages/colormath/color_conversions.py:503: SyntaxWarning: invalid escape sequence '\*' logger.debug(" \* New values: %.3f, %.3f, %.3f", /usr/lib/python3/dist-packages/colormath/color_objects.py:452: SyntaxWarning: invalid escape sequence '\-' logger.debug(" \- Original illuminant: %s", self.illuminant) /usr/lib/python3/dist-packages/colormath/color_objects.py:453: SyntaxWarning: invalid escape sequence '\-' logger.debug(" \- Target illuminant: %s", target_illuminant) /usr/lib/python3/dist-packages/colormath/color_objects.py:459: SyntaxWarning: invalid escape sequence '\*' logger.debug(" \* Applying transformation from %s to %s ", Setting up python3-contourpy (1.3.0-2) ... Setting up python3-humanize (4.11.0-1) ... Setting up python3-jsonschema-specifications (2023.12.1-2) ... Setting up dh-python (6.20240824) ... Setting up python3-scipy (1.13.1-5) ... Setting up python3-spectra (0.0.11-4) ... Setting up python3-rich (13.7.1-1) ... Setting up python3-jsonschema (4.19.2-5) ... Setting up python3-rich-click (1.6.0-1) ... Setting up python3-nbformat (5.9.1-1) ... Setting up python3-plotly (5.20.0+dfsg-1) ... Setting up python3-ufolib2 (0.16.0+dfsg1-1) ... Setting up python3-fonttools (4.46.0-1+b1) ... Setting up python3-matplotlib (3.8.3-3) ... Processing triggers for libc-bin (2.40-3) ... ┌───────────────┐ │ Build │ └───────────────┘ dpkg-buildpackage: info: source package multiqc dpkg-buildpackage: info: source version 1.21+dfsg-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: host architecture amd64  dpkg-source --before-build .  debian/rules clean dh clean --buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory '/srv/build/multiqc-1.21+dfsg' dh_auto_clean I: pybuild base:311: python3.12 setup.py clean running clean removing '/srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build' (and everything under it) 'build/bdist.linux-x86_64' does not exist -- can't clean it 'build/scripts-3.12' does not exist -- can't clean it rm -rf multiqc.egg-info/ make[1]: Leaving directory '/srv/build/multiqc-1.21+dfsg' dh_autoreconf_clean -O--buildsystem=pybuild dh_clean -O--buildsystem=pybuild  debian/rules binary dh binary --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:311: python3.12 setup.py config running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py build running build running build_py creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc copying multiqc/__main__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc copying multiqc/multiqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc copying multiqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc running egg_info creating multiqc.egg-info writing multiqc.egg-info/PKG-INFO writing dependency_links to multiqc.egg-info/dependency_links.txt writing entry points to multiqc.egg-info/entry_points.txt writing requirements to multiqc.egg-info/requires.txt writing top-level names to multiqc.egg-info/top_level.txt writing manifest file 'multiqc.egg-info/SOURCES.txt' reading manifest file 'multiqc.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'multiqc.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules' to be distributed and are already explicitly excluding 'multiqc.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.adapterRemoval' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.adapterRemoval' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.adapterRemoval' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.adapterRemoval' to be distributed and are already explicitly excluding 'multiqc.modules.adapterRemoval' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.afterqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.afterqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.afterqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.afterqc' to be distributed and are already explicitly excluding 'multiqc.modules.afterqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.anglerfish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.anglerfish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.anglerfish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.anglerfish' to be distributed and are already explicitly excluding 'multiqc.modules.anglerfish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bakta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bakta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bakta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bakta' to be distributed and are already explicitly excluding 'multiqc.modules.bakta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bamdst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bamdst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bamdst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bamdst' to be distributed and are already explicitly excluding 'multiqc.modules.bamdst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bamtools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bamtools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bamtools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bamtools' to be distributed and are already explicitly excluding 'multiqc.modules.bamtools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bbduk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bbduk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bbduk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bbduk' to be distributed and are already explicitly excluding 'multiqc.modules.bbduk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bbmap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bbmap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bbmap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bbmap' to be distributed and are already explicitly excluding 'multiqc.modules.bbmap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bcftools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bcftools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bcftools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bcftools' to be distributed and are already explicitly excluding 'multiqc.modules.bcftools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bcl2fastq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bcl2fastq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bcl2fastq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bcl2fastq' to be distributed and are already explicitly excluding 'multiqc.modules.bcl2fastq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bclconvert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bclconvert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bclconvert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bclconvert' to be distributed and are already explicitly excluding 'multiqc.modules.bclconvert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.biobambam2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.biobambam2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.biobambam2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.biobambam2' to be distributed and are already explicitly excluding 'multiqc.modules.biobambam2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.biobloomtools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.biobloomtools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.biobloomtools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.biobloomtools' to be distributed and are already explicitly excluding 'multiqc.modules.biobloomtools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.biscuit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.biscuit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.biscuit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.biscuit' to be distributed and are already explicitly excluding 'multiqc.modules.biscuit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bismark' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bismark' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bismark' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bismark' to be distributed and are already explicitly excluding 'multiqc.modules.bismark' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bowtie1' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bowtie1' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bowtie1' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bowtie1' to be distributed and are already explicitly excluding 'multiqc.modules.bowtie1' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bowtie2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bowtie2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bowtie2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bowtie2' to be distributed and are already explicitly excluding 'multiqc.modules.bowtie2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bracken' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bracken' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bracken' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bracken' to be distributed and are already explicitly excluding 'multiqc.modules.bracken' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.busco' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.busco' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.busco' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.busco' to be distributed and are already explicitly excluding 'multiqc.modules.busco' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bustools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bustools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bustools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bustools' to be distributed and are already explicitly excluding 'multiqc.modules.bustools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.ccs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.ccs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.ccs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.ccs' to be distributed and are already explicitly excluding 'multiqc.modules.ccs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.cellranger' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.cellranger' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.cellranger' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.cellranger' to be distributed and are already explicitly excluding 'multiqc.modules.cellranger' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.checkqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.checkqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.checkqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.checkqc' to be distributed and are already explicitly excluding 'multiqc.modules.checkqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.clipandmerge' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.clipandmerge' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.clipandmerge' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.clipandmerge' to be distributed and are already explicitly excluding 'multiqc.modules.clipandmerge' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.clusterflow' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.clusterflow' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.clusterflow' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.clusterflow' to be distributed and are already explicitly excluding 'multiqc.modules.clusterflow' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.conpair' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.conpair' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.conpair' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.conpair' to be distributed and are already explicitly excluding 'multiqc.modules.conpair' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.custom_content' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.custom_content' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.custom_content' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.custom_content' to be distributed and are already explicitly excluding 'multiqc.modules.custom_content' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.cutadapt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.cutadapt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.cutadapt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.cutadapt' to be distributed and are already explicitly excluding 'multiqc.modules.cutadapt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.damageprofiler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.damageprofiler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.damageprofiler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.damageprofiler' to be distributed and are already explicitly excluding 'multiqc.modules.damageprofiler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.dedup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.dedup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.dedup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.dedup' to be distributed and are already explicitly excluding 'multiqc.modules.dedup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.deeptools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.deeptools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.deeptools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.deeptools' to be distributed and are already explicitly excluding 'multiqc.modules.deeptools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.diamond' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.diamond' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.diamond' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.diamond' to be distributed and are already explicitly excluding 'multiqc.modules.diamond' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.disambiguate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.disambiguate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.disambiguate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.disambiguate' to be distributed and are already explicitly excluding 'multiqc.modules.disambiguate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.dragen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.dragen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.dragen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.dragen' to be distributed and are already explicitly excluding 'multiqc.modules.dragen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.dragen_fastqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.dragen_fastqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.dragen_fastqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.dragen_fastqc' to be distributed and are already explicitly excluding 'multiqc.modules.dragen_fastqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.dragen_fastqc.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.dragen_fastqc.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.dragen_fastqc.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.dragen_fastqc.assets.js' to be distributed and are already explicitly excluding 'multiqc.modules.dragen_fastqc.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.eigenstratdatabasetools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.eigenstratdatabasetools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.eigenstratdatabasetools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.eigenstratdatabasetools' to be distributed and are already explicitly excluding 'multiqc.modules.eigenstratdatabasetools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastp' to be distributed and are already explicitly excluding 'multiqc.modules.fastp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastq_screen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastq_screen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastq_screen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastq_screen' to be distributed and are already explicitly excluding 'multiqc.modules.fastq_screen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastqc' to be distributed and are already explicitly excluding 'multiqc.modules.fastqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastqc.assets.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastqc.assets.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastqc.assets.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastqc.assets.css' to be distributed and are already explicitly excluding 'multiqc.modules.fastqc.assets.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastqc.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastqc.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastqc.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastqc.assets.js' to be distributed and are already explicitly excluding 'multiqc.modules.fastqc.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastqc.fastqc_theoretical_gc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastqc.fastqc_theoretical_gc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastqc.fastqc_theoretical_gc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastqc.fastqc_theoretical_gc' to be distributed and are already explicitly excluding 'multiqc.modules.fastqc.fastqc_theoretical_gc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.featureCounts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.featureCounts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.featureCounts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.featureCounts' to be distributed and are already explicitly excluding 'multiqc.modules.featureCounts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fgbio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fgbio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fgbio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fgbio' to be distributed and are already explicitly excluding 'multiqc.modules.fgbio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.filtlong' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.filtlong' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.filtlong' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.filtlong' to be distributed and are already explicitly excluding 'multiqc.modules.filtlong' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.flash' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.flash' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.flash' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.flash' to be distributed and are already explicitly excluding 'multiqc.modules.flash' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.flexbar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.flexbar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.flexbar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.flexbar' to be distributed and are already explicitly excluding 'multiqc.modules.flexbar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.freyja' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.freyja' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.freyja' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.freyja' to be distributed and are already explicitly excluding 'multiqc.modules.freyja' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.gatk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.gatk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.gatk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.gatk' to be distributed and are already explicitly excluding 'multiqc.modules.gatk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.gffcompare' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.gffcompare' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.gffcompare' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.gffcompare' to be distributed and are already explicitly excluding 'multiqc.modules.gffcompare' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.goleft_indexcov' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.goleft_indexcov' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.goleft_indexcov' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.goleft_indexcov' to be distributed and are already explicitly excluding 'multiqc.modules.goleft_indexcov' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.gopeaks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.gopeaks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.gopeaks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.gopeaks' to be distributed and are already explicitly excluding 'multiqc.modules.gopeaks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.happy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.happy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.happy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.happy' to be distributed and are already explicitly excluding 'multiqc.modules.happy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hicexplorer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hicexplorer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hicexplorer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hicexplorer' to be distributed and are already explicitly excluding 'multiqc.modules.hicexplorer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hicpro' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hicpro' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hicpro' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hicpro' to be distributed and are already explicitly excluding 'multiqc.modules.hicpro' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hicup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hicup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hicup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hicup' to be distributed and are already explicitly excluding 'multiqc.modules.hicup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hifiasm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hifiasm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hifiasm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hifiasm' to be distributed and are already explicitly excluding 'multiqc.modules.hifiasm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hisat2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hisat2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hisat2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hisat2' to be distributed and are already explicitly excluding 'multiqc.modules.hisat2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.homer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.homer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.homer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.homer' to be distributed and are already explicitly excluding 'multiqc.modules.homer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hops' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hops' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hops' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hops' to be distributed and are already explicitly excluding 'multiqc.modules.hops' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.htseq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.htseq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.htseq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.htseq' to be distributed and are already explicitly excluding 'multiqc.modules.htseq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.humid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.humid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.humid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.humid' to be distributed and are already explicitly excluding 'multiqc.modules.humid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.interop' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.interop' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.interop' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.interop' to be distributed and are already explicitly excluding 'multiqc.modules.interop' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.isoseq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.isoseq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.isoseq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.isoseq' to be distributed and are already explicitly excluding 'multiqc.modules.isoseq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.ivar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.ivar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.ivar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.ivar' to be distributed and are already explicitly excluding 'multiqc.modules.ivar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.jcvi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.jcvi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.jcvi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.jcvi' to be distributed and are already explicitly excluding 'multiqc.modules.jcvi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.jellyfish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.jellyfish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.jellyfish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.jellyfish' to be distributed and are already explicitly excluding 'multiqc.modules.jellyfish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.kaiju' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.kaiju' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.kaiju' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.kaiju' to be distributed and are already explicitly excluding 'multiqc.modules.kaiju' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.kallisto' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.kallisto' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.kallisto' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.kallisto' to be distributed and are already explicitly excluding 'multiqc.modules.kallisto' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.kat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.kat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.kat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.kat' to be distributed and are already explicitly excluding 'multiqc.modules.kat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.kraken' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.kraken' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.kraken' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.kraken' to be distributed and are already explicitly excluding 'multiqc.modules.kraken' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.leehom' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.leehom' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.leehom' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.leehom' to be distributed and are already explicitly excluding 'multiqc.modules.leehom' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.librarian' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.librarian' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.librarian' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.librarian' to be distributed and are already explicitly excluding 'multiqc.modules.librarian' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.lima' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.lima' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.lima' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.lima' to be distributed and are already explicitly excluding 'multiqc.modules.lima' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.longranger' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.longranger' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.longranger' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.longranger' to be distributed and are already explicitly excluding 'multiqc.modules.longranger' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.macs2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.macs2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.macs2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.macs2' to be distributed and are already explicitly excluding 'multiqc.modules.macs2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.malt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.malt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.malt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.malt' to be distributed and are already explicitly excluding 'multiqc.modules.malt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mapdamage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mapdamage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mapdamage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mapdamage' to be distributed and are already explicitly excluding 'multiqc.modules.mapdamage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.megahit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.megahit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.megahit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.megahit' to be distributed and are already explicitly excluding 'multiqc.modules.megahit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.metaphlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.metaphlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.metaphlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.metaphlan' to be distributed and are already explicitly excluding 'multiqc.modules.metaphlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.methylqa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.methylqa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.methylqa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.methylqa' to be distributed and are already explicitly excluding 'multiqc.modules.methylqa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.minionqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.minionqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.minionqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.minionqc' to be distributed and are already explicitly excluding 'multiqc.modules.minionqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mirtop' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mirtop' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mirtop' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mirtop' to be distributed and are already explicitly excluding 'multiqc.modules.mirtop' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mirtrace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mirtrace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mirtrace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mirtrace' to be distributed and are already explicitly excluding 'multiqc.modules.mirtrace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mosdepth' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mosdepth' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mosdepth' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mosdepth' to be distributed and are already explicitly excluding 'multiqc.modules.mosdepth' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.motus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.motus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.motus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.motus' to be distributed and are already explicitly excluding 'multiqc.modules.motus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mtnucratio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mtnucratio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mtnucratio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mtnucratio' to be distributed and are already explicitly excluding 'multiqc.modules.mtnucratio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.multivcfanalyzer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.multivcfanalyzer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.multivcfanalyzer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.multivcfanalyzer' to be distributed and are already explicitly excluding 'multiqc.modules.multivcfanalyzer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.nanostat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.nanostat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.nanostat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.nanostat' to be distributed and are already explicitly excluding 'multiqc.modules.nanostat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.nextclade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.nextclade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.nextclade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.nextclade' to be distributed and are already explicitly excluding 'multiqc.modules.nextclade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.ngsderive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.ngsderive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.ngsderive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.ngsderive' to be distributed and are already explicitly excluding 'multiqc.modules.ngsderive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.nonpareil' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.nonpareil' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.nonpareil' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.nonpareil' to be distributed and are already explicitly excluding 'multiqc.modules.nonpareil' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.odgi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.odgi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.odgi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.odgi' to be distributed and are already explicitly excluding 'multiqc.modules.odgi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.optitype' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.optitype' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.optitype' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.optitype' to be distributed and are already explicitly excluding 'multiqc.modules.optitype' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.pangolin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.pangolin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.pangolin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.pangolin' to be distributed and are already explicitly excluding 'multiqc.modules.pangolin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.pbmarkdup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.pbmarkdup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.pbmarkdup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.pbmarkdup' to be distributed and are already explicitly excluding 'multiqc.modules.pbmarkdup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.peddy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.peddy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.peddy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.peddy' to be distributed and are already explicitly excluding 'multiqc.modules.peddy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.phantompeakqualtools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.phantompeakqualtools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.phantompeakqualtools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.phantompeakqualtools' to be distributed and are already explicitly excluding 'multiqc.modules.phantompeakqualtools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.picard' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.picard' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.picard' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.picard' to be distributed and are already explicitly excluding 'multiqc.modules.picard' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.porechop' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.porechop' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.porechop' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.porechop' to be distributed and are already explicitly excluding 'multiqc.modules.porechop' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.preseq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.preseq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.preseq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.preseq' to be distributed and are already explicitly excluding 'multiqc.modules.preseq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.prinseqplusplus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.prinseqplusplus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.prinseqplusplus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.prinseqplusplus' to be distributed and are already explicitly excluding 'multiqc.modules.prinseqplusplus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.prokka' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.prokka' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.prokka' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.prokka' to be distributed and are already explicitly excluding 'multiqc.modules.prokka' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.purple' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.purple' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.purple' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.purple' to be distributed and are already explicitly excluding 'multiqc.modules.purple' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.pychopper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.pychopper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.pychopper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.pychopper' to be distributed and are already explicitly excluding 'multiqc.modules.pychopper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.pycoqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.pycoqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.pycoqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.pycoqc' to be distributed and are already explicitly excluding 'multiqc.modules.pycoqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.qc3C' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.qc3C' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.qc3C' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.qc3C' to be distributed and are already explicitly excluding 'multiqc.modules.qc3C' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.qorts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.qorts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.qorts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.qorts' to be distributed and are already explicitly excluding 'multiqc.modules.qorts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.qualimap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.qualimap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.qualimap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.qualimap' to be distributed and are already explicitly excluding 'multiqc.modules.qualimap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.quast' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.quast' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.quast' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.quast' to be distributed and are already explicitly excluding 'multiqc.modules.quast' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rna_seqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rna_seqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rna_seqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rna_seqc' to be distributed and are already explicitly excluding 'multiqc.modules.rna_seqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rockhopper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rockhopper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rockhopper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rockhopper' to be distributed and are already explicitly excluding 'multiqc.modules.rockhopper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rsem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rsem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rsem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rsem' to be distributed and are already explicitly excluding 'multiqc.modules.rsem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rseqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rseqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rseqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rseqc' to be distributed and are already explicitly excluding 'multiqc.modules.rseqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rseqc.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rseqc.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rseqc.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rseqc.assets.js' to be distributed and are already explicitly excluding 'multiqc.modules.rseqc.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.salmon' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.salmon' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.salmon' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.salmon' to be distributed and are already explicitly excluding 'multiqc.modules.salmon' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sambamba' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sambamba' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sambamba' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sambamba' to be distributed and are already explicitly excluding 'multiqc.modules.sambamba' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.samblaster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.samblaster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.samblaster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.samblaster' to be distributed and are already explicitly excluding 'multiqc.modules.samblaster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.samtools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.samtools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.samtools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.samtools' to be distributed and are already explicitly excluding 'multiqc.modules.samtools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sargasso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sargasso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sargasso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sargasso' to be distributed and are already explicitly excluding 'multiqc.modules.sargasso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.seqera_cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.seqera_cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.seqera_cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.seqera_cli' to be distributed and are already explicitly excluding 'multiqc.modules.seqera_cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.seqwho' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.seqwho' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.seqwho' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.seqwho' to be distributed and are already explicitly excluding 'multiqc.modules.seqwho' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.seqyclean' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.seqyclean' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.seqyclean' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.seqyclean' to be distributed and are already explicitly excluding 'multiqc.modules.seqyclean' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sexdeterrmine' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sexdeterrmine' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sexdeterrmine' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sexdeterrmine' to be distributed and are already explicitly excluding 'multiqc.modules.sexdeterrmine' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sickle' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sickle' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sickle' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sickle' to be distributed and are already explicitly excluding 'multiqc.modules.sickle' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.skewer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.skewer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.skewer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.skewer' to be distributed and are already explicitly excluding 'multiqc.modules.skewer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.slamdunk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.slamdunk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.slamdunk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.slamdunk' to be distributed and are already explicitly excluding 'multiqc.modules.slamdunk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.snippy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.snippy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.snippy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.snippy' to be distributed and are already explicitly excluding 'multiqc.modules.snippy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.snpeff' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.snpeff' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.snpeff' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.snpeff' to be distributed and are already explicitly excluding 'multiqc.modules.snpeff' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.snpsplit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.snpsplit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.snpsplit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.snpsplit' to be distributed and are already explicitly excluding 'multiqc.modules.snpsplit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.somalier' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.somalier' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.somalier' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.somalier' to be distributed and are already explicitly excluding 'multiqc.modules.somalier' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sortmerna' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sortmerna' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sortmerna' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sortmerna' to be distributed and are already explicitly excluding 'multiqc.modules.sortmerna' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sourmash' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sourmash' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sourmash' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sourmash' to be distributed and are already explicitly excluding 'multiqc.modules.sourmash' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.spaceranger' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.spaceranger' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.spaceranger' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.spaceranger' to be distributed and are already explicitly excluding 'multiqc.modules.spaceranger' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.stacks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.stacks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.stacks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.stacks' to be distributed and are already explicitly excluding 'multiqc.modules.stacks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.star' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.star' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.star' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.star' to be distributed and are already explicitly excluding 'multiqc.modules.star' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.supernova' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.supernova' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.supernova' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.supernova' to be distributed and are already explicitly excluding 'multiqc.modules.supernova' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.theta2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.theta2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.theta2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.theta2' to be distributed and are already explicitly excluding 'multiqc.modules.theta2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.tophat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.tophat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.tophat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.tophat' to be distributed and are already explicitly excluding 'multiqc.modules.tophat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.trimmomatic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.trimmomatic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.trimmomatic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.trimmomatic' to be distributed and are already explicitly excluding 'multiqc.modules.trimmomatic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.truvari' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.truvari' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.truvari' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.truvari' to be distributed and are already explicitly excluding 'multiqc.modules.truvari' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.umitools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.umitools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.umitools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.umitools' to be distributed and are already explicitly excluding 'multiqc.modules.umitools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.varscan2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.varscan2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.varscan2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.varscan2' to be distributed and are already explicitly excluding 'multiqc.modules.varscan2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.vcftools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.vcftools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.vcftools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.vcftools' to be distributed and are already explicitly excluding 'multiqc.modules.vcftools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.vep' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.vep' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.vep' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.vep' to be distributed and are already explicitly excluding 'multiqc.modules.vep' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.verifybamid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.verifybamid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.verifybamid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.verifybamid' to be distributed and are already explicitly excluding 'multiqc.modules.verifybamid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.whatshap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.whatshap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.whatshap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.whatshap' to be distributed and are already explicitly excluding 'multiqc.modules.whatshap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.xengsort' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.xengsort' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.xengsort' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.xengsort' to be distributed and are already explicitly excluding 'multiqc.modules.xengsort' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.xenome' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.xenome' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.xenome' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.xenome' to be distributed and are already explicitly excluding 'multiqc.modules.xenome' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.plots' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.plots' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.plots' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.plots' to be distributed and are already explicitly excluding 'multiqc.plots' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.plots.plotly' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.plots.plotly' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.plots.plotly' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.plots.plotly' to be distributed and are already explicitly excluding 'multiqc.plots.plotly' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates' to be distributed and are already explicitly excluding 'multiqc.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default' to be distributed and are already explicitly excluding 'multiqc.templates.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default.assets.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default.assets.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default.assets.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default.assets.css' to be distributed and are already explicitly excluding 'multiqc.templates.default.assets.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default.assets.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default.assets.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default.assets.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default.assets.img' to be distributed and are already explicitly excluding 'multiqc.templates.default.assets.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default.assets.js' to be distributed and are already explicitly excluding 'multiqc.templates.default.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default.assets.js.plots' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default.assets.js.plots' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default.assets.js.plots' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default.assets.js.plots' to be distributed and are already explicitly excluding 'multiqc.templates.default.assets.js.plots' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.gathered' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.gathered' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.gathered' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.gathered' to be distributed and are already explicitly excluding 'multiqc.templates.gathered' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.geo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.geo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.geo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.geo' to be distributed and are already explicitly excluding 'multiqc.templates.geo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.geo.assets.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.geo.assets.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.geo.assets.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.geo.assets.img' to be distributed and are already explicitly excluding 'multiqc.templates.geo.assets.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.highcharts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.highcharts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.highcharts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.highcharts' to be distributed and are already explicitly excluding 'multiqc.templates.highcharts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.highcharts.assets.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.highcharts.assets.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.highcharts.assets.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.highcharts.assets.css' to be distributed and are already explicitly excluding 'multiqc.templates.highcharts.assets.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.highcharts.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.highcharts.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.highcharts.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.highcharts.assets.js' to be distributed and are already explicitly excluding 'multiqc.templates.highcharts.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.highcharts.plots' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.highcharts.plots' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.highcharts.plots' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.highcharts.plots' to be distributed and are already explicitly excluding 'multiqc.templates.highcharts.plots' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.sections' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.sections' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.sections' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.sections' to be distributed and are already explicitly excluding 'multiqc.templates.sections' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.simple' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.simple' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.simple' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.simple' to be distributed and are already explicitly excluding 'multiqc.templates.simple' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.utils' to be distributed and are already explicitly excluding 'multiqc.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules copying multiqc/modules/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules copying multiqc/modules/base_module.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules copying multiqc/modules/profile_runtime.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules copying multiqc/modules/software_versions.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/adapterRemoval copying multiqc/modules/adapterRemoval/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/adapterRemoval copying multiqc/modules/adapterRemoval/adapterRemoval.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/adapterRemoval creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/afterqc copying multiqc/modules/afterqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/afterqc copying multiqc/modules/afterqc/afterqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/afterqc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/anglerfish copying multiqc/modules/anglerfish/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/anglerfish copying multiqc/modules/anglerfish/anglerfish.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/anglerfish creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bakta copying multiqc/modules/bakta/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bakta copying multiqc/modules/bakta/bakta.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bakta creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamdst copying multiqc/modules/bamdst/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamdst copying multiqc/modules/bamdst/bamdst.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamdst creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools copying multiqc/modules/bamtools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools copying multiqc/modules/bamtools/bamtools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools copying multiqc/modules/bamtools/stats.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbduk copying multiqc/modules/bbduk/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbduk copying multiqc/modules/bbduk/bbduk.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbduk creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/bbmap.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/bbmap_filetypes.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_aqhist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_basic_hist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_bhist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_bqhist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_covhist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_idhist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_ihist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_indelhist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_mhist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_qahist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_qchist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap copying multiqc/modules/bbmap/plot_qhist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools copying multiqc/modules/bcftools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools copying multiqc/modules/bcftools/bcftools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools copying multiqc/modules/bcftools/stats.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcl2fastq copying multiqc/modules/bcl2fastq/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcl2fastq copying multiqc/modules/bcl2fastq/bcl2fastq.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcl2fastq creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bclconvert copying multiqc/modules/bclconvert/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bclconvert copying multiqc/modules/bclconvert/bclconvert.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bclconvert creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobambam2 copying multiqc/modules/biobambam2/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobambam2 copying multiqc/modules/biobambam2/biobambam2.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobambam2 creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobloomtools copying multiqc/modules/biobloomtools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobloomtools copying multiqc/modules/biobloomtools/biobloomtools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobloomtools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biscuit copying multiqc/modules/biscuit/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biscuit copying multiqc/modules/biscuit/biscuit.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biscuit creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bismark copying multiqc/modules/bismark/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bismark copying multiqc/modules/bismark/bismark.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bismark creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie1 copying multiqc/modules/bowtie1/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie1 copying multiqc/modules/bowtie1/bowtie1.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie1 creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie2 copying multiqc/modules/bowtie2/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie2 copying multiqc/modules/bowtie2/bowtie2.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie2 creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bracken copying multiqc/modules/bracken/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bracken copying multiqc/modules/bracken/bracken.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bracken creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/busco copying multiqc/modules/busco/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/busco copying multiqc/modules/busco/busco.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/busco creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bustools copying multiqc/modules/bustools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bustools copying multiqc/modules/bustools/bustools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bustools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ccs copying multiqc/modules/ccs/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ccs copying multiqc/modules/ccs/ccs.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ccs creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger copying multiqc/modules/cellranger/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger copying multiqc/modules/cellranger/cellranger.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger copying multiqc/modules/cellranger/count.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger copying multiqc/modules/cellranger/utils.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger copying multiqc/modules/cellranger/vdj.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/checkqc copying multiqc/modules/checkqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/checkqc copying multiqc/modules/checkqc/checkqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/checkqc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clipandmerge copying multiqc/modules/clipandmerge/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clipandmerge copying multiqc/modules/clipandmerge/clipandmerge.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clipandmerge creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clusterflow copying multiqc/modules/clusterflow/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clusterflow copying multiqc/modules/clusterflow/clusterflow.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clusterflow creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/conpair copying multiqc/modules/conpair/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/conpair copying multiqc/modules/conpair/conpair.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/conpair creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/custom_content copying multiqc/modules/custom_content/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/custom_content copying multiqc/modules/custom_content/custom_content.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/custom_content creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cutadapt copying multiqc/modules/cutadapt/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cutadapt copying multiqc/modules/cutadapt/cutadapt.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cutadapt creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/damageprofiler copying multiqc/modules/damageprofiler/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/damageprofiler copying multiqc/modules/damageprofiler/damageprofiler.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/damageprofiler creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dedup copying multiqc/modules/dedup/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dedup copying multiqc/modules/dedup/dedup.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dedup creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/bamPEFragmentSizeDistribution.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/bamPEFragmentSizeTable.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/deeptools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/estimateReadFiltering.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/plotCorrelation.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/plotCoverage.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/plotEnrichment.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/plotFingerprint.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/plotPCA.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools copying multiqc/modules/deeptools/plotProfile.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/diamond copying multiqc/modules/diamond/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/diamond copying multiqc/modules/diamond/diamond.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/diamond creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/disambiguate copying multiqc/modules/disambiguate/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/disambiguate copying multiqc/modules/disambiguate/disambiguate.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/disambiguate creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/coverage_hist.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/coverage_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/coverage_per_contig.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/dragen.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/dragen_gc_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/fragment_length.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/mapping_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/overall_mean_cov.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/ploidy_estimation_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/rna_quant_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/rna_transcript_cov.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/sc_atac_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/sc_rna_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/time_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/trimmer_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/utils.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen copying multiqc/modules/dragen/vc_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc copying multiqc/modules/dragen_fastqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc copying multiqc/modules/dragen_fastqc/base_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc copying multiqc/modules/dragen_fastqc/content_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc copying multiqc/modules/dragen_fastqc/dragen_fastqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc copying multiqc/modules/dragen_fastqc/gc_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc copying multiqc/modules/dragen_fastqc/read_metrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc copying multiqc/modules/dragen_fastqc/util.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/assets creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/assets/js copying multiqc/modules/dragen_fastqc/assets/js/multiqc_dragen_fastqc.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/assets/js creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/eigenstratdatabasetools copying multiqc/modules/eigenstratdatabasetools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/eigenstratdatabasetools copying multiqc/modules/eigenstratdatabasetools/eigenstratdatabasetools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/eigenstratdatabasetools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastp copying multiqc/modules/fastp/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastp copying multiqc/modules/fastp/fastp.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastp creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastq_screen copying multiqc/modules/fastq_screen/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastq_screen copying multiqc/modules/fastq_screen/fastq_screen.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastq_screen creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc copying multiqc/modules/fastqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc copying multiqc/modules/fastqc/fastqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/assets creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/assets/css copying multiqc/modules/fastqc/assets/css/multiqc_fastqc.css -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/assets/css creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/assets/js copying multiqc/modules/fastqc/assets/js/multiqc_fastqc.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/assets/js creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc copying multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_genome.txt -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc copying multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_txome.txt -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc copying multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_genome.txt -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc copying multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_txome.txt -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/featureCounts copying multiqc/modules/featureCounts/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/featureCounts copying multiqc/modules/featureCounts/feature_counts.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/featureCounts creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio copying multiqc/modules/fgbio/ErrorRateByReadPosition.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio copying multiqc/modules/fgbio/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio copying multiqc/modules/fgbio/fgbio.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio copying multiqc/modules/fgbio/groupreadsbyumi.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/filtlong copying multiqc/modules/filtlong/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/filtlong copying multiqc/modules/filtlong/filtlong.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/filtlong creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flash copying multiqc/modules/flash/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flash copying multiqc/modules/flash/flash.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flash creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flexbar copying multiqc/modules/flexbar/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flexbar copying multiqc/modules/flexbar/flexbar.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flexbar creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/freyja copying multiqc/modules/freyja/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/freyja copying multiqc/modules/freyja/freyja.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/freyja creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk copying multiqc/modules/gatk/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk copying multiqc/modules/gatk/analyze_saturation_mutagenesis.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk copying multiqc/modules/gatk/base_recalibrator.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk copying multiqc/modules/gatk/gatk.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk copying multiqc/modules/gatk/varianteval.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gffcompare copying multiqc/modules/gffcompare/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gffcompare copying multiqc/modules/gffcompare/gffcompare.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gffcompare creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/goleft_indexcov copying multiqc/modules/goleft_indexcov/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/goleft_indexcov copying multiqc/modules/goleft_indexcov/goleft_indexcov.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/goleft_indexcov creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gopeaks copying multiqc/modules/gopeaks/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gopeaks copying multiqc/modules/gopeaks/gopeaks.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gopeaks creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/happy copying multiqc/modules/happy/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/happy copying multiqc/modules/happy/happy.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/happy creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicexplorer copying multiqc/modules/hicexplorer/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicexplorer copying multiqc/modules/hicexplorer/hicexplorer.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicexplorer creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicpro copying multiqc/modules/hicpro/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicpro copying multiqc/modules/hicpro/hicpro.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicpro creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicup copying multiqc/modules/hicup/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicup copying multiqc/modules/hicup/hicup.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicup creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hifiasm copying multiqc/modules/hifiasm/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hifiasm copying multiqc/modules/hifiasm/hifiasm.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hifiasm creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hisat2 copying multiqc/modules/hisat2/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hisat2 copying multiqc/modules/hisat2/hisat2.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hisat2 creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer copying multiqc/modules/homer/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer copying multiqc/modules/homer/findpeaks.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer copying multiqc/modules/homer/homer.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer copying multiqc/modules/homer/tagdirectory.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hops copying multiqc/modules/hops/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hops copying multiqc/modules/hops/hops.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hops creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/htseq copying multiqc/modules/htseq/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/htseq copying multiqc/modules/htseq/htseq.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/htseq creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid copying multiqc/modules/humid/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid copying multiqc/modules/humid/clusters.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid copying multiqc/modules/humid/counts.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid copying multiqc/modules/humid/humid.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid copying multiqc/modules/humid/neighbours.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid copying multiqc/modules/humid/stats.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/interop copying multiqc/modules/interop/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/interop copying multiqc/modules/interop/interop.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/interop creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/isoseq copying multiqc/modules/isoseq/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/isoseq copying multiqc/modules/isoseq/isoseq.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/isoseq creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ivar copying multiqc/modules/ivar/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ivar copying multiqc/modules/ivar/ivar.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ivar creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jcvi copying multiqc/modules/jcvi/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jcvi copying multiqc/modules/jcvi/jcvi.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jcvi creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jellyfish copying multiqc/modules/jellyfish/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jellyfish copying multiqc/modules/jellyfish/jellyfish.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jellyfish creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kaiju copying multiqc/modules/kaiju/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kaiju copying multiqc/modules/kaiju/kaiju.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kaiju creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kallisto copying multiqc/modules/kallisto/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kallisto copying multiqc/modules/kallisto/kallisto.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kallisto creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kat copying multiqc/modules/kat/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kat copying multiqc/modules/kat/kat.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kat creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kraken copying multiqc/modules/kraken/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kraken copying multiqc/modules/kraken/kraken.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kraken creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/leehom copying multiqc/modules/leehom/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/leehom copying multiqc/modules/leehom/leehom.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/leehom creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/librarian copying multiqc/modules/librarian/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/librarian copying multiqc/modules/librarian/librarian.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/librarian creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/lima copying multiqc/modules/lima/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/lima copying multiqc/modules/lima/lima.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/lima creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/longranger copying multiqc/modules/longranger/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/longranger copying multiqc/modules/longranger/longranger.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/longranger creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/macs2 copying multiqc/modules/macs2/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/macs2 copying multiqc/modules/macs2/macs2.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/macs2 creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/malt copying multiqc/modules/malt/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/malt copying multiqc/modules/malt/malt.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/malt creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mapdamage copying multiqc/modules/mapdamage/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mapdamage copying multiqc/modules/mapdamage/mapdamage.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mapdamage creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/megahit copying multiqc/modules/megahit/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/megahit copying multiqc/modules/megahit/megahit.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/megahit creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/metaphlan copying multiqc/modules/metaphlan/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/metaphlan copying multiqc/modules/metaphlan/metaphlan.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/metaphlan creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/methylqa copying multiqc/modules/methylqa/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/methylqa copying multiqc/modules/methylqa/methylqa.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/methylqa creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/minionqc copying multiqc/modules/minionqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/minionqc copying multiqc/modules/minionqc/minionqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/minionqc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtop copying multiqc/modules/mirtop/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtop copying multiqc/modules/mirtop/mirtop.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtop creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtrace copying multiqc/modules/mirtrace/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtrace copying multiqc/modules/mirtrace/mirtrace.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtrace creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mosdepth copying multiqc/modules/mosdepth/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mosdepth copying multiqc/modules/mosdepth/mosdepth.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mosdepth creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/motus copying multiqc/modules/motus/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/motus copying multiqc/modules/motus/motus.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/motus creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mtnucratio copying multiqc/modules/mtnucratio/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mtnucratio copying multiqc/modules/mtnucratio/mtnucratio.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mtnucratio creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/multivcfanalyzer copying multiqc/modules/multivcfanalyzer/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/multivcfanalyzer copying multiqc/modules/multivcfanalyzer/multivcfanalyzer.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/multivcfanalyzer creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nanostat copying multiqc/modules/nanostat/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nanostat copying multiqc/modules/nanostat/nanostat.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nanostat creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nextclade copying multiqc/modules/nextclade/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nextclade copying multiqc/modules/nextclade/nextclade.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nextclade creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ngsderive copying multiqc/modules/ngsderive/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ngsderive copying multiqc/modules/ngsderive/ngsderive.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ngsderive creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nonpareil copying multiqc/modules/nonpareil/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nonpareil copying multiqc/modules/nonpareil/nonpareil.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nonpareil creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/odgi copying multiqc/modules/odgi/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/odgi copying multiqc/modules/odgi/odgi.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/odgi creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/optitype copying multiqc/modules/optitype/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/optitype copying multiqc/modules/optitype/optitype.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/optitype creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pangolin copying multiqc/modules/pangolin/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pangolin copying multiqc/modules/pangolin/pangolin.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pangolin creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pbmarkdup copying multiqc/modules/pbmarkdup/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pbmarkdup copying multiqc/modules/pbmarkdup/pbmarkdup.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pbmarkdup creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/peddy copying multiqc/modules/peddy/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/peddy copying multiqc/modules/peddy/peddy.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/peddy creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/phantompeakqualtools copying multiqc/modules/phantompeakqualtools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/phantompeakqualtools copying multiqc/modules/phantompeakqualtools/phantompeakqualtools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/phantompeakqualtools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/AlignmentSummaryMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/BaseDistributionByCycleMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/CrosscheckFingerprints.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/ExtractIlluminaBarcodes.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/GcBiasMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/HsMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/IlluminaBasecallingMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/IlluminaLaneMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/InsertSizeMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/MarkDuplicates.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/MarkIlluminaAdapters.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/OxoGMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/QualityByCycleMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/QualityScoreDistributionMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/QualityYieldMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/RnaSeqMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/RrbsSummaryMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/TargetedPcrMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/ValidateSamFile.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/VariantCallingMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/WgsMetrics.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/picard.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard copying multiqc/modules/picard/util.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/porechop copying multiqc/modules/porechop/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/porechop copying multiqc/modules/porechop/porechop.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/porechop creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/preseq copying multiqc/modules/preseq/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/preseq copying multiqc/modules/preseq/preseq.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/preseq creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prinseqplusplus copying multiqc/modules/prinseqplusplus/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prinseqplusplus copying multiqc/modules/prinseqplusplus/prinseqplusplus.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prinseqplusplus creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prokka copying multiqc/modules/prokka/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prokka copying multiqc/modules/prokka/prokka.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prokka creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/purple copying multiqc/modules/purple/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/purple copying multiqc/modules/purple/purple.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/purple creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pychopper copying multiqc/modules/pychopper/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pychopper copying multiqc/modules/pychopper/pychopper.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pychopper creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pycoqc copying multiqc/modules/pycoqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pycoqc copying multiqc/modules/pycoqc/pycoqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pycoqc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qc3C copying multiqc/modules/qc3C/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qc3C copying multiqc/modules/qc3C/qc3C.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qc3C creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qorts copying multiqc/modules/qorts/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qorts copying multiqc/modules/qorts/qorts.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qorts creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap copying multiqc/modules/qualimap/QM_BamQC.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap copying multiqc/modules/qualimap/QM_RNASeq.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap copying multiqc/modules/qualimap/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap copying multiqc/modules/qualimap/qualimap.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/quast copying multiqc/modules/quast/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/quast copying multiqc/modules/quast/quast.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/quast creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rna_seqc copying multiqc/modules/rna_seqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rna_seqc copying multiqc/modules/rna_seqc/rna_seqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rna_seqc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rockhopper copying multiqc/modules/rockhopper/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rockhopper copying multiqc/modules/rockhopper/rockhopper.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rockhopper creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rsem copying multiqc/modules/rsem/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rsem copying multiqc/modules/rsem/rsem.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rsem creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/bam_stat.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/gene_body_coverage.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/infer_experiment.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/inner_distance.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/junction_annotation.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/junction_saturation.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/read_distribution.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/read_duplication.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/read_gc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/rseqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc copying multiqc/modules/rseqc/tin.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/assets creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/assets/js copying multiqc/modules/rseqc/assets/js/multiqc_rseqc.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/assets/js creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/salmon copying multiqc/modules/salmon/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/salmon copying multiqc/modules/salmon/salmon.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/salmon creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba copying multiqc/modules/sambamba/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba copying multiqc/modules/sambamba/markdup.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba copying multiqc/modules/sambamba/sambamba.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samblaster copying multiqc/modules/samblaster/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samblaster copying multiqc/modules/samblaster/samblaster.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samblaster creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools copying multiqc/modules/samtools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools copying multiqc/modules/samtools/coverage.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools copying multiqc/modules/samtools/flagstat.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools copying multiqc/modules/samtools/idxstats.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools copying multiqc/modules/samtools/rmdup.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools copying multiqc/modules/samtools/samtools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools copying multiqc/modules/samtools/stats.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sargasso copying multiqc/modules/sargasso/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sargasso copying multiqc/modules/sargasso/sargasso.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sargasso creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqera_cli copying multiqc/modules/seqera_cli/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqera_cli copying multiqc/modules/seqera_cli/seqera_cli.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqera_cli creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqwho copying multiqc/modules/seqwho/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqwho copying multiqc/modules/seqwho/seqwho.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqwho creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqyclean copying multiqc/modules/seqyclean/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqyclean copying multiqc/modules/seqyclean/seqyclean.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqyclean creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sexdeterrmine copying multiqc/modules/sexdeterrmine/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sexdeterrmine copying multiqc/modules/sexdeterrmine/sexdeterrmine.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sexdeterrmine creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sickle copying multiqc/modules/sickle/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sickle copying multiqc/modules/sickle/sickle.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sickle creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/skewer copying multiqc/modules/skewer/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/skewer copying multiqc/modules/skewer/skewer.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/skewer creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/slamdunk copying multiqc/modules/slamdunk/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/slamdunk copying multiqc/modules/slamdunk/slamdunk.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/slamdunk creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snippy copying multiqc/modules/snippy/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snippy copying multiqc/modules/snippy/snippy.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snippy creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpeff copying multiqc/modules/snpeff/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpeff copying multiqc/modules/snpeff/snpeff.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpeff creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpsplit copying multiqc/modules/snpsplit/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpsplit copying multiqc/modules/snpsplit/snpsplit.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpsplit creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/somalier copying multiqc/modules/somalier/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/somalier copying multiqc/modules/somalier/somalier.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/somalier creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sortmerna copying multiqc/modules/sortmerna/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sortmerna copying multiqc/modules/sortmerna/sortmerna.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sortmerna creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash copying multiqc/modules/sourmash/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash copying multiqc/modules/sourmash/compare.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash copying multiqc/modules/sourmash/gather.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash copying multiqc/modules/sourmash/sourmash.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger copying multiqc/modules/spaceranger/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger copying multiqc/modules/spaceranger/_utils.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger copying multiqc/modules/spaceranger/count.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger copying multiqc/modules/spaceranger/spaceranger.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/stacks copying multiqc/modules/stacks/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/stacks copying multiqc/modules/stacks/stacks.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/stacks creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/star copying multiqc/modules/star/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/star copying multiqc/modules/star/star.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/star creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/supernova copying multiqc/modules/supernova/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/supernova copying multiqc/modules/supernova/supernova.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/supernova creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/theta2 copying multiqc/modules/theta2/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/theta2 copying multiqc/modules/theta2/theta2.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/theta2 creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/tophat copying multiqc/modules/tophat/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/tophat copying multiqc/modules/tophat/tophat.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/tophat creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/trimmomatic copying multiqc/modules/trimmomatic/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/trimmomatic copying multiqc/modules/trimmomatic/trimmomatic.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/trimmomatic creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari copying multiqc/modules/truvari/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari copying multiqc/modules/truvari/bench.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari copying multiqc/modules/truvari/truvari.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/umitools copying multiqc/modules/umitools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/umitools copying multiqc/modules/umitools/umitools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/umitools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/varscan2 copying multiqc/modules/varscan2/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/varscan2 copying multiqc/modules/varscan2/varscan2.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/varscan2 creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools copying multiqc/modules/vcftools/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools copying multiqc/modules/vcftools/relatedness2.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools copying multiqc/modules/vcftools/tstv_by_count.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools copying multiqc/modules/vcftools/tstv_by_qual.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools copying multiqc/modules/vcftools/tstv_summary.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools copying multiqc/modules/vcftools/vcftools.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vep copying multiqc/modules/vep/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vep copying multiqc/modules/vep/vep.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vep creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/verifybamid copying multiqc/modules/verifybamid/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/verifybamid copying multiqc/modules/verifybamid/verifybamid.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/verifybamid creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/whatshap copying multiqc/modules/whatshap/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/whatshap copying multiqc/modules/whatshap/whatshap.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/whatshap creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xengsort copying multiqc/modules/xengsort/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xengsort copying multiqc/modules/xengsort/xengsort.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xengsort creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xenome copying multiqc/modules/xenome/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xenome copying multiqc/modules/xenome/xenome.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xenome creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/bargraph.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/beeswarm.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/box.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/heatmap.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/linegraph.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/scatter.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/table.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/table_object.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots copying multiqc/plots/violin.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/bar.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/box.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/heatmap.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/line.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/plot.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/scatter.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/table.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly copying multiqc/plots/plotly/violin.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates copying multiqc/templates/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/base.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/content.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/foot.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/footer.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/general_stats.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/head.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/header.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/includes.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/nav.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default copying multiqc/templates/default/toolbox.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/css copying multiqc/templates/default/assets/css/default_multiqc.css -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/css creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img copying multiqc/templates/default/assets/img/MultiQC_logo.png -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img copying multiqc/templates/default/assets/img/MultiQC_logo_dark.svg -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img copying multiqc/templates/default/assets/img/favicon-16x16.png -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img copying multiqc/templates/default/assets/img/favicon-32x32.png -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img copying multiqc/templates/default/assets/img/favicon-96x96.png -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img copying multiqc/templates/default/assets/img/seqera_logo.png -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img copying multiqc/templates/default/assets/img/seqera_logo_mono.png -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js copying multiqc/templates/default/assets/js/flat.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js copying multiqc/templates/default/assets/js/multiqc.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js copying multiqc/templates/default/assets/js/plotting.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js copying multiqc/templates/default/assets/js/tables.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js copying multiqc/templates/default/assets/js/toolbox.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots copying multiqc/templates/default/assets/js/plots/bar.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots copying multiqc/templates/default/assets/js/plots/box.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots copying multiqc/templates/default/assets/js/plots/heatmap.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots copying multiqc/templates/default/assets/js/plots/line.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots copying multiqc/templates/default/assets/js/plots/scatter.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots copying multiqc/templates/default/assets/js/plots/violin.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/gathered copying multiqc/templates/gathered/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/gathered copying multiqc/templates/gathered/content.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/gathered copying multiqc/templates/gathered/nav.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/gathered creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo copying multiqc/templates/geo/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo copying multiqc/templates/geo/includes.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/emailme.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/flames.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/glyphicons-halflings-white.png -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/glyphicons-halflings.png -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/hot.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/mchammer.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/microfab.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/new.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/new2.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/progress.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/rainbow.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img copying multiqc/templates/geo/assets/img/stars.gif -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts copying multiqc/templates/highcharts/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts copying multiqc/templates/highcharts/includes.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/css copying multiqc/templates/highcharts/assets/css/default_multiqc.css -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/css creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js copying multiqc/templates/highcharts/assets/js/multiqc_mpl.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js copying multiqc/templates/highcharts/assets/js/multiqc_plotting.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js copying multiqc/templates/highcharts/assets/js/multiqc_tables.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js copying multiqc/templates/highcharts/assets/js/multiqc_toolbox.js -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/bargraph.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/beeswarm.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/boxplot.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/heatmap.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/linegraph.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/scatter.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/table.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots copying multiqc/templates/highcharts/plots/table_object.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/sections copying multiqc/templates/sections/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/sections copying multiqc/templates/sections/content.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/sections creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple copying multiqc/templates/simple/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple copying multiqc/templates/simple/foot.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple copying multiqc/templates/simple/header.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple copying multiqc/templates/simple/includes.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple copying multiqc/templates/simple/nav.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple copying multiqc/templates/simple/toolbox.html -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple creating /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/__init__.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/config.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/config_defaults.yaml -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/log.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/lzstring.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/megaqc.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/mqc_colour.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/plugin_hooks.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/report.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/search_patterns.yaml -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/software_versions.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/strict_helpers.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils copying multiqc/utils/util_functions.py -> /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils debian/rules override_dh_auto_test make[1]: Entering directory '/srv/build/multiqc-1.21+dfsg' cp -a multiqc*.egg-info /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build PYTHONPATH=/srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build dh_auto_test I: pybuild base:311: cd /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build; python3.12 -m unittest discover -v ---------------------------------------------------------------------- Ran 0 tests in 0.000s NO TESTS RAN make[1]: Leaving directory '/srv/build/multiqc-1.21+dfsg' create-stamp debian/debhelper-build-stamp dh_testroot -O--buildsystem=pybuild dh_prep -O--buildsystem=pybuild dh_auto_install --destdir=debian/multiqc/ -O--buildsystem=pybuild I: pybuild base:311: /usr/bin/python3 setup.py install --root /srv/build/multiqc-1.21+dfsg/debian/multiqc running install /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running build running build_py running egg_info writing multiqc.egg-info/PKG-INFO writing dependency_links to multiqc.egg-info/dependency_links.txt writing entry points to multiqc.egg-info/entry_points.txt writing requirements to multiqc.egg-info/requires.txt writing top-level names to multiqc.egg-info/top_level.txt reading manifest file 'multiqc.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'multiqc.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules' to be distributed and are already explicitly excluding 'multiqc.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.adapterRemoval' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.adapterRemoval' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.adapterRemoval' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.adapterRemoval' to be distributed and are already explicitly excluding 'multiqc.modules.adapterRemoval' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.afterqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.afterqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.afterqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.afterqc' to be distributed and are already explicitly excluding 'multiqc.modules.afterqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.anglerfish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.anglerfish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.anglerfish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.anglerfish' to be distributed and are already explicitly excluding 'multiqc.modules.anglerfish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bakta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bakta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bakta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bakta' to be distributed and are already explicitly excluding 'multiqc.modules.bakta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bamdst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bamdst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bamdst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bamdst' to be distributed and are already explicitly excluding 'multiqc.modules.bamdst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bamtools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bamtools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bamtools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bamtools' to be distributed and are already explicitly excluding 'multiqc.modules.bamtools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bbduk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bbduk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bbduk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bbduk' to be distributed and are already explicitly excluding 'multiqc.modules.bbduk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bbmap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bbmap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bbmap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bbmap' to be distributed and are already explicitly excluding 'multiqc.modules.bbmap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bcftools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bcftools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bcftools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bcftools' to be distributed and are already explicitly excluding 'multiqc.modules.bcftools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bcl2fastq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bcl2fastq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bcl2fastq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bcl2fastq' to be distributed and are already explicitly excluding 'multiqc.modules.bcl2fastq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bclconvert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bclconvert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bclconvert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bclconvert' to be distributed and are already explicitly excluding 'multiqc.modules.bclconvert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.biobambam2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.biobambam2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.biobambam2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.biobambam2' to be distributed and are already explicitly excluding 'multiqc.modules.biobambam2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.biobloomtools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.biobloomtools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.biobloomtools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.biobloomtools' to be distributed and are already explicitly excluding 'multiqc.modules.biobloomtools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.biscuit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.biscuit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.biscuit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.biscuit' to be distributed and are already explicitly excluding 'multiqc.modules.biscuit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bismark' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bismark' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bismark' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bismark' to be distributed and are already explicitly excluding 'multiqc.modules.bismark' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bowtie1' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bowtie1' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bowtie1' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bowtie1' to be distributed and are already explicitly excluding 'multiqc.modules.bowtie1' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bowtie2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bowtie2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bowtie2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bowtie2' to be distributed and are already explicitly excluding 'multiqc.modules.bowtie2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bracken' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bracken' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bracken' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bracken' to be distributed and are already explicitly excluding 'multiqc.modules.bracken' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.busco' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.busco' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.busco' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.busco' to be distributed and are already explicitly excluding 'multiqc.modules.busco' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.bustools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.bustools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.bustools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.bustools' to be distributed and are already explicitly excluding 'multiqc.modules.bustools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.ccs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.ccs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.ccs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.ccs' to be distributed and are already explicitly excluding 'multiqc.modules.ccs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.cellranger' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.cellranger' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.cellranger' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.cellranger' to be distributed and are already explicitly excluding 'multiqc.modules.cellranger' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.checkqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.checkqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.checkqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.checkqc' to be distributed and are already explicitly excluding 'multiqc.modules.checkqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.clipandmerge' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.clipandmerge' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.clipandmerge' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.clipandmerge' to be distributed and are already explicitly excluding 'multiqc.modules.clipandmerge' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.clusterflow' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.clusterflow' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.clusterflow' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.clusterflow' to be distributed and are already explicitly excluding 'multiqc.modules.clusterflow' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.conpair' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.conpair' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.conpair' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.conpair' to be distributed and are already explicitly excluding 'multiqc.modules.conpair' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.custom_content' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.custom_content' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.custom_content' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.custom_content' to be distributed and are already explicitly excluding 'multiqc.modules.custom_content' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.cutadapt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.cutadapt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.cutadapt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.cutadapt' to be distributed and are already explicitly excluding 'multiqc.modules.cutadapt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.damageprofiler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.damageprofiler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.damageprofiler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.damageprofiler' to be distributed and are already explicitly excluding 'multiqc.modules.damageprofiler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.dedup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.dedup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.dedup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.dedup' to be distributed and are already explicitly excluding 'multiqc.modules.dedup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.deeptools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.deeptools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.deeptools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.deeptools' to be distributed and are already explicitly excluding 'multiqc.modules.deeptools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.diamond' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.diamond' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.diamond' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.diamond' to be distributed and are already explicitly excluding 'multiqc.modules.diamond' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.disambiguate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.disambiguate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.disambiguate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.disambiguate' to be distributed and are already explicitly excluding 'multiqc.modules.disambiguate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.dragen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.dragen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.dragen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.dragen' to be distributed and are already explicitly excluding 'multiqc.modules.dragen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.dragen_fastqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.dragen_fastqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.dragen_fastqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.dragen_fastqc' to be distributed and are already explicitly excluding 'multiqc.modules.dragen_fastqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.dragen_fastqc.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.dragen_fastqc.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.dragen_fastqc.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.dragen_fastqc.assets.js' to be distributed and are already explicitly excluding 'multiqc.modules.dragen_fastqc.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.eigenstratdatabasetools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.eigenstratdatabasetools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.eigenstratdatabasetools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.eigenstratdatabasetools' to be distributed and are already explicitly excluding 'multiqc.modules.eigenstratdatabasetools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastp' to be distributed and are already explicitly excluding 'multiqc.modules.fastp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastq_screen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastq_screen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastq_screen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastq_screen' to be distributed and are already explicitly excluding 'multiqc.modules.fastq_screen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastqc' to be distributed and are already explicitly excluding 'multiqc.modules.fastqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastqc.assets.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastqc.assets.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastqc.assets.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastqc.assets.css' to be distributed and are already explicitly excluding 'multiqc.modules.fastqc.assets.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastqc.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastqc.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastqc.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastqc.assets.js' to be distributed and are already explicitly excluding 'multiqc.modules.fastqc.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fastqc.fastqc_theoretical_gc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fastqc.fastqc_theoretical_gc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fastqc.fastqc_theoretical_gc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fastqc.fastqc_theoretical_gc' to be distributed and are already explicitly excluding 'multiqc.modules.fastqc.fastqc_theoretical_gc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.featureCounts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.featureCounts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.featureCounts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.featureCounts' to be distributed and are already explicitly excluding 'multiqc.modules.featureCounts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.fgbio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.fgbio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.fgbio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.fgbio' to be distributed and are already explicitly excluding 'multiqc.modules.fgbio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.filtlong' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.filtlong' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.filtlong' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.filtlong' to be distributed and are already explicitly excluding 'multiqc.modules.filtlong' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.flash' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.flash' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.flash' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.flash' to be distributed and are already explicitly excluding 'multiqc.modules.flash' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.flexbar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.flexbar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.flexbar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.flexbar' to be distributed and are already explicitly excluding 'multiqc.modules.flexbar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.freyja' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.freyja' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.freyja' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.freyja' to be distributed and are already explicitly excluding 'multiqc.modules.freyja' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.gatk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.gatk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.gatk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.gatk' to be distributed and are already explicitly excluding 'multiqc.modules.gatk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.gffcompare' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.gffcompare' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.gffcompare' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.gffcompare' to be distributed and are already explicitly excluding 'multiqc.modules.gffcompare' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.goleft_indexcov' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.goleft_indexcov' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.goleft_indexcov' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.goleft_indexcov' to be distributed and are already explicitly excluding 'multiqc.modules.goleft_indexcov' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.gopeaks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.gopeaks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.gopeaks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.gopeaks' to be distributed and are already explicitly excluding 'multiqc.modules.gopeaks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.happy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.happy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.happy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.happy' to be distributed and are already explicitly excluding 'multiqc.modules.happy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hicexplorer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hicexplorer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hicexplorer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hicexplorer' to be distributed and are already explicitly excluding 'multiqc.modules.hicexplorer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hicpro' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hicpro' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hicpro' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hicpro' to be distributed and are already explicitly excluding 'multiqc.modules.hicpro' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hicup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hicup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hicup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hicup' to be distributed and are already explicitly excluding 'multiqc.modules.hicup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hifiasm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hifiasm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hifiasm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hifiasm' to be distributed and are already explicitly excluding 'multiqc.modules.hifiasm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hisat2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hisat2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hisat2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hisat2' to be distributed and are already explicitly excluding 'multiqc.modules.hisat2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.homer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.homer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.homer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.homer' to be distributed and are already explicitly excluding 'multiqc.modules.homer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.hops' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.hops' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.hops' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.hops' to be distributed and are already explicitly excluding 'multiqc.modules.hops' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.htseq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.htseq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.htseq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.htseq' to be distributed and are already explicitly excluding 'multiqc.modules.htseq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.humid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.humid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.humid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.humid' to be distributed and are already explicitly excluding 'multiqc.modules.humid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.interop' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.interop' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.interop' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.interop' to be distributed and are already explicitly excluding 'multiqc.modules.interop' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.isoseq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.isoseq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.isoseq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.isoseq' to be distributed and are already explicitly excluding 'multiqc.modules.isoseq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.ivar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.ivar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.ivar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.ivar' to be distributed and are already explicitly excluding 'multiqc.modules.ivar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.jcvi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.jcvi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.jcvi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.jcvi' to be distributed and are already explicitly excluding 'multiqc.modules.jcvi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.jellyfish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.jellyfish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.jellyfish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.jellyfish' to be distributed and are already explicitly excluding 'multiqc.modules.jellyfish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.kaiju' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.kaiju' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.kaiju' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.kaiju' to be distributed and are already explicitly excluding 'multiqc.modules.kaiju' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.kallisto' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.kallisto' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.kallisto' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.kallisto' to be distributed and are already explicitly excluding 'multiqc.modules.kallisto' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.kat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.kat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.kat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.kat' to be distributed and are already explicitly excluding 'multiqc.modules.kat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.kraken' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.kraken' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.kraken' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.kraken' to be distributed and are already explicitly excluding 'multiqc.modules.kraken' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.leehom' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.leehom' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.leehom' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.leehom' to be distributed and are already explicitly excluding 'multiqc.modules.leehom' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.librarian' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.librarian' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.librarian' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.librarian' to be distributed and are already explicitly excluding 'multiqc.modules.librarian' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.lima' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.lima' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.lima' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.lima' to be distributed and are already explicitly excluding 'multiqc.modules.lima' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.longranger' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.longranger' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.longranger' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.longranger' to be distributed and are already explicitly excluding 'multiqc.modules.longranger' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.macs2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.macs2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.macs2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.macs2' to be distributed and are already explicitly excluding 'multiqc.modules.macs2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.malt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.malt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.malt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.malt' to be distributed and are already explicitly excluding 'multiqc.modules.malt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mapdamage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mapdamage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mapdamage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mapdamage' to be distributed and are already explicitly excluding 'multiqc.modules.mapdamage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.megahit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.megahit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.megahit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.megahit' to be distributed and are already explicitly excluding 'multiqc.modules.megahit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.metaphlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.metaphlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.metaphlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.metaphlan' to be distributed and are already explicitly excluding 'multiqc.modules.metaphlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.methylqa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.methylqa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.methylqa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.methylqa' to be distributed and are already explicitly excluding 'multiqc.modules.methylqa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.minionqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.minionqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.minionqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.minionqc' to be distributed and are already explicitly excluding 'multiqc.modules.minionqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mirtop' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mirtop' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mirtop' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mirtop' to be distributed and are already explicitly excluding 'multiqc.modules.mirtop' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mirtrace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mirtrace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mirtrace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mirtrace' to be distributed and are already explicitly excluding 'multiqc.modules.mirtrace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mosdepth' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mosdepth' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mosdepth' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mosdepth' to be distributed and are already explicitly excluding 'multiqc.modules.mosdepth' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.motus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.motus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.motus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.motus' to be distributed and are already explicitly excluding 'multiqc.modules.motus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.mtnucratio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.mtnucratio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.mtnucratio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.mtnucratio' to be distributed and are already explicitly excluding 'multiqc.modules.mtnucratio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.multivcfanalyzer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.multivcfanalyzer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.multivcfanalyzer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.multivcfanalyzer' to be distributed and are already explicitly excluding 'multiqc.modules.multivcfanalyzer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.nanostat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.nanostat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.nanostat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.nanostat' to be distributed and are already explicitly excluding 'multiqc.modules.nanostat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.nextclade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.nextclade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.nextclade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.nextclade' to be distributed and are already explicitly excluding 'multiqc.modules.nextclade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.ngsderive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.ngsderive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.ngsderive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.ngsderive' to be distributed and are already explicitly excluding 'multiqc.modules.ngsderive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.nonpareil' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.nonpareil' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.nonpareil' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.nonpareil' to be distributed and are already explicitly excluding 'multiqc.modules.nonpareil' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.odgi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.odgi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.odgi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.odgi' to be distributed and are already explicitly excluding 'multiqc.modules.odgi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.optitype' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.optitype' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.optitype' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.optitype' to be distributed and are already explicitly excluding 'multiqc.modules.optitype' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.pangolin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.pangolin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.pangolin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.pangolin' to be distributed and are already explicitly excluding 'multiqc.modules.pangolin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.pbmarkdup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.pbmarkdup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.pbmarkdup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.pbmarkdup' to be distributed and are already explicitly excluding 'multiqc.modules.pbmarkdup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.peddy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.peddy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.peddy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.peddy' to be distributed and are already explicitly excluding 'multiqc.modules.peddy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.phantompeakqualtools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.phantompeakqualtools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.phantompeakqualtools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.phantompeakqualtools' to be distributed and are already explicitly excluding 'multiqc.modules.phantompeakqualtools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.picard' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.picard' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.picard' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.picard' to be distributed and are already explicitly excluding 'multiqc.modules.picard' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.porechop' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.porechop' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.porechop' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.porechop' to be distributed and are already explicitly excluding 'multiqc.modules.porechop' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.preseq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.preseq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.preseq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.preseq' to be distributed and are already explicitly excluding 'multiqc.modules.preseq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.prinseqplusplus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.prinseqplusplus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.prinseqplusplus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.prinseqplusplus' to be distributed and are already explicitly excluding 'multiqc.modules.prinseqplusplus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.prokka' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.prokka' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.prokka' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.prokka' to be distributed and are already explicitly excluding 'multiqc.modules.prokka' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.purple' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.purple' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.purple' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.purple' to be distributed and are already explicitly excluding 'multiqc.modules.purple' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.pychopper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.pychopper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.pychopper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.pychopper' to be distributed and are already explicitly excluding 'multiqc.modules.pychopper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.pycoqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.pycoqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.pycoqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.pycoqc' to be distributed and are already explicitly excluding 'multiqc.modules.pycoqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.qc3C' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.qc3C' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.qc3C' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.qc3C' to be distributed and are already explicitly excluding 'multiqc.modules.qc3C' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.qorts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.qorts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.qorts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.qorts' to be distributed and are already explicitly excluding 'multiqc.modules.qorts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.qualimap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.qualimap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.qualimap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.qualimap' to be distributed and are already explicitly excluding 'multiqc.modules.qualimap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.quast' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.quast' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.quast' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.quast' to be distributed and are already explicitly excluding 'multiqc.modules.quast' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rna_seqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rna_seqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rna_seqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rna_seqc' to be distributed and are already explicitly excluding 'multiqc.modules.rna_seqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rockhopper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rockhopper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rockhopper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rockhopper' to be distributed and are already explicitly excluding 'multiqc.modules.rockhopper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rsem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rsem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rsem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rsem' to be distributed and are already explicitly excluding 'multiqc.modules.rsem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rseqc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rseqc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rseqc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rseqc' to be distributed and are already explicitly excluding 'multiqc.modules.rseqc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.rseqc.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.rseqc.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.rseqc.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.rseqc.assets.js' to be distributed and are already explicitly excluding 'multiqc.modules.rseqc.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.salmon' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.salmon' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.salmon' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.salmon' to be distributed and are already explicitly excluding 'multiqc.modules.salmon' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sambamba' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sambamba' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sambamba' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sambamba' to be distributed and are already explicitly excluding 'multiqc.modules.sambamba' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.samblaster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.samblaster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.samblaster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.samblaster' to be distributed and are already explicitly excluding 'multiqc.modules.samblaster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.samtools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.samtools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.samtools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.samtools' to be distributed and are already explicitly excluding 'multiqc.modules.samtools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sargasso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sargasso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sargasso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sargasso' to be distributed and are already explicitly excluding 'multiqc.modules.sargasso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.seqera_cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.seqera_cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.seqera_cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.seqera_cli' to be distributed and are already explicitly excluding 'multiqc.modules.seqera_cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.seqwho' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.seqwho' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.seqwho' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.seqwho' to be distributed and are already explicitly excluding 'multiqc.modules.seqwho' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.seqyclean' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.seqyclean' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.seqyclean' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.seqyclean' to be distributed and are already explicitly excluding 'multiqc.modules.seqyclean' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sexdeterrmine' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sexdeterrmine' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sexdeterrmine' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sexdeterrmine' to be distributed and are already explicitly excluding 'multiqc.modules.sexdeterrmine' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sickle' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sickle' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sickle' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sickle' to be distributed and are already explicitly excluding 'multiqc.modules.sickle' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.skewer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.skewer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.skewer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.skewer' to be distributed and are already explicitly excluding 'multiqc.modules.skewer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.slamdunk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.slamdunk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.slamdunk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.slamdunk' to be distributed and are already explicitly excluding 'multiqc.modules.slamdunk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.snippy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.snippy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.snippy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.snippy' to be distributed and are already explicitly excluding 'multiqc.modules.snippy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.snpeff' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.snpeff' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.snpeff' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.snpeff' to be distributed and are already explicitly excluding 'multiqc.modules.snpeff' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.snpsplit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.snpsplit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.snpsplit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.snpsplit' to be distributed and are already explicitly excluding 'multiqc.modules.snpsplit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.somalier' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.somalier' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.somalier' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.somalier' to be distributed and are already explicitly excluding 'multiqc.modules.somalier' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sortmerna' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sortmerna' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sortmerna' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sortmerna' to be distributed and are already explicitly excluding 'multiqc.modules.sortmerna' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.sourmash' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.sourmash' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.sourmash' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.sourmash' to be distributed and are already explicitly excluding 'multiqc.modules.sourmash' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.spaceranger' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.spaceranger' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.spaceranger' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.spaceranger' to be distributed and are already explicitly excluding 'multiqc.modules.spaceranger' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.stacks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.stacks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.stacks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.stacks' to be distributed and are already explicitly excluding 'multiqc.modules.stacks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.star' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.star' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.star' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.star' to be distributed and are already explicitly excluding 'multiqc.modules.star' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.supernova' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.supernova' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.supernova' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.supernova' to be distributed and are already explicitly excluding 'multiqc.modules.supernova' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.theta2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.theta2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.theta2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.theta2' to be distributed and are already explicitly excluding 'multiqc.modules.theta2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.tophat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.tophat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.tophat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.tophat' to be distributed and are already explicitly excluding 'multiqc.modules.tophat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.trimmomatic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.trimmomatic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.trimmomatic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.trimmomatic' to be distributed and are already explicitly excluding 'multiqc.modules.trimmomatic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.truvari' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.truvari' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.truvari' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.truvari' to be distributed and are already explicitly excluding 'multiqc.modules.truvari' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.umitools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.umitools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.umitools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.umitools' to be distributed and are already explicitly excluding 'multiqc.modules.umitools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.varscan2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.varscan2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.varscan2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.varscan2' to be distributed and are already explicitly excluding 'multiqc.modules.varscan2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.vcftools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.vcftools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.vcftools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.vcftools' to be distributed and are already explicitly excluding 'multiqc.modules.vcftools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.vep' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.vep' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.vep' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.vep' to be distributed and are already explicitly excluding 'multiqc.modules.vep' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.verifybamid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.verifybamid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.verifybamid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.verifybamid' to be distributed and are already explicitly excluding 'multiqc.modules.verifybamid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.whatshap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.whatshap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.whatshap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.whatshap' to be distributed and are already explicitly excluding 'multiqc.modules.whatshap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.xengsort' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.xengsort' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.xengsort' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.xengsort' to be distributed and are already explicitly excluding 'multiqc.modules.xengsort' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.modules.xenome' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.modules.xenome' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.modules.xenome' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.modules.xenome' to be distributed and are already explicitly excluding 'multiqc.modules.xenome' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.plots' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.plots' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.plots' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.plots' to be distributed and are already explicitly excluding 'multiqc.plots' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.plots.plotly' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.plots.plotly' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.plots.plotly' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.plots.plotly' to be distributed and are already explicitly excluding 'multiqc.plots.plotly' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates' to be distributed and are already explicitly excluding 'multiqc.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default' to be distributed and are already explicitly excluding 'multiqc.templates.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default.assets.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default.assets.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default.assets.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default.assets.css' to be distributed and are already explicitly excluding 'multiqc.templates.default.assets.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default.assets.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default.assets.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default.assets.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default.assets.img' to be distributed and are already explicitly excluding 'multiqc.templates.default.assets.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default.assets.js' to be distributed and are already explicitly excluding 'multiqc.templates.default.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.default.assets.js.plots' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.default.assets.js.plots' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.default.assets.js.plots' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.default.assets.js.plots' to be distributed and are already explicitly excluding 'multiqc.templates.default.assets.js.plots' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.gathered' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.gathered' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.gathered' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.gathered' to be distributed and are already explicitly excluding 'multiqc.templates.gathered' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.geo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.geo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.geo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.geo' to be distributed and are already explicitly excluding 'multiqc.templates.geo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.geo.assets.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.geo.assets.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.geo.assets.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.geo.assets.img' to be distributed and are already explicitly excluding 'multiqc.templates.geo.assets.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.highcharts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.highcharts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.highcharts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.highcharts' to be distributed and are already explicitly excluding 'multiqc.templates.highcharts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.highcharts.assets.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.highcharts.assets.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.highcharts.assets.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.highcharts.assets.css' to be distributed and are already explicitly excluding 'multiqc.templates.highcharts.assets.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.highcharts.assets.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.highcharts.assets.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.highcharts.assets.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.highcharts.assets.js' to be distributed and are already explicitly excluding 'multiqc.templates.highcharts.assets.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.highcharts.plots' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.highcharts.plots' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.highcharts.plots' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.highcharts.plots' to be distributed and are already explicitly excluding 'multiqc.templates.highcharts.plots' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.sections' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.sections' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.sections' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.sections' to be distributed and are already explicitly excluding 'multiqc.templates.sections' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.templates.simple' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.templates.simple' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.templates.simple' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.templates.simple' to be distributed and are already explicitly excluding 'multiqc.templates.simple' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-packages/setuptools/command/build_py.py:218: _Warning: Package 'multiqc.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'multiqc.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'multiqc.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'multiqc.utils' to be distributed and are already explicitly excluding 'multiqc.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) running install_lib creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/__main__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/__pycache__/multiqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/__pycache__ creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/includes.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/glyphicons-halflings.png -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/emailme.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/glyphicons-halflings-white.png -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/progress.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/new.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/stars.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/hot.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/flames.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/rainbow.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/microfab.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/new2.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/geo/assets/img/mchammer.gif -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/assets/img creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/__pycache__ creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/base.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/footer.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/toolbox.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/foot.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/general_stats.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/head.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/content.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/nav.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/includes.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/header.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plotting.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/flat.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/toolbox.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/tables.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots/scatter.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots/heatmap.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots/line.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots/bar.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots/violin.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/plots/box.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/js/multiqc.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/js creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/css copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/css/default_multiqc.css -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/css creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img/favicon-96x96.png -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img/seqera_logo_mono.png -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img/favicon-32x32.png -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img/MultiQC_logo.png -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img/MultiQC_logo_dark.svg -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img/favicon-16x16.png -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/default/assets/img/seqera_logo.png -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/assets/img copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/gathered creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/gathered/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/gathered/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/gathered/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/gathered/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/gathered copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/gathered/content.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/gathered copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/gathered/nav.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/gathered creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple/toolbox.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple/foot.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple/nav.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple/includes.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/simple/header.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/sections creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/sections/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/sections/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/sections/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/sections/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/sections copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/sections/content.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/sections creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/linegraph.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/__pycache__/heatmap.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/__pycache__/scatter.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/__pycache__/linegraph.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/__pycache__/bargraph.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/__pycache__/beeswarm.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/__pycache__/table.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/heatmap.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/boxplot.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/scatter.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/beeswarm.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/table.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/bargraph.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/plots/table_object.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/includes.html -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/assets creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js/multiqc_plotting.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js/multiqc_toolbox.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js/multiqc_tables.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/js/multiqc_mpl.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/assets/js creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/assets/css copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/templates/highcharts/assets/css/default_multiqc.css -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/assets/css copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/multiqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flexbar creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flexbar/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flexbar/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flexbar/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flexbar/__pycache__/flexbar.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flexbar/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flexbar/flexbar.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flexbar copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flexbar/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flexbar creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/stats.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/__pycache__/flagstat.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/__pycache__/coverage.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/__pycache__/idxstats.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/__pycache__/rmdup.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/__pycache__/stats.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/__pycache__/samtools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/idxstats.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/coverage.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/samtools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/flagstat.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samtools/rmdup.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/MarkIlluminaAdapters.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/HsMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/QualityByCycleMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/TargetedPcrMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/WgsMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/MarkDuplicates.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/MarkIlluminaAdapters.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/AlignmentSummaryMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/QualityYieldMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/ExtractIlluminaBarcodes.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/QualityByCycleMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/VariantCallingMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/HsMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/TargetedPcrMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/OxoGMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/GcBiasMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/InsertSizeMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/IlluminaBasecallingMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/CrosscheckFingerprints.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/RnaSeqMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/util.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/IlluminaLaneMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/QualityScoreDistributionMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/picard.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/BaseDistributionByCycleMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/RrbsSummaryMetrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__pycache__/ValidateSamFile.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/QualityYieldMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/CrosscheckFingerprints.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/RnaSeqMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/AlignmentSummaryMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/picard.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/InsertSizeMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/ValidateSamFile.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/VariantCallingMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/IlluminaBasecallingMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/GcBiasMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/MarkDuplicates.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/util.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/WgsMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/ExtractIlluminaBarcodes.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/OxoGMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/RrbsSummaryMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/BaseDistributionByCycleMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/IlluminaLaneMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/picard/QualityScoreDistributionMetrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nanostat creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nanostat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nanostat/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nanostat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nanostat/__pycache__/nanostat.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nanostat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nanostat/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nanostat copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nanostat/nanostat.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nanostat creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/goleft_indexcov creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/goleft_indexcov/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/goleft_indexcov/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/goleft_indexcov/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/goleft_indexcov/__pycache__/goleft_indexcov.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/goleft_indexcov/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/goleft_indexcov/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/goleft_indexcov copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/goleft_indexcov/goleft_indexcov.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/goleft_indexcov creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/longranger creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/longranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/longranger/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/longranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/longranger/__pycache__/longranger.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/longranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/longranger/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/longranger copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/longranger/longranger.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/longranger creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobloomtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobloomtools/biobloomtools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobloomtools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobloomtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobloomtools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobloomtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobloomtools/__pycache__/biobloomtools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobloomtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobloomtools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobloomtools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pangolin creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pangolin/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pangolin/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pangolin/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pangolin/__pycache__/pangolin.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pangolin/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pangolin/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pangolin copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pangolin/pangolin.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pangolin creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mtnucratio creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mtnucratio/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mtnucratio/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mtnucratio/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mtnucratio/__pycache__/mtnucratio.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mtnucratio/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mtnucratio/mtnucratio.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mtnucratio copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mtnucratio/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mtnucratio creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kallisto copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kallisto/kallisto.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kallisto creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kallisto/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kallisto/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kallisto/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kallisto/__pycache__/kallisto.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kallisto/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kallisto/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kallisto creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/methylqa creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/methylqa/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/methylqa/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/methylqa/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/methylqa/__pycache__/methylqa.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/methylqa/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/methylqa/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/methylqa copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/methylqa/methylqa.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/methylqa creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/coverage_per_contig.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/mapping_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/utils.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/trimmer_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/fragment_length.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/mapping_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/sc_rna_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/coverage_per_contig.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/rna_transcript_cov.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/utils.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/coverage_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/time_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/ploidy_estimation_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/rna_quant_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/overall_mean_cov.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/dragen.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/sc_atac_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/dragen_gc_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/coverage_hist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__pycache__/vc_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/vc_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/coverage_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/sc_rna_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/fragment_length.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/sc_atac_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/overall_mean_cov.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/trimmer_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/rna_quant_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/rna_transcript_cov.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/coverage_hist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/time_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/ploidy_estimation_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/dragen.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen/dragen_gc_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/stacks creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/stacks/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/stacks/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/stacks/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/stacks/__pycache__/stacks.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/stacks/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/stacks/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/stacks copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/stacks/stacks.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/stacks creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/diamond creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/diamond/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/diamond/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/diamond/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/diamond/__pycache__/diamond.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/diamond/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/diamond/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/diamond copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/diamond/diamond.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/diamond creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger/__pycache__/_utils.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger/__pycache__/count.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger/__pycache__/spaceranger.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger/count.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger/_utils.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/spaceranger/spaceranger.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rna_seqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rna_seqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rna_seqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rna_seqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rna_seqc/__pycache__/rna_seqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rna_seqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rna_seqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rna_seqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rna_seqc/rna_seqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rna_seqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xenome creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xenome/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xenome/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xenome/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xenome/__pycache__/xenome.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xenome/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xenome/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xenome copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xenome/xenome.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xenome creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpsplit creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpsplit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpsplit/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpsplit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpsplit/__pycache__/snpsplit.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpsplit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpsplit/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpsplit copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpsplit/snpsplit.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpsplit creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pycoqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pycoqc/pycoqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pycoqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pycoqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pycoqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pycoqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pycoqc/__pycache__/pycoqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pycoqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pycoqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pycoqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/theta2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/theta2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/theta2/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/theta2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/theta2/__pycache__/theta2.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/theta2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/theta2/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/theta2 copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/theta2/theta2.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/theta2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sickle creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sickle/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sickle/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sickle/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sickle/__pycache__/sickle.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sickle/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sickle/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sickle copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sickle/sickle.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sickle creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/__pycache__/base_module.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/__pycache__ creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/freyja copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/freyja/freyja.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/freyja creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/freyja/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/freyja/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/freyja/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/freyja/__pycache__/freyja.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/freyja/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/freyja/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/freyja creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gffcompare creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gffcompare/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gffcompare/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gffcompare/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gffcompare/__pycache__/gffcompare.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gffcompare/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gffcompare/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gffcompare copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gffcompare/gffcompare.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gffcompare creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prinseqplusplus creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prinseqplusplus/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prinseqplusplus/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prinseqplusplus/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prinseqplusplus/__pycache__/prinseqplusplus.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prinseqplusplus/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prinseqplusplus/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prinseqplusplus copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prinseqplusplus/prinseqplusplus.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prinseqplusplus creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap/QM_BamQC.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap/__pycache__/QM_BamQC.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap/__pycache__/qualimap.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap/qualimap.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qualimap/QM_RNASeq.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/damageprofiler creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/damageprofiler/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/damageprofiler/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/damageprofiler/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/damageprofiler/__pycache__/damageprofiler.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/damageprofiler/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/damageprofiler/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/damageprofiler copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/damageprofiler/damageprofiler.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/damageprofiler creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqwho creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqwho/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqwho/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqwho/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqwho/__pycache__/seqwho.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqwho/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqwho/seqwho.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqwho copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqwho/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqwho creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/motus creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/motus/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/motus/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/motus/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/motus/__pycache__/motus.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/motus/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/motus/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/motus copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/motus/motus.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/motus creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flash creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flash/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flash/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flash/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flash/__pycache__/flash.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flash/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flash/flash.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flash copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/flash/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flash creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/salmon creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/salmon/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/salmon/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/salmon/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/salmon/__pycache__/salmon.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/salmon/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/salmon/salmon.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/salmon copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/salmon/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/salmon creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/counts.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/stats.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/__pycache__/counts.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/__pycache__/clusters.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/__pycache__/stats.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/__pycache__/humid.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/__pycache__/neighbours.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/clusters.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/humid.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/humid/neighbours.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qc3C creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qc3C/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qc3C/__pycache__/qc3C.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qc3C/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qc3C/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qc3C/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qc3C/qc3C.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qc3C copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qc3C/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qc3C creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/lima creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/lima/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/lima/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/lima/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/lima/__pycache__/lima.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/lima/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/lima/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/lima copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/lima/lima.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/lima creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bustools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bustools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bustools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bustools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bustools/__pycache__/bustools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bustools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bustools/bustools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bustools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bustools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bustools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie2/__pycache__/bowtie2.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie2/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie2/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie2 copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie2/bowtie2.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/verifybamid creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/verifybamid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/verifybamid/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/verifybamid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/verifybamid/__pycache__/verifybamid.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/verifybamid/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/verifybamid/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/verifybamid copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/verifybamid/verifybamid.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/verifybamid creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jcvi creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jcvi/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jcvi/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jcvi/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jcvi/__pycache__/jcvi.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jcvi/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jcvi/jcvi.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jcvi copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jcvi/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jcvi creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clipandmerge creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clipandmerge/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clipandmerge/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clipandmerge/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clipandmerge/__pycache__/clipandmerge.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clipandmerge/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clipandmerge/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clipandmerge copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clipandmerge/clipandmerge.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clipandmerge creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer/findpeaks.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer/__pycache__/findpeaks.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer/__pycache__/homer.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer/__pycache__/tagdirectory.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer/homer.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer/tagdirectory.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/homer/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/plotPCA.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/plotProfile.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/plotEnrichment.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/bamPEFragmentSizeTable.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/plotPCA.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/plotCoverage.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/plotFingerprint.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/plotCorrelation.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/deeptools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/bamPEFragmentSizeDistribution.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__pycache__/estimateReadFiltering.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/estimateReadFiltering.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/plotProfile.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/plotFingerprint.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/bamPEFragmentSizeTable.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/plotCorrelation.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/bamPEFragmentSizeDistribution.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/plotCoverage.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/deeptools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/deeptools/plotEnrichment.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/featureCounts copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/featureCounts/feature_counts.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/featureCounts creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/featureCounts/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/featureCounts/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/featureCounts/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/featureCounts/__pycache__/feature_counts.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/featureCounts/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/featureCounts/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/featureCounts creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pychopper creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pychopper/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pychopper/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pychopper/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pychopper/__pycache__/pychopper.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pychopper/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pychopper/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pychopper copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pychopper/pychopper.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pychopper creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamdst creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamdst/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamdst/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamdst/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamdst/__pycache__/bamdst.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamdst/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamdst/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamdst copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamdst/bamdst.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamdst creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vep copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vep/vep.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vep creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vep/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vep/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vep/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vep/__pycache__/vep.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vep/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vep/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vep creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/macs2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/macs2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/macs2/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/macs2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/macs2/__pycache__/macs2.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/macs2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/macs2/macs2.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/macs2 copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/macs2/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/macs2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/__pycache__/tstv_by_qual.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/__pycache__/vcftools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/__pycache__/tstv_summary.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/__pycache__/relatedness2.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/__pycache__/tstv_by_count.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/tstv_summary.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/relatedness2.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/vcftools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/tstv_by_qual.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/vcftools/tstv_by_count.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/metaphlan creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/metaphlan/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/metaphlan/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/metaphlan/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/metaphlan/__pycache__/metaphlan.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/metaphlan/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/metaphlan/metaphlan.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/metaphlan copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/metaphlan/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/metaphlan creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbduk creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbduk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbduk/__pycache__/bbduk.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbduk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbduk/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbduk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbduk/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbduk copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbduk/bbduk.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbduk creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xengsort creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xengsort/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xengsort/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xengsort/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xengsort/__pycache__/xengsort.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xengsort/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xengsort/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xengsort copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/xengsort/xengsort.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xengsort creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/custom_content creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/custom_content/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/custom_content/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/custom_content/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/custom_content/__pycache__/custom_content.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/custom_content/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/custom_content/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/custom_content copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/custom_content/custom_content.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/custom_content creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bismark copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bismark/bismark.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bismark creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bismark/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bismark/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bismark/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bismark/__pycache__/bismark.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bismark/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bismark/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bismark creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/phantompeakqualtools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/phantompeakqualtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/phantompeakqualtools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/phantompeakqualtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/phantompeakqualtools/__pycache__/phantompeakqualtools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/phantompeakqualtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/phantompeakqualtools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/phantompeakqualtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/phantompeakqualtools/phantompeakqualtools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/phantompeakqualtools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/busco copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/busco/busco.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/busco creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/busco/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/busco/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/busco/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/busco/__pycache__/busco.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/busco/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/busco/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/busco creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastq_screen creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastq_screen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastq_screen/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastq_screen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastq_screen/__pycache__/fastq_screen.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastq_screen/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastq_screen/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastq_screen copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastq_screen/fastq_screen.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastq_screen creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtrace creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtrace/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtrace/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtrace/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtrace/__pycache__/mirtrace.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtrace/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtrace/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtrace copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtrace/mirtrace.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtrace creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/utils.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/__pycache__/count.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/__pycache__/utils.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/__pycache__/cellranger.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/__pycache__/vdj.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/count.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/cellranger.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cellranger/vdj.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/multivcfanalyzer creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/multivcfanalyzer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/multivcfanalyzer/__pycache__/multivcfanalyzer.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/multivcfanalyzer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/multivcfanalyzer/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/multivcfanalyzer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/multivcfanalyzer/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/multivcfanalyzer copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/multivcfanalyzer/multivcfanalyzer.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/multivcfanalyzer creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/megahit creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/megahit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/megahit/__pycache__/megahit.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/megahit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/megahit/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/megahit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/megahit/megahit.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/megahit copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/megahit/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/megahit creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie1 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie1/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie1/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie1/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie1/__pycache__/bowtie1.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie1/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie1/bowtie1.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie1 copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bowtie1/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie1 copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samblaster creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samblaster/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samblaster/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samblaster/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samblaster/__pycache__/samblaster.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samblaster/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samblaster/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samblaster copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/samblaster/samblaster.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samblaster creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari/bench.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari/truvari.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari/__pycache__/bench.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari/__pycache__/truvari.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/truvari/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpeff creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpeff/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpeff/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpeff/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpeff/__pycache__/snpeff.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpeff/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpeff/snpeff.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpeff copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snpeff/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpeff creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/quast copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/quast/quast.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/quast creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/quast/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/quast/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/quast/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/quast/__pycache__/quast.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/quast/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/quast/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/quast creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/malt creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/malt/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/malt/__pycache__/malt.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/malt/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/malt/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/malt/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/malt/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/malt copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/malt/malt.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/malt creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/adapterRemoval copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/adapterRemoval/adapterRemoval.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/adapterRemoval creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/adapterRemoval/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/adapterRemoval/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/adapterRemoval/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/adapterRemoval/__pycache__/adapterRemoval.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/adapterRemoval/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/adapterRemoval/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/adapterRemoval creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/tophat creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/tophat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/tophat/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/tophat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/tophat/__pycache__/tophat.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/tophat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/tophat/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/tophat copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/tophat/tophat.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/tophat creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/htseq creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/htseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/htseq/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/htseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/htseq/__pycache__/htseq.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/htseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/htseq/htseq.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/htseq copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/htseq/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/htseq creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcl2fastq creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcl2fastq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcl2fastq/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcl2fastq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcl2fastq/__pycache__/bcl2fastq.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcl2fastq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcl2fastq/bcl2fastq.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcl2fastq copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcl2fastq/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcl2fastq creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hisat2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hisat2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hisat2/__pycache__/hisat2.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hisat2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hisat2/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hisat2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hisat2/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hisat2 copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hisat2/hisat2.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hisat2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/varscan2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/varscan2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/varscan2/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/varscan2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/varscan2/__pycache__/varscan2.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/varscan2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/varscan2/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/varscan2 copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/varscan2/varscan2.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/varscan2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/purple creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/purple/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/purple/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/purple/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/purple/__pycache__/purple.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/purple/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/purple/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/purple copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/purple/purple.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/purple creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/somalier creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/somalier/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/somalier/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/somalier/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/somalier/__pycache__/somalier.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/somalier/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/somalier/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/somalier copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/somalier/somalier.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/somalier creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kat copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kat/kat.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kat creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kat/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kat/__pycache__/kat.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kat/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kat/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kat creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicexplorer copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicexplorer/hicexplorer.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicexplorer creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicexplorer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicexplorer/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicexplorer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicexplorer/__pycache__/hicexplorer.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicexplorer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicexplorer/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicexplorer creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/afterqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/afterqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/afterqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/afterqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/afterqc/__pycache__/afterqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/afterqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/afterqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/afterqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/afterqc/afterqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/afterqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastp creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastp/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastp/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastp/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastp/__pycache__/fastp.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastp/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastp/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastp copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastp/fastp.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastp creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/trimmomatic creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/trimmomatic/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/trimmomatic/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/trimmomatic/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/trimmomatic/__pycache__/trimmomatic.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/trimmomatic/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/trimmomatic/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/trimmomatic copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/trimmomatic/trimmomatic.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/trimmomatic creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jellyfish creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jellyfish/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jellyfish/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jellyfish/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jellyfish/__pycache__/jellyfish.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jellyfish/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jellyfish/jellyfish.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jellyfish copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/jellyfish/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jellyfish creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicup creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicup/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicup/__pycache__/hicup.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicup/hicup.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicup copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicup/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicup creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cutadapt creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cutadapt/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cutadapt/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cutadapt/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cutadapt/__pycache__/cutadapt.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cutadapt/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cutadapt/cutadapt.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cutadapt copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/cutadapt/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cutadapt creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/preseq creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/preseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/preseq/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/preseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/preseq/__pycache__/preseq.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/preseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/preseq/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/preseq copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/preseq/preseq.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/preseq creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/umitools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/umitools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/umitools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/umitools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/umitools/__pycache__/umitools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/umitools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/umitools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/umitools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/umitools/umitools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/umitools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/odgi creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/odgi/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/odgi/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/odgi/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/odgi/__pycache__/odgi.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/odgi/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/odgi/odgi.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/odgi copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/odgi/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/odgi creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/star creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/star/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/star/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/star/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/star/__pycache__/star.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/star/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/star/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/star copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/star/star.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/star creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rsem creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rsem/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rsem/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rsem/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rsem/__pycache__/rsem.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rsem/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rsem/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rsem copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rsem/rsem.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rsem creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/skewer creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/skewer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/skewer/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/skewer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/skewer/__pycache__/skewer.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/skewer/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/skewer/skewer.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/skewer copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/skewer/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/skewer creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools/stats.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools/__pycache__/bcftools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools/__pycache__/stats.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bcftools/bcftools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/supernova creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/supernova/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/supernova/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/supernova/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/supernova/__pycache__/supernova.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/supernova/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/supernova/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/supernova copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/supernova/supernova.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/supernova creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/__pycache__/dragen_fastqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/__pycache__/content_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/__pycache__/gc_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/__pycache__/read_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/__pycache__/util.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/__pycache__/base_metrics.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/base_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/read_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/gc_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/content_metrics.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/util.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/dragen_fastqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/assets creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dragen_fastqc/assets/js/multiqc_dragen_fastqc.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/assets/js creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ivar creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ivar/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ivar/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ivar/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ivar/__pycache__/ivar.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ivar/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ivar/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ivar copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ivar/ivar.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ivar creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bakta creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bakta/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bakta/__pycache__/bakta.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bakta/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bakta/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bakta/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bakta/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bakta copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bakta/bakta.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bakta copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/profile_runtime.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/software_versions.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rockhopper creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rockhopper/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rockhopper/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rockhopper/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rockhopper/__pycache__/rockhopper.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rockhopper/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rockhopper/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rockhopper copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rockhopper/rockhopper.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rockhopper creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mosdepth creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mosdepth/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mosdepth/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mosdepth/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mosdepth/__pycache__/mosdepth.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mosdepth/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mosdepth/mosdepth.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mosdepth copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mosdepth/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mosdepth creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kaiju creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kaiju/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kaiju/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kaiju/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kaiju/__pycache__/kaiju.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kaiju/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kaiju/kaiju.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kaiju copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kaiju/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kaiju creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqera_cli creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqera_cli/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqera_cli/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqera_cli/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqera_cli/__pycache__/seqera_cli.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqera_cli/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqera_cli/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqera_cli copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqera_cli/seqera_cli.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqera_cli creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash/compare.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash/__pycache__/compare.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash/__pycache__/gather.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash/__pycache__/sourmash.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash/gather.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sourmash/sourmash.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/conpair creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/conpair/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/conpair/__pycache__/conpair.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/conpair/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/conpair/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/conpair/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/conpair/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/conpair copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/conpair/conpair.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/conpair creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/minionqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/minionqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/minionqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/minionqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/minionqc/__pycache__/minionqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/minionqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/minionqc/minionqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/minionqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/minionqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/minionqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicpro creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicpro/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicpro/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicpro/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicpro/__pycache__/hicpro.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicpro/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicpro/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicpro copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hicpro/hicpro.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicpro creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/base_recalibrator.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/__pycache__/gatk.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/__pycache__/varianteval.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/__pycache__/analyze_saturation_mutagenesis.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/__pycache__/base_recalibrator.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/analyze_saturation_mutagenesis.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/varianteval.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gatk/gatk.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/__pycache__/fastqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/fastqc_theoretical_gc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_txome.txt -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/fastqc_theoretical_gc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_genome.txt -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/fastqc_theoretical_gc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_txome.txt -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/fastqc_theoretical_gc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_genome.txt -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/fastqc_theoretical_gc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/fastqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/assets creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/assets/js/multiqc_fastqc.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/assets/js creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/assets/css copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fastqc/assets/css/multiqc_fastqc.css -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/assets/css creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nonpareil creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nonpareil/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nonpareil/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nonpareil/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nonpareil/__pycache__/nonpareil.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nonpareil/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nonpareil/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nonpareil copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nonpareil/nonpareil.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nonpareil creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clusterflow creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clusterflow/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clusterflow/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clusterflow/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clusterflow/__pycache__/clusterflow.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clusterflow/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clusterflow/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clusterflow copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/clusterflow/clusterflow.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clusterflow creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qorts creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qorts/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qorts/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qorts/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qorts/__pycache__/qorts.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qorts/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qorts/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qorts copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/qorts/qorts.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qorts creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/whatshap creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/whatshap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/whatshap/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/whatshap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/whatshap/__pycache__/whatshap.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/whatshap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/whatshap/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/whatshap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/whatshap/whatshap.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/whatshap creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kraken copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kraken/kraken.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kraken creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kraken/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kraken/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kraken/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kraken/__pycache__/kraken.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kraken/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/kraken/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kraken creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pbmarkdup creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pbmarkdup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pbmarkdup/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pbmarkdup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pbmarkdup/__pycache__/pbmarkdup.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pbmarkdup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pbmarkdup/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pbmarkdup copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/pbmarkdup/pbmarkdup.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pbmarkdup creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hifiasm creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hifiasm/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hifiasm/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hifiasm/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hifiasm/__pycache__/hifiasm.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hifiasm/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hifiasm/hifiasm.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hifiasm copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hifiasm/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hifiasm creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nextclade creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nextclade/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nextclade/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nextclade/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nextclade/__pycache__/nextclade.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nextclade/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nextclade/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nextclade copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/nextclade/nextclade.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nextclade creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sortmerna copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sortmerna/sortmerna.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sortmerna creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sortmerna/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sortmerna/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sortmerna/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sortmerna/__pycache__/sortmerna.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sortmerna/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sortmerna/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sortmerna creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/porechop creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/porechop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/porechop/__pycache__/porechop.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/porechop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/porechop/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/porechop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/porechop/porechop.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/porechop copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/porechop/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/porechop creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/disambiguate creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/disambiguate/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/disambiguate/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/disambiguate/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/disambiguate/__pycache__/disambiguate.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/disambiguate/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/disambiguate/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/disambiguate copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/disambiguate/disambiguate.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/disambiguate creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqyclean creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqyclean/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqyclean/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqyclean/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqyclean/__pycache__/seqyclean.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqyclean/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqyclean/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqyclean copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/seqyclean/seqyclean.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqyclean creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/interop creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/interop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/interop/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/interop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/interop/__pycache__/interop.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/interop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/interop/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/interop copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/interop/interop.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/interop creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/slamdunk copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/slamdunk/slamdunk.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/slamdunk creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/slamdunk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/slamdunk/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/slamdunk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/slamdunk/__pycache__/slamdunk.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/slamdunk/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/slamdunk/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/slamdunk creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/anglerfish creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/anglerfish/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/anglerfish/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/anglerfish/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/anglerfish/__pycache__/anglerfish.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/anglerfish/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/anglerfish/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/anglerfish copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/anglerfish/anglerfish.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/anglerfish creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/filtlong creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/filtlong/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/filtlong/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/filtlong/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/filtlong/__pycache__/filtlong.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/filtlong/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/filtlong/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/filtlong copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/filtlong/filtlong.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/filtlong creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/happy creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/happy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/happy/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/happy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/happy/__pycache__/happy.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/happy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/happy/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/happy copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/happy/happy.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/happy creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_bhist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_idhist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_idhist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_indelhist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_qhist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/bbmap_filetypes.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_aqhist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_qahist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_mhist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_basic_hist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_covhist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_bhist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_ihist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_bqhist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/plot_qchist.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__pycache__/bbmap.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_indelhist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_covhist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_aqhist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_basic_hist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_bqhist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/bbmap.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_qahist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_ihist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_mhist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_qhist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/plot_qchist.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bbmap/bbmap_filetypes.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prokka creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prokka/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prokka/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prokka/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prokka/__pycache__/prokka.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prokka/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prokka/prokka.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prokka copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/prokka/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prokka creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtop creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtop/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtop/__pycache__/mirtop.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtop/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtop/mirtop.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtop copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mirtop/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtop creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/isoseq copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/isoseq/isoseq.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/isoseq creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/isoseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/isoseq/__pycache__/isoseq.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/isoseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/isoseq/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/isoseq/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/isoseq/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/isoseq creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gopeaks creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gopeaks/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gopeaks/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gopeaks/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gopeaks/__pycache__/gopeaks.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gopeaks/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gopeaks/gopeaks.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gopeaks copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/gopeaks/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gopeaks creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba/__pycache__/markdup.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba/__pycache__/sambamba.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba/markdup.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sambamba/sambamba.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mapdamage creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mapdamage/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mapdamage/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mapdamage/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mapdamage/__pycache__/mapdamage.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mapdamage/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mapdamage/mapdamage.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mapdamage copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/mapdamage/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mapdamage creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobambam2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobambam2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobambam2/__pycache__/biobambam2.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobambam2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobambam2/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobambam2/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobambam2/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobambam2 copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biobambam2/biobambam2.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobambam2 creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/eigenstratdatabasetools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/eigenstratdatabasetools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/eigenstratdatabasetools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/eigenstratdatabasetools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/eigenstratdatabasetools/__pycache__/eigenstratdatabasetools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/eigenstratdatabasetools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/eigenstratdatabasetools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/eigenstratdatabasetools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/eigenstratdatabasetools/eigenstratdatabasetools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/eigenstratdatabasetools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snippy creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snippy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snippy/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snippy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snippy/__pycache__/snippy.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snippy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snippy/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snippy copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/snippy/snippy.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snippy creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sargasso creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sargasso/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sargasso/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sargasso/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sargasso/__pycache__/sargasso.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sargasso/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sargasso/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sargasso copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sargasso/sargasso.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sargasso creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/leehom creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/leehom/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/leehom/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/leehom/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/leehom/__pycache__/leehom.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/leehom/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/leehom/leehom.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/leehom copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/leehom/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/leehom creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/optitype creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/optitype/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/optitype/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/optitype/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/optitype/__pycache__/optitype.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/optitype/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/optitype/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/optitype copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/optitype/optitype.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/optitype creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/peddy creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/peddy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/peddy/__pycache__/peddy.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/peddy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/peddy/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/peddy/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/peddy/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/peddy copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/peddy/peddy.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/peddy copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/base_module.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ccs creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ccs/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ccs/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ccs/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ccs/__pycache__/ccs.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ccs/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ccs/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ccs copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ccs/ccs.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ccs creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools/stats.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools/__pycache__/bamtools.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools/__pycache__/stats.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools/bamtools.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bamtools/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio/__pycache__/ErrorRateByReadPosition.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio/__pycache__/groupreadsbyumi.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio/__pycache__/fgbio.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio/ErrorRateByReadPosition.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio/groupreadsbyumi.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/fgbio/fgbio.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dedup creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dedup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dedup/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dedup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dedup/__pycache__/dedup.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dedup/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dedup/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dedup copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/dedup/dedup.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dedup creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sexdeterrmine creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sexdeterrmine/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sexdeterrmine/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sexdeterrmine/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sexdeterrmine/__pycache__/sexdeterrmine.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sexdeterrmine/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sexdeterrmine/sexdeterrmine.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sexdeterrmine copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/sexdeterrmine/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sexdeterrmine creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/read_distribution.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/__pycache__/rseqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/inner_distance.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/junction_saturation.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/rseqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/read_duplication.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/junction_annotation.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/read_gc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/infer_experiment.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/gene_body_coverage.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/tin.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/bam_stat.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/assets creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/assets/js copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/rseqc/assets/js/multiqc_rseqc.js -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/assets/js creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bracken creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bracken/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bracken/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bracken/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bracken/__pycache__/bracken.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bracken/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bracken/bracken.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bracken copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bracken/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bracken creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hops creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hops/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hops/__pycache__/hops.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hops/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hops/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hops/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hops/hops.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hops copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/hops/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hops creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/checkqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/checkqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/checkqc/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/checkqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/checkqc/__pycache__/checkqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/checkqc/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/checkqc/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/checkqc copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/checkqc/checkqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/checkqc creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/librarian creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/librarian/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/librarian/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/librarian/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/librarian/__pycache__/librarian.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/librarian/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/librarian/librarian.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/librarian copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/librarian/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/librarian creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ngsderive creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ngsderive/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ngsderive/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ngsderive/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ngsderive/__pycache__/ngsderive.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ngsderive/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ngsderive/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ngsderive copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/ngsderive/ngsderive.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ngsderive creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bclconvert creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bclconvert/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bclconvert/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bclconvert/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bclconvert/__pycache__/bclconvert.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bclconvert/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bclconvert/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bclconvert copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/bclconvert/bclconvert.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bclconvert creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biscuit creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biscuit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biscuit/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biscuit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biscuit/__pycache__/biscuit.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biscuit/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biscuit/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biscuit copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/modules/biscuit/biscuit.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biscuit creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/util_functions.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/config.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/strict_helpers.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/mqc_colour.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/log.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/util_functions.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/report.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/megaqc.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/lzstring.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/software_versions.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/strict_helpers.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/plugin_hooks.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__pycache__/config.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/megaqc.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/plugin_hooks.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/search_patterns.yaml -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/mqc_colour.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/report.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/config_defaults.yaml -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/log.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/software_versions.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/utils/lzstring.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/linegraph.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/bar.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/plot.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/heatmap.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/bar.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/scatter.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/violin.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/line.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/plot.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/table.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__pycache__/box.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/heatmap.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/violin.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/scatter.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/table.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/line.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/plotly/box.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly creating /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/heatmap.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/__init__.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/scatter.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/linegraph.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/bargraph.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/violin.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/beeswarm.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/table.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/box.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__pycache__/table_object.cpython-312.pyc -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__pycache__ copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/heatmap.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/violin.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/scatter.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/beeswarm.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/__init__.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/table.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/bargraph.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/table_object.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots copying /srv/build/multiqc-1.21+dfsg/.pybuild/cpython3_3.12_multiqc/build/multiqc/plots/box.py -> /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/__main__.py to __main__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/geo/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/default/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/gathered/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/simple/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/sections/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/linegraph.py to linegraph.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/heatmap.py to heatmap.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/boxplot.py to boxplot.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/scatter.py to scatter.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/beeswarm.py to beeswarm.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/table.py to table.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/bargraph.py to bargraph.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/templates/highcharts/plots/table_object.py to table_object.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/multiqc.py to multiqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flexbar/flexbar.py to flexbar.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flexbar/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/stats.py to stats.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/idxstats.py to idxstats.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/coverage.py to coverage.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/samtools.py to samtools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/flagstat.py to flagstat.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samtools/rmdup.py to rmdup.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/MarkIlluminaAdapters.py to MarkIlluminaAdapters.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/HsMetrics.py to HsMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/QualityByCycleMetrics.py to QualityByCycleMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/TargetedPcrMetrics.py to TargetedPcrMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/QualityYieldMetrics.py to QualityYieldMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/CrosscheckFingerprints.py to CrosscheckFingerprints.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/RnaSeqMetrics.py to RnaSeqMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/AlignmentSummaryMetrics.py to AlignmentSummaryMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/picard.py to picard.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/InsertSizeMetrics.py to InsertSizeMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/ValidateSamFile.py to ValidateSamFile.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/VariantCallingMetrics.py to VariantCallingMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/IlluminaBasecallingMetrics.py to IlluminaBasecallingMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/GcBiasMetrics.py to GcBiasMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/MarkDuplicates.py to MarkDuplicates.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/util.py to util.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/WgsMetrics.py to WgsMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/ExtractIlluminaBarcodes.py to ExtractIlluminaBarcodes.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/OxoGMetrics.py to OxoGMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/RrbsSummaryMetrics.py to RrbsSummaryMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/BaseDistributionByCycleMetrics.py to BaseDistributionByCycleMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/IlluminaLaneMetrics.py to IlluminaLaneMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/picard/QualityScoreDistributionMetrics.py to QualityScoreDistributionMetrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nanostat/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nanostat/nanostat.py to nanostat.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/goleft_indexcov/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/goleft_indexcov/goleft_indexcov.py to goleft_indexcov.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/longranger/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/longranger/longranger.py to longranger.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobloomtools/biobloomtools.py to biobloomtools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobloomtools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pangolin/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pangolin/pangolin.py to pangolin.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mtnucratio/mtnucratio.py to mtnucratio.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mtnucratio/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kallisto/kallisto.py to kallisto.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kallisto/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/methylqa/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/methylqa/methylqa.py to methylqa.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/coverage_per_contig.py to coverage_per_contig.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/mapping_metrics.py to mapping_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/utils.py to utils.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/vc_metrics.py to vc_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/coverage_metrics.py to coverage_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/sc_rna_metrics.py to sc_rna_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/fragment_length.py to fragment_length.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/sc_atac_metrics.py to sc_atac_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/overall_mean_cov.py to overall_mean_cov.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/trimmer_metrics.py to trimmer_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/rna_quant_metrics.py to rna_quant_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/rna_transcript_cov.py to rna_transcript_cov.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/coverage_hist.py to coverage_hist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/time_metrics.py to time_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/ploidy_estimation_metrics.py to ploidy_estimation_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/dragen.py to dragen.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen/dragen_gc_metrics.py to dragen_gc_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/stacks/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/stacks/stacks.py to stacks.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/diamond/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/diamond/diamond.py to diamond.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/count.py to count.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/_utils.py to _utils.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/spaceranger/spaceranger.py to spaceranger.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rna_seqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rna_seqc/rna_seqc.py to rna_seqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xenome/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xenome/xenome.py to xenome.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpsplit/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpsplit/snpsplit.py to snpsplit.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pycoqc/pycoqc.py to pycoqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pycoqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/theta2/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/theta2/theta2.py to theta2.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sickle/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sickle/sickle.py to sickle.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/freyja/freyja.py to freyja.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/freyja/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gffcompare/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gffcompare/gffcompare.py to gffcompare.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prinseqplusplus/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prinseqplusplus/prinseqplusplus.py to prinseqplusplus.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap/QM_BamQC.py to QM_BamQC.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap/qualimap.py to qualimap.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qualimap/QM_RNASeq.py to QM_RNASeq.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/damageprofiler/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/damageprofiler/damageprofiler.py to damageprofiler.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqwho/seqwho.py to seqwho.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqwho/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/motus/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/motus/motus.py to motus.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flash/flash.py to flash.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/flash/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/salmon/salmon.py to salmon.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/salmon/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/counts.py to counts.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/stats.py to stats.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/clusters.py to clusters.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/humid.py to humid.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/humid/neighbours.py to neighbours.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qc3C/qc3C.py to qc3C.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qc3C/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/lima/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/lima/lima.py to lima.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bustools/bustools.py to bustools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bustools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie2/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie2/bowtie2.py to bowtie2.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/verifybamid/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/verifybamid/verifybamid.py to verifybamid.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jcvi/jcvi.py to jcvi.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jcvi/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clipandmerge/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clipandmerge/clipandmerge.py to clipandmerge.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/findpeaks.py to findpeaks.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/homer.py to homer.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/tagdirectory.py to tagdirectory.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/homer/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/plotPCA.py to plotPCA.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/estimateReadFiltering.py to estimateReadFiltering.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/plotProfile.py to plotProfile.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/plotFingerprint.py to plotFingerprint.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/bamPEFragmentSizeTable.py to bamPEFragmentSizeTable.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/plotCorrelation.py to plotCorrelation.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/bamPEFragmentSizeDistribution.py to bamPEFragmentSizeDistribution.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/plotCoverage.py to plotCoverage.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/deeptools.py to deeptools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/deeptools/plotEnrichment.py to plotEnrichment.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/featureCounts/feature_counts.py to feature_counts.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/featureCounts/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pychopper/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pychopper/pychopper.py to pychopper.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamdst/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamdst/bamdst.py to bamdst.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vep/vep.py to vep.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vep/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/macs2/macs2.py to macs2.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/macs2/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/tstv_summary.py to tstv_summary.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/relatedness2.py to relatedness2.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/vcftools.py to vcftools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/tstv_by_qual.py to tstv_by_qual.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/vcftools/tstv_by_count.py to tstv_by_count.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/metaphlan/metaphlan.py to metaphlan.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/metaphlan/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbduk/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbduk/bbduk.py to bbduk.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xengsort/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/xengsort/xengsort.py to xengsort.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/custom_content/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/custom_content/custom_content.py to custom_content.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bismark/bismark.py to bismark.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bismark/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/phantompeakqualtools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/phantompeakqualtools/phantompeakqualtools.py to phantompeakqualtools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/busco/busco.py to busco.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/busco/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastq_screen/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastq_screen/fastq_screen.py to fastq_screen.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtrace/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtrace/mirtrace.py to mirtrace.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/utils.py to utils.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/count.py to count.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/cellranger.py to cellranger.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cellranger/vdj.py to vdj.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/multivcfanalyzer/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/multivcfanalyzer/multivcfanalyzer.py to multivcfanalyzer.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/megahit/megahit.py to megahit.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/megahit/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie1/bowtie1.py to bowtie1.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bowtie1/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samblaster/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/samblaster/samblaster.py to samblaster.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari/bench.py to bench.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari/truvari.py to truvari.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/truvari/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpeff/snpeff.py to snpeff.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snpeff/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/quast/quast.py to quast.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/quast/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/malt/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/malt/malt.py to malt.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/adapterRemoval/adapterRemoval.py to adapterRemoval.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/adapterRemoval/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/tophat/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/tophat/tophat.py to tophat.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/htseq/htseq.py to htseq.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/htseq/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcl2fastq/bcl2fastq.py to bcl2fastq.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcl2fastq/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hisat2/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hisat2/hisat2.py to hisat2.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/varscan2/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/varscan2/varscan2.py to varscan2.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/purple/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/purple/purple.py to purple.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/somalier/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/somalier/somalier.py to somalier.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kat/kat.py to kat.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kat/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicexplorer/hicexplorer.py to hicexplorer.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicexplorer/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/afterqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/afterqc/afterqc.py to afterqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastp/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastp/fastp.py to fastp.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/trimmomatic/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/trimmomatic/trimmomatic.py to trimmomatic.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jellyfish/jellyfish.py to jellyfish.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/jellyfish/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicup/hicup.py to hicup.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicup/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cutadapt/cutadapt.py to cutadapt.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/cutadapt/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/preseq/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/preseq/preseq.py to preseq.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/umitools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/umitools/umitools.py to umitools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/odgi/odgi.py to odgi.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/odgi/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/star/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/star/star.py to star.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rsem/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rsem/rsem.py to rsem.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/skewer/skewer.py to skewer.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/skewer/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools/stats.py to stats.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bcftools/bcftools.py to bcftools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/supernova/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/supernova/supernova.py to supernova.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/base_metrics.py to base_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/read_metrics.py to read_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/gc_metrics.py to gc_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/content_metrics.py to content_metrics.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/util.py to util.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dragen_fastqc/dragen_fastqc.py to dragen_fastqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ivar/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ivar/ivar.py to ivar.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bakta/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bakta/bakta.py to bakta.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/profile_runtime.py to profile_runtime.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/software_versions.py to software_versions.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rockhopper/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rockhopper/rockhopper.py to rockhopper.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mosdepth/mosdepth.py to mosdepth.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mosdepth/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kaiju/kaiju.py to kaiju.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kaiju/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqera_cli/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqera_cli/seqera_cli.py to seqera_cli.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/compare.py to compare.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/gather.py to gather.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sourmash/sourmash.py to sourmash.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/conpair/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/conpair/conpair.py to conpair.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/minionqc/minionqc.py to minionqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/minionqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicpro/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hicpro/hicpro.py to hicpro.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/base_recalibrator.py to base_recalibrator.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/analyze_saturation_mutagenesis.py to analyze_saturation_mutagenesis.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/varianteval.py to varianteval.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gatk/gatk.py to gatk.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fastqc/fastqc.py to fastqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nonpareil/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nonpareil/nonpareil.py to nonpareil.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clusterflow/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/clusterflow/clusterflow.py to clusterflow.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qorts/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/qorts/qorts.py to qorts.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/whatshap/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/whatshap/whatshap.py to whatshap.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kraken/kraken.py to kraken.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/kraken/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pbmarkdup/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/pbmarkdup/pbmarkdup.py to pbmarkdup.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hifiasm/hifiasm.py to hifiasm.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hifiasm/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nextclade/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/nextclade/nextclade.py to nextclade.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sortmerna/sortmerna.py to sortmerna.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sortmerna/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/porechop/porechop.py to porechop.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/porechop/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/disambiguate/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/disambiguate/disambiguate.py to disambiguate.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqyclean/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/seqyclean/seqyclean.py to seqyclean.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/interop/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/interop/interop.py to interop.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/slamdunk/slamdunk.py to slamdunk.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/slamdunk/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/anglerfish/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/anglerfish/anglerfish.py to anglerfish.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/filtlong/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/filtlong/filtlong.py to filtlong.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/happy/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/happy/happy.py to happy.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_bhist.py to plot_bhist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_idhist.py to plot_idhist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_indelhist.py to plot_indelhist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_covhist.py to plot_covhist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_aqhist.py to plot_aqhist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_basic_hist.py to plot_basic_hist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_bqhist.py to plot_bqhist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/bbmap.py to bbmap.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_qahist.py to plot_qahist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_ihist.py to plot_ihist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_mhist.py to plot_mhist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_qhist.py to plot_qhist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/plot_qchist.py to plot_qchist.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bbmap/bbmap_filetypes.py to bbmap_filetypes.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prokka/prokka.py to prokka.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/prokka/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtop/mirtop.py to mirtop.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mirtop/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/isoseq/isoseq.py to isoseq.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/isoseq/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gopeaks/gopeaks.py to gopeaks.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/gopeaks/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba/markdup.py to markdup.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sambamba/sambamba.py to sambamba.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mapdamage/mapdamage.py to mapdamage.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/mapdamage/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobambam2/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biobambam2/biobambam2.py to biobambam2.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/eigenstratdatabasetools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/eigenstratdatabasetools/eigenstratdatabasetools.py to eigenstratdatabasetools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snippy/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/snippy/snippy.py to snippy.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sargasso/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sargasso/sargasso.py to sargasso.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/leehom/leehom.py to leehom.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/leehom/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/optitype/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/optitype/optitype.py to optitype.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/peddy/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/peddy/peddy.py to peddy.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/base_module.py to base_module.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ccs/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ccs/ccs.py to ccs.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools/stats.py to stats.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools/bamtools.py to bamtools.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bamtools/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/ErrorRateByReadPosition.py to ErrorRateByReadPosition.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/groupreadsbyumi.py to groupreadsbyumi.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/fgbio/fgbio.py to fgbio.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dedup/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/dedup/dedup.py to dedup.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sexdeterrmine/sexdeterrmine.py to sexdeterrmine.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/sexdeterrmine/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/read_distribution.py to read_distribution.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/inner_distance.py to inner_distance.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/junction_saturation.py to junction_saturation.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/rseqc.py to rseqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/read_duplication.py to read_duplication.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/junction_annotation.py to junction_annotation.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/read_gc.py to read_gc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/infer_experiment.py to infer_experiment.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/gene_body_coverage.py to gene_body_coverage.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/tin.py to tin.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/rseqc/bam_stat.py to bam_stat.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bracken/bracken.py to bracken.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bracken/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hops/hops.py to hops.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/hops/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/checkqc/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/checkqc/checkqc.py to checkqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/librarian/librarian.py to librarian.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/librarian/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ngsderive/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/ngsderive/ngsderive.py to ngsderive.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bclconvert/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/bclconvert/bclconvert.py to bclconvert.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biscuit/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/modules/biscuit/biscuit.py to biscuit.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/util_functions.py to util_functions.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/config.py to config.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/strict_helpers.py to strict_helpers.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/megaqc.py to megaqc.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/plugin_hooks.py to plugin_hooks.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/mqc_colour.py to mqc_colour.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/report.py to report.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/log.py to log.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/software_versions.py to software_versions.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/utils/lzstring.py to lzstring.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/linegraph.py to linegraph.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/bar.py to bar.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/plot.py to plot.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/heatmap.py to heatmap.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/violin.py to violin.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/scatter.py to scatter.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/table.py to table.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/line.py to line.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/plotly/box.py to box.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/heatmap.py to heatmap.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/violin.py to violin.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/scatter.py to scatter.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/beeswarm.py to beeswarm.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/__init__.py to __init__.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/table.py to table.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/bargraph.py to bargraph.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/table_object.py to table_object.cpython-312.pyc byte-compiling /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc/plots/box.py to box.cpython-312.pyc running install_egg_info Copying multiqc.egg-info to /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/lib/python3.12/dist-packages/multiqc-1.21.egg-info Skipping SOURCES.txt running install_scripts Installing multiqc script to /srv/build/multiqc-1.21+dfsg/debian/multiqc/usr/bin debian/rules override_dh_install make[1]: Entering directory '/srv/build/multiqc-1.21+dfsg' dh_install mkdir -p debian/multiqc/usr/lib/python3/dist-packages/multiqc/templates/default/assets/css/ cp -a debian/missing-sources/jquery-toast-plugin/jquery.toast.min.css debian/multiqc/usr/lib/python3/dist-packages/multiqc/templates/default/assets/css/jquery.toast.css make[1]: Leaving directory '/srv/build/multiqc-1.21+dfsg' debian/rules override_dh_installdocs make[1]: Entering directory '/srv/build/multiqc-1.21+dfsg' dh_installdocs for html in `find debian -name "*.html"` ; do \ sed -i \ -e 's#https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/[^/]*/clipboard.min.js#file:///usr/share/javascript/clipboard.js#g' \ -e 's#https://cdnjs.cloudflare.com/ajax/libs/filesaver.js/[^/]*/filesaver.min.js#file:///usr/share/javascript/filesaver/FileSaver.min.js#g' \ ${html} ; \ done make[1]: Leaving directory '/srv/build/multiqc-1.21+dfsg' dh_installchangelogs -O--buildsystem=pybuild dh_installman -O--buildsystem=pybuild dh_python3 -O--buildsystem=pybuild I: dh_python3 pydist:302: Cannot find package that provides kaleido. Please add package that provides it to Build-Depends or add "kaleido python3-kaleido" line to debian/py3dist-overrides or add proper dependency to Depends by hand and ignore this info. dh_installsystemduser -O--buildsystem=pybuild dh_perl -O--buildsystem=pybuild dh_link -O--buildsystem=pybuild dh_strip_nondeterminism -O--buildsystem=pybuild dh_compress -O--buildsystem=pybuild dh_fixperms -O--buildsystem=pybuild dh_missing -O--buildsystem=pybuild dh_installdeb -O--buildsystem=pybuild dh_gencontrol -O--buildsystem=pybuild dh_md5sums -O--buildsystem=pybuild dh_builddeb -O--buildsystem=pybuild dpkg-deb: building package 'multiqc' in '../multiqc_1.21+dfsg-2_all.deb'.  dpkg-genbuildinfo --build=binary -O../multiqc_1.21+dfsg-2_amd64.buildinfo  dpkg-genchanges -DDistribution=landing --build=binary -mDebian Med Packaging Team -eDebian Med Packaging Team -O../multiqc_1.21+dfsg-2_amd64.changes dpkg-genchanges: info: binary-only upload (no source code included)  dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) This build required 55.4MiB of dedicated disk space. ┌────────────────────────────────────┐ │ Retrieving build artifacts │ └────────────────────────────────────┘ Copied 5 files. Done.