<86>Jun 4 04:07:00 userdel[2675390]: delete user 'rooter' <86>Jun 4 04:07:00 groupadd[2675429]: group added to /etc/group: name=rooter, GID=1295 <86>Jun 4 04:07:00 groupadd[2675429]: group added to /etc/gshadow: name=rooter <86>Jun 4 04:07:00 groupadd[2675429]: new group: name=rooter, GID=1295 <86>Jun 4 04:07:00 useradd[2675449]: new user: name=rooter, UID=1295, GID=1295, home=/root, shell=/bin/bash, from=none <86>Jun 4 04:07:00 userdel[2675488]: delete user 'builder' <86>Jun 4 04:07:00 userdel[2675488]: removed group 'builder' owned by 'builder' <86>Jun 4 04:07:00 userdel[2675488]: removed shadow group 'builder' owned by 'builder' <86>Jun 4 04:07:00 groupadd[2675512]: group added to /etc/group: name=builder, GID=1296 <86>Jun 4 04:07:00 groupadd[2675512]: group added to /etc/gshadow: name=builder <86>Jun 4 04:07:00 groupadd[2675512]: new group: name=builder, GID=1296 <86>Jun 4 04:07:00 useradd[2675522]: new user: name=builder, UID=1296, GID=1296, home=/usr/src, shell=/bin/bash, from=none /usr/src/in/srpm/python3-module-pelican-4.6.0-alt7.src.rpm: license not found in '/usr/share/license' directory: AGPLv3 WARNING: %python3_build is deprecated and will be removed in future, please use %pyproject_build instead WARNING: %python3_install is deprecated and will be removed in future, please use %pyproject_install instead <13>Jun 4 04:07:03 rpmi: python-sphinx-objects.inv-1:2.3.12.20230514-alt1 sisyphus+320581.100.1.1 1684213745 installed <13>Jun 4 04:07:03 rpmi: libxslt-1.1.37-alt1 sisyphus+307481.100.1.1 1664360521 installed <13>Jun 4 04:07:03 rpmi: libncurses-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835246 installed <13>Jun 4 04:07:03 rpmi: libtinfo-devel-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835246 installed <13>Jun 4 04:07:03 rpmi: libncurses-devel-6.3.20220618-alt1 sisyphus+302449.100.1.1 1655835246 installed <13>Jun 4 04:07:03 rpmi: libmpdec3-2.5.1-alt3 sisyphus+314490.500.5.1 1675432004 installed <13>Jun 4 04:07:03 rpmi: libgdbm-1.8.3-alt10 sisyphus+278100.1600.1.1 1626058413 installed <13>Jun 4 04:07:03 rpmi: libexpat-2.5.0-alt1 sisyphus+309227.100.1.1 1667075764 installed <13>Jun 4 04:07:03 rpmi: libp11-kit-0.24.1-alt1 sisyphus+293720.100.1.1 1642535264 installed <13>Jun 4 04:07:03 rpmi: libtasn1-4.19.0-alt1 sisyphus+305700.100.1.1 1661359624 installed <13>Jun 4 04:07:03 rpmi: rpm-macros-alternatives-0.5.2-alt2 sisyphus+315270.200.2.1 1676457367 installed <13>Jun 4 04:07:03 rpmi: alternatives-0.5.2-alt2 sisyphus+315270.200.2.1 1676457367 installed <13>Jun 4 04:07:03 rpmi: ca-certificates-2022.12.14-alt1 sisyphus+311754.200.1.1 1671046143 installed <13>Jun 4 04:07:03 rpmi: ca-trust-0.1.4-alt1 sisyphus+308690.100.1.1 1666182992 installed <13>Jun 4 04:07:03 rpmi: p11-kit-trust-0.24.1-alt1 sisyphus+293720.100.1.1 1642535264 installed <13>Jun 4 04:07:03 rpmi: libcrypto1.1-1.1.1u-alt1 sisyphus+322200.100.1.1 1685474736 installed <13>Jun 4 04:07:03 rpmi: libssl1.1-1.1.1u-alt1 sisyphus+322200.100.1.1 1685474736 installed <13>Jun 4 04:07:03 rpmi: python3-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363630 installed <13>Jun 4 04:07:04 rpmi: python3-base-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363630 installed <13>Jun 4 04:07:04 rpmi: python3-module-six-1.16.0-alt1 sisyphus+283489.100.2.1 1629527308 installed <13>Jun 4 04:07:04 rpmi: python3-module-Pygments-2.15.1-alt1 sisyphus+321159.100.2.1 1684486730 installed <13>Jun 4 04:07:04 rpmi: python3-module-pytz-1:2022.6-alt1 sisyphus+311396.200.1.1 1670517427 installed <13>Jun 4 04:07:04 rpmi: python3-module-markupsafe-1:2.1.2-alt1 sisyphus+313626.100.1.1 1674030215 installed <13>Jun 4 04:07:04 rpmi: python3-module-jinja2-3.1.2-alt1 sisyphus+303664.100.1.1 1657809843 installed <13>Jun 4 04:07:04 rpmi: python3-module-feedgenerator-1.9-alt1 sisyphus+236525.40.6.1 1568238138 installed <13>Jun 4 04:07:04 rpmi: python3-module-alabaster-0.7.6-alt4 sisyphus+281697.200.1.1 1627919931 installed <13>Jun 4 04:07:04 rpmi: python3-module-dateutil-2.8.2-alt2 sisyphus+319889.300.1.1 1683215971 installed <13>Jun 4 04:07:04 rpmi: python3-module-genshi-0.7.7-alt1 sisyphus+299111.100.1.1 1651061009 installed <13>Jun 4 04:07:04 rpmi: libpython3-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363630 installed <13>Jun 4 04:07:05 rpmi: python3-module-babel-1:2.12.1-alt1 sisyphus+317409.100.1.1 1679678193 installed <13>Jun 4 04:07:05 rpmi: python3-module-blinker-1.6.2-alt2 sisyphus+320605.100.1.1 1684236585 installed <13>Jun 4 04:07:05 rpmi: python3-module-pycparser-2.21-alt1.1 sisyphus+309935.7300.4.1 1668527005 installed <13>Jun 4 04:07:05 rpmi: python3-module-cffi-1.15.1-alt1 sisyphus+308243.100.2.1 1665650114 installed <13>Jun 4 04:07:05 rpmi: python3-module-cryptography-40.0.2-alt1 sisyphus+318920.100.1.1 1681998082 installed <13>Jun 4 04:07:05 rpmi: python3-module-openssl-23.1.1-alt2 sisyphus+319053.1700.6.1 1682668601 installed <13>Jun 4 04:07:05 rpmi: python3-module-urllib3-2:1.26.14-alt2 sisyphus+318352.100.1.1 1681194106 installed <13>Jun 4 04:07:05 rpmi: python3-module-charset-normalizer-2.1.1-alt1 sisyphus+311047.100.1.1 1669992940 installed <13>Jun 4 04:07:05 rpmi: python3-module-webencodings-0.5.1-alt2 sisyphus+276020.100.1.1 1624812421 installed <13>Jun 4 04:07:05 rpmi: python3-module-html5lib-1:1.1-alt1 sisyphus+278096.120.5.1 1626086978 installed <13>Jun 4 04:07:05 rpmi: python3-module-lxml-4.9.2-alt2 sisyphus+319423.100.1.1 1682592949 installed <13>Jun 4 04:07:05 rpmi: python3-module-docutils-0.18.1-alt2 sisyphus+298475.100.1.1 1650019614 installed <13>Jun 4 04:07:05 rpmi: python3-module-idna-3.4-alt1 sisyphus+307942.100.1.1 1665051373 installed <13>Jun 4 04:07:05 rpmi: python3-module-requests-2.31.0-alt1 sisyphus+321663.100.2.1 1684917021 installed <13>Jun 4 04:07:05 rpmi: python3-module-imagesize-1.4.1-alt1 sisyphus+318084.100.1.1 1680697673 installed <13>Jun 4 04:07:05 rpmi: python3-module-packaging-23.1-alt1 sisyphus+318906.100.2.1 1683015285 installed <13>Jun 4 04:07:05 rpmi: python3-module-snowballstemmer-2.2.0-alt1 sisyphus+319215.100.1.1 1682346633 installed <13>Jun 4 04:07:05 rpmi: python3-module-sphinxcontrib-applehelp-1.0.4-alt1 sisyphus+315438.100.1.1 1676719519 installed <13>Jun 4 04:07:05 rpmi: python3-module-sphinxcontrib-devhelp-1.0.2-alt1 sisyphus+276003.100.2.2 1624879024 installed <13>Jun 4 04:07:05 rpmi: python3-module-sphinxcontrib-jquery-4.1-alt2 sisyphus+317619.100.1.1 1680000409 installed <13>Jun 4 04:07:05 rpmi: python3-module-sphinxcontrib-jsmath-1.0.1-alt1 sisyphus+276004.100.1.1 1624811634 installed <13>Jun 4 04:07:05 rpmi: python3-module-sphinxcontrib-htmlhelp-2.0.0-alt2 sisyphus+298571.100.1.1 1650103344 installed <13>Jun 4 04:07:05 rpmi: python3-module-sphinxcontrib-qthelp-1.0.3-alt2 sisyphus+304787.100.1.1 1659628584 installed <13>Jun 4 04:07:05 rpmi: python3-module-sphinxcontrib-serializinghtml-1.1.5-alt2 sisyphus+298572.100.1.1 1650104574 installed <13>Jun 4 04:07:06 rpmi: python3-module-sphinx-1:6.1.3-alt1 sisyphus+317496.100.2.1 1682012961 installed <13>Jun 4 04:07:06 rpmi: tests-for-installed-python3-pkgs-0.1.22-alt1 sisyphus+319076.100.3.1 1682536051 installed <13>Jun 4 04:07:06 rpmi: rpm-build-python3-0.1.22-alt1 sisyphus+319076.100.3.1 1682536051 installed <13>Jun 4 04:07:06 rpmi: python3-dev-3.10.8-alt1.1 sisyphus+311926.100.2.1 1671363630 installed <13>Jun 4 04:07:06 rpmi: python3-module-pelican-4.6.0-alt7 sisyphus+318628.100.1.1 1681736994 installed <13>Jun 4 04:07:06 rpmi: python3-module-mock-5.0.2-alt1 sisyphus+321633.100.2.2 1684864598 installed <13>Jun 4 04:07:06 rpmi: python3-module-unidecode-0.04.17-alt1.git20141218.1.3 sisyphus+280484.100.1.1 1627013522 installed WARNING: %python3_build is deprecated and will be removed in future, please use %pyproject_build instead WARNING: %python3_install is deprecated and will be removed in future, please use %pyproject_install instead Building target platforms: x86_64 Building for target x86_64 Wrote: /usr/src/in/nosrpm/python3-module-pelican-4.6.0-alt7.nosrc.rpm (w1.gzdio) <13>Jun 4 04:07:09 rpmi: python3-module-pkg_resources-1:67.8.0-alt1 sisyphus+321626.100.2.1 1684831100 installed <13>Jun 4 04:07:09 rpmi: python3-module-setuptools-1:67.8.0-alt1 sisyphus+321626.100.2.1 1684831100 installed WARNING: %python3_build is deprecated and will be removed in future, please use %pyproject_build instead WARNING: %python3_install is deprecated and will be removed in future, please use %pyproject_install instead Installing python3-module-pelican-4.6.0-alt7.src.rpm Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /usr/src/tmp/rpm-tmp.16141 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + rm -rf pelican-4.6.0 + echo 'Source #0 (pelican-4.6.0.tar):' Source #0 (pelican-4.6.0.tar): + /bin/tar -xf /usr/src/RPM/SOURCES/pelican-4.6.0.tar + cd pelican-4.6.0 + /bin/chmod -c -Rf u+rwX,go-w . + echo 'Patch #1 (python3-module-pelican-4.6.0-alt-cannot-import-Markup-from-jinja2.patch):' Patch #1 (python3-module-pelican-4.6.0-alt-cannot-import-Markup-from-jinja2.patch): + /usr/bin/patch -p1 patching file pelican/utils.py patching file pelican/writers.py + rm -rf pelican.egg-info + sed -i 1d pelican/tools/pelican_import.py + sed -i 1d pelican/tools/pelican_quickstart.py + sed -i 1d pelican/tools/pelican_themes.py + sed -i 1d pelican/tools/templates/pelicanconf.py.jinja2 + sed -i 1d pelican/tools/templates/publishconf.py.jinja2 + touch pelican/plugins/__init__.py + exit 0 Executing(%build): /bin/sh -e /usr/src/tmp/rpm-tmp.16141 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd pelican-4.6.0 + CFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto' + export CFLAGS + CXXFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto' + export CXXFLAGS + FFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -flto=auto' + export FFLAGS + /usr/bin/python3 setup.py build running build running build_py creating build creating build/lib creating build/lib/pelican copying pelican/writers.py -> build/lib/pelican copying pelican/utils.py -> build/lib/pelican copying pelican/urlwrappers.py -> build/lib/pelican copying pelican/signals.py -> build/lib/pelican copying pelican/settings.py -> build/lib/pelican copying pelican/server.py -> build/lib/pelican copying pelican/rstdirectives.py -> build/lib/pelican copying pelican/readers.py -> build/lib/pelican copying pelican/paginator.py -> build/lib/pelican copying pelican/log.py -> build/lib/pelican copying pelican/generators.py -> build/lib/pelican copying pelican/contents.py -> build/lib/pelican copying pelican/cache.py -> build/lib/pelican copying pelican/__main__.py -> build/lib/pelican copying pelican/__init__.py -> build/lib/pelican creating build/lib/pelican/tools copying pelican/tools/pelican_themes.py -> build/lib/pelican/tools copying pelican/tools/pelican_quickstart.py -> build/lib/pelican/tools copying pelican/tools/pelican_import.py -> build/lib/pelican/tools copying pelican/tools/__init__.py -> build/lib/pelican/tools creating build/lib/pelican/tests copying pelican/tests/test_utils.py -> build/lib/pelican/tests copying pelican/tests/test_urlwrappers.py -> build/lib/pelican/tests copying pelican/tests/test_testsuite.py -> build/lib/pelican/tests copying pelican/tests/test_settings.py -> build/lib/pelican/tests copying pelican/tests/test_server.py -> build/lib/pelican/tests copying pelican/tests/test_rstdirectives.py -> build/lib/pelican/tests copying pelican/tests/test_readers.py -> build/lib/pelican/tests copying pelican/tests/test_plugins.py -> build/lib/pelican/tests copying pelican/tests/test_pelican.py -> build/lib/pelican/tests copying pelican/tests/test_paginator.py -> build/lib/pelican/tests copying pelican/tests/test_log.py -> build/lib/pelican/tests copying pelican/tests/test_importer.py -> build/lib/pelican/tests copying pelican/tests/test_generators.py -> build/lib/pelican/tests copying pelican/tests/test_contents.py -> build/lib/pelican/tests copying pelican/tests/test_cache.py -> build/lib/pelican/tests copying pelican/tests/support.py -> build/lib/pelican/tests copying pelican/tests/default_conf.py -> build/lib/pelican/tests copying pelican/tests/__init__.py -> build/lib/pelican/tests creating build/lib/pelican/plugins copying pelican/plugins/__init__.py -> build/lib/pelican/plugins copying pelican/plugins/signals.py -> build/lib/pelican/plugins copying pelican/plugins/_utils.py -> build/lib/pelican/plugins 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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.dummy_plugins.normal_plugin.normal_submodule_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.dummy_plugins.normal_plugin.normal_submodule_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_submodule_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_submodule_plugin' to be distributed and are already explicitly excluding 'pelican.tests.dummy_plugins.normal_plugin.normal_submodule_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/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tests.dummy_plugins.normal_plugin.normal_submodule_plugin.subpackage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tests.dummy_plugins.normal_plugin.normal_submodule_plugin.subpackage' as an importable package[^1], but it 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_submodule_plugin.subpackage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can 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_submodule_plugin.subpackage' to be distributed and are already explicitly excluding 'pelican.tests.dummy_plugins.normal_plugin.normal_submodule_plugin.subpackage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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) /usr/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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/lib64/python3/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) /usr/lib64/python3/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pelican.tools.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pelican.tools.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.tools.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.tools.templates' to be distributed and are already explicitly excluding 'pelican.tools.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) 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/tools/templates copying pelican/tools/templates/Makefile.jinja2 -> build/lib/pelican/tools/templates copying pelican/tools/templates/pelicanconf.py.jinja2 -> build/lib/pelican/tools/templates copying pelican/tools/templates/publishconf.py.jinja2 -> build/lib/pelican/tools/templates copying pelican/tools/templates/tasks.py.jinja2 -> build/lib/pelican/tools/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/dummy_plugins/normal_plugin/normal_submodule_plugin copying pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin/__init__.py -> build/lib/pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin copying pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin/subplugin.py -> build/lib/pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin creating build/lib/pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin/subpackage copying pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin/subpackage/__init__.py -> build/lib/pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin/subpackage copying pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin/subpackage/subpackage.py -> build/lib/pelican/tests/dummy_plugins/normal_plugin/normal_submodule_plugin/subpackage 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 + sphinx-build-3 docs html Running Sphinx v6.1.3 making output directory... done building [mo]: targets for 0 po files that are out of date writing output... building [html]: 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/lib/python3/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 /usr/src/tmp/sphinx-err-90_owhrk.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: Bad exit status from /usr/src/tmp/rpm-tmp.16141 (%build) RPM build errors: Bad exit status from /usr/src/tmp/rpm-tmp.16141 (%build) Command exited with non-zero status 1 1.08user 0.21system 0:01.37elapsed 94%CPU (0avgtext+0avgdata 53200maxresident)k 0inputs+0outputs (0major+30810minor)pagefaults 0swaps hsh-rebuild: rebuild of `python3-module-pelican-4.6.0-alt7.src.rpm' failed. Command exited with non-zero status 1 3.34user 2.19system 0:14.60elapsed 37%CPU (0avgtext+0avgdata 110544maxresident)k 22600inputs+0outputs (0major+249978minor)pagefaults 0swaps