=> Bootstrap dependency digest>=20211023: found digest-20220214 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Building for py38-pelican-4.5.0nb2 => Removing useless import of pelican. (cd /tmp/www/py-pelican/work/pelican-4.5.0/ && /usr/bin/env USETOOLS=no PTHREAD_CFLAGS=\ -pthread\ PTHREAD_LDFLAGS=\ -pthread PTHREAD_LIBS= PTHREADBASE=/usr DL_CFLAGS=\ -pthread\ DL_LDFLAGS=\ -pthread DL_LIBS= PYTHON=/usr/pkg/bin/python3.8 CC=gcc CFLAGS=-O2\ -fPIC\ -D_FORTIFY_SOURCE=2\ -I/usr/include\ -I/usr/pkg/include/python3.8 CPPFLAGS=-I/usr/include\ -I/usr/pkg/include/python3.8 CXX=c++ CXXFLAGS=-O2\ -fPIC\ -D_FORTIFY_SOURCE=2\ -I/usr/include\ -I/usr/pkg/include/python3.8 COMPILER_RPATH_FLAG=-Wl,-R F77=gfortran FC=gfortran FFLAGS=-O LANG=C LC_ALL=C LC_COLLATE=C LC_CTYPE=C LC_MESSAGES=C LC_MONETARY=C LC_NUMERIC=C LC_TIME=C LDFLAGS=-Wl,-zrelro\ -L/usr/lib\ -Wl,-R/usr/lib\ -Wl,-R/usr/pkg/lib LINKER_RPATH_FLAG=-R PATH=/tmp/www/py-pelican/work/.cwrapper/bin:/tmp/www/py-pelican/work/.buildlink/bin:/tmp/www/py-pelican/work/.gcc/bin:/tmp/www/py-pelican/work/.tools/bin:/usr/pkg/bin:/usr/bin:/bin:/usr/pkg/bin:/usr/local/bin:/usr/pkg/bin:/usr/X11R7/bin PREFIX=/usr/pkg MAKELEVEL=0 CONFIG_SITE= PKG_SYSCONFDIR=/usr/pkg/etc CXXCPP=cpp HOME=/tmp/www/py-pelican/work/.home CWRAPPERS_CONFIG_DIR=/tmp/www/py-pelican/work/.cwrapper/config CPP=cpp LOCALBASE=/usr/pkg X11BASE=/usr/X11R7 PKGMANDIR=man PKGINFODIR=info PKGGNUDIR=gnu/ MAKECONF=/dev/null OBJECT_FMT=ELF USETOOLS=no BSD_INSTALL_PROGRAM=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL_MAN=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL=/usr/bin/install BSD_INSTALL_PROGRAM_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_MAN_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_GAME=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 2555 BSD_INSTALL_GAME_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 664 BSD_INSTALL_GAME_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 775 INSTALL_INFO= MAKEINFO=/tmp/www/py-pelican/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/www/py-pelican/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/www/py-pelican/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/www/py-pelican/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/www/py-pelican/work/.buildlink/lib/pkgconfig:/tmp/www/py-pelican/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/www/py-pelican/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/www/py-pelican/work/.cwrapper/config /usr/pkg/bin/python3.8 setup.py build -j4) running build running build_py creating build creating build/lib creating build/lib/pelican copying pelican/__init__.py -> build/lib/pelican copying pelican/__main__.py -> build/lib/pelican copying pelican/cache.py -> build/lib/pelican copying pelican/contents.py -> build/lib/pelican copying pelican/generators.py -> build/lib/pelican copying pelican/log.py -> build/lib/pelican copying pelican/paginator.py -> build/lib/pelican copying pelican/readers.py -> build/lib/pelican copying pelican/rstdirectives.py -> build/lib/pelican copying pelican/server.py -> build/lib/pelican copying pelican/settings.py -> build/lib/pelican copying pelican/urlwrappers.py -> build/lib/pelican copying pelican/utils.py -> build/lib/pelican copying pelican/writers.py -> build/lib/pelican creating build/lib/pelican/tests copying pelican/tests/__init__.py -> build/lib/pelican/tests copying pelican/tests/default_conf.py -> build/lib/pelican/tests copying pelican/tests/support.py -> build/lib/pelican/tests copying pelican/tests/test_cache.py -> build/lib/pelican/tests copying pelican/tests/test_contents.py -> build/lib/pelican/tests copying pelican/tests/test_generators.py -> build/lib/pelican/tests copying pelican/tests/test_importer.py -> build/lib/pelican/tests copying pelican/tests/test_log.py -> build/lib/pelican/tests copying pelican/tests/test_paginator.py -> build/lib/pelican/tests copying pelican/tests/test_pelican.py -> build/lib/pelican/tests copying pelican/tests/test_plugins.py -> build/lib/pelican/tests copying pelican/tests/test_readers.py -> build/lib/pelican/tests copying pelican/tests/test_rstdirectives.py -> build/lib/pelican/tests copying pelican/tests/test_server.py -> build/lib/pelican/tests copying pelican/tests/test_settings.py -> build/lib/pelican/tests copying pelican/tests/test_testsuite.py -> build/lib/pelican/tests copying pelican/tests/test_urlwrappers.py -> build/lib/pelican/tests copying pelican/tests/test_utils.py -> build/lib/pelican/tests creating build/lib/pelican/tools copying pelican/tools/__init__.py -> build/lib/pelican/tools copying pelican/tools/pelican_import.py -> build/lib/pelican/tools copying pelican/tools/pelican_quickstart.py -> build/lib/pelican/tools copying pelican/tools/pelican_themes.py -> build/lib/pelican/tools running egg_info creating pelican.egg-info writing pelican.egg-info/PKG-INFO writing dependency_links to pelican.egg-info/dependency_links.txt writing entry points to pelican.egg-info/entry_points.txt writing requirements to pelican.egg-info/requires.txt writing top-level names to pelican.egg-info/top_level.txt writing manifest file 'pelican.egg-info/SOURCES.txt' reading manifest file 'pelican.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'pelican.egg-info/SOURCES.txt' /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.plugins' to be distributed and are already explicitly excluding 'pelican.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.TestPages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.TestPages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.TestPages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.TestPages' to be distributed and are already explicitly excluding 'pelican.tests.TestPages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.content' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.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 'pelican.tests.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 'pelican.tests.content' to be distributed and are already explicitly excluding 'pelican.tests.content' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.content.TestCategory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.content.TestCategory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.content.TestCategory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.content.TestCategory' to be distributed and are already explicitly excluding 'pelican.tests.content.TestCategory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.cyclic_intersite_links' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.cyclic_intersite_links' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.cyclic_intersite_links' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.cyclic_intersite_links' to be distributed and are already explicitly excluding 'pelican.tests.cyclic_intersite_links' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.dummy_plugins.namespace_plugin.pelican.plugins.ns_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.dummy_plugins.namespace_plugin.pelican.plugins.ns_plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.dummy_plugins.namespace_plugin.pelican.plugins.ns_plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.dummy_plugins.namespace_plugin.pelican.plugins.ns_plugin' to be distributed and are already explicitly excluding 'pelican.tests.dummy_plugins.namespace_plugin.pelican.plugins.ns_plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.dummy_plugins.normal_plugin.normal_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.dummy_plugins.normal_plugin.normal_plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.dummy_plugins.normal_plugin.normal_plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.dummy_plugins.normal_plugin.normal_plugin' to be distributed and are already explicitly excluding 'pelican.tests.dummy_plugins.normal_plugin.normal_plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.mixed_content' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.mixed_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 'pelican.tests.mixed_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 'pelican.tests.mixed_content' to be distributed and are already explicitly excluding 'pelican.tests.mixed_content' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.nested_content.maindir' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.nested_content.maindir' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.nested_content.maindir' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.nested_content.maindir' to be distributed and are already explicitly excluding 'pelican.tests.nested_content.maindir' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.nested_content.maindir.subdir' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.nested_content.maindir.subdir' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.nested_content.maindir.subdir' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.nested_content.maindir.subdir' to be distributed and are already explicitly excluding 'pelican.tests.nested_content.maindir.subdir' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic' to be distributed and are already explicitly excluding 'pelican.tests.output.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.author' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.author' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic.author' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic.author' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.author' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.category' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.category' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic.category' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic.category' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.category' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.drafts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.drafts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic.drafts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic.drafts' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.drafts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.feeds' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.feeds' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic.feeds' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic.feeds' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.feeds' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.override' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.override' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic.override' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic.override' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.override' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.pages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.pages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic.pages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic.pages' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.pages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.tag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.tag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic.tag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic.tag' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.tag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.theme.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.theme.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 'pelican.tests.output.basic.theme.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 'pelican.tests.output.basic.theme.css' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.theme.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.theme.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.theme.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 'pelican.tests.output.basic.theme.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 'pelican.tests.output.basic.theme.fonts' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.theme.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) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.basic.theme.images.icons' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.basic.theme.images.icons' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.basic.theme.images.icons' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.basic.theme.images.icons' to be distributed and are already explicitly excluding 'pelican.tests.output.basic.theme.images.icons' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom' to be distributed and are already explicitly excluding 'pelican.tests.output.custom' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.author' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.author' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom.author' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom.author' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.author' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.category' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.category' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom.category' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom.category' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.category' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.drafts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.drafts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom.drafts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom.drafts' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.drafts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.feeds' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.feeds' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom.feeds' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom.feeds' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.feeds' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.override' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.override' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom.override' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom.override' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.override' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.pages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.pages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom.pages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom.pages' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.pages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.tag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.tag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom.tag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom.tag' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.tag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.theme.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.theme.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 'pelican.tests.output.custom.theme.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 'pelican.tests.output.custom.theme.css' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.theme.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.theme.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.theme.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 'pelican.tests.output.custom.theme.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 'pelican.tests.output.custom.theme.fonts' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.theme.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) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom.theme.images.icons' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom.theme.images.icons' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom.theme.images.icons' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom.theme.images.icons' to be distributed and are already explicitly excluding 'pelican.tests.output.custom.theme.images.icons' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.author' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.author' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.author' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.author' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.author' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.category' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.category' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.category' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.category' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.category' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.drafts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.drafts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.drafts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.drafts' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.drafts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.feeds' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.feeds' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.feeds' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.feeds' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.feeds' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.override' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.override' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.override' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.override' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.override' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.pages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.pages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.pages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.pages' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.pages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.posts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.posts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.posts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.posts' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.posts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.tag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.tag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.tag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.tag' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.tag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.theme.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.theme.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 'pelican.tests.output.custom_locale.theme.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 'pelican.tests.output.custom_locale.theme.css' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.theme.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.theme.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.theme.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 'pelican.tests.output.custom_locale.theme.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 'pelican.tests.output.custom_locale.theme.fonts' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.theme.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) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.output.custom_locale.theme.images.icons' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.output.custom_locale.theme.images.icons' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.output.custom_locale.theme.images.icons' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.output.custom_locale.theme.images.icons' to be distributed and are already explicitly excluding 'pelican.tests.output.custom_locale.theme.images.icons' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.parse_error' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.parse_error' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.parse_error' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.parse_error' to be distributed and are already explicitly excluding 'pelican.tests.parse_error' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/pelican/plugins copying pelican/plugins/_utils.py -> build/lib/pelican/plugins copying pelican/plugins/signals.py -> build/lib/pelican/plugins creating build/lib/pelican/themes creating build/lib/pelican/themes/notmyidea creating build/lib/pelican/themes/notmyidea/static creating build/lib/pelican/themes/notmyidea/static/css copying pelican/themes/notmyidea/static/css/fonts.css -> build/lib/pelican/themes/notmyidea/static/css copying pelican/themes/notmyidea/static/css/main.css -> build/lib/pelican/themes/notmyidea/static/css copying pelican/themes/notmyidea/static/css/pygment.css -> build/lib/pelican/themes/notmyidea/static/css copying pelican/themes/notmyidea/static/css/reset.css -> build/lib/pelican/themes/notmyidea/static/css copying pelican/themes/notmyidea/static/css/typogrify.css -> build/lib/pelican/themes/notmyidea/static/css copying pelican/themes/notmyidea/static/css/wide.css -> build/lib/pelican/themes/notmyidea/static/css creating build/lib/pelican/themes/notmyidea/static/fonts copying pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.eot -> build/lib/pelican/themes/notmyidea/static/fonts copying pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.svg -> build/lib/pelican/themes/notmyidea/static/fonts copying pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.ttf -> build/lib/pelican/themes/notmyidea/static/fonts copying pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.woff -> build/lib/pelican/themes/notmyidea/static/fonts copying pelican/themes/notmyidea/static/fonts/Yanone_Kaffeesatz_400.woff2 -> build/lib/pelican/themes/notmyidea/static/fonts copying pelican/themes/notmyidea/static/fonts/font.css -> build/lib/pelican/themes/notmyidea/static/fonts creating build/lib/pelican/themes/notmyidea/static/images creating build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/aboutme.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/bitbucket.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/delicious.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/facebook.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/github.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/gitorious.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/gittip.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/google-groups.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/google-plus.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/hackernews.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/lastfm.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/linkedin.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/reddit.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/rss.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/slideshare.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/speakerdeck.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/stackoverflow.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/twitter.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/vimeo.png -> build/lib/pelican/themes/notmyidea/static/images/icons copying pelican/themes/notmyidea/static/images/icons/youtube.png -> build/lib/pelican/themes/notmyidea/static/images/icons creating build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/analytics.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/archives.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/article.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/article_infos.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/author.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/authors.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/base.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/category.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/comments.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/disqus_script.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/github.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/index.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/page.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/period_archives.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/tag.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/taglist.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/tags.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/translations.html -> build/lib/pelican/themes/notmyidea/templates copying pelican/themes/notmyidea/templates/twitter.html -> build/lib/pelican/themes/notmyidea/templates creating build/lib/pelican/themes/simple creating build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/archives.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/article.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/author.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/authors.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/base.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/categories.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/category.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/gosquared.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/index.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/page.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/pagination.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/period_archives.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/tag.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/tags.html -> build/lib/pelican/themes/simple/templates copying pelican/themes/simple/templates/translations.html -> build/lib/pelican/themes/simple/templates creating build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/bad_page.rst -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/draft_page.rst -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/draft_page_markdown.md -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/draft_page_with_template.rst -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/hidden_page.rst -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/hidden_page_markdown.md -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/hidden_page_with_template.rst -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/page.rst -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/page_markdown.md -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/page_used_for_sorting_test.rst -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/page_with_category_and_tag_links.md -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/page_with_static_links.md -> build/lib/pelican/tests/TestPages copying pelican/tests/TestPages/page_with_template.rst -> build/lib/pelican/tests/TestPages creating build/lib/pelican/tests/content copying pelican/tests/content/2012-11-29_rst_w_filename_meta#foo-bar.rst -> build/lib/pelican/tests/content copying pelican/tests/content/2012-11-30_md_w_filename_meta#foo-bar.md -> build/lib/pelican/tests/content copying pelican/tests/content/article.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_attributes_containing_double_quotes.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_capitalized_metadata.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_code_block.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_comments.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_duplicate_tags_authors.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_inline_svg.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_keywords.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_markdown_and_footnote.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_markdown_and_nested_metadata.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_markdown_and_nonascii_summary.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_markdown_and_summary_metadata_multi.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_markdown_and_summary_metadata_single.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_markdown_extension.markdown -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_markdown_markup_extensions.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_md_extension.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_metadata.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_metadata.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_metadata_and_contents.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_metadata_explicit_date_implicit_modified.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_metadata_explicit_dates.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_metadata_implicit_date_explicit_modified.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_metadata_implicit_dates.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_mkd_extension.mkd -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_multiple_authors.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_multiple_authors.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_multiple_authors_list.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_multiple_authors_semicolon.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_multiple_metadata_tags.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_nonconformant_meta_tags.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_null_attributes.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_template.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_typogrify_dashes.md -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_typogrify_dashes.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_uppercase_metadata.html -> build/lib/pelican/tests/content copying pelican/tests/content/article_with_uppercase_metadata.rst -> build/lib/pelican/tests/content copying pelican/tests/content/article_without_category.rst -> build/lib/pelican/tests/content copying pelican/tests/content/bloggerexport.xml -> build/lib/pelican/tests/content copying pelican/tests/content/empty.md -> build/lib/pelican/tests/content copying pelican/tests/content/empty_with_bom.md -> build/lib/pelican/tests/content copying pelican/tests/content/wordpressexport.xml -> build/lib/pelican/tests/content creating build/lib/pelican/tests/content/TestCategory copying pelican/tests/content/TestCategory/article_with_category.rst -> build/lib/pelican/tests/content/TestCategory copying pelican/tests/content/TestCategory/article_without_category.rst -> build/lib/pelican/tests/content/TestCategory creating build/lib/pelican/tests/cyclic_intersite_links copying pelican/tests/cyclic_intersite_links/first-article.rst -> build/lib/pelican/tests/cyclic_intersite_links copying pelican/tests/cyclic_intersite_links/second-article.rst -> build/lib/pelican/tests/cyclic_intersite_links copying pelican/tests/cyclic_intersite_links/third-article.rst -> build/lib/pelican/tests/cyclic_intersite_links creating build/lib/pelican/tests/dummy_plugins creating build/lib/pelican/tests/dummy_plugins/namespace_plugin creating build/lib/pelican/tests/dummy_plugins/namespace_plugin/pelican creating build/lib/pelican/tests/dummy_plugins/namespace_plugin/pelican/plugins creating build/lib/pelican/tests/dummy_plugins/namespace_plugin/pelican/plugins/ns_plugin copying pelican/tests/dummy_plugins/namespace_plugin/pelican/plugins/ns_plugin/__init__.py -> build/lib/pelican/tests/dummy_plugins/namespace_plugin/pelican/plugins/ns_plugin creating build/lib/pelican/tests/dummy_plugins/normal_plugin creating build/lib/pelican/tests/dummy_plugins/normal_plugin/normal_plugin copying pelican/tests/dummy_plugins/normal_plugin/normal_plugin/__init__.py -> build/lib/pelican/tests/dummy_plugins/normal_plugin/normal_plugin copying pelican/tests/dummy_plugins/normal_plugin/normal_plugin/submodule.py -> build/lib/pelican/tests/dummy_plugins/normal_plugin/normal_plugin creating build/lib/pelican/tests/mixed_content copying pelican/tests/mixed_content/short_page.md -> build/lib/pelican/tests/mixed_content creating build/lib/pelican/tests/nested_content creating build/lib/pelican/tests/nested_content/maindir copying pelican/tests/nested_content/maindir/maindir.md -> build/lib/pelican/tests/nested_content/maindir creating build/lib/pelican/tests/nested_content/maindir/subdir copying pelican/tests/nested_content/maindir/subdir/subdir.md -> build/lib/pelican/tests/nested_content/maindir/subdir creating build/lib/pelican/tests/output creating build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/a-markdown-powered-article.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/archives.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/article-1.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/article-2.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/article-3.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/authors.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/categories.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/filename_metadata-example.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/index.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/oh-yeah-fr.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/oh-yeah.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/second-article-fr.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/second-article.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/tags.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/this-is-a-super-article.html -> build/lib/pelican/tests/output/basic copying pelican/tests/output/basic/unbelievable.html -> build/lib/pelican/tests/output/basic creating build/lib/pelican/tests/output/basic/author copying pelican/tests/output/basic/author/alexis-metaireau.html -> build/lib/pelican/tests/output/basic/author creating build/lib/pelican/tests/output/basic/category copying pelican/tests/output/basic/category/bar.html -> build/lib/pelican/tests/output/basic/category copying pelican/tests/output/basic/category/cat1.html -> build/lib/pelican/tests/output/basic/category copying pelican/tests/output/basic/category/misc.html -> build/lib/pelican/tests/output/basic/category copying pelican/tests/output/basic/category/yeah.html -> build/lib/pelican/tests/output/basic/category creating build/lib/pelican/tests/output/basic/drafts copying pelican/tests/output/basic/drafts/a-draft-article-without-date.html -> build/lib/pelican/tests/output/basic/drafts copying pelican/tests/output/basic/drafts/a-draft-article.html -> build/lib/pelican/tests/output/basic/drafts creating build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/alexis-metaireau.atom.xml -> build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/alexis-metaireau.rss.xml -> build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/all-en.atom.xml -> build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/all-fr.atom.xml -> build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/all.atom.xml -> build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/bar.atom.xml -> build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/cat1.atom.xml -> build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/misc.atom.xml -> build/lib/pelican/tests/output/basic/feeds copying pelican/tests/output/basic/feeds/yeah.atom.xml -> build/lib/pelican/tests/output/basic/feeds creating build/lib/pelican/tests/output/basic/override copying pelican/tests/output/basic/override/index.html -> build/lib/pelican/tests/output/basic/override creating build/lib/pelican/tests/output/basic/pages copying pelican/tests/output/basic/pages/this-is-a-test-hidden-page.html -> build/lib/pelican/tests/output/basic/pages copying pelican/tests/output/basic/pages/this-is-a-test-page.html -> build/lib/pelican/tests/output/basic/pages creating build/lib/pelican/tests/output/basic/tag copying pelican/tests/output/basic/tag/bar.html -> build/lib/pelican/tests/output/basic/tag copying pelican/tests/output/basic/tag/baz.html -> build/lib/pelican/tests/output/basic/tag copying pelican/tests/output/basic/tag/foo.html -> build/lib/pelican/tests/output/basic/tag copying pelican/tests/output/basic/tag/foobar.html -> build/lib/pelican/tests/output/basic/tag copying pelican/tests/output/basic/tag/oh.html -> build/lib/pelican/tests/output/basic/tag copying pelican/tests/output/basic/tag/yeah.html -> build/lib/pelican/tests/output/basic/tag creating build/lib/pelican/tests/output/basic/theme creating build/lib/pelican/tests/output/basic/theme/css copying pelican/tests/output/basic/theme/css/fonts.css -> build/lib/pelican/tests/output/basic/theme/css copying pelican/tests/output/basic/theme/css/main.css -> build/lib/pelican/tests/output/basic/theme/css copying pelican/tests/output/basic/theme/css/pygment.css -> build/lib/pelican/tests/output/basic/theme/css copying pelican/tests/output/basic/theme/css/reset.css -> build/lib/pelican/tests/output/basic/theme/css copying pelican/tests/output/basic/theme/css/typogrify.css -> build/lib/pelican/tests/output/basic/theme/css copying pelican/tests/output/basic/theme/css/wide.css -> build/lib/pelican/tests/output/basic/theme/css creating build/lib/pelican/tests/output/basic/theme/fonts copying pelican/tests/output/basic/theme/fonts/font.css -> build/lib/pelican/tests/output/basic/theme/fonts creating build/lib/pelican/tests/output/basic/theme/images creating build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/aboutme.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/bitbucket.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/delicious.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/facebook.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/github.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/gitorious.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/gittip.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/google-groups.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/google-plus.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/hackernews.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/lastfm.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/linkedin.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/reddit.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/rss.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/slideshare.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/speakerdeck.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/stackoverflow.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/twitter.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/vimeo.png -> build/lib/pelican/tests/output/basic/theme/images/icons copying pelican/tests/output/basic/theme/images/icons/youtube.png -> build/lib/pelican/tests/output/basic/theme/images/icons creating build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/a-markdown-powered-article.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/archives.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/article-1.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/article-2.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/article-3.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/authors.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/categories.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/filename_metadata-example.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/index.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/index2.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/index3.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/jinja2_template.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/oh-yeah-fr.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/oh-yeah.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/second-article-fr.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/second-article.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/tags.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/this-is-a-super-article.html -> build/lib/pelican/tests/output/custom copying pelican/tests/output/custom/unbelievable.html -> build/lib/pelican/tests/output/custom creating build/lib/pelican/tests/output/custom/author copying pelican/tests/output/custom/author/alexis-metaireau.html -> build/lib/pelican/tests/output/custom/author copying pelican/tests/output/custom/author/alexis-metaireau2.html -> build/lib/pelican/tests/output/custom/author copying pelican/tests/output/custom/author/alexis-metaireau3.html -> build/lib/pelican/tests/output/custom/author creating build/lib/pelican/tests/output/custom/category copying pelican/tests/output/custom/category/bar.html -> build/lib/pelican/tests/output/custom/category copying pelican/tests/output/custom/category/cat1.html -> build/lib/pelican/tests/output/custom/category copying pelican/tests/output/custom/category/misc.html -> build/lib/pelican/tests/output/custom/category copying pelican/tests/output/custom/category/yeah.html -> build/lib/pelican/tests/output/custom/category creating build/lib/pelican/tests/output/custom/drafts copying pelican/tests/output/custom/drafts/a-draft-article-without-date.html -> build/lib/pelican/tests/output/custom/drafts copying pelican/tests/output/custom/drafts/a-draft-article.html -> build/lib/pelican/tests/output/custom/drafts creating build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/alexis-metaireau.atom.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/alexis-metaireau.rss.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/all-en.atom.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/all-fr.atom.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/all.atom.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/all.rss.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/bar.atom.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/bar.rss.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/cat1.atom.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/cat1.rss.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/misc.atom.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/misc.rss.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/yeah.atom.xml -> build/lib/pelican/tests/output/custom/feeds copying pelican/tests/output/custom/feeds/yeah.rss.xml -> build/lib/pelican/tests/output/custom/feeds creating build/lib/pelican/tests/output/custom/override copying pelican/tests/output/custom/override/index.html -> build/lib/pelican/tests/output/custom/override creating build/lib/pelican/tests/output/custom/pages copying pelican/tests/output/custom/pages/this-is-a-test-hidden-page.html -> build/lib/pelican/tests/output/custom/pages copying pelican/tests/output/custom/pages/this-is-a-test-page.html -> build/lib/pelican/tests/output/custom/pages creating build/lib/pelican/tests/output/custom/tag copying pelican/tests/output/custom/tag/bar.html -> build/lib/pelican/tests/output/custom/tag copying pelican/tests/output/custom/tag/baz.html -> build/lib/pelican/tests/output/custom/tag copying pelican/tests/output/custom/tag/foo.html -> build/lib/pelican/tests/output/custom/tag copying pelican/tests/output/custom/tag/foobar.html -> build/lib/pelican/tests/output/custom/tag copying pelican/tests/output/custom/tag/oh.html -> build/lib/pelican/tests/output/custom/tag copying pelican/tests/output/custom/tag/yeah.html -> build/lib/pelican/tests/output/custom/tag creating build/lib/pelican/tests/output/custom/theme creating build/lib/pelican/tests/output/custom/theme/css copying pelican/tests/output/custom/theme/css/fonts.css -> build/lib/pelican/tests/output/custom/theme/css copying pelican/tests/output/custom/theme/css/main.css -> build/lib/pelican/tests/output/custom/theme/css copying pelican/tests/output/custom/theme/css/pygment.css -> build/lib/pelican/tests/output/custom/theme/css copying pelican/tests/output/custom/theme/css/reset.css -> build/lib/pelican/tests/output/custom/theme/css copying pelican/tests/output/custom/theme/css/typogrify.css -> build/lib/pelican/tests/output/custom/theme/css copying pelican/tests/output/custom/theme/css/wide.css -> build/lib/pelican/tests/output/custom/theme/css creating build/lib/pelican/tests/output/custom/theme/fonts copying pelican/tests/output/custom/theme/fonts/font.css -> build/lib/pelican/tests/output/custom/theme/fonts creating build/lib/pelican/tests/output/custom/theme/images creating build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/aboutme.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/bitbucket.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/delicious.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/facebook.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/github.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/gitorious.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/gittip.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/google-groups.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/google-plus.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/hackernews.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/lastfm.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/linkedin.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/reddit.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/rss.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/slideshare.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/speakerdeck.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/stackoverflow.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/twitter.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/vimeo.png -> build/lib/pelican/tests/output/custom/theme/images/icons copying pelican/tests/output/custom/theme/images/icons/youtube.png -> build/lib/pelican/tests/output/custom/theme/images/icons creating build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/archives.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/authors.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/categories.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/index.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/index2.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/index3.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/jinja2_template.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/oh-yeah-fr.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/second-article-fr.html -> build/lib/pelican/tests/output/custom_locale copying pelican/tests/output/custom_locale/tags.html -> build/lib/pelican/tests/output/custom_locale creating build/lib/pelican/tests/output/custom_locale/author copying pelican/tests/output/custom_locale/author/alexis-metaireau.html -> build/lib/pelican/tests/output/custom_locale/author copying pelican/tests/output/custom_locale/author/alexis-metaireau2.html -> build/lib/pelican/tests/output/custom_locale/author copying pelican/tests/output/custom_locale/author/alexis-metaireau3.html -> build/lib/pelican/tests/output/custom_locale/author creating build/lib/pelican/tests/output/custom_locale/category copying pelican/tests/output/custom_locale/category/bar.html -> build/lib/pelican/tests/output/custom_locale/category copying pelican/tests/output/custom_locale/category/cat1.html -> build/lib/pelican/tests/output/custom_locale/category copying pelican/tests/output/custom_locale/category/misc.html -> build/lib/pelican/tests/output/custom_locale/category copying pelican/tests/output/custom_locale/category/yeah.html -> build/lib/pelican/tests/output/custom_locale/category creating build/lib/pelican/tests/output/custom_locale/drafts copying pelican/tests/output/custom_locale/drafts/a-draft-article-without-date.html -> build/lib/pelican/tests/output/custom_locale/drafts copying pelican/tests/output/custom_locale/drafts/a-draft-article.html -> build/lib/pelican/tests/output/custom_locale/drafts creating build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/alexis-metaireau.atom.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/alexis-metaireau.rss.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/all-en.atom.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/all-fr.atom.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/all.atom.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/all.rss.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/bar.atom.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/bar.rss.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/cat1.atom.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/cat1.rss.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/misc.atom.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/misc.rss.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/yeah.atom.xml -> build/lib/pelican/tests/output/custom_locale/feeds copying pelican/tests/output/custom_locale/feeds/yeah.rss.xml -> build/lib/pelican/tests/output/custom_locale/feeds creating build/lib/pelican/tests/output/custom_locale/override copying pelican/tests/output/custom_locale/override/index.html -> build/lib/pelican/tests/output/custom_locale/override creating build/lib/pelican/tests/output/custom_locale/pages copying pelican/tests/output/custom_locale/pages/this-is-a-test-hidden-page.html -> build/lib/pelican/tests/output/custom_locale/pages copying pelican/tests/output/custom_locale/pages/this-is-a-test-page.html -> build/lib/pelican/tests/output/custom_locale/pages creating build/lib/pelican/tests/output/custom_locale/posts creating build/lib/pelican/tests/output/custom_locale/posts/2010 creating build/lib/pelican/tests/output/custom_locale/posts/2010/décembre creating build/lib/pelican/tests/output/custom_locale/posts/2010/décembre/02 creating build/lib/pelican/tests/output/custom_locale/posts/2010/décembre/02/this-is-a-super-article copying pelican/tests/output/custom_locale/posts/2010/décembre/02/this-is-a-super-article/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2010/décembre/02/this-is-a-super-article creating build/lib/pelican/tests/output/custom_locale/posts/2010/octobre creating build/lib/pelican/tests/output/custom_locale/posts/2010/octobre/15 creating build/lib/pelican/tests/output/custom_locale/posts/2010/octobre/15/unbelievable copying pelican/tests/output/custom_locale/posts/2010/octobre/15/unbelievable/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2010/octobre/15/unbelievable creating build/lib/pelican/tests/output/custom_locale/posts/2010/octobre/20 creating build/lib/pelican/tests/output/custom_locale/posts/2010/octobre/20/oh-yeah copying pelican/tests/output/custom_locale/posts/2010/octobre/20/oh-yeah/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2010/octobre/20/oh-yeah creating build/lib/pelican/tests/output/custom_locale/posts/2011 creating build/lib/pelican/tests/output/custom_locale/posts/2011/avril creating build/lib/pelican/tests/output/custom_locale/posts/2011/avril/20 creating build/lib/pelican/tests/output/custom_locale/posts/2011/avril/20/a-markdown-powered-article copying pelican/tests/output/custom_locale/posts/2011/avril/20/a-markdown-powered-article/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2011/avril/20/a-markdown-powered-article creating build/lib/pelican/tests/output/custom_locale/posts/2011/février creating build/lib/pelican/tests/output/custom_locale/posts/2011/février/17 creating build/lib/pelican/tests/output/custom_locale/posts/2011/février/17/article-1 copying pelican/tests/output/custom_locale/posts/2011/février/17/article-1/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2011/février/17/article-1 creating build/lib/pelican/tests/output/custom_locale/posts/2011/février/17/article-2 copying pelican/tests/output/custom_locale/posts/2011/février/17/article-2/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2011/février/17/article-2 creating build/lib/pelican/tests/output/custom_locale/posts/2011/février/17/article-3 copying pelican/tests/output/custom_locale/posts/2011/février/17/article-3/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2011/février/17/article-3 creating build/lib/pelican/tests/output/custom_locale/posts/2012 creating build/lib/pelican/tests/output/custom_locale/posts/2012/février creating build/lib/pelican/tests/output/custom_locale/posts/2012/février/29 creating build/lib/pelican/tests/output/custom_locale/posts/2012/février/29/second-article copying pelican/tests/output/custom_locale/posts/2012/février/29/second-article/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2012/février/29/second-article creating build/lib/pelican/tests/output/custom_locale/posts/2012/novembre creating build/lib/pelican/tests/output/custom_locale/posts/2012/novembre/30 creating build/lib/pelican/tests/output/custom_locale/posts/2012/novembre/30/filename_metadata-example copying pelican/tests/output/custom_locale/posts/2012/novembre/30/filename_metadata-example/index.html -> build/lib/pelican/tests/output/custom_locale/posts/2012/novembre/30/filename_metadata-example creating build/lib/pelican/tests/output/custom_locale/tag copying pelican/tests/output/custom_locale/tag/bar.html -> build/lib/pelican/tests/output/custom_locale/tag copying pelican/tests/output/custom_locale/tag/baz.html -> build/lib/pelican/tests/output/custom_locale/tag copying pelican/tests/output/custom_locale/tag/foo.html -> build/lib/pelican/tests/output/custom_locale/tag copying pelican/tests/output/custom_locale/tag/foobar.html -> build/lib/pelican/tests/output/custom_locale/tag copying pelican/tests/output/custom_locale/tag/oh.html -> build/lib/pelican/tests/output/custom_locale/tag copying pelican/tests/output/custom_locale/tag/yeah.html -> build/lib/pelican/tests/output/custom_locale/tag creating build/lib/pelican/tests/output/custom_locale/theme creating build/lib/pelican/tests/output/custom_locale/theme/css copying pelican/tests/output/custom_locale/theme/css/fonts.css -> build/lib/pelican/tests/output/custom_locale/theme/css copying pelican/tests/output/custom_locale/theme/css/main.css -> build/lib/pelican/tests/output/custom_locale/theme/css copying pelican/tests/output/custom_locale/theme/css/pygment.css -> build/lib/pelican/tests/output/custom_locale/theme/css copying pelican/tests/output/custom_locale/theme/css/reset.css -> build/lib/pelican/tests/output/custom_locale/theme/css copying pelican/tests/output/custom_locale/theme/css/typogrify.css -> build/lib/pelican/tests/output/custom_locale/theme/css copying pelican/tests/output/custom_locale/theme/css/wide.css -> build/lib/pelican/tests/output/custom_locale/theme/css creating build/lib/pelican/tests/output/custom_locale/theme/fonts copying pelican/tests/output/custom_locale/theme/fonts/font.css -> build/lib/pelican/tests/output/custom_locale/theme/fonts creating build/lib/pelican/tests/output/custom_locale/theme/images creating build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/aboutme.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/bitbucket.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/delicious.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/facebook.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/github.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/gitorious.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/gittip.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/google-groups.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/google-plus.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/hackernews.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/lastfm.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/linkedin.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/reddit.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/rss.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/slideshare.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/speakerdeck.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/stackoverflow.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/twitter.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/vimeo.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons copying pelican/tests/output/custom_locale/theme/images/icons/youtube.png -> build/lib/pelican/tests/output/custom_locale/theme/images/icons creating build/lib/pelican/tests/parse_error copying pelican/tests/parse_error/parse_error.rst -> build/lib/pelican/tests/parse_error creating build/lib/pelican/tests/theme_overrides creating build/lib/pelican/tests/theme_overrides/level1 copying pelican/tests/theme_overrides/level1/article.html -> build/lib/pelican/tests/theme_overrides/level1 creating build/lib/pelican/tests/theme_overrides/level2 copying pelican/tests/theme_overrides/level2/article.html -> build/lib/pelican/tests/theme_overrides/level2 copying pelican/tests/theme_overrides/level2/authors.html -> build/lib/pelican/tests/theme_overrides/level2 /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.theme_overrides.level1' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.theme_overrides.level1' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.theme_overrides.level1' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.theme_overrides.level1' to be distributed and are already explicitly excluding 'pelican.tests.theme_overrides.level1' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.theme_overrides.level2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.theme_overrides.level2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.tests.theme_overrides.level2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.tests.theme_overrides.level2' to be distributed and are already explicitly excluding 'pelican.tests.theme_overrides.level2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.themes.notmyidea.static.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.themes.notmyidea.static.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 'pelican.themes.notmyidea.static.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 'pelican.themes.notmyidea.static.css' to be distributed and are already explicitly excluding 'pelican.themes.notmyidea.static.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.themes.notmyidea.static.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.themes.notmyidea.static.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 'pelican.themes.notmyidea.static.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 'pelican.themes.notmyidea.static.fonts' to be distributed and are already explicitly excluding 'pelican.themes.notmyidea.static.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) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.themes.notmyidea.static.images.icons' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.themes.notmyidea.static.images.icons' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'pelican.themes.notmyidea.static.images.icons' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'pelican.themes.notmyidea.static.images.icons' to be distributed and are already explicitly excluding 'pelican.themes.notmyidea.static.images.icons' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.themes.notmyidea.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.themes.notmyidea.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 'pelican.themes.notmyidea.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 'pelican.themes.notmyidea.templates' to be distributed and are already explicitly excluding 'pelican.themes.notmyidea.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.8/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.themes.simple.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.themes.simple.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 'pelican.themes.simple.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 'pelican.themes.simple.templates' to be distributed and are already explicitly excluding 'pelican.themes.simple.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) cd /tmp/www/py-pelican/work/pelican-4.5.0/docs/ && make SPHINXBUILD=/usr/pkg/bin/sphinx-build-3.8 text man /usr/pkg/bin/sphinx-build-3.8 -b text -d _build/doctrees . _build/text Running Sphinx v7.0.0 making output directory... done building [mo]: targets for 0 po files that are out of date writing output... building [text]: targets for 16 source files that are out of date updating environment: [new config] 16 added, 0 changed, 0 removed reading sources... [ 6%] changelog Exception occurred: File "/usr/pkg/lib/python3.8/site-packages/sphinx/ext/extlinks.py", line 103, in role title = caption % part TypeError: not all arguments converted during string formatting The full traceback has been saved in /tmp/sphinx-err-hfple3al.log, if you want to report the issue to the developers. Please also report this if it was a user error, so that a better error message can be provided next time. A bug report can be filed in the tracker at . Thanks! *** Error code 2 Stop. make[2]: stopped in /tmp/www/py-pelican/work/pelican-4.5.0/docs *** Error code 1 Stop. make[1]: stopped in /amd/pkgsrc/CHROOT/P/pkgsrc/www/py-pelican *** Error code 1 Stop. make: stopped in /amd/pkgsrc/CHROOT/P/pkgsrc/www/py-pelican