=> "/opt/local/bin/bmake" ["-C", "/data/jenkins/workspace/pkgsrc-trunk-x86_64/biology/py-multiqc", "all", "PYTHON_VERSION_REQD=314", "BATCH=1", "DEPENDS_TARGET=/nonexistent"]
===> Building for py314-multiqc-1.25.2nb1
* Building wheel...
/opt/local/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated
!!

        ********************************************************************************
        Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0).

        By 2027-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  corresp(dist, value, root_dir)
/opt/local/lib/python3.14/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: GNU General Public License v3 (GPLv3)

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  dist._finalize_license_expression()
/opt/local/lib/python3.14/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: GNU General Public License v3 (GPLv3)

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  self._finalize_license_expression()
running bdist_wheel
running build
running build_py
creating build/lib/multiqc
copying multiqc/__init__.py -> build/lib/multiqc
copying multiqc/__main__.py -> build/lib/multiqc
copying multiqc/base_module.py -> build/lib/multiqc
copying multiqc/config.py -> build/lib/multiqc
copying multiqc/interactive.py -> build/lib/multiqc
copying multiqc/report.py -> build/lib/multiqc
copying multiqc/types.py -> build/lib/multiqc
copying multiqc/validation.py -> build/lib/multiqc
copying multiqc/multiqc.py -> build/lib/multiqc
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'
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.core' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.core' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.core' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.core' to be distributed and are
        already explicitly excluding 'multiqc.core' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.ccs.tests' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.ccs.tests' as an importable package[^1],
        but it is absent 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.tests' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more 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.tests' to be distributed and are
        already explicitly excluding 'multiqc.modules.ccs.tests' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.dragen.tests' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.dragen.tests' as an importable package[^1],
        but it is absent 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.tests' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more 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.tests' to be distributed and are
        already explicitly excluding 'multiqc.modules.dragen.tests' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.ganon' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.ganon' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.ganon' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.ganon' to be distributed and are
        already explicitly excluding 'multiqc.modules.ganon' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.glimpse' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.glimpse' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.glimpse' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.glimpse' to be distributed and are
        already explicitly excluding 'multiqc.modules.glimpse' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.haplocheck' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.haplocheck' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.haplocheck' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.haplocheck' to be distributed and are
        already explicitly excluding 'multiqc.modules.haplocheck' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.hostile' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.hostile' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.hostile' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.hostile' to be distributed and are
        already explicitly excluding 'multiqc.modules.hostile' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.nanoq' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.nanoq' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.nanoq' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.nanoq' to be distributed and are
        already explicitly excluding 'multiqc.modules.nanoq' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.ngsbits' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.ngsbits' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.ngsbits' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.ngsbits' to be distributed and are
        already explicitly excluding 'multiqc.modules.ngsbits' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.pairtools' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.pairtools' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.pairtools' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.pairtools' to be distributed and are
        already explicitly excluding 'multiqc.modules.pairtools' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.picard.tests' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.picard.tests' as an importable package[^1],
        but it is absent 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.tests' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more 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.tests' to be distributed and are
        already explicitly excluding 'multiqc.modules.picard.tests' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.samtools.tests' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.samtools.tests' as an importable package[^1],
        but it is absent 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.tests' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more 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.tests' to be distributed and are
        already explicitly excluding 'multiqc.modules.samtools.tests' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.sequali' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.sequali' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.sequali' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.sequali' to be distributed and are
        already explicitly excluding 'multiqc.modules.sequali' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.umicollapse' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.umicollapse' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.umicollapse' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.umicollapse' to be distributed and are
        already explicitly excluding 'multiqc.modules.umicollapse' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.umicollapse.tests' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.umicollapse.tests' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.umicollapse.tests' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.umicollapse.tests' to be distributed and are
        already explicitly excluding 'multiqc.modules.umicollapse.tests' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.umitools.tests' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.umitools.tests' as an importable package[^1],
        but it is absent 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.tests' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more 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.tests' to be distributed and are
        already explicitly excluding 'multiqc.modules.umitools.tests' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.modules.vg' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.modules.vg' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'multiqc.modules.vg' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'multiqc.modules.vg' to be distributed and are
        already explicitly excluding 'multiqc.modules.vg' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.templates.default.assets.fonts' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.templates.default.assets.fonts' as an importable package[^1],
        but it is 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.fonts' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read 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.fonts' to be distributed and are
        already explicitly excluding 'multiqc.templates.default.assets.fonts' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.templates.default.assets.js.packages' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.templates.default.assets.js.packages' as an importable package[^1],
        but it is 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.packages' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read 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.packages' to be distributed and are
        already explicitly excluding 'multiqc.templates.default.assets.js.packages' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'multiqc.templates.geo.assets.css' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'multiqc.templates.geo.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.geo.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.geo.assets.css' to be distributed and are
        already explicitly excluding 'multiqc.templates.geo.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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.14/site-packages/setuptools/command/build_py.py:215: _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)
copying multiqc/config_defaults.yaml -> build/lib/multiqc
copying multiqc/py.typed -> build/lib/multiqc
copying multiqc/search_patterns.yaml -> build/lib/multiqc
creating build/lib/multiqc/core
copying multiqc/core/__init__.py -> build/lib/multiqc/core
copying multiqc/core/exceptions.py -> build/lib/multiqc/core
copying multiqc/core/exec_modules.py -> build/lib/multiqc/core
copying multiqc/core/file_search.py -> build/lib/multiqc/core
copying multiqc/core/log_and_rich.py -> build/lib/multiqc/core
copying multiqc/core/order_modules_and_sections.py -> build/lib/multiqc/core
copying multiqc/core/plugin_hooks.py -> build/lib/multiqc/core
copying multiqc/core/software_versions.py -> build/lib/multiqc/core
copying multiqc/core/strict_helpers.py -> build/lib/multiqc/core
copying multiqc/core/tmp_dir.py -> build/lib/multiqc/core
copying multiqc/core/update_config.py -> build/lib/multiqc/core
copying multiqc/core/version_check.py -> build/lib/multiqc/core
copying multiqc/core/write_results.py -> build/lib/multiqc/core
creating build/lib/multiqc/modules
copying multiqc/modules/__init__.py -> build/lib/multiqc/modules
copying multiqc/modules/profile_runtime.py -> build/lib/multiqc/modules
copying multiqc/modules/software_versions.py -> build/lib/multiqc/modules
creating build/lib/multiqc/modules/adapterremoval
copying multiqc/modules/adapterremoval/__init__.py -> build/lib/multiqc/modules/adapterremoval
copying multiqc/modules/adapterremoval/adapterremoval.py -> build/lib/multiqc/modules/adapterremoval
creating build/lib/multiqc/modules/afterqc
copying multiqc/modules/afterqc/__init__.py -> build/lib/multiqc/modules/afterqc
copying multiqc/modules/afterqc/afterqc.py -> build/lib/multiqc/modules/afterqc
creating build/lib/multiqc/modules/anglerfish
copying multiqc/modules/anglerfish/__init__.py -> build/lib/multiqc/modules/anglerfish
copying multiqc/modules/anglerfish/anglerfish.py -> build/lib/multiqc/modules/anglerfish
creating build/lib/multiqc/modules/bakta
copying multiqc/modules/bakta/__init__.py -> build/lib/multiqc/modules/bakta
copying multiqc/modules/bakta/bakta.py -> build/lib/multiqc/modules/bakta
creating build/lib/multiqc/modules/bamdst
copying multiqc/modules/bamdst/__init__.py -> build/lib/multiqc/modules/bamdst
copying multiqc/modules/bamdst/bamdst.py -> build/lib/multiqc/modules/bamdst
creating build/lib/multiqc/modules/bamtools
copying multiqc/modules/bamtools/__init__.py -> build/lib/multiqc/modules/bamtools
copying multiqc/modules/bamtools/bamtools.py -> build/lib/multiqc/modules/bamtools
copying multiqc/modules/bamtools/stats.py -> build/lib/multiqc/modules/bamtools
creating build/lib/multiqc/modules/bbduk
copying multiqc/modules/bbduk/__init__.py -> build/lib/multiqc/modules/bbduk
copying multiqc/modules/bbduk/bbduk.py -> build/lib/multiqc/modules/bbduk
creating build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/__init__.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/bbmap.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/bbmap_filetypes.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_aqhist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_basic_hist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_bhist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_bqhist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_covhist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_idhist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_ihist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_indelhist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_mhist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_qahist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_qchist.py -> build/lib/multiqc/modules/bbmap
copying multiqc/modules/bbmap/plot_qhist.py -> build/lib/multiqc/modules/bbmap
creating build/lib/multiqc/modules/bcftools
copying multiqc/modules/bcftools/__init__.py -> build/lib/multiqc/modules/bcftools
copying multiqc/modules/bcftools/bcftools.py -> build/lib/multiqc/modules/bcftools
copying multiqc/modules/bcftools/stats.py -> build/lib/multiqc/modules/bcftools
creating build/lib/multiqc/modules/bcl2fastq
copying multiqc/modules/bcl2fastq/__init__.py -> build/lib/multiqc/modules/bcl2fastq
copying multiqc/modules/bcl2fastq/bcl2fastq.py -> build/lib/multiqc/modules/bcl2fastq
creating build/lib/multiqc/modules/bclconvert
copying multiqc/modules/bclconvert/__init__.py -> build/lib/multiqc/modules/bclconvert
copying multiqc/modules/bclconvert/bclconvert.py -> build/lib/multiqc/modules/bclconvert
creating build/lib/multiqc/modules/biobambam2
copying multiqc/modules/biobambam2/__init__.py -> build/lib/multiqc/modules/biobambam2
copying multiqc/modules/biobambam2/biobambam2.py -> build/lib/multiqc/modules/biobambam2
creating build/lib/multiqc/modules/biobloomtools
copying multiqc/modules/biobloomtools/__init__.py -> build/lib/multiqc/modules/biobloomtools
copying multiqc/modules/biobloomtools/biobloomtools.py -> build/lib/multiqc/modules/biobloomtools
creating build/lib/multiqc/modules/biscuit
copying multiqc/modules/biscuit/__init__.py -> build/lib/multiqc/modules/biscuit
copying multiqc/modules/biscuit/biscuit.py -> build/lib/multiqc/modules/biscuit
creating build/lib/multiqc/modules/bismark
copying multiqc/modules/bismark/__init__.py -> build/lib/multiqc/modules/bismark
copying multiqc/modules/bismark/bismark.py -> build/lib/multiqc/modules/bismark
creating build/lib/multiqc/modules/bowtie1
copying multiqc/modules/bowtie1/__init__.py -> build/lib/multiqc/modules/bowtie1
copying multiqc/modules/bowtie1/bowtie1.py -> build/lib/multiqc/modules/bowtie1
creating build/lib/multiqc/modules/bowtie2
copying multiqc/modules/bowtie2/__init__.py -> build/lib/multiqc/modules/bowtie2
copying multiqc/modules/bowtie2/bowtie2.py -> build/lib/multiqc/modules/bowtie2
creating build/lib/multiqc/modules/busco
copying multiqc/modules/busco/__init__.py -> build/lib/multiqc/modules/busco
copying multiqc/modules/busco/busco.py -> build/lib/multiqc/modules/busco
creating build/lib/multiqc/modules/bustools
copying multiqc/modules/bustools/__init__.py -> build/lib/multiqc/modules/bustools
copying multiqc/modules/bustools/bustools.py -> build/lib/multiqc/modules/bustools
creating build/lib/multiqc/modules/ccs
copying multiqc/modules/ccs/__init__.py -> build/lib/multiqc/modules/ccs
copying multiqc/modules/ccs/ccs.py -> build/lib/multiqc/modules/ccs
creating build/lib/multiqc/modules/ccs/tests
copying multiqc/modules/ccs/tests/__init__.py -> build/lib/multiqc/modules/ccs/tests
copying multiqc/modules/ccs/tests/test_ccs.py -> build/lib/multiqc/modules/ccs/tests
creating build/lib/multiqc/modules/cellranger
copying multiqc/modules/cellranger/__init__.py -> build/lib/multiqc/modules/cellranger
copying multiqc/modules/cellranger/cellranger.py -> build/lib/multiqc/modules/cellranger
copying multiqc/modules/cellranger/count.py -> build/lib/multiqc/modules/cellranger
copying multiqc/modules/cellranger/utils.py -> build/lib/multiqc/modules/cellranger
copying multiqc/modules/cellranger/vdj.py -> build/lib/multiqc/modules/cellranger
creating build/lib/multiqc/modules/checkqc
copying multiqc/modules/checkqc/__init__.py -> build/lib/multiqc/modules/checkqc
copying multiqc/modules/checkqc/checkqc.py -> build/lib/multiqc/modules/checkqc
creating build/lib/multiqc/modules/clipandmerge
copying multiqc/modules/clipandmerge/__init__.py -> build/lib/multiqc/modules/clipandmerge
copying multiqc/modules/clipandmerge/clipandmerge.py -> build/lib/multiqc/modules/clipandmerge
creating build/lib/multiqc/modules/clusterflow
copying multiqc/modules/clusterflow/__init__.py -> build/lib/multiqc/modules/clusterflow
copying multiqc/modules/clusterflow/clusterflow.py -> build/lib/multiqc/modules/clusterflow
creating build/lib/multiqc/modules/conpair
copying multiqc/modules/conpair/__init__.py -> build/lib/multiqc/modules/conpair
copying multiqc/modules/conpair/conpair.py -> build/lib/multiqc/modules/conpair
creating build/lib/multiqc/modules/custom_content
copying multiqc/modules/custom_content/__init__.py -> build/lib/multiqc/modules/custom_content
copying multiqc/modules/custom_content/custom_content.py -> build/lib/multiqc/modules/custom_content
creating build/lib/multiqc/modules/cutadapt
copying multiqc/modules/cutadapt/__init__.py -> build/lib/multiqc/modules/cutadapt
copying multiqc/modules/cutadapt/cutadapt.py -> build/lib/multiqc/modules/cutadapt
creating build/lib/multiqc/modules/damageprofiler
copying multiqc/modules/damageprofiler/__init__.py -> build/lib/multiqc/modules/damageprofiler
copying multiqc/modules/damageprofiler/damageprofiler.py -> build/lib/multiqc/modules/damageprofiler
creating build/lib/multiqc/modules/dedup
copying multiqc/modules/dedup/__init__.py -> build/lib/multiqc/modules/dedup
copying multiqc/modules/dedup/dedup.py -> build/lib/multiqc/modules/dedup
creating build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/__init__.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/bamPEFragmentSizeDistribution.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/bamPEFragmentSizeTable.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/deeptools.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/estimateReadFiltering.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/plotCorrelation.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/plotCoverage.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/plotEnrichment.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/plotFingerprint.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/plotPCA.py -> build/lib/multiqc/modules/deeptools
copying multiqc/modules/deeptools/plotProfile.py -> build/lib/multiqc/modules/deeptools
creating build/lib/multiqc/modules/diamond
copying multiqc/modules/diamond/__init__.py -> build/lib/multiqc/modules/diamond
copying multiqc/modules/diamond/diamond.py -> build/lib/multiqc/modules/diamond
creating build/lib/multiqc/modules/disambiguate
copying multiqc/modules/disambiguate/__init__.py -> build/lib/multiqc/modules/disambiguate
copying multiqc/modules/disambiguate/disambiguate.py -> build/lib/multiqc/modules/disambiguate
creating build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/__init__.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/coverage_hist.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/coverage_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/coverage_per_contig.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/dragen.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/dragen_gc_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/fragment_length.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/mapping_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/overall_mean_cov.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/ploidy_estimation_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/rna_quant_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/rna_transcript_cov.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/sc_atac_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/sc_rna_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/time_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/trimmer_metrics.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/utils.py -> build/lib/multiqc/modules/dragen
copying multiqc/modules/dragen/vc_metrics.py -> build/lib/multiqc/modules/dragen
creating build/lib/multiqc/modules/dragen/tests
copying multiqc/modules/dragen/tests/__init__.py -> build/lib/multiqc/modules/dragen/tests
copying multiqc/modules/dragen/tests/test_dragen.py -> build/lib/multiqc/modules/dragen/tests
creating build/lib/multiqc/modules/dragen_fastqc
copying multiqc/modules/dragen_fastqc/__init__.py -> build/lib/multiqc/modules/dragen_fastqc
copying multiqc/modules/dragen_fastqc/base_metrics.py -> build/lib/multiqc/modules/dragen_fastqc
copying multiqc/modules/dragen_fastqc/content_metrics.py -> build/lib/multiqc/modules/dragen_fastqc
copying multiqc/modules/dragen_fastqc/dragen_fastqc.py -> build/lib/multiqc/modules/dragen_fastqc
copying multiqc/modules/dragen_fastqc/gc_metrics.py -> build/lib/multiqc/modules/dragen_fastqc
copying multiqc/modules/dragen_fastqc/read_metrics.py -> build/lib/multiqc/modules/dragen_fastqc
copying multiqc/modules/dragen_fastqc/util.py -> build/lib/multiqc/modules/dragen_fastqc
creating build/lib/multiqc/modules/dragen_fastqc/assets/js
copying multiqc/modules/dragen_fastqc/assets/js/multiqc_dragen_fastqc.js -> build/lib/multiqc/modules/dragen_fastqc/assets/js
creating build/lib/multiqc/modules/eigenstratdatabasetools
copying multiqc/modules/eigenstratdatabasetools/__init__.py -> build/lib/multiqc/modules/eigenstratdatabasetools
copying multiqc/modules/eigenstratdatabasetools/eigenstratdatabasetools.py -> build/lib/multiqc/modules/eigenstratdatabasetools
creating build/lib/multiqc/modules/fastp
copying multiqc/modules/fastp/__init__.py -> build/lib/multiqc/modules/fastp
copying multiqc/modules/fastp/fastp.py -> build/lib/multiqc/modules/fastp
creating build/lib/multiqc/modules/fastq_screen
copying multiqc/modules/fastq_screen/__init__.py -> build/lib/multiqc/modules/fastq_screen
copying multiqc/modules/fastq_screen/fastq_screen.py -> build/lib/multiqc/modules/fastq_screen
creating build/lib/multiqc/modules/fastqc
copying multiqc/modules/fastqc/__init__.py -> build/lib/multiqc/modules/fastqc
copying multiqc/modules/fastqc/fastqc.py -> build/lib/multiqc/modules/fastqc
creating build/lib/multiqc/modules/fastqc/assets/css
copying multiqc/modules/fastqc/assets/css/multiqc_fastqc.css -> build/lib/multiqc/modules/fastqc/assets/css
creating build/lib/multiqc/modules/fastqc/assets/js
copying multiqc/modules/fastqc/assets/js/multiqc_fastqc.js -> build/lib/multiqc/modules/fastqc/assets/js
creating build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc
copying multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_genome.txt -> build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc
copying multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_txome.txt -> build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc
copying multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_genome.txt -> build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc
copying multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_txome.txt -> build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc
creating build/lib/multiqc/modules/featurecounts
copying multiqc/modules/featurecounts/__init__.py -> build/lib/multiqc/modules/featurecounts
copying multiqc/modules/featurecounts/featurecounts.py -> build/lib/multiqc/modules/featurecounts
creating build/lib/multiqc/modules/fgbio
copying multiqc/modules/fgbio/__init__.py -> build/lib/multiqc/modules/fgbio
copying multiqc/modules/fgbio/error_rate_by_read_position.py -> build/lib/multiqc/modules/fgbio
copying multiqc/modules/fgbio/fgbio.py -> build/lib/multiqc/modules/fgbio
copying multiqc/modules/fgbio/group_reads_by_umi.py -> build/lib/multiqc/modules/fgbio
creating build/lib/multiqc/modules/filtlong
copying multiqc/modules/filtlong/__init__.py -> build/lib/multiqc/modules/filtlong
copying multiqc/modules/filtlong/filtlong.py -> build/lib/multiqc/modules/filtlong
creating build/lib/multiqc/modules/flash
copying multiqc/modules/flash/__init__.py -> build/lib/multiqc/modules/flash
copying multiqc/modules/flash/flash.py -> build/lib/multiqc/modules/flash
creating build/lib/multiqc/modules/flexbar
copying multiqc/modules/flexbar/__init__.py -> build/lib/multiqc/modules/flexbar
copying multiqc/modules/flexbar/flexbar.py -> build/lib/multiqc/modules/flexbar
creating build/lib/multiqc/modules/freyja
copying multiqc/modules/freyja/__init__.py -> build/lib/multiqc/modules/freyja
copying multiqc/modules/freyja/freyja.py -> build/lib/multiqc/modules/freyja
creating build/lib/multiqc/modules/ganon
copying multiqc/modules/ganon/__init__.py -> build/lib/multiqc/modules/ganon
copying multiqc/modules/ganon/ganon.py -> build/lib/multiqc/modules/ganon
creating build/lib/multiqc/modules/gatk
copying multiqc/modules/gatk/__init__.py -> build/lib/multiqc/modules/gatk
copying multiqc/modules/gatk/analyze_saturation_mutagenesis.py -> build/lib/multiqc/modules/gatk
copying multiqc/modules/gatk/base_recalibrator.py -> build/lib/multiqc/modules/gatk
copying multiqc/modules/gatk/gatk.py -> build/lib/multiqc/modules/gatk
copying multiqc/modules/gatk/varianteval.py -> build/lib/multiqc/modules/gatk
creating build/lib/multiqc/modules/gffcompare
copying multiqc/modules/gffcompare/__init__.py -> build/lib/multiqc/modules/gffcompare
copying multiqc/modules/gffcompare/gffcompare.py -> build/lib/multiqc/modules/gffcompare
creating build/lib/multiqc/modules/glimpse
copying multiqc/modules/glimpse/__init__.py -> build/lib/multiqc/modules/glimpse
copying multiqc/modules/glimpse/err_grp.py -> build/lib/multiqc/modules/glimpse
copying multiqc/modules/glimpse/err_spl.py -> build/lib/multiqc/modules/glimpse
copying multiqc/modules/glimpse/glimpse.py -> build/lib/multiqc/modules/glimpse
creating build/lib/multiqc/modules/goleft_indexcov
copying multiqc/modules/goleft_indexcov/__init__.py -> build/lib/multiqc/modules/goleft_indexcov
copying multiqc/modules/goleft_indexcov/goleft_indexcov.py -> build/lib/multiqc/modules/goleft_indexcov
creating build/lib/multiqc/modules/gopeaks
copying multiqc/modules/gopeaks/__init__.py -> build/lib/multiqc/modules/gopeaks
copying multiqc/modules/gopeaks/gopeaks.py -> build/lib/multiqc/modules/gopeaks
creating build/lib/multiqc/modules/haplocheck
copying multiqc/modules/haplocheck/__init__.py -> build/lib/multiqc/modules/haplocheck
copying multiqc/modules/haplocheck/haplocheck.py -> build/lib/multiqc/modules/haplocheck
creating build/lib/multiqc/modules/happy
copying multiqc/modules/happy/__init__.py -> build/lib/multiqc/modules/happy
copying multiqc/modules/happy/happy.py -> build/lib/multiqc/modules/happy
creating build/lib/multiqc/modules/hicexplorer
copying multiqc/modules/hicexplorer/__init__.py -> build/lib/multiqc/modules/hicexplorer
copying multiqc/modules/hicexplorer/hicexplorer.py -> build/lib/multiqc/modules/hicexplorer
creating build/lib/multiqc/modules/hicpro
copying multiqc/modules/hicpro/__init__.py -> build/lib/multiqc/modules/hicpro
copying multiqc/modules/hicpro/hicpro.py -> build/lib/multiqc/modules/hicpro
creating build/lib/multiqc/modules/hicup
copying multiqc/modules/hicup/__init__.py -> build/lib/multiqc/modules/hicup
copying multiqc/modules/hicup/hicup.py -> build/lib/multiqc/modules/hicup
creating build/lib/multiqc/modules/hifiasm
copying multiqc/modules/hifiasm/__init__.py -> build/lib/multiqc/modules/hifiasm
copying multiqc/modules/hifiasm/hifiasm.py -> build/lib/multiqc/modules/hifiasm
creating build/lib/multiqc/modules/hisat2
copying multiqc/modules/hisat2/__init__.py -> build/lib/multiqc/modules/hisat2
copying multiqc/modules/hisat2/hisat2.py -> build/lib/multiqc/modules/hisat2
creating build/lib/multiqc/modules/homer
copying multiqc/modules/homer/__init__.py -> build/lib/multiqc/modules/homer
copying multiqc/modules/homer/findpeaks.py -> build/lib/multiqc/modules/homer
copying multiqc/modules/homer/homer.py -> build/lib/multiqc/modules/homer
copying multiqc/modules/homer/tagdirectory.py -> build/lib/multiqc/modules/homer
creating build/lib/multiqc/modules/hops
copying multiqc/modules/hops/__init__.py -> build/lib/multiqc/modules/hops
copying multiqc/modules/hops/hops.py -> build/lib/multiqc/modules/hops
creating build/lib/multiqc/modules/hostile
copying multiqc/modules/hostile/__init__.py -> build/lib/multiqc/modules/hostile
copying multiqc/modules/hostile/hostile.py -> build/lib/multiqc/modules/hostile
creating build/lib/multiqc/modules/htseq
copying multiqc/modules/htseq/__init__.py -> build/lib/multiqc/modules/htseq
copying multiqc/modules/htseq/htseq.py -> build/lib/multiqc/modules/htseq
creating build/lib/multiqc/modules/humid
copying multiqc/modules/humid/__init__.py -> build/lib/multiqc/modules/humid
copying multiqc/modules/humid/clusters.py -> build/lib/multiqc/modules/humid
copying multiqc/modules/humid/counts.py -> build/lib/multiqc/modules/humid
copying multiqc/modules/humid/humid.py -> build/lib/multiqc/modules/humid
copying multiqc/modules/humid/neighbours.py -> build/lib/multiqc/modules/humid
copying multiqc/modules/humid/stats.py -> build/lib/multiqc/modules/humid
creating build/lib/multiqc/modules/interop
copying multiqc/modules/interop/__init__.py -> build/lib/multiqc/modules/interop
copying multiqc/modules/interop/interop.py -> build/lib/multiqc/modules/interop
creating build/lib/multiqc/modules/isoseq
copying multiqc/modules/isoseq/__init__.py -> build/lib/multiqc/modules/isoseq
copying multiqc/modules/isoseq/isoseq.py -> build/lib/multiqc/modules/isoseq
creating build/lib/multiqc/modules/ivar
copying multiqc/modules/ivar/__init__.py -> build/lib/multiqc/modules/ivar
copying multiqc/modules/ivar/ivar.py -> build/lib/multiqc/modules/ivar
creating build/lib/multiqc/modules/jcvi
copying multiqc/modules/jcvi/__init__.py -> build/lib/multiqc/modules/jcvi
copying multiqc/modules/jcvi/jcvi.py -> build/lib/multiqc/modules/jcvi
creating build/lib/multiqc/modules/jellyfish
copying multiqc/modules/jellyfish/__init__.py -> build/lib/multiqc/modules/jellyfish
copying multiqc/modules/jellyfish/jellyfish.py -> build/lib/multiqc/modules/jellyfish
creating build/lib/multiqc/modules/kaiju
copying multiqc/modules/kaiju/__init__.py -> build/lib/multiqc/modules/kaiju
copying multiqc/modules/kaiju/kaiju.py -> build/lib/multiqc/modules/kaiju
creating build/lib/multiqc/modules/kallisto
copying multiqc/modules/kallisto/__init__.py -> build/lib/multiqc/modules/kallisto
copying multiqc/modules/kallisto/kallisto.py -> build/lib/multiqc/modules/kallisto
creating build/lib/multiqc/modules/kat
copying multiqc/modules/kat/__init__.py -> build/lib/multiqc/modules/kat
copying multiqc/modules/kat/kat.py -> build/lib/multiqc/modules/kat
creating build/lib/multiqc/modules/kraken
copying multiqc/modules/kraken/__init__.py -> build/lib/multiqc/modules/kraken
copying multiqc/modules/kraken/kraken.py -> build/lib/multiqc/modules/kraken
creating build/lib/multiqc/modules/leehom
copying multiqc/modules/leehom/__init__.py -> build/lib/multiqc/modules/leehom
copying multiqc/modules/leehom/leehom.py -> build/lib/multiqc/modules/leehom
creating build/lib/multiqc/modules/librarian
copying multiqc/modules/librarian/__init__.py -> build/lib/multiqc/modules/librarian
copying multiqc/modules/librarian/librarian.py -> build/lib/multiqc/modules/librarian
creating build/lib/multiqc/modules/lima
copying multiqc/modules/lima/__init__.py -> build/lib/multiqc/modules/lima
copying multiqc/modules/lima/lima.py -> build/lib/multiqc/modules/lima
creating build/lib/multiqc/modules/longranger
copying multiqc/modules/longranger/__init__.py -> build/lib/multiqc/modules/longranger
copying multiqc/modules/longranger/longranger.py -> build/lib/multiqc/modules/longranger
creating build/lib/multiqc/modules/macs2
copying multiqc/modules/macs2/__init__.py -> build/lib/multiqc/modules/macs2
copying multiqc/modules/macs2/macs2.py -> build/lib/multiqc/modules/macs2
creating build/lib/multiqc/modules/malt
copying multiqc/modules/malt/__init__.py -> build/lib/multiqc/modules/malt
copying multiqc/modules/malt/malt.py -> build/lib/multiqc/modules/malt
creating build/lib/multiqc/modules/mapdamage
copying multiqc/modules/mapdamage/__init__.py -> build/lib/multiqc/modules/mapdamage
copying multiqc/modules/mapdamage/mapdamage.py -> build/lib/multiqc/modules/mapdamage
creating build/lib/multiqc/modules/megahit
copying multiqc/modules/megahit/__init__.py -> build/lib/multiqc/modules/megahit
copying multiqc/modules/megahit/megahit.py -> build/lib/multiqc/modules/megahit
creating build/lib/multiqc/modules/metaphlan
copying multiqc/modules/metaphlan/__init__.py -> build/lib/multiqc/modules/metaphlan
copying multiqc/modules/metaphlan/metaphlan.py -> build/lib/multiqc/modules/metaphlan
creating build/lib/multiqc/modules/methylqa
copying multiqc/modules/methylqa/__init__.py -> build/lib/multiqc/modules/methylqa
copying multiqc/modules/methylqa/methylqa.py -> build/lib/multiqc/modules/methylqa
creating build/lib/multiqc/modules/minionqc
copying multiqc/modules/minionqc/__init__.py -> build/lib/multiqc/modules/minionqc
copying multiqc/modules/minionqc/minionqc.py -> build/lib/multiqc/modules/minionqc
creating build/lib/multiqc/modules/mirtop
copying multiqc/modules/mirtop/__init__.py -> build/lib/multiqc/modules/mirtop
copying multiqc/modules/mirtop/mirtop.py -> build/lib/multiqc/modules/mirtop
creating build/lib/multiqc/modules/mirtrace
copying multiqc/modules/mirtrace/__init__.py -> build/lib/multiqc/modules/mirtrace
copying multiqc/modules/mirtrace/mirtrace.py -> build/lib/multiqc/modules/mirtrace
creating build/lib/multiqc/modules/mosdepth
copying multiqc/modules/mosdepth/__init__.py -> build/lib/multiqc/modules/mosdepth
copying multiqc/modules/mosdepth/mosdepth.py -> build/lib/multiqc/modules/mosdepth
creating build/lib/multiqc/modules/motus
copying multiqc/modules/motus/__init__.py -> build/lib/multiqc/modules/motus
copying multiqc/modules/motus/motus.py -> build/lib/multiqc/modules/motus
creating build/lib/multiqc/modules/mtnucratio
copying multiqc/modules/mtnucratio/__init__.py -> build/lib/multiqc/modules/mtnucratio
copying multiqc/modules/mtnucratio/mtnucratio.py -> build/lib/multiqc/modules/mtnucratio
creating build/lib/multiqc/modules/multivcfanalyzer
copying multiqc/modules/multivcfanalyzer/__init__.py -> build/lib/multiqc/modules/multivcfanalyzer
copying multiqc/modules/multivcfanalyzer/multivcfanalyzer.py -> build/lib/multiqc/modules/multivcfanalyzer
creating build/lib/multiqc/modules/nanoq
copying multiqc/modules/nanoq/__init__.py -> build/lib/multiqc/modules/nanoq
copying multiqc/modules/nanoq/nanoq.py -> build/lib/multiqc/modules/nanoq
creating build/lib/multiqc/modules/nanostat
copying multiqc/modules/nanostat/__init__.py -> build/lib/multiqc/modules/nanostat
copying multiqc/modules/nanostat/nanostat.py -> build/lib/multiqc/modules/nanostat
creating build/lib/multiqc/modules/nextclade
copying multiqc/modules/nextclade/__init__.py -> build/lib/multiqc/modules/nextclade
copying multiqc/modules/nextclade/nextclade.py -> build/lib/multiqc/modules/nextclade
creating build/lib/multiqc/modules/ngsbits
copying multiqc/modules/ngsbits/__init__.py -> build/lib/multiqc/modules/ngsbits
copying multiqc/modules/ngsbits/mappingqc.py -> build/lib/multiqc/modules/ngsbits
copying multiqc/modules/ngsbits/ngsbits.py -> build/lib/multiqc/modules/ngsbits
copying multiqc/modules/ngsbits/readqc.py -> build/lib/multiqc/modules/ngsbits
copying multiqc/modules/ngsbits/samplegender.py -> build/lib/multiqc/modules/ngsbits
copying multiqc/modules/ngsbits/utils.py -> build/lib/multiqc/modules/ngsbits
creating build/lib/multiqc/modules/ngsderive
copying multiqc/modules/ngsderive/__init__.py -> build/lib/multiqc/modules/ngsderive
copying multiqc/modules/ngsderive/ngsderive.py -> build/lib/multiqc/modules/ngsderive
creating build/lib/multiqc/modules/nonpareil
copying multiqc/modules/nonpareil/__init__.py -> build/lib/multiqc/modules/nonpareil
copying multiqc/modules/nonpareil/nonpareil.py -> build/lib/multiqc/modules/nonpareil
creating build/lib/multiqc/modules/odgi
copying multiqc/modules/odgi/__init__.py -> build/lib/multiqc/modules/odgi
copying multiqc/modules/odgi/odgi.py -> build/lib/multiqc/modules/odgi
creating build/lib/multiqc/modules/optitype
copying multiqc/modules/optitype/__init__.py -> build/lib/multiqc/modules/optitype
copying multiqc/modules/optitype/optitype.py -> build/lib/multiqc/modules/optitype
creating build/lib/multiqc/modules/pairtools
copying multiqc/modules/pairtools/__init__.py -> build/lib/multiqc/modules/pairtools
copying multiqc/modules/pairtools/pairtools.py -> build/lib/multiqc/modules/pairtools
copying multiqc/modules/pairtools/params.yml -> build/lib/multiqc/modules/pairtools
copying multiqc/modules/pairtools/utils.py -> build/lib/multiqc/modules/pairtools
creating build/lib/multiqc/modules/pangolin
copying multiqc/modules/pangolin/__init__.py -> build/lib/multiqc/modules/pangolin
copying multiqc/modules/pangolin/pangolin.py -> build/lib/multiqc/modules/pangolin
creating build/lib/multiqc/modules/pbmarkdup
copying multiqc/modules/pbmarkdup/__init__.py -> build/lib/multiqc/modules/pbmarkdup
copying multiqc/modules/pbmarkdup/pbmarkdup.py -> build/lib/multiqc/modules/pbmarkdup
creating build/lib/multiqc/modules/peddy
copying multiqc/modules/peddy/__init__.py -> build/lib/multiqc/modules/peddy
copying multiqc/modules/peddy/peddy.py -> build/lib/multiqc/modules/peddy
creating build/lib/multiqc/modules/phantompeakqualtools
copying multiqc/modules/phantompeakqualtools/__init__.py -> build/lib/multiqc/modules/phantompeakqualtools
copying multiqc/modules/phantompeakqualtools/phantompeakqualtools.py -> build/lib/multiqc/modules/phantompeakqualtools
creating build/lib/multiqc/modules/picard
copying multiqc/modules/picard/AlignmentSummaryMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/BaseDistributionByCycleMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/CrosscheckFingerprints.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/ExtractIlluminaBarcodes.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/GcBiasMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/HsMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/IlluminaBasecallingMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/IlluminaLaneMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/InsertSizeMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/MarkDuplicates.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/MarkIlluminaAdapters.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/OxoGMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/QualityByCycleMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/QualityScoreDistributionMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/QualityYieldMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/RnaSeqMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/RrbsSummaryMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/TargetedPcrMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/ValidateSamFile.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/VariantCallingMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/WgsMetrics.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/__init__.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/picard.py -> build/lib/multiqc/modules/picard
copying multiqc/modules/picard/util.py -> build/lib/multiqc/modules/picard
creating build/lib/multiqc/modules/picard/tests
copying multiqc/modules/picard/tests/__init__.py -> build/lib/multiqc/modules/picard/tests
copying multiqc/modules/picard/tests/test_picard.py -> build/lib/multiqc/modules/picard/tests
creating build/lib/multiqc/modules/porechop
copying multiqc/modules/porechop/__init__.py -> build/lib/multiqc/modules/porechop
copying multiqc/modules/porechop/porechop.py -> build/lib/multiqc/modules/porechop
creating build/lib/multiqc/modules/preseq
copying multiqc/modules/preseq/__init__.py -> build/lib/multiqc/modules/preseq
copying multiqc/modules/preseq/preseq.py -> build/lib/multiqc/modules/preseq
creating build/lib/multiqc/modules/prinseqplusplus
copying multiqc/modules/prinseqplusplus/__init__.py -> build/lib/multiqc/modules/prinseqplusplus
copying multiqc/modules/prinseqplusplus/prinseqplusplus.py -> build/lib/multiqc/modules/prinseqplusplus
creating build/lib/multiqc/modules/prokka
copying multiqc/modules/prokka/__init__.py -> build/lib/multiqc/modules/prokka
copying multiqc/modules/prokka/prokka.py -> build/lib/multiqc/modules/prokka
creating build/lib/multiqc/modules/purple
copying multiqc/modules/purple/__init__.py -> build/lib/multiqc/modules/purple
copying multiqc/modules/purple/purple.py -> build/lib/multiqc/modules/purple
creating build/lib/multiqc/modules/pychopper
copying multiqc/modules/pychopper/__init__.py -> build/lib/multiqc/modules/pychopper
copying multiqc/modules/pychopper/pychopper.py -> build/lib/multiqc/modules/pychopper
creating build/lib/multiqc/modules/pycoqc
copying multiqc/modules/pycoqc/__init__.py -> build/lib/multiqc/modules/pycoqc
copying multiqc/modules/pycoqc/pycoqc.py -> build/lib/multiqc/modules/pycoqc
creating build/lib/multiqc/modules/qc3C
copying multiqc/modules/qc3C/__init__.py -> build/lib/multiqc/modules/qc3C
copying multiqc/modules/qc3C/qc3C.py -> build/lib/multiqc/modules/qc3C
creating build/lib/multiqc/modules/qorts
copying multiqc/modules/qorts/__init__.py -> build/lib/multiqc/modules/qorts
copying multiqc/modules/qorts/qorts.py -> build/lib/multiqc/modules/qorts
creating build/lib/multiqc/modules/qualimap
copying multiqc/modules/qualimap/QM_BamQC.py -> build/lib/multiqc/modules/qualimap
copying multiqc/modules/qualimap/QM_RNASeq.py -> build/lib/multiqc/modules/qualimap
copying multiqc/modules/qualimap/__init__.py -> build/lib/multiqc/modules/qualimap
copying multiqc/modules/qualimap/qualimap.py -> build/lib/multiqc/modules/qualimap
creating build/lib/multiqc/modules/quast
copying multiqc/modules/quast/__init__.py -> build/lib/multiqc/modules/quast
copying multiqc/modules/quast/quast.py -> build/lib/multiqc/modules/quast
creating build/lib/multiqc/modules/rna_seqc
copying multiqc/modules/rna_seqc/__init__.py -> build/lib/multiqc/modules/rna_seqc
copying multiqc/modules/rna_seqc/rna_seqc.py -> build/lib/multiqc/modules/rna_seqc
creating build/lib/multiqc/modules/rockhopper
copying multiqc/modules/rockhopper/__init__.py -> build/lib/multiqc/modules/rockhopper
copying multiqc/modules/rockhopper/rockhopper.py -> build/lib/multiqc/modules/rockhopper
creating build/lib/multiqc/modules/rsem
copying multiqc/modules/rsem/__init__.py -> build/lib/multiqc/modules/rsem
copying multiqc/modules/rsem/rsem.py -> build/lib/multiqc/modules/rsem
creating build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/__init__.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/bam_stat.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/gene_body_coverage.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/infer_experiment.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/inner_distance.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/junction_annotation.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/junction_saturation.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/read_distribution.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/read_duplication.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/read_gc.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/rseqc.py -> build/lib/multiqc/modules/rseqc
copying multiqc/modules/rseqc/tin.py -> build/lib/multiqc/modules/rseqc
creating build/lib/multiqc/modules/salmon
copying multiqc/modules/salmon/__init__.py -> build/lib/multiqc/modules/salmon
copying multiqc/modules/salmon/salmon.py -> build/lib/multiqc/modules/salmon
creating build/lib/multiqc/modules/sambamba
copying multiqc/modules/sambamba/__init__.py -> build/lib/multiqc/modules/sambamba
copying multiqc/modules/sambamba/markdup.py -> build/lib/multiqc/modules/sambamba
copying multiqc/modules/sambamba/sambamba.py -> build/lib/multiqc/modules/sambamba
creating build/lib/multiqc/modules/samblaster
copying multiqc/modules/samblaster/__init__.py -> build/lib/multiqc/modules/samblaster
copying multiqc/modules/samblaster/samblaster.py -> build/lib/multiqc/modules/samblaster
creating build/lib/multiqc/modules/samtools
copying multiqc/modules/samtools/__init__.py -> build/lib/multiqc/modules/samtools
copying multiqc/modules/samtools/coverage.py -> build/lib/multiqc/modules/samtools
copying multiqc/modules/samtools/flagstat.py -> build/lib/multiqc/modules/samtools
copying multiqc/modules/samtools/idxstats.py -> build/lib/multiqc/modules/samtools
copying multiqc/modules/samtools/markdup.py -> build/lib/multiqc/modules/samtools
copying multiqc/modules/samtools/rmdup.py -> build/lib/multiqc/modules/samtools
copying multiqc/modules/samtools/samtools.py -> build/lib/multiqc/modules/samtools
copying multiqc/modules/samtools/stats.py -> build/lib/multiqc/modules/samtools
creating build/lib/multiqc/modules/samtools/tests
copying multiqc/modules/samtools/tests/__init__.py -> build/lib/multiqc/modules/samtools/tests
copying multiqc/modules/samtools/tests/test_flagstat.py -> build/lib/multiqc/modules/samtools/tests
creating build/lib/multiqc/modules/sargasso
copying multiqc/modules/sargasso/__init__.py -> build/lib/multiqc/modules/sargasso
copying multiqc/modules/sargasso/sargasso.py -> build/lib/multiqc/modules/sargasso
creating build/lib/multiqc/modules/seqera_cli
copying multiqc/modules/seqera_cli/__init__.py -> build/lib/multiqc/modules/seqera_cli
copying multiqc/modules/seqera_cli/seqera_cli.py -> build/lib/multiqc/modules/seqera_cli
creating build/lib/multiqc/modules/sequali
copying multiqc/modules/sequali/__init__.py -> build/lib/multiqc/modules/sequali
copying multiqc/modules/sequali/sequali.py -> build/lib/multiqc/modules/sequali
creating build/lib/multiqc/modules/seqwho
copying multiqc/modules/seqwho/__init__.py -> build/lib/multiqc/modules/seqwho
copying multiqc/modules/seqwho/seqwho.py -> build/lib/multiqc/modules/seqwho
creating build/lib/multiqc/modules/seqyclean
copying multiqc/modules/seqyclean/__init__.py -> build/lib/multiqc/modules/seqyclean
copying multiqc/modules/seqyclean/seqyclean.py -> build/lib/multiqc/modules/seqyclean
creating build/lib/multiqc/modules/sexdeterrmine
copying multiqc/modules/sexdeterrmine/__init__.py -> build/lib/multiqc/modules/sexdeterrmine
copying multiqc/modules/sexdeterrmine/sexdeterrmine.py -> build/lib/multiqc/modules/sexdeterrmine
creating build/lib/multiqc/modules/sickle
copying multiqc/modules/sickle/__init__.py -> build/lib/multiqc/modules/sickle
copying multiqc/modules/sickle/sickle.py -> build/lib/multiqc/modules/sickle
creating build/lib/multiqc/modules/skewer
copying multiqc/modules/skewer/__init__.py -> build/lib/multiqc/modules/skewer
copying multiqc/modules/skewer/skewer.py -> build/lib/multiqc/modules/skewer
creating build/lib/multiqc/modules/slamdunk
copying multiqc/modules/slamdunk/__init__.py -> build/lib/multiqc/modules/slamdunk
copying multiqc/modules/slamdunk/slamdunk.py -> build/lib/multiqc/modules/slamdunk
creating build/lib/multiqc/modules/snippy
copying multiqc/modules/snippy/__init__.py -> build/lib/multiqc/modules/snippy
copying multiqc/modules/snippy/snippy.py -> build/lib/multiqc/modules/snippy
creating build/lib/multiqc/modules/snpeff
copying multiqc/modules/snpeff/__init__.py -> build/lib/multiqc/modules/snpeff
copying multiqc/modules/snpeff/snpeff.py -> build/lib/multiqc/modules/snpeff
creating build/lib/multiqc/modules/snpsplit
copying multiqc/modules/snpsplit/__init__.py -> build/lib/multiqc/modules/snpsplit
copying multiqc/modules/snpsplit/snpsplit.py -> build/lib/multiqc/modules/snpsplit
creating build/lib/multiqc/modules/somalier
copying multiqc/modules/somalier/__init__.py -> build/lib/multiqc/modules/somalier
copying multiqc/modules/somalier/somalier.py -> build/lib/multiqc/modules/somalier
creating build/lib/multiqc/modules/sortmerna
copying multiqc/modules/sortmerna/__init__.py -> build/lib/multiqc/modules/sortmerna
copying multiqc/modules/sortmerna/sortmerna.py -> build/lib/multiqc/modules/sortmerna
creating build/lib/multiqc/modules/sourmash
copying multiqc/modules/sourmash/__init__.py -> build/lib/multiqc/modules/sourmash
copying multiqc/modules/sourmash/compare.py -> build/lib/multiqc/modules/sourmash
copying multiqc/modules/sourmash/gather.py -> build/lib/multiqc/modules/sourmash
copying multiqc/modules/sourmash/sourmash.py -> build/lib/multiqc/modules/sourmash
creating build/lib/multiqc/modules/spaceranger
copying multiqc/modules/spaceranger/__init__.py -> build/lib/multiqc/modules/spaceranger
copying multiqc/modules/spaceranger/count.py -> build/lib/multiqc/modules/spaceranger
copying multiqc/modules/spaceranger/spaceranger.py -> build/lib/multiqc/modules/spaceranger
copying multiqc/modules/spaceranger/utils.py -> build/lib/multiqc/modules/spaceranger
creating build/lib/multiqc/modules/stacks
copying multiqc/modules/stacks/__init__.py -> build/lib/multiqc/modules/stacks
copying multiqc/modules/stacks/stacks.py -> build/lib/multiqc/modules/stacks
creating build/lib/multiqc/modules/star
copying multiqc/modules/star/__init__.py -> build/lib/multiqc/modules/star
copying multiqc/modules/star/star.py -> build/lib/multiqc/modules/star
creating build/lib/multiqc/modules/supernova
copying multiqc/modules/supernova/__init__.py -> build/lib/multiqc/modules/supernova
copying multiqc/modules/supernova/supernova.py -> build/lib/multiqc/modules/supernova
creating build/lib/multiqc/modules/theta2
copying multiqc/modules/theta2/__init__.py -> build/lib/multiqc/modules/theta2
copying multiqc/modules/theta2/theta2.py -> build/lib/multiqc/modules/theta2
creating build/lib/multiqc/modules/tophat
copying multiqc/modules/tophat/__init__.py -> build/lib/multiqc/modules/tophat
copying multiqc/modules/tophat/tophat.py -> build/lib/multiqc/modules/tophat
creating build/lib/multiqc/modules/trimmomatic
copying multiqc/modules/trimmomatic/__init__.py -> build/lib/multiqc/modules/trimmomatic
copying multiqc/modules/trimmomatic/trimmomatic.py -> build/lib/multiqc/modules/trimmomatic
creating build/lib/multiqc/modules/truvari
copying multiqc/modules/truvari/__init__.py -> build/lib/multiqc/modules/truvari
copying multiqc/modules/truvari/truvari.py -> build/lib/multiqc/modules/truvari
creating build/lib/multiqc/modules/umicollapse
copying multiqc/modules/umicollapse/__init__.py -> build/lib/multiqc/modules/umicollapse
copying multiqc/modules/umicollapse/umicollapse.py -> build/lib/multiqc/modules/umicollapse
creating build/lib/multiqc/modules/umicollapse/tests
copying multiqc/modules/umicollapse/tests/__init__.py -> build/lib/multiqc/modules/umicollapse/tests
copying multiqc/modules/umicollapse/tests/test_umicollapse.py -> build/lib/multiqc/modules/umicollapse/tests
creating build/lib/multiqc/modules/umitools
copying multiqc/modules/umitools/__init__.py -> build/lib/multiqc/modules/umitools
copying multiqc/modules/umitools/umitools.py -> build/lib/multiqc/modules/umitools
creating build/lib/multiqc/modules/umitools/tests
copying multiqc/modules/umitools/tests/__init__.py -> build/lib/multiqc/modules/umitools/tests
copying multiqc/modules/umitools/tests/test_umitools.py -> build/lib/multiqc/modules/umitools/tests
creating build/lib/multiqc/modules/varscan2
copying multiqc/modules/varscan2/__init__.py -> build/lib/multiqc/modules/varscan2
copying multiqc/modules/varscan2/varscan2.py -> build/lib/multiqc/modules/varscan2
creating build/lib/multiqc/modules/vcftools
copying multiqc/modules/vcftools/__init__.py -> build/lib/multiqc/modules/vcftools
copying multiqc/modules/vcftools/relatedness2.py -> build/lib/multiqc/modules/vcftools
copying multiqc/modules/vcftools/tstv_by_count.py -> build/lib/multiqc/modules/vcftools
copying multiqc/modules/vcftools/tstv_by_qual.py -> build/lib/multiqc/modules/vcftools
copying multiqc/modules/vcftools/tstv_summary.py -> build/lib/multiqc/modules/vcftools
copying multiqc/modules/vcftools/vcftools.py -> build/lib/multiqc/modules/vcftools
creating build/lib/multiqc/modules/vep
copying multiqc/modules/vep/__init__.py -> build/lib/multiqc/modules/vep
copying multiqc/modules/vep/vep.py -> build/lib/multiqc/modules/vep
creating build/lib/multiqc/modules/verifybamid
copying multiqc/modules/verifybamid/__init__.py -> build/lib/multiqc/modules/verifybamid
copying multiqc/modules/verifybamid/verifybamid.py -> build/lib/multiqc/modules/verifybamid
creating build/lib/multiqc/modules/vg
copying multiqc/modules/vg/__init__.py -> build/lib/multiqc/modules/vg
copying multiqc/modules/vg/vg.py -> build/lib/multiqc/modules/vg
creating build/lib/multiqc/modules/whatshap
copying multiqc/modules/whatshap/__init__.py -> build/lib/multiqc/modules/whatshap
copying multiqc/modules/whatshap/whatshap.py -> build/lib/multiqc/modules/whatshap
creating build/lib/multiqc/modules/xengsort
copying multiqc/modules/xengsort/__init__.py -> build/lib/multiqc/modules/xengsort
copying multiqc/modules/xengsort/xengsort.py -> build/lib/multiqc/modules/xengsort
creating build/lib/multiqc/modules/xenome
copying multiqc/modules/xenome/__init__.py -> build/lib/multiqc/modules/xenome
copying multiqc/modules/xenome/xenome.py -> build/lib/multiqc/modules/xenome
creating build/lib/multiqc/plots
copying multiqc/plots/__init__.py -> build/lib/multiqc/plots
copying multiqc/plots/bargraph.py -> build/lib/multiqc/plots
copying multiqc/plots/box.py -> build/lib/multiqc/plots
copying multiqc/plots/heatmap.py -> build/lib/multiqc/plots
copying multiqc/plots/linegraph.py -> build/lib/multiqc/plots
copying multiqc/plots/scatter.py -> build/lib/multiqc/plots
copying multiqc/plots/table.py -> build/lib/multiqc/plots
copying multiqc/plots/table_object.py -> build/lib/multiqc/plots
copying multiqc/plots/violin.py -> build/lib/multiqc/plots
creating build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/__init__.py -> build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/bar.py -> build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/box.py -> build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/heatmap.py -> build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/line.py -> build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/plot.py -> build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/scatter.py -> build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/table.py -> build/lib/multiqc/plots/plotly
copying multiqc/plots/plotly/violin.py -> build/lib/multiqc/plots/plotly
creating build/lib/multiqc/templates
copying multiqc/templates/__init__.py -> build/lib/multiqc/templates
creating build/lib/multiqc/templates/default
copying multiqc/templates/default/__init__.py -> build/lib/multiqc/templates/default
copying multiqc/templates/default/base.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/content.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/foot.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/footer.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/general_stats.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/head.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/header.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/includes.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/nav.html -> build/lib/multiqc/templates/default
copying multiqc/templates/default/toolbox.html -> build/lib/multiqc/templates/default
creating build/lib/multiqc/templates/default/assets/css
copying multiqc/templates/default/assets/css/bootstrap.min.css -> build/lib/multiqc/templates/default/assets/css
copying multiqc/templates/default/assets/css/default_multiqc.css -> build/lib/multiqc/templates/default/assets/css
copying multiqc/templates/default/assets/css/jquery.toast.css -> build/lib/multiqc/templates/default/assets/css
creating build/lib/multiqc/templates/default/assets/fonts
copying multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.eot -> build/lib/multiqc/templates/default/assets/fonts
copying multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.svg -> build/lib/multiqc/templates/default/assets/fonts
copying multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.ttf -> build/lib/multiqc/templates/default/assets/fonts
copying multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.woff -> build/lib/multiqc/templates/default/assets/fonts
copying multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.woff2 -> build/lib/multiqc/templates/default/assets/fonts
creating build/lib/multiqc/templates/default/assets/img
copying multiqc/templates/default/assets/img/MultiQC_logo.png -> build/lib/multiqc/templates/default/assets/img
copying multiqc/templates/default/assets/img/MultiQC_logo_dark.svg -> build/lib/multiqc/templates/default/assets/img
copying multiqc/templates/default/assets/img/favicon-16x16.png -> build/lib/multiqc/templates/default/assets/img
copying multiqc/templates/default/assets/img/favicon-32x32.png -> build/lib/multiqc/templates/default/assets/img
copying multiqc/templates/default/assets/img/favicon-96x96.png -> build/lib/multiqc/templates/default/assets/img
copying multiqc/templates/default/assets/img/seqera_logo.png -> build/lib/multiqc/templates/default/assets/img
copying multiqc/templates/default/assets/img/seqera_logo_mono.png -> build/lib/multiqc/templates/default/assets/img
creating build/lib/multiqc/templates/default/assets/js
copying multiqc/templates/default/assets/js/decompress.js -> build/lib/multiqc/templates/default/assets/js
copying multiqc/templates/default/assets/js/flat.js -> build/lib/multiqc/templates/default/assets/js
copying multiqc/templates/default/assets/js/multiqc.js -> build/lib/multiqc/templates/default/assets/js
copying multiqc/templates/default/assets/js/plotting.js -> build/lib/multiqc/templates/default/assets/js
copying multiqc/templates/default/assets/js/render.js -> build/lib/multiqc/templates/default/assets/js
copying multiqc/templates/default/assets/js/tables.js -> build/lib/multiqc/templates/default/assets/js
copying multiqc/templates/default/assets/js/toolbox.js -> build/lib/multiqc/templates/default/assets/js
creating build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/FileSaver.min.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/bootstrap.min.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/jquery-3.1.1.min.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/jquery-ui.min.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/jquery.tablesorter.min.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/jquery.toast.min.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/jszip.min.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/pako_inflate.min.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/plotly-2.27.0.js -> build/lib/multiqc/templates/default/assets/js/packages
copying multiqc/templates/default/assets/js/packages/plotly-2.27.0.min.js -> build/lib/multiqc/templates/default/assets/js/packages
creating build/lib/multiqc/templates/default/assets/js/plots
copying multiqc/templates/default/assets/js/plots/bar.js -> build/lib/multiqc/templates/default/assets/js/plots
copying multiqc/templates/default/assets/js/plots/box.js -> build/lib/multiqc/templates/default/assets/js/plots
copying multiqc/templates/default/assets/js/plots/heatmap.js -> build/lib/multiqc/templates/default/assets/js/plots
copying multiqc/templates/default/assets/js/plots/line.js -> build/lib/multiqc/templates/default/assets/js/plots
copying multiqc/templates/default/assets/js/plots/scatter.js -> build/lib/multiqc/templates/default/assets/js/plots
copying multiqc/templates/default/assets/js/plots/violin.js -> build/lib/multiqc/templates/default/assets/js/plots
creating build/lib/multiqc/templates/gathered
copying multiqc/templates/gathered/__init__.py -> build/lib/multiqc/templates/gathered
copying multiqc/templates/gathered/content.html -> build/lib/multiqc/templates/gathered
copying multiqc/templates/gathered/nav.html -> build/lib/multiqc/templates/gathered
creating build/lib/multiqc/templates/geo
copying multiqc/templates/geo/__init__.py -> build/lib/multiqc/templates/geo
copying multiqc/templates/geo/includes.html -> build/lib/multiqc/templates/geo
creating build/lib/multiqc/templates/geo/assets/css
copying multiqc/templates/geo/assets/css/bootstrap.min.css -> build/lib/multiqc/templates/geo/assets/css
creating build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/emailme.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/flames.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/glyphicons-halflings-white.png -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/glyphicons-halflings.png -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/hot.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/mchammer.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/microfab.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/new.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/new2.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/progress.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/rainbow.gif -> build/lib/multiqc/templates/geo/assets/img
copying multiqc/templates/geo/assets/img/stars.gif -> build/lib/multiqc/templates/geo/assets/img
creating build/lib/multiqc/templates/sections
copying multiqc/templates/sections/__init__.py -> build/lib/multiqc/templates/sections
copying multiqc/templates/sections/content.html -> build/lib/multiqc/templates/sections
creating build/lib/multiqc/templates/simple
copying multiqc/templates/simple/__init__.py -> build/lib/multiqc/templates/simple
copying multiqc/templates/simple/foot.html -> build/lib/multiqc/templates/simple
copying multiqc/templates/simple/footer.html -> build/lib/multiqc/templates/simple
copying multiqc/templates/simple/header.html -> build/lib/multiqc/templates/simple
copying multiqc/templates/simple/includes.html -> build/lib/multiqc/templates/simple
copying multiqc/templates/simple/nav.html -> build/lib/multiqc/templates/simple
copying multiqc/templates/simple/toolbox.html -> build/lib/multiqc/templates/simple
creating build/lib/multiqc/utils
copying multiqc/utils/__init__.py -> build/lib/multiqc/utils
copying multiqc/utils/config.py -> build/lib/multiqc/utils
copying multiqc/utils/megaqc.py -> build/lib/multiqc/utils
copying multiqc/utils/mqc_colour.py -> build/lib/multiqc/utils
copying multiqc/utils/pyaml_env.py -> build/lib/multiqc/utils
copying multiqc/utils/report.py -> build/lib/multiqc/utils
copying multiqc/utils/testing.py -> build/lib/multiqc/utils
copying multiqc/utils/util_functions.py -> build/lib/multiqc/utils
installing to build/bdist.solaris-2.11-i86pc.64bit/wheel
running install
running install_lib
creating build/bdist.solaris-2.11-i86pc.64bit/wheel
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc
copying build/lib/multiqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/__main__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/base_module.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/config.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/interactive.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/report.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/types.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/validation.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/multiqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/config_defaults.yaml -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/py.typed -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
copying build/lib/multiqc/search_patterns.yaml -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/core
copying build/lib/multiqc/core/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/exceptions.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/exec_modules.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/file_search.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/log_and_rich.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/order_modules_and_sections.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/plugin_hooks.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/software_versions.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/strict_helpers.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/tmp_dir.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/update_config.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/version_check.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
copying build/lib/multiqc/core/write_results.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/core
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules
copying build/lib/multiqc/modules/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules
copying build/lib/multiqc/modules/profile_runtime.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules
copying build/lib/multiqc/modules/software_versions.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/adapterremoval
copying build/lib/multiqc/modules/adapterremoval/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/adapterremoval
copying build/lib/multiqc/modules/adapterremoval/adapterremoval.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/adapterremoval
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/afterqc
copying build/lib/multiqc/modules/afterqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/afterqc
copying build/lib/multiqc/modules/afterqc/afterqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/afterqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/anglerfish
copying build/lib/multiqc/modules/anglerfish/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/anglerfish
copying build/lib/multiqc/modules/anglerfish/anglerfish.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/anglerfish
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bakta
copying build/lib/multiqc/modules/bakta/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bakta
copying build/lib/multiqc/modules/bakta/bakta.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bakta
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bamdst
copying build/lib/multiqc/modules/bamdst/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bamdst
copying build/lib/multiqc/modules/bamdst/bamdst.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bamdst
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bamtools
copying build/lib/multiqc/modules/bamtools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bamtools
copying build/lib/multiqc/modules/bamtools/bamtools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bamtools
copying build/lib/multiqc/modules/bamtools/stats.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bamtools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bbduk
copying build/lib/multiqc/modules/bbduk/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbduk
copying build/lib/multiqc/modules/bbduk/bbduk.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbduk
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/bbmap.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/bbmap_filetypes.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_aqhist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_basic_hist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_bhist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_bqhist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_covhist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_idhist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_ihist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_indelhist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_mhist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_qahist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_qchist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
copying build/lib/multiqc/modules/bbmap/plot_qhist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bbmap
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bcftools
copying build/lib/multiqc/modules/bcftools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bcftools
copying build/lib/multiqc/modules/bcftools/bcftools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bcftools
copying build/lib/multiqc/modules/bcftools/stats.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bcftools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bcl2fastq
copying build/lib/multiqc/modules/bcl2fastq/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bcl2fastq
copying build/lib/multiqc/modules/bcl2fastq/bcl2fastq.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bcl2fastq
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bclconvert
copying build/lib/multiqc/modules/bclconvert/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bclconvert
copying build/lib/multiqc/modules/bclconvert/bclconvert.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bclconvert
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/biobambam2
copying build/lib/multiqc/modules/biobambam2/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/biobambam2
copying build/lib/multiqc/modules/biobambam2/biobambam2.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/biobambam2
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/biobloomtools
copying build/lib/multiqc/modules/biobloomtools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/biobloomtools
copying build/lib/multiqc/modules/biobloomtools/biobloomtools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/biobloomtools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/biscuit
copying build/lib/multiqc/modules/biscuit/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/biscuit
copying build/lib/multiqc/modules/biscuit/biscuit.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/biscuit
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bismark
copying build/lib/multiqc/modules/bismark/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bismark
copying build/lib/multiqc/modules/bismark/bismark.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bismark
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bowtie1
copying build/lib/multiqc/modules/bowtie1/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bowtie1
copying build/lib/multiqc/modules/bowtie1/bowtie1.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bowtie1
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bowtie2
copying build/lib/multiqc/modules/bowtie2/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bowtie2
copying build/lib/multiqc/modules/bowtie2/bowtie2.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bowtie2
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/busco
copying build/lib/multiqc/modules/busco/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/busco
copying build/lib/multiqc/modules/busco/busco.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/busco
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/bustools
copying build/lib/multiqc/modules/bustools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bustools
copying build/lib/multiqc/modules/bustools/bustools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/bustools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/ccs
copying build/lib/multiqc/modules/ccs/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ccs
copying build/lib/multiqc/modules/ccs/ccs.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ccs
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/ccs/tests
copying build/lib/multiqc/modules/ccs/tests/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ccs/tests
copying build/lib/multiqc/modules/ccs/tests/test_ccs.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ccs/tests
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/cellranger
copying build/lib/multiqc/modules/cellranger/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/cellranger
copying build/lib/multiqc/modules/cellranger/cellranger.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/cellranger
copying build/lib/multiqc/modules/cellranger/count.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/cellranger
copying build/lib/multiqc/modules/cellranger/utils.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/cellranger
copying build/lib/multiqc/modules/cellranger/vdj.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/cellranger
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/checkqc
copying build/lib/multiqc/modules/checkqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/checkqc
copying build/lib/multiqc/modules/checkqc/checkqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/checkqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/clipandmerge
copying build/lib/multiqc/modules/clipandmerge/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/clipandmerge
copying build/lib/multiqc/modules/clipandmerge/clipandmerge.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/clipandmerge
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/clusterflow
copying build/lib/multiqc/modules/clusterflow/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/clusterflow
copying build/lib/multiqc/modules/clusterflow/clusterflow.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/clusterflow
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/conpair
copying build/lib/multiqc/modules/conpair/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/conpair
copying build/lib/multiqc/modules/conpair/conpair.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/conpair
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/custom_content
copying build/lib/multiqc/modules/custom_content/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/custom_content
copying build/lib/multiqc/modules/custom_content/custom_content.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/custom_content
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/cutadapt
copying build/lib/multiqc/modules/cutadapt/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/cutadapt
copying build/lib/multiqc/modules/cutadapt/cutadapt.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/cutadapt
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/damageprofiler
copying build/lib/multiqc/modules/damageprofiler/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/damageprofiler
copying build/lib/multiqc/modules/damageprofiler/damageprofiler.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/damageprofiler
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/dedup
copying build/lib/multiqc/modules/dedup/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dedup
copying build/lib/multiqc/modules/dedup/dedup.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dedup
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/bamPEFragmentSizeDistribution.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/bamPEFragmentSizeTable.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/deeptools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/estimateReadFiltering.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/plotCorrelation.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/plotCoverage.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/plotEnrichment.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/plotFingerprint.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/plotPCA.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
copying build/lib/multiqc/modules/deeptools/plotProfile.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/deeptools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/diamond
copying build/lib/multiqc/modules/diamond/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/diamond
copying build/lib/multiqc/modules/diamond/diamond.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/diamond
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/disambiguate
copying build/lib/multiqc/modules/disambiguate/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/disambiguate
copying build/lib/multiqc/modules/disambiguate/disambiguate.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/disambiguate
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/coverage_hist.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/coverage_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/coverage_per_contig.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/dragen.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/dragen_gc_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/fragment_length.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/mapping_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/overall_mean_cov.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/ploidy_estimation_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/rna_quant_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/rna_transcript_cov.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/sc_atac_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/sc_rna_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/time_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/trimmer_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/utils.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
copying build/lib/multiqc/modules/dragen/vc_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/dragen/tests
copying build/lib/multiqc/modules/dragen/tests/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen/tests
copying build/lib/multiqc/modules/dragen/tests/test_dragen.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen/tests
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/dragen_fastqc
copying build/lib/multiqc/modules/dragen_fastqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen_fastqc
copying build/lib/multiqc/modules/dragen_fastqc/base_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen_fastqc
copying build/lib/multiqc/modules/dragen_fastqc/content_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen_fastqc
copying build/lib/multiqc/modules/dragen_fastqc/dragen_fastqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen_fastqc
copying build/lib/multiqc/modules/dragen_fastqc/gc_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen_fastqc
copying build/lib/multiqc/modules/dragen_fastqc/read_metrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen_fastqc
copying build/lib/multiqc/modules/dragen_fastqc/util.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen_fastqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/dragen_fastqc/assets
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/dragen_fastqc/assets/js
copying build/lib/multiqc/modules/dragen_fastqc/assets/js/multiqc_dragen_fastqc.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/dragen_fastqc/assets/js
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/eigenstratdatabasetools
copying build/lib/multiqc/modules/eigenstratdatabasetools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/eigenstratdatabasetools
copying build/lib/multiqc/modules/eigenstratdatabasetools/eigenstratdatabasetools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/eigenstratdatabasetools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/fastp
copying build/lib/multiqc/modules/fastp/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastp
copying build/lib/multiqc/modules/fastp/fastp.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastp
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/fastq_screen
copying build/lib/multiqc/modules/fastq_screen/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastq_screen
copying build/lib/multiqc/modules/fastq_screen/fastq_screen.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastq_screen
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/fastqc
copying build/lib/multiqc/modules/fastqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastqc
copying build/lib/multiqc/modules/fastqc/fastqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/fastqc/assets
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/fastqc/assets/css
copying build/lib/multiqc/modules/fastqc/assets/css/multiqc_fastqc.css -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastqc/assets/css
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/fastqc/assets/js
copying build/lib/multiqc/modules/fastqc/assets/js/multiqc_fastqc.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastqc/assets/js
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/fastqc/fastqc_theoretical_gc
copying build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_genome.txt -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastqc/fastqc_theoretical_gc
copying build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_txome.txt -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastqc/fastqc_theoretical_gc
copying build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_genome.txt -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastqc/fastqc_theoretical_gc
copying build/lib/multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_txome.txt -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fastqc/fastqc_theoretical_gc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/featurecounts
copying build/lib/multiqc/modules/featurecounts/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/featurecounts
copying build/lib/multiqc/modules/featurecounts/featurecounts.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/featurecounts
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/fgbio
copying build/lib/multiqc/modules/fgbio/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fgbio
copying build/lib/multiqc/modules/fgbio/error_rate_by_read_position.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fgbio
copying build/lib/multiqc/modules/fgbio/fgbio.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fgbio
copying build/lib/multiqc/modules/fgbio/group_reads_by_umi.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/fgbio
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/filtlong
copying build/lib/multiqc/modules/filtlong/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/filtlong
copying build/lib/multiqc/modules/filtlong/filtlong.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/filtlong
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/flash
copying build/lib/multiqc/modules/flash/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/flash
copying build/lib/multiqc/modules/flash/flash.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/flash
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/flexbar
copying build/lib/multiqc/modules/flexbar/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/flexbar
copying build/lib/multiqc/modules/flexbar/flexbar.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/flexbar
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/freyja
copying build/lib/multiqc/modules/freyja/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/freyja
copying build/lib/multiqc/modules/freyja/freyja.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/freyja
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/ganon
copying build/lib/multiqc/modules/ganon/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ganon
copying build/lib/multiqc/modules/ganon/ganon.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ganon
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/gatk
copying build/lib/multiqc/modules/gatk/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gatk
copying build/lib/multiqc/modules/gatk/analyze_saturation_mutagenesis.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gatk
copying build/lib/multiqc/modules/gatk/base_recalibrator.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gatk
copying build/lib/multiqc/modules/gatk/gatk.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gatk
copying build/lib/multiqc/modules/gatk/varianteval.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gatk
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/gffcompare
copying build/lib/multiqc/modules/gffcompare/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gffcompare
copying build/lib/multiqc/modules/gffcompare/gffcompare.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gffcompare
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/glimpse
copying build/lib/multiqc/modules/glimpse/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/glimpse
copying build/lib/multiqc/modules/glimpse/err_grp.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/glimpse
copying build/lib/multiqc/modules/glimpse/err_spl.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/glimpse
copying build/lib/multiqc/modules/glimpse/glimpse.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/glimpse
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/goleft_indexcov
copying build/lib/multiqc/modules/goleft_indexcov/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/goleft_indexcov
copying build/lib/multiqc/modules/goleft_indexcov/goleft_indexcov.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/goleft_indexcov
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/gopeaks
copying build/lib/multiqc/modules/gopeaks/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gopeaks
copying build/lib/multiqc/modules/gopeaks/gopeaks.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/gopeaks
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/haplocheck
copying build/lib/multiqc/modules/haplocheck/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/haplocheck
copying build/lib/multiqc/modules/haplocheck/haplocheck.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/haplocheck
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/happy
copying build/lib/multiqc/modules/happy/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/happy
copying build/lib/multiqc/modules/happy/happy.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/happy
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/hicexplorer
copying build/lib/multiqc/modules/hicexplorer/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hicexplorer
copying build/lib/multiqc/modules/hicexplorer/hicexplorer.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hicexplorer
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/hicpro
copying build/lib/multiqc/modules/hicpro/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hicpro
copying build/lib/multiqc/modules/hicpro/hicpro.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hicpro
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/hicup
copying build/lib/multiqc/modules/hicup/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hicup
copying build/lib/multiqc/modules/hicup/hicup.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hicup
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/hifiasm
copying build/lib/multiqc/modules/hifiasm/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hifiasm
copying build/lib/multiqc/modules/hifiasm/hifiasm.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hifiasm
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/hisat2
copying build/lib/multiqc/modules/hisat2/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hisat2
copying build/lib/multiqc/modules/hisat2/hisat2.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hisat2
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/homer
copying build/lib/multiqc/modules/homer/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/homer
copying build/lib/multiqc/modules/homer/findpeaks.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/homer
copying build/lib/multiqc/modules/homer/homer.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/homer
copying build/lib/multiqc/modules/homer/tagdirectory.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/homer
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/hops
copying build/lib/multiqc/modules/hops/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hops
copying build/lib/multiqc/modules/hops/hops.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hops
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/hostile
copying build/lib/multiqc/modules/hostile/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hostile
copying build/lib/multiqc/modules/hostile/hostile.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/hostile
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/htseq
copying build/lib/multiqc/modules/htseq/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/htseq
copying build/lib/multiqc/modules/htseq/htseq.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/htseq
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/humid
copying build/lib/multiqc/modules/humid/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/humid
copying build/lib/multiqc/modules/humid/clusters.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/humid
copying build/lib/multiqc/modules/humid/counts.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/humid
copying build/lib/multiqc/modules/humid/humid.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/humid
copying build/lib/multiqc/modules/humid/neighbours.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/humid
copying build/lib/multiqc/modules/humid/stats.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/humid
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/interop
copying build/lib/multiqc/modules/interop/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/interop
copying build/lib/multiqc/modules/interop/interop.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/interop
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/isoseq
copying build/lib/multiqc/modules/isoseq/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/isoseq
copying build/lib/multiqc/modules/isoseq/isoseq.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/isoseq
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/ivar
copying build/lib/multiqc/modules/ivar/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ivar
copying build/lib/multiqc/modules/ivar/ivar.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ivar
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/jcvi
copying build/lib/multiqc/modules/jcvi/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/jcvi
copying build/lib/multiqc/modules/jcvi/jcvi.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/jcvi
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/jellyfish
copying build/lib/multiqc/modules/jellyfish/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/jellyfish
copying build/lib/multiqc/modules/jellyfish/jellyfish.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/jellyfish
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/kaiju
copying build/lib/multiqc/modules/kaiju/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/kaiju
copying build/lib/multiqc/modules/kaiju/kaiju.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/kaiju
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/kallisto
copying build/lib/multiqc/modules/kallisto/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/kallisto
copying build/lib/multiqc/modules/kallisto/kallisto.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/kallisto
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/kat
copying build/lib/multiqc/modules/kat/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/kat
copying build/lib/multiqc/modules/kat/kat.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/kat
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/kraken
copying build/lib/multiqc/modules/kraken/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/kraken
copying build/lib/multiqc/modules/kraken/kraken.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/kraken
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/leehom
copying build/lib/multiqc/modules/leehom/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/leehom
copying build/lib/multiqc/modules/leehom/leehom.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/leehom
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/librarian
copying build/lib/multiqc/modules/librarian/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/librarian
copying build/lib/multiqc/modules/librarian/librarian.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/librarian
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/lima
copying build/lib/multiqc/modules/lima/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/lima
copying build/lib/multiqc/modules/lima/lima.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/lima
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/longranger
copying build/lib/multiqc/modules/longranger/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/longranger
copying build/lib/multiqc/modules/longranger/longranger.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/longranger
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/macs2
copying build/lib/multiqc/modules/macs2/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/macs2
copying build/lib/multiqc/modules/macs2/macs2.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/macs2
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/malt
copying build/lib/multiqc/modules/malt/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/malt
copying build/lib/multiqc/modules/malt/malt.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/malt
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/mapdamage
copying build/lib/multiqc/modules/mapdamage/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mapdamage
copying build/lib/multiqc/modules/mapdamage/mapdamage.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mapdamage
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/megahit
copying build/lib/multiqc/modules/megahit/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/megahit
copying build/lib/multiqc/modules/megahit/megahit.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/megahit
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/metaphlan
copying build/lib/multiqc/modules/metaphlan/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/metaphlan
copying build/lib/multiqc/modules/metaphlan/metaphlan.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/metaphlan
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/methylqa
copying build/lib/multiqc/modules/methylqa/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/methylqa
copying build/lib/multiqc/modules/methylqa/methylqa.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/methylqa
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/minionqc
copying build/lib/multiqc/modules/minionqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/minionqc
copying build/lib/multiqc/modules/minionqc/minionqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/minionqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/mirtop
copying build/lib/multiqc/modules/mirtop/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mirtop
copying build/lib/multiqc/modules/mirtop/mirtop.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mirtop
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/mirtrace
copying build/lib/multiqc/modules/mirtrace/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mirtrace
copying build/lib/multiqc/modules/mirtrace/mirtrace.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mirtrace
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/mosdepth
copying build/lib/multiqc/modules/mosdepth/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mosdepth
copying build/lib/multiqc/modules/mosdepth/mosdepth.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mosdepth
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/motus
copying build/lib/multiqc/modules/motus/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/motus
copying build/lib/multiqc/modules/motus/motus.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/motus
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/mtnucratio
copying build/lib/multiqc/modules/mtnucratio/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mtnucratio
copying build/lib/multiqc/modules/mtnucratio/mtnucratio.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/mtnucratio
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/multivcfanalyzer
copying build/lib/multiqc/modules/multivcfanalyzer/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/multivcfanalyzer
copying build/lib/multiqc/modules/multivcfanalyzer/multivcfanalyzer.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/multivcfanalyzer
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/nanoq
copying build/lib/multiqc/modules/nanoq/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/nanoq
copying build/lib/multiqc/modules/nanoq/nanoq.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/nanoq
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/nanostat
copying build/lib/multiqc/modules/nanostat/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/nanostat
copying build/lib/multiqc/modules/nanostat/nanostat.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/nanostat
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/nextclade
copying build/lib/multiqc/modules/nextclade/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/nextclade
copying build/lib/multiqc/modules/nextclade/nextclade.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/nextclade
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/ngsbits
copying build/lib/multiqc/modules/ngsbits/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ngsbits
copying build/lib/multiqc/modules/ngsbits/mappingqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ngsbits
copying build/lib/multiqc/modules/ngsbits/ngsbits.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ngsbits
copying build/lib/multiqc/modules/ngsbits/readqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ngsbits
copying build/lib/multiqc/modules/ngsbits/samplegender.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ngsbits
copying build/lib/multiqc/modules/ngsbits/utils.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ngsbits
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/ngsderive
copying build/lib/multiqc/modules/ngsderive/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ngsderive
copying build/lib/multiqc/modules/ngsderive/ngsderive.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/ngsderive
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/nonpareil
copying build/lib/multiqc/modules/nonpareil/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/nonpareil
copying build/lib/multiqc/modules/nonpareil/nonpareil.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/nonpareil
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/odgi
copying build/lib/multiqc/modules/odgi/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/odgi
copying build/lib/multiqc/modules/odgi/odgi.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/odgi
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/optitype
copying build/lib/multiqc/modules/optitype/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/optitype
copying build/lib/multiqc/modules/optitype/optitype.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/optitype
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/pairtools
copying build/lib/multiqc/modules/pairtools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pairtools
copying build/lib/multiqc/modules/pairtools/pairtools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pairtools
copying build/lib/multiqc/modules/pairtools/params.yml -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pairtools
copying build/lib/multiqc/modules/pairtools/utils.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pairtools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/pangolin
copying build/lib/multiqc/modules/pangolin/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pangolin
copying build/lib/multiqc/modules/pangolin/pangolin.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pangolin
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/pbmarkdup
copying build/lib/multiqc/modules/pbmarkdup/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pbmarkdup
copying build/lib/multiqc/modules/pbmarkdup/pbmarkdup.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pbmarkdup
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/peddy
copying build/lib/multiqc/modules/peddy/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/peddy
copying build/lib/multiqc/modules/peddy/peddy.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/peddy
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/phantompeakqualtools
copying build/lib/multiqc/modules/phantompeakqualtools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/phantompeakqualtools
copying build/lib/multiqc/modules/phantompeakqualtools/phantompeakqualtools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/phantompeakqualtools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/picard
copying build/lib/multiqc/modules/picard/AlignmentSummaryMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/BaseDistributionByCycleMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/CrosscheckFingerprints.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/ExtractIlluminaBarcodes.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/GcBiasMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/HsMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/IlluminaBasecallingMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/IlluminaLaneMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/InsertSizeMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/MarkDuplicates.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/MarkIlluminaAdapters.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/OxoGMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/QualityByCycleMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/QualityScoreDistributionMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/QualityYieldMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/RnaSeqMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/RrbsSummaryMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/TargetedPcrMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/ValidateSamFile.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/VariantCallingMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/WgsMetrics.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/picard.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
copying build/lib/multiqc/modules/picard/util.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/picard/tests
copying build/lib/multiqc/modules/picard/tests/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard/tests
copying build/lib/multiqc/modules/picard/tests/test_picard.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/picard/tests
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/porechop
copying build/lib/multiqc/modules/porechop/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/porechop
copying build/lib/multiqc/modules/porechop/porechop.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/porechop
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/preseq
copying build/lib/multiqc/modules/preseq/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/preseq
copying build/lib/multiqc/modules/preseq/preseq.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/preseq
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/prinseqplusplus
copying build/lib/multiqc/modules/prinseqplusplus/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/prinseqplusplus
copying build/lib/multiqc/modules/prinseqplusplus/prinseqplusplus.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/prinseqplusplus
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/prokka
copying build/lib/multiqc/modules/prokka/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/prokka
copying build/lib/multiqc/modules/prokka/prokka.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/prokka
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/purple
copying build/lib/multiqc/modules/purple/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/purple
copying build/lib/multiqc/modules/purple/purple.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/purple
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/pychopper
copying build/lib/multiqc/modules/pychopper/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pychopper
copying build/lib/multiqc/modules/pychopper/pychopper.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pychopper
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/pycoqc
copying build/lib/multiqc/modules/pycoqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pycoqc
copying build/lib/multiqc/modules/pycoqc/pycoqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/pycoqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/qc3C
copying build/lib/multiqc/modules/qc3C/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/qc3C
copying build/lib/multiqc/modules/qc3C/qc3C.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/qc3C
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/qorts
copying build/lib/multiqc/modules/qorts/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/qorts
copying build/lib/multiqc/modules/qorts/qorts.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/qorts
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/qualimap
copying build/lib/multiqc/modules/qualimap/QM_BamQC.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/qualimap
copying build/lib/multiqc/modules/qualimap/QM_RNASeq.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/qualimap
copying build/lib/multiqc/modules/qualimap/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/qualimap
copying build/lib/multiqc/modules/qualimap/qualimap.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/qualimap
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/quast
copying build/lib/multiqc/modules/quast/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/quast
copying build/lib/multiqc/modules/quast/quast.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/quast
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/rna_seqc
copying build/lib/multiqc/modules/rna_seqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rna_seqc
copying build/lib/multiqc/modules/rna_seqc/rna_seqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rna_seqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/rockhopper
copying build/lib/multiqc/modules/rockhopper/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rockhopper
copying build/lib/multiqc/modules/rockhopper/rockhopper.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rockhopper
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/rsem
copying build/lib/multiqc/modules/rsem/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rsem
copying build/lib/multiqc/modules/rsem/rsem.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rsem
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/bam_stat.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/gene_body_coverage.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/infer_experiment.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/inner_distance.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/junction_annotation.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/junction_saturation.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/read_distribution.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/read_duplication.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/read_gc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/rseqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
copying build/lib/multiqc/modules/rseqc/tin.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/rseqc
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/salmon
copying build/lib/multiqc/modules/salmon/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/salmon
copying build/lib/multiqc/modules/salmon/salmon.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/salmon
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/sambamba
copying build/lib/multiqc/modules/sambamba/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sambamba
copying build/lib/multiqc/modules/sambamba/markdup.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sambamba
copying build/lib/multiqc/modules/sambamba/sambamba.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sambamba
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/samblaster
copying build/lib/multiqc/modules/samblaster/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samblaster
copying build/lib/multiqc/modules/samblaster/samblaster.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samblaster
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/samtools
copying build/lib/multiqc/modules/samtools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools
copying build/lib/multiqc/modules/samtools/coverage.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools
copying build/lib/multiqc/modules/samtools/flagstat.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools
copying build/lib/multiqc/modules/samtools/idxstats.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools
copying build/lib/multiqc/modules/samtools/markdup.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools
copying build/lib/multiqc/modules/samtools/rmdup.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools
copying build/lib/multiqc/modules/samtools/samtools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools
copying build/lib/multiqc/modules/samtools/stats.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/samtools/tests
copying build/lib/multiqc/modules/samtools/tests/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools/tests
copying build/lib/multiqc/modules/samtools/tests/test_flagstat.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/samtools/tests
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/sargasso
copying build/lib/multiqc/modules/sargasso/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sargasso
copying build/lib/multiqc/modules/sargasso/sargasso.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sargasso
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/seqera_cli
copying build/lib/multiqc/modules/seqera_cli/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/seqera_cli
copying build/lib/multiqc/modules/seqera_cli/seqera_cli.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/seqera_cli
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/sequali
copying build/lib/multiqc/modules/sequali/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sequali
copying build/lib/multiqc/modules/sequali/sequali.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sequali
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/seqwho
copying build/lib/multiqc/modules/seqwho/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/seqwho
copying build/lib/multiqc/modules/seqwho/seqwho.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/seqwho
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/seqyclean
copying build/lib/multiqc/modules/seqyclean/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/seqyclean
copying build/lib/multiqc/modules/seqyclean/seqyclean.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/seqyclean
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/sexdeterrmine
copying build/lib/multiqc/modules/sexdeterrmine/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sexdeterrmine
copying build/lib/multiqc/modules/sexdeterrmine/sexdeterrmine.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sexdeterrmine
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/sickle
copying build/lib/multiqc/modules/sickle/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sickle
copying build/lib/multiqc/modules/sickle/sickle.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sickle
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/skewer
copying build/lib/multiqc/modules/skewer/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/skewer
copying build/lib/multiqc/modules/skewer/skewer.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/skewer
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/slamdunk
copying build/lib/multiqc/modules/slamdunk/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/slamdunk
copying build/lib/multiqc/modules/slamdunk/slamdunk.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/slamdunk
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/snippy
copying build/lib/multiqc/modules/snippy/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/snippy
copying build/lib/multiqc/modules/snippy/snippy.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/snippy
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/snpeff
copying build/lib/multiqc/modules/snpeff/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/snpeff
copying build/lib/multiqc/modules/snpeff/snpeff.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/snpeff
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/snpsplit
copying build/lib/multiqc/modules/snpsplit/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/snpsplit
copying build/lib/multiqc/modules/snpsplit/snpsplit.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/snpsplit
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/somalier
copying build/lib/multiqc/modules/somalier/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/somalier
copying build/lib/multiqc/modules/somalier/somalier.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/somalier
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/sortmerna
copying build/lib/multiqc/modules/sortmerna/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sortmerna
copying build/lib/multiqc/modules/sortmerna/sortmerna.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sortmerna
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/sourmash
copying build/lib/multiqc/modules/sourmash/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sourmash
copying build/lib/multiqc/modules/sourmash/compare.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sourmash
copying build/lib/multiqc/modules/sourmash/gather.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sourmash
copying build/lib/multiqc/modules/sourmash/sourmash.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/sourmash
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/spaceranger
copying build/lib/multiqc/modules/spaceranger/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/spaceranger
copying build/lib/multiqc/modules/spaceranger/count.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/spaceranger
copying build/lib/multiqc/modules/spaceranger/spaceranger.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/spaceranger
copying build/lib/multiqc/modules/spaceranger/utils.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/spaceranger
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/stacks
copying build/lib/multiqc/modules/stacks/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/stacks
copying build/lib/multiqc/modules/stacks/stacks.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/stacks
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/star
copying build/lib/multiqc/modules/star/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/star
copying build/lib/multiqc/modules/star/star.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/star
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/supernova
copying build/lib/multiqc/modules/supernova/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/supernova
copying build/lib/multiqc/modules/supernova/supernova.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/supernova
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/theta2
copying build/lib/multiqc/modules/theta2/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/theta2
copying build/lib/multiqc/modules/theta2/theta2.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/theta2
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/tophat
copying build/lib/multiqc/modules/tophat/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/tophat
copying build/lib/multiqc/modules/tophat/tophat.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/tophat
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/trimmomatic
copying build/lib/multiqc/modules/trimmomatic/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/trimmomatic
copying build/lib/multiqc/modules/trimmomatic/trimmomatic.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/trimmomatic
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/truvari
copying build/lib/multiqc/modules/truvari/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/truvari
copying build/lib/multiqc/modules/truvari/truvari.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/truvari
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/umicollapse
copying build/lib/multiqc/modules/umicollapse/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/umicollapse
copying build/lib/multiqc/modules/umicollapse/umicollapse.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/umicollapse
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/umicollapse/tests
copying build/lib/multiqc/modules/umicollapse/tests/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/umicollapse/tests
copying build/lib/multiqc/modules/umicollapse/tests/test_umicollapse.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/umicollapse/tests
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/umitools
copying build/lib/multiqc/modules/umitools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/umitools
copying build/lib/multiqc/modules/umitools/umitools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/umitools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/umitools/tests
copying build/lib/multiqc/modules/umitools/tests/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/umitools/tests
copying build/lib/multiqc/modules/umitools/tests/test_umitools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/umitools/tests
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/varscan2
copying build/lib/multiqc/modules/varscan2/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/varscan2
copying build/lib/multiqc/modules/varscan2/varscan2.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/varscan2
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/vcftools
copying build/lib/multiqc/modules/vcftools/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vcftools
copying build/lib/multiqc/modules/vcftools/relatedness2.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vcftools
copying build/lib/multiqc/modules/vcftools/tstv_by_count.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vcftools
copying build/lib/multiqc/modules/vcftools/tstv_by_qual.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vcftools
copying build/lib/multiqc/modules/vcftools/tstv_summary.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vcftools
copying build/lib/multiqc/modules/vcftools/vcftools.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vcftools
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/vep
copying build/lib/multiqc/modules/vep/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vep
copying build/lib/multiqc/modules/vep/vep.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vep
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/verifybamid
copying build/lib/multiqc/modules/verifybamid/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/verifybamid
copying build/lib/multiqc/modules/verifybamid/verifybamid.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/verifybamid
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/vg
copying build/lib/multiqc/modules/vg/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vg
copying build/lib/multiqc/modules/vg/vg.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/vg
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/whatshap
copying build/lib/multiqc/modules/whatshap/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/whatshap
copying build/lib/multiqc/modules/whatshap/whatshap.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/whatshap
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/xengsort
copying build/lib/multiqc/modules/xengsort/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/xengsort
copying build/lib/multiqc/modules/xengsort/xengsort.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/xengsort
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/modules/xenome
copying build/lib/multiqc/modules/xenome/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/xenome
copying build/lib/multiqc/modules/xenome/xenome.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/modules/xenome
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/plots
copying build/lib/multiqc/plots/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
copying build/lib/multiqc/plots/bargraph.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
copying build/lib/multiqc/plots/box.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
copying build/lib/multiqc/plots/heatmap.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
copying build/lib/multiqc/plots/linegraph.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
copying build/lib/multiqc/plots/scatter.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
copying build/lib/multiqc/plots/table.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
copying build/lib/multiqc/plots/table_object.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
copying build/lib/multiqc/plots/violin.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/bar.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/box.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/heatmap.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/line.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/plot.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/scatter.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/table.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
copying build/lib/multiqc/plots/plotly/violin.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/plots/plotly
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates
copying build/lib/multiqc/templates/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/default
copying build/lib/multiqc/templates/default/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/base.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/content.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/foot.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/footer.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/general_stats.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/head.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/header.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/includes.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/nav.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
copying build/lib/multiqc/templates/default/toolbox.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/default/assets
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/default/assets/css
copying build/lib/multiqc/templates/default/assets/css/bootstrap.min.css -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/css
copying build/lib/multiqc/templates/default/assets/css/default_multiqc.css -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/css
copying build/lib/multiqc/templates/default/assets/css/jquery.toast.css -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/css
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/default/assets/fonts
copying build/lib/multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.eot -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/fonts
copying build/lib/multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.svg -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/fonts
copying build/lib/multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.ttf -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/fonts
copying build/lib/multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.woff -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/fonts
copying build/lib/multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.woff2 -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/fonts
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/default/assets/img
copying build/lib/multiqc/templates/default/assets/img/MultiQC_logo.png -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/img
copying build/lib/multiqc/templates/default/assets/img/MultiQC_logo_dark.svg -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/img
copying build/lib/multiqc/templates/default/assets/img/favicon-16x16.png -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/img
copying build/lib/multiqc/templates/default/assets/img/favicon-32x32.png -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/img
copying build/lib/multiqc/templates/default/assets/img/favicon-96x96.png -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/img
copying build/lib/multiqc/templates/default/assets/img/seqera_logo.png -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/img
copying build/lib/multiqc/templates/default/assets/img/seqera_logo_mono.png -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/img
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/default/assets/js
copying build/lib/multiqc/templates/default/assets/js/decompress.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js
copying build/lib/multiqc/templates/default/assets/js/flat.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js
copying build/lib/multiqc/templates/default/assets/js/multiqc.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js
copying build/lib/multiqc/templates/default/assets/js/plotting.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js
copying build/lib/multiqc/templates/default/assets/js/render.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js
copying build/lib/multiqc/templates/default/assets/js/tables.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js
copying build/lib/multiqc/templates/default/assets/js/toolbox.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/FileSaver.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/bootstrap.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/jquery-3.1.1.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/jquery-ui.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/jquery.tablesorter.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/jquery.toast.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/jszip.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/pako_inflate.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/plotly-2.27.0.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
copying build/lib/multiqc/templates/default/assets/js/packages/plotly-2.27.0.min.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/packages
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/default/assets/js/plots
copying build/lib/multiqc/templates/default/assets/js/plots/bar.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/plots
copying build/lib/multiqc/templates/default/assets/js/plots/box.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/plots
copying build/lib/multiqc/templates/default/assets/js/plots/heatmap.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/plots
copying build/lib/multiqc/templates/default/assets/js/plots/line.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/plots
copying build/lib/multiqc/templates/default/assets/js/plots/scatter.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/plots
copying build/lib/multiqc/templates/default/assets/js/plots/violin.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/default/assets/js/plots
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/gathered
copying build/lib/multiqc/templates/gathered/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/gathered
copying build/lib/multiqc/templates/gathered/content.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/gathered
copying build/lib/multiqc/templates/gathered/nav.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/gathered
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/geo
copying build/lib/multiqc/templates/geo/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo
copying build/lib/multiqc/templates/geo/includes.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/geo/assets
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/geo/assets/css
copying build/lib/multiqc/templates/geo/assets/css/bootstrap.min.css -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/css
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/emailme.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/flames.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/glyphicons-halflings-white.png -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/glyphicons-halflings.png -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/hot.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/mchammer.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/microfab.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/new.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/new2.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/progress.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/rainbow.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
copying build/lib/multiqc/templates/geo/assets/img/stars.gif -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/geo/assets/img
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/sections
copying build/lib/multiqc/templates/sections/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/sections
copying build/lib/multiqc/templates/sections/content.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/sections
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/templates/simple
copying build/lib/multiqc/templates/simple/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/simple
copying build/lib/multiqc/templates/simple/foot.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/simple
copying build/lib/multiqc/templates/simple/footer.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/simple
copying build/lib/multiqc/templates/simple/header.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/simple
copying build/lib/multiqc/templates/simple/includes.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/simple
copying build/lib/multiqc/templates/simple/nav.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/simple
copying build/lib/multiqc/templates/simple/toolbox.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/templates/simple
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc/utils
copying build/lib/multiqc/utils/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/utils
copying build/lib/multiqc/utils/config.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/utils
copying build/lib/multiqc/utils/megaqc.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/utils
copying build/lib/multiqc/utils/mqc_colour.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/utils
copying build/lib/multiqc/utils/pyaml_env.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/utils
copying build/lib/multiqc/utils/report.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/utils
copying build/lib/multiqc/utils/testing.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/utils
copying build/lib/multiqc/utils/util_functions.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc/utils
running install_egg_info
Copying multiqc.egg-info to build/bdist.solaris-2.11-i86pc.64bit/wheel/./multiqc-1.25.2-py3.14.egg-info
running install_scripts
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/multiqc-1.25.2.dist-info/WHEEL
creating '/tmp/work/biology/py-multiqc/work/multiqc-1.25.2/dist/.tmp-m_um4g9x/multiqc-1.25.2-py3-none-any.whl' and adding 'build/bdist.solaris-2.11-i86pc.64bit/wheel' to it
adding 'multiqc/__init__.py'
adding 'multiqc/__main__.py'
adding 'multiqc/base_module.py'
adding 'multiqc/config.py'
adding 'multiqc/config_defaults.yaml'
adding 'multiqc/interactive.py'
adding 'multiqc/multiqc.py'
adding 'multiqc/py.typed'
adding 'multiqc/report.py'
adding 'multiqc/search_patterns.yaml'
adding 'multiqc/types.py'
adding 'multiqc/validation.py'
adding 'multiqc/core/__init__.py'
adding 'multiqc/core/exceptions.py'
adding 'multiqc/core/exec_modules.py'
adding 'multiqc/core/file_search.py'
adding 'multiqc/core/log_and_rich.py'
adding 'multiqc/core/order_modules_and_sections.py'
adding 'multiqc/core/plugin_hooks.py'
adding 'multiqc/core/software_versions.py'
adding 'multiqc/core/strict_helpers.py'
adding 'multiqc/core/tmp_dir.py'
adding 'multiqc/core/update_config.py'
adding 'multiqc/core/version_check.py'
adding 'multiqc/core/write_results.py'
adding 'multiqc/modules/__init__.py'
adding 'multiqc/modules/profile_runtime.py'
adding 'multiqc/modules/software_versions.py'
adding 'multiqc/modules/adapterremoval/__init__.py'
adding 'multiqc/modules/adapterremoval/adapterremoval.py'
adding 'multiqc/modules/afterqc/__init__.py'
adding 'multiqc/modules/afterqc/afterqc.py'
adding 'multiqc/modules/anglerfish/__init__.py'
adding 'multiqc/modules/anglerfish/anglerfish.py'
adding 'multiqc/modules/bakta/__init__.py'
adding 'multiqc/modules/bakta/bakta.py'
adding 'multiqc/modules/bamdst/__init__.py'
adding 'multiqc/modules/bamdst/bamdst.py'
adding 'multiqc/modules/bamtools/__init__.py'
adding 'multiqc/modules/bamtools/bamtools.py'
adding 'multiqc/modules/bamtools/stats.py'
adding 'multiqc/modules/bbduk/__init__.py'
adding 'multiqc/modules/bbduk/bbduk.py'
adding 'multiqc/modules/bbmap/__init__.py'
adding 'multiqc/modules/bbmap/bbmap.py'
adding 'multiqc/modules/bbmap/bbmap_filetypes.py'
adding 'multiqc/modules/bbmap/plot_aqhist.py'
adding 'multiqc/modules/bbmap/plot_basic_hist.py'
adding 'multiqc/modules/bbmap/plot_bhist.py'
adding 'multiqc/modules/bbmap/plot_bqhist.py'
adding 'multiqc/modules/bbmap/plot_covhist.py'
adding 'multiqc/modules/bbmap/plot_idhist.py'
adding 'multiqc/modules/bbmap/plot_ihist.py'
adding 'multiqc/modules/bbmap/plot_indelhist.py'
adding 'multiqc/modules/bbmap/plot_mhist.py'
adding 'multiqc/modules/bbmap/plot_qahist.py'
adding 'multiqc/modules/bbmap/plot_qchist.py'
adding 'multiqc/modules/bbmap/plot_qhist.py'
adding 'multiqc/modules/bcftools/__init__.py'
adding 'multiqc/modules/bcftools/bcftools.py'
adding 'multiqc/modules/bcftools/stats.py'
adding 'multiqc/modules/bcl2fastq/__init__.py'
adding 'multiqc/modules/bcl2fastq/bcl2fastq.py'
adding 'multiqc/modules/bclconvert/__init__.py'
adding 'multiqc/modules/bclconvert/bclconvert.py'
adding 'multiqc/modules/biobambam2/__init__.py'
adding 'multiqc/modules/biobambam2/biobambam2.py'
adding 'multiqc/modules/biobloomtools/__init__.py'
adding 'multiqc/modules/biobloomtools/biobloomtools.py'
adding 'multiqc/modules/biscuit/__init__.py'
adding 'multiqc/modules/biscuit/biscuit.py'
adding 'multiqc/modules/bismark/__init__.py'
adding 'multiqc/modules/bismark/bismark.py'
adding 'multiqc/modules/bowtie1/__init__.py'
adding 'multiqc/modules/bowtie1/bowtie1.py'
adding 'multiqc/modules/bowtie2/__init__.py'
adding 'multiqc/modules/bowtie2/bowtie2.py'
adding 'multiqc/modules/busco/__init__.py'
adding 'multiqc/modules/busco/busco.py'
adding 'multiqc/modules/bustools/__init__.py'
adding 'multiqc/modules/bustools/bustools.py'
adding 'multiqc/modules/ccs/__init__.py'
adding 'multiqc/modules/ccs/ccs.py'
adding 'multiqc/modules/ccs/tests/__init__.py'
adding 'multiqc/modules/ccs/tests/test_ccs.py'
adding 'multiqc/modules/cellranger/__init__.py'
adding 'multiqc/modules/cellranger/cellranger.py'
adding 'multiqc/modules/cellranger/count.py'
adding 'multiqc/modules/cellranger/utils.py'
adding 'multiqc/modules/cellranger/vdj.py'
adding 'multiqc/modules/checkqc/__init__.py'
adding 'multiqc/modules/checkqc/checkqc.py'
adding 'multiqc/modules/clipandmerge/__init__.py'
adding 'multiqc/modules/clipandmerge/clipandmerge.py'
adding 'multiqc/modules/clusterflow/__init__.py'
adding 'multiqc/modules/clusterflow/clusterflow.py'
adding 'multiqc/modules/conpair/__init__.py'
adding 'multiqc/modules/conpair/conpair.py'
adding 'multiqc/modules/custom_content/__init__.py'
adding 'multiqc/modules/custom_content/custom_content.py'
adding 'multiqc/modules/cutadapt/__init__.py'
adding 'multiqc/modules/cutadapt/cutadapt.py'
adding 'multiqc/modules/damageprofiler/__init__.py'
adding 'multiqc/modules/damageprofiler/damageprofiler.py'
adding 'multiqc/modules/dedup/__init__.py'
adding 'multiqc/modules/dedup/dedup.py'
adding 'multiqc/modules/deeptools/__init__.py'
adding 'multiqc/modules/deeptools/bamPEFragmentSizeDistribution.py'
adding 'multiqc/modules/deeptools/bamPEFragmentSizeTable.py'
adding 'multiqc/modules/deeptools/deeptools.py'
adding 'multiqc/modules/deeptools/estimateReadFiltering.py'
adding 'multiqc/modules/deeptools/plotCorrelation.py'
adding 'multiqc/modules/deeptools/plotCoverage.py'
adding 'multiqc/modules/deeptools/plotEnrichment.py'
adding 'multiqc/modules/deeptools/plotFingerprint.py'
adding 'multiqc/modules/deeptools/plotPCA.py'
adding 'multiqc/modules/deeptools/plotProfile.py'
adding 'multiqc/modules/diamond/__init__.py'
adding 'multiqc/modules/diamond/diamond.py'
adding 'multiqc/modules/disambiguate/__init__.py'
adding 'multiqc/modules/disambiguate/disambiguate.py'
adding 'multiqc/modules/dragen/__init__.py'
adding 'multiqc/modules/dragen/coverage_hist.py'
adding 'multiqc/modules/dragen/coverage_metrics.py'
adding 'multiqc/modules/dragen/coverage_per_contig.py'
adding 'multiqc/modules/dragen/dragen.py'
adding 'multiqc/modules/dragen/dragen_gc_metrics.py'
adding 'multiqc/modules/dragen/fragment_length.py'
adding 'multiqc/modules/dragen/mapping_metrics.py'
adding 'multiqc/modules/dragen/overall_mean_cov.py'
adding 'multiqc/modules/dragen/ploidy_estimation_metrics.py'
adding 'multiqc/modules/dragen/rna_quant_metrics.py'
adding 'multiqc/modules/dragen/rna_transcript_cov.py'
adding 'multiqc/modules/dragen/sc_atac_metrics.py'
adding 'multiqc/modules/dragen/sc_rna_metrics.py'
adding 'multiqc/modules/dragen/time_metrics.py'
adding 'multiqc/modules/dragen/trimmer_metrics.py'
adding 'multiqc/modules/dragen/utils.py'
adding 'multiqc/modules/dragen/vc_metrics.py'
adding 'multiqc/modules/dragen/tests/__init__.py'
adding 'multiqc/modules/dragen/tests/test_dragen.py'
adding 'multiqc/modules/dragen_fastqc/__init__.py'
adding 'multiqc/modules/dragen_fastqc/base_metrics.py'
adding 'multiqc/modules/dragen_fastqc/content_metrics.py'
adding 'multiqc/modules/dragen_fastqc/dragen_fastqc.py'
adding 'multiqc/modules/dragen_fastqc/gc_metrics.py'
adding 'multiqc/modules/dragen_fastqc/read_metrics.py'
adding 'multiqc/modules/dragen_fastqc/util.py'
adding 'multiqc/modules/dragen_fastqc/assets/js/multiqc_dragen_fastqc.js'
adding 'multiqc/modules/eigenstratdatabasetools/__init__.py'
adding 'multiqc/modules/eigenstratdatabasetools/eigenstratdatabasetools.py'
adding 'multiqc/modules/fastp/__init__.py'
adding 'multiqc/modules/fastp/fastp.py'
adding 'multiqc/modules/fastq_screen/__init__.py'
adding 'multiqc/modules/fastq_screen/fastq_screen.py'
adding 'multiqc/modules/fastqc/__init__.py'
adding 'multiqc/modules/fastqc/fastqc.py'
adding 'multiqc/modules/fastqc/assets/css/multiqc_fastqc.css'
adding 'multiqc/modules/fastqc/assets/js/multiqc_fastqc.js'
adding 'multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_genome.txt'
adding 'multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_hg38_txome.txt'
adding 'multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_genome.txt'
adding 'multiqc/modules/fastqc/fastqc_theoretical_gc/fastqc_theoretical_gc_mm10_txome.txt'
adding 'multiqc/modules/featurecounts/__init__.py'
adding 'multiqc/modules/featurecounts/featurecounts.py'
adding 'multiqc/modules/fgbio/__init__.py'
adding 'multiqc/modules/fgbio/error_rate_by_read_position.py'
adding 'multiqc/modules/fgbio/fgbio.py'
adding 'multiqc/modules/fgbio/group_reads_by_umi.py'
adding 'multiqc/modules/filtlong/__init__.py'
adding 'multiqc/modules/filtlong/filtlong.py'
adding 'multiqc/modules/flash/__init__.py'
adding 'multiqc/modules/flash/flash.py'
adding 'multiqc/modules/flexbar/__init__.py'
adding 'multiqc/modules/flexbar/flexbar.py'
adding 'multiqc/modules/freyja/__init__.py'
adding 'multiqc/modules/freyja/freyja.py'
adding 'multiqc/modules/ganon/__init__.py'
adding 'multiqc/modules/ganon/ganon.py'
adding 'multiqc/modules/gatk/__init__.py'
adding 'multiqc/modules/gatk/analyze_saturation_mutagenesis.py'
adding 'multiqc/modules/gatk/base_recalibrator.py'
adding 'multiqc/modules/gatk/gatk.py'
adding 'multiqc/modules/gatk/varianteval.py'
adding 'multiqc/modules/gffcompare/__init__.py'
adding 'multiqc/modules/gffcompare/gffcompare.py'
adding 'multiqc/modules/glimpse/__init__.py'
adding 'multiqc/modules/glimpse/err_grp.py'
adding 'multiqc/modules/glimpse/err_spl.py'
adding 'multiqc/modules/glimpse/glimpse.py'
adding 'multiqc/modules/goleft_indexcov/__init__.py'
adding 'multiqc/modules/goleft_indexcov/goleft_indexcov.py'
adding 'multiqc/modules/gopeaks/__init__.py'
adding 'multiqc/modules/gopeaks/gopeaks.py'
adding 'multiqc/modules/haplocheck/__init__.py'
adding 'multiqc/modules/haplocheck/haplocheck.py'
adding 'multiqc/modules/happy/__init__.py'
adding 'multiqc/modules/happy/happy.py'
adding 'multiqc/modules/hicexplorer/__init__.py'
adding 'multiqc/modules/hicexplorer/hicexplorer.py'
adding 'multiqc/modules/hicpro/__init__.py'
adding 'multiqc/modules/hicpro/hicpro.py'
adding 'multiqc/modules/hicup/__init__.py'
adding 'multiqc/modules/hicup/hicup.py'
adding 'multiqc/modules/hifiasm/__init__.py'
adding 'multiqc/modules/hifiasm/hifiasm.py'
adding 'multiqc/modules/hisat2/__init__.py'
adding 'multiqc/modules/hisat2/hisat2.py'
adding 'multiqc/modules/homer/__init__.py'
adding 'multiqc/modules/homer/findpeaks.py'
adding 'multiqc/modules/homer/homer.py'
adding 'multiqc/modules/homer/tagdirectory.py'
adding 'multiqc/modules/hops/__init__.py'
adding 'multiqc/modules/hops/hops.py'
adding 'multiqc/modules/hostile/__init__.py'
adding 'multiqc/modules/hostile/hostile.py'
adding 'multiqc/modules/htseq/__init__.py'
adding 'multiqc/modules/htseq/htseq.py'
adding 'multiqc/modules/humid/__init__.py'
adding 'multiqc/modules/humid/clusters.py'
adding 'multiqc/modules/humid/counts.py'
adding 'multiqc/modules/humid/humid.py'
adding 'multiqc/modules/humid/neighbours.py'
adding 'multiqc/modules/humid/stats.py'
adding 'multiqc/modules/interop/__init__.py'
adding 'multiqc/modules/interop/interop.py'
adding 'multiqc/modules/isoseq/__init__.py'
adding 'multiqc/modules/isoseq/isoseq.py'
adding 'multiqc/modules/ivar/__init__.py'
adding 'multiqc/modules/ivar/ivar.py'
adding 'multiqc/modules/jcvi/__init__.py'
adding 'multiqc/modules/jcvi/jcvi.py'
adding 'multiqc/modules/jellyfish/__init__.py'
adding 'multiqc/modules/jellyfish/jellyfish.py'
adding 'multiqc/modules/kaiju/__init__.py'
adding 'multiqc/modules/kaiju/kaiju.py'
adding 'multiqc/modules/kallisto/__init__.py'
adding 'multiqc/modules/kallisto/kallisto.py'
adding 'multiqc/modules/kat/__init__.py'
adding 'multiqc/modules/kat/kat.py'
adding 'multiqc/modules/kraken/__init__.py'
adding 'multiqc/modules/kraken/kraken.py'
adding 'multiqc/modules/leehom/__init__.py'
adding 'multiqc/modules/leehom/leehom.py'
adding 'multiqc/modules/librarian/__init__.py'
adding 'multiqc/modules/librarian/librarian.py'
adding 'multiqc/modules/lima/__init__.py'
adding 'multiqc/modules/lima/lima.py'
adding 'multiqc/modules/longranger/__init__.py'
adding 'multiqc/modules/longranger/longranger.py'
adding 'multiqc/modules/macs2/__init__.py'
adding 'multiqc/modules/macs2/macs2.py'
adding 'multiqc/modules/malt/__init__.py'
adding 'multiqc/modules/malt/malt.py'
adding 'multiqc/modules/mapdamage/__init__.py'
adding 'multiqc/modules/mapdamage/mapdamage.py'
adding 'multiqc/modules/megahit/__init__.py'
adding 'multiqc/modules/megahit/megahit.py'
adding 'multiqc/modules/metaphlan/__init__.py'
adding 'multiqc/modules/metaphlan/metaphlan.py'
adding 'multiqc/modules/methylqa/__init__.py'
adding 'multiqc/modules/methylqa/methylqa.py'
adding 'multiqc/modules/minionqc/__init__.py'
adding 'multiqc/modules/minionqc/minionqc.py'
adding 'multiqc/modules/mirtop/__init__.py'
adding 'multiqc/modules/mirtop/mirtop.py'
adding 'multiqc/modules/mirtrace/__init__.py'
adding 'multiqc/modules/mirtrace/mirtrace.py'
adding 'multiqc/modules/mosdepth/__init__.py'
adding 'multiqc/modules/mosdepth/mosdepth.py'
adding 'multiqc/modules/motus/__init__.py'
adding 'multiqc/modules/motus/motus.py'
adding 'multiqc/modules/mtnucratio/__init__.py'
adding 'multiqc/modules/mtnucratio/mtnucratio.py'
adding 'multiqc/modules/multivcfanalyzer/__init__.py'
adding 'multiqc/modules/multivcfanalyzer/multivcfanalyzer.py'
adding 'multiqc/modules/nanoq/__init__.py'
adding 'multiqc/modules/nanoq/nanoq.py'
adding 'multiqc/modules/nanostat/__init__.py'
adding 'multiqc/modules/nanostat/nanostat.py'
adding 'multiqc/modules/nextclade/__init__.py'
adding 'multiqc/modules/nextclade/nextclade.py'
adding 'multiqc/modules/ngsbits/__init__.py'
adding 'multiqc/modules/ngsbits/mappingqc.py'
adding 'multiqc/modules/ngsbits/ngsbits.py'
adding 'multiqc/modules/ngsbits/readqc.py'
adding 'multiqc/modules/ngsbits/samplegender.py'
adding 'multiqc/modules/ngsbits/utils.py'
adding 'multiqc/modules/ngsderive/__init__.py'
adding 'multiqc/modules/ngsderive/ngsderive.py'
adding 'multiqc/modules/nonpareil/__init__.py'
adding 'multiqc/modules/nonpareil/nonpareil.py'
adding 'multiqc/modules/odgi/__init__.py'
adding 'multiqc/modules/odgi/odgi.py'
adding 'multiqc/modules/optitype/__init__.py'
adding 'multiqc/modules/optitype/optitype.py'
adding 'multiqc/modules/pairtools/__init__.py'
adding 'multiqc/modules/pairtools/pairtools.py'
adding 'multiqc/modules/pairtools/params.yml'
adding 'multiqc/modules/pairtools/utils.py'
adding 'multiqc/modules/pangolin/__init__.py'
adding 'multiqc/modules/pangolin/pangolin.py'
adding 'multiqc/modules/pbmarkdup/__init__.py'
adding 'multiqc/modules/pbmarkdup/pbmarkdup.py'
adding 'multiqc/modules/peddy/__init__.py'
adding 'multiqc/modules/peddy/peddy.py'
adding 'multiqc/modules/phantompeakqualtools/__init__.py'
adding 'multiqc/modules/phantompeakqualtools/phantompeakqualtools.py'
adding 'multiqc/modules/picard/AlignmentSummaryMetrics.py'
adding 'multiqc/modules/picard/BaseDistributionByCycleMetrics.py'
adding 'multiqc/modules/picard/CrosscheckFingerprints.py'
adding 'multiqc/modules/picard/ExtractIlluminaBarcodes.py'
adding 'multiqc/modules/picard/GcBiasMetrics.py'
adding 'multiqc/modules/picard/HsMetrics.py'
adding 'multiqc/modules/picard/IlluminaBasecallingMetrics.py'
adding 'multiqc/modules/picard/IlluminaLaneMetrics.py'
adding 'multiqc/modules/picard/InsertSizeMetrics.py'
adding 'multiqc/modules/picard/MarkDuplicates.py'
adding 'multiqc/modules/picard/MarkIlluminaAdapters.py'
adding 'multiqc/modules/picard/OxoGMetrics.py'
adding 'multiqc/modules/picard/QualityByCycleMetrics.py'
adding 'multiqc/modules/picard/QualityScoreDistributionMetrics.py'
adding 'multiqc/modules/picard/QualityYieldMetrics.py'
adding 'multiqc/modules/picard/RnaSeqMetrics.py'
adding 'multiqc/modules/picard/RrbsSummaryMetrics.py'
adding 'multiqc/modules/picard/TargetedPcrMetrics.py'
adding 'multiqc/modules/picard/ValidateSamFile.py'
adding 'multiqc/modules/picard/VariantCallingMetrics.py'
adding 'multiqc/modules/picard/WgsMetrics.py'
adding 'multiqc/modules/picard/__init__.py'
adding 'multiqc/modules/picard/picard.py'
adding 'multiqc/modules/picard/util.py'
adding 'multiqc/modules/picard/tests/__init__.py'
adding 'multiqc/modules/picard/tests/test_picard.py'
adding 'multiqc/modules/porechop/__init__.py'
adding 'multiqc/modules/porechop/porechop.py'
adding 'multiqc/modules/preseq/__init__.py'
adding 'multiqc/modules/preseq/preseq.py'
adding 'multiqc/modules/prinseqplusplus/__init__.py'
adding 'multiqc/modules/prinseqplusplus/prinseqplusplus.py'
adding 'multiqc/modules/prokka/__init__.py'
adding 'multiqc/modules/prokka/prokka.py'
adding 'multiqc/modules/purple/__init__.py'
adding 'multiqc/modules/purple/purple.py'
adding 'multiqc/modules/pychopper/__init__.py'
adding 'multiqc/modules/pychopper/pychopper.py'
adding 'multiqc/modules/pycoqc/__init__.py'
adding 'multiqc/modules/pycoqc/pycoqc.py'
adding 'multiqc/modules/qc3C/__init__.py'
adding 'multiqc/modules/qc3C/qc3C.py'
adding 'multiqc/modules/qorts/__init__.py'
adding 'multiqc/modules/qorts/qorts.py'
adding 'multiqc/modules/qualimap/QM_BamQC.py'
adding 'multiqc/modules/qualimap/QM_RNASeq.py'
adding 'multiqc/modules/qualimap/__init__.py'
adding 'multiqc/modules/qualimap/qualimap.py'
adding 'multiqc/modules/quast/__init__.py'
adding 'multiqc/modules/quast/quast.py'
adding 'multiqc/modules/rna_seqc/__init__.py'
adding 'multiqc/modules/rna_seqc/rna_seqc.py'
adding 'multiqc/modules/rockhopper/__init__.py'
adding 'multiqc/modules/rockhopper/rockhopper.py'
adding 'multiqc/modules/rsem/__init__.py'
adding 'multiqc/modules/rsem/rsem.py'
adding 'multiqc/modules/rseqc/__init__.py'
adding 'multiqc/modules/rseqc/bam_stat.py'
adding 'multiqc/modules/rseqc/gene_body_coverage.py'
adding 'multiqc/modules/rseqc/infer_experiment.py'
adding 'multiqc/modules/rseqc/inner_distance.py'
adding 'multiqc/modules/rseqc/junction_annotation.py'
adding 'multiqc/modules/rseqc/junction_saturation.py'
adding 'multiqc/modules/rseqc/read_distribution.py'
adding 'multiqc/modules/rseqc/read_duplication.py'
adding 'multiqc/modules/rseqc/read_gc.py'
adding 'multiqc/modules/rseqc/rseqc.py'
adding 'multiqc/modules/rseqc/tin.py'
adding 'multiqc/modules/salmon/__init__.py'
adding 'multiqc/modules/salmon/salmon.py'
adding 'multiqc/modules/sambamba/__init__.py'
adding 'multiqc/modules/sambamba/markdup.py'
adding 'multiqc/modules/sambamba/sambamba.py'
adding 'multiqc/modules/samblaster/__init__.py'
adding 'multiqc/modules/samblaster/samblaster.py'
adding 'multiqc/modules/samtools/__init__.py'
adding 'multiqc/modules/samtools/coverage.py'
adding 'multiqc/modules/samtools/flagstat.py'
adding 'multiqc/modules/samtools/idxstats.py'
adding 'multiqc/modules/samtools/markdup.py'
adding 'multiqc/modules/samtools/rmdup.py'
adding 'multiqc/modules/samtools/samtools.py'
adding 'multiqc/modules/samtools/stats.py'
adding 'multiqc/modules/samtools/tests/__init__.py'
adding 'multiqc/modules/samtools/tests/test_flagstat.py'
adding 'multiqc/modules/sargasso/__init__.py'
adding 'multiqc/modules/sargasso/sargasso.py'
adding 'multiqc/modules/seqera_cli/__init__.py'
adding 'multiqc/modules/seqera_cli/seqera_cli.py'
adding 'multiqc/modules/sequali/__init__.py'
adding 'multiqc/modules/sequali/sequali.py'
adding 'multiqc/modules/seqwho/__init__.py'
adding 'multiqc/modules/seqwho/seqwho.py'
adding 'multiqc/modules/seqyclean/__init__.py'
adding 'multiqc/modules/seqyclean/seqyclean.py'
adding 'multiqc/modules/sexdeterrmine/__init__.py'
adding 'multiqc/modules/sexdeterrmine/sexdeterrmine.py'
adding 'multiqc/modules/sickle/__init__.py'
adding 'multiqc/modules/sickle/sickle.py'
adding 'multiqc/modules/skewer/__init__.py'
adding 'multiqc/modules/skewer/skewer.py'
adding 'multiqc/modules/slamdunk/__init__.py'
adding 'multiqc/modules/slamdunk/slamdunk.py'
adding 'multiqc/modules/snippy/__init__.py'
adding 'multiqc/modules/snippy/snippy.py'
adding 'multiqc/modules/snpeff/__init__.py'
adding 'multiqc/modules/snpeff/snpeff.py'
adding 'multiqc/modules/snpsplit/__init__.py'
adding 'multiqc/modules/snpsplit/snpsplit.py'
adding 'multiqc/modules/somalier/__init__.py'
adding 'multiqc/modules/somalier/somalier.py'
adding 'multiqc/modules/sortmerna/__init__.py'
adding 'multiqc/modules/sortmerna/sortmerna.py'
adding 'multiqc/modules/sourmash/__init__.py'
adding 'multiqc/modules/sourmash/compare.py'
adding 'multiqc/modules/sourmash/gather.py'
adding 'multiqc/modules/sourmash/sourmash.py'
adding 'multiqc/modules/spaceranger/__init__.py'
adding 'multiqc/modules/spaceranger/count.py'
adding 'multiqc/modules/spaceranger/spaceranger.py'
adding 'multiqc/modules/spaceranger/utils.py'
adding 'multiqc/modules/stacks/__init__.py'
adding 'multiqc/modules/stacks/stacks.py'
adding 'multiqc/modules/star/__init__.py'
adding 'multiqc/modules/star/star.py'
adding 'multiqc/modules/supernova/__init__.py'
adding 'multiqc/modules/supernova/supernova.py'
adding 'multiqc/modules/theta2/__init__.py'
adding 'multiqc/modules/theta2/theta2.py'
adding 'multiqc/modules/tophat/__init__.py'
adding 'multiqc/modules/tophat/tophat.py'
adding 'multiqc/modules/trimmomatic/__init__.py'
adding 'multiqc/modules/trimmomatic/trimmomatic.py'
adding 'multiqc/modules/truvari/__init__.py'
adding 'multiqc/modules/truvari/truvari.py'
adding 'multiqc/modules/umicollapse/__init__.py'
adding 'multiqc/modules/umicollapse/umicollapse.py'
adding 'multiqc/modules/umicollapse/tests/__init__.py'
adding 'multiqc/modules/umicollapse/tests/test_umicollapse.py'
adding 'multiqc/modules/umitools/__init__.py'
adding 'multiqc/modules/umitools/umitools.py'
adding 'multiqc/modules/umitools/tests/__init__.py'
adding 'multiqc/modules/umitools/tests/test_umitools.py'
adding 'multiqc/modules/varscan2/__init__.py'
adding 'multiqc/modules/varscan2/varscan2.py'
adding 'multiqc/modules/vcftools/__init__.py'
adding 'multiqc/modules/vcftools/relatedness2.py'
adding 'multiqc/modules/vcftools/tstv_by_count.py'
adding 'multiqc/modules/vcftools/tstv_by_qual.py'
adding 'multiqc/modules/vcftools/tstv_summary.py'
adding 'multiqc/modules/vcftools/vcftools.py'
adding 'multiqc/modules/vep/__init__.py'
adding 'multiqc/modules/vep/vep.py'
adding 'multiqc/modules/verifybamid/__init__.py'
adding 'multiqc/modules/verifybamid/verifybamid.py'
adding 'multiqc/modules/vg/__init__.py'
adding 'multiqc/modules/vg/vg.py'
adding 'multiqc/modules/whatshap/__init__.py'
adding 'multiqc/modules/whatshap/whatshap.py'
adding 'multiqc/modules/xengsort/__init__.py'
adding 'multiqc/modules/xengsort/xengsort.py'
adding 'multiqc/modules/xenome/__init__.py'
adding 'multiqc/modules/xenome/xenome.py'
adding 'multiqc/plots/__init__.py'
adding 'multiqc/plots/bargraph.py'
adding 'multiqc/plots/box.py'
adding 'multiqc/plots/heatmap.py'
adding 'multiqc/plots/linegraph.py'
adding 'multiqc/plots/scatter.py'
adding 'multiqc/plots/table.py'
adding 'multiqc/plots/table_object.py'
adding 'multiqc/plots/violin.py'
adding 'multiqc/plots/plotly/__init__.py'
adding 'multiqc/plots/plotly/bar.py'
adding 'multiqc/plots/plotly/box.py'
adding 'multiqc/plots/plotly/heatmap.py'
adding 'multiqc/plots/plotly/line.py'
adding 'multiqc/plots/plotly/plot.py'
adding 'multiqc/plots/plotly/scatter.py'
adding 'multiqc/plots/plotly/table.py'
adding 'multiqc/plots/plotly/violin.py'
adding 'multiqc/templates/__init__.py'
adding 'multiqc/templates/default/__init__.py'
adding 'multiqc/templates/default/base.html'
adding 'multiqc/templates/default/content.html'
adding 'multiqc/templates/default/foot.html'
adding 'multiqc/templates/default/footer.html'
adding 'multiqc/templates/default/general_stats.html'
adding 'multiqc/templates/default/head.html'
adding 'multiqc/templates/default/header.html'
adding 'multiqc/templates/default/includes.html'
adding 'multiqc/templates/default/nav.html'
adding 'multiqc/templates/default/toolbox.html'
adding 'multiqc/templates/default/assets/css/bootstrap.min.css'
adding 'multiqc/templates/default/assets/css/default_multiqc.css'
adding 'multiqc/templates/default/assets/css/jquery.toast.css'
adding 'multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.eot'
adding 'multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.svg'
adding 'multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.ttf'
adding 'multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.woff'
adding 'multiqc/templates/default/assets/fonts/glyphicons-halflings-regular.woff2'
adding 'multiqc/templates/default/assets/img/MultiQC_logo.png'
adding 'multiqc/templates/default/assets/img/MultiQC_logo_dark.svg'
adding 'multiqc/templates/default/assets/img/favicon-16x16.png'
adding 'multiqc/templates/default/assets/img/favicon-32x32.png'
adding 'multiqc/templates/default/assets/img/favicon-96x96.png'
adding 'multiqc/templates/default/assets/img/seqera_logo.png'
adding 'multiqc/templates/default/assets/img/seqera_logo_mono.png'
adding 'multiqc/templates/default/assets/js/decompress.js'
adding 'multiqc/templates/default/assets/js/flat.js'
adding 'multiqc/templates/default/assets/js/multiqc.js'
adding 'multiqc/templates/default/assets/js/plotting.js'
adding 'multiqc/templates/default/assets/js/render.js'
adding 'multiqc/templates/default/assets/js/tables.js'
adding 'multiqc/templates/default/assets/js/toolbox.js'
adding 'multiqc/templates/default/assets/js/packages/FileSaver.min.js'
adding 'multiqc/templates/default/assets/js/packages/bootstrap.min.js'
adding 'multiqc/templates/default/assets/js/packages/jquery-3.1.1.min.js'
adding 'multiqc/templates/default/assets/js/packages/jquery-ui.min.js'
adding 'multiqc/templates/default/assets/js/packages/jquery.tablesorter.min.js'
adding 'multiqc/templates/default/assets/js/packages/jquery.toast.min.js'
adding 'multiqc/templates/default/assets/js/packages/jszip.min.js'
adding 'multiqc/templates/default/assets/js/packages/pako_inflate.min.js'
adding 'multiqc/templates/default/assets/js/packages/plotly-2.27.0.js'
adding 'multiqc/templates/default/assets/js/packages/plotly-2.27.0.min.js'
adding 'multiqc/templates/default/assets/js/plots/bar.js'
adding 'multiqc/templates/default/assets/js/plots/box.js'
adding 'multiqc/templates/default/assets/js/plots/heatmap.js'
adding 'multiqc/templates/default/assets/js/plots/line.js'
adding 'multiqc/templates/default/assets/js/plots/scatter.js'
adding 'multiqc/templates/default/assets/js/plots/violin.js'
adding 'multiqc/templates/gathered/__init__.py'
adding 'multiqc/templates/gathered/content.html'
adding 'multiqc/templates/gathered/nav.html'
adding 'multiqc/templates/geo/__init__.py'
adding 'multiqc/templates/geo/includes.html'
adding 'multiqc/templates/geo/assets/css/bootstrap.min.css'
adding 'multiqc/templates/geo/assets/img/emailme.gif'
adding 'multiqc/templates/geo/assets/img/flames.gif'
adding 'multiqc/templates/geo/assets/img/glyphicons-halflings-white.png'
adding 'multiqc/templates/geo/assets/img/glyphicons-halflings.png'
adding 'multiqc/templates/geo/assets/img/hot.gif'
adding 'multiqc/templates/geo/assets/img/mchammer.gif'
adding 'multiqc/templates/geo/assets/img/microfab.gif'
adding 'multiqc/templates/geo/assets/img/new.gif'
adding 'multiqc/templates/geo/assets/img/new2.gif'
adding 'multiqc/templates/geo/assets/img/progress.gif'
adding 'multiqc/templates/geo/assets/img/rainbow.gif'
adding 'multiqc/templates/geo/assets/img/stars.gif'
adding 'multiqc/templates/sections/__init__.py'
adding 'multiqc/templates/sections/content.html'
adding 'multiqc/templates/simple/__init__.py'
adding 'multiqc/templates/simple/foot.html'
adding 'multiqc/templates/simple/footer.html'
adding 'multiqc/templates/simple/header.html'
adding 'multiqc/templates/simple/includes.html'
adding 'multiqc/templates/simple/nav.html'
adding 'multiqc/templates/simple/toolbox.html'
adding 'multiqc/utils/__init__.py'
adding 'multiqc/utils/config.py'
adding 'multiqc/utils/megaqc.py'
adding 'multiqc/utils/mqc_colour.py'
adding 'multiqc/utils/pyaml_env.py'
adding 'multiqc/utils/report.py'
adding 'multiqc/utils/testing.py'
adding 'multiqc/utils/util_functions.py'
adding 'multiqc-1.25.2.dist-info/licenses/LICENSE'
adding 'multiqc-1.25.2.dist-info/METADATA'
adding 'multiqc-1.25.2.dist-info/WHEEL'
adding 'multiqc-1.25.2.dist-info/entry_points.txt'
adding 'multiqc-1.25.2.dist-info/top_level.txt'
adding 'multiqc-1.25.2.dist-info/RECORD'
removing build/bdist.solaris-2.11-i86pc.64bit/wheel
Successfully built multiqc-1.25.2-py3-none-any.whl