2025-09-08T03:53:01,284 Created temporary directory: /tmp/pip-build-tracker-0ixscde0 2025-09-08T03:53:01,285 Initialized build tracking at /tmp/pip-build-tracker-0ixscde0 2025-09-08T03:53:01,285 Created build tracker: /tmp/pip-build-tracker-0ixscde0 2025-09-08T03:53:01,285 Entered build tracker: /tmp/pip-build-tracker-0ixscde0 2025-09-08T03:53:01,285 Created temporary directory: /tmp/pip-wheel-tbnnfhqc 2025-09-08T03:53:01,289 Created temporary directory: /tmp/pip-ephem-wheel-cache-0ewk6gsj 2025-09-08T03:53:01,348 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-09-08T03:53:01,351 2 location(s) to search for versions of publiforge: 2025-09-08T03:53:01,351 * https://pypi.org/simple/publiforge/ 2025-09-08T03:53:01,351 * https://www.piwheels.org/simple/publiforge/ 2025-09-08T03:53:01,351 Fetching project page and analyzing links: https://pypi.org/simple/publiforge/ 2025-09-08T03:53:01,352 Getting page https://pypi.org/simple/publiforge/ 2025-09-08T03:53:01,353 Found index url https://pypi.org/simple/ 2025-09-08T03:53:01,428 Fetched page https://pypi.org/simple/publiforge/ as application/vnd.pypi.simple.v1+json 2025-09-08T03:53:01,429 Found link https://files.pythonhosted.org/packages/eb/e9/c48710181b0fabcdb65e51ba05ce1b39809ff351ac566be9467443e3be68/PubliForge-0.5.tar.gz (from https://pypi.org/simple/publiforge/), version: 0.5 2025-09-08T03:53:01,430 Found link https://files.pythonhosted.org/packages/76/32/79f947887100a55a6d90312bc2f667f2b44a79460ca81bded6cbc9194d65/PubliForge-0.5.1.tar.gz (from https://pypi.org/simple/publiforge/), version: 0.5.1 2025-09-08T03:53:01,430 Found link https://files.pythonhosted.org/packages/33/8c/1057344a688eac7f4750f3a60b7cdd57a38033f834211e366c058d91fda6/PubliForge-0.6.tar.gz (from https://pypi.org/simple/publiforge/), version: 0.6 2025-09-08T03:53:01,430 Found link https://files.pythonhosted.org/packages/bc/d5/7a12945ea459ec20b888c87beb6712d5d8fafe2bcb59d97bbf26b9071998/PubliForge-0.7.tar.gz (from https://pypi.org/simple/publiforge/), version: 0.7 2025-09-08T03:53:01,430 Found link https://files.pythonhosted.org/packages/60/6a/084b0d0d919bddf8045a0ed312d5b877c5d3bd9e4e20109687d69b19dd1e/PubliForge-1.2.tar.gz (from https://pypi.org/simple/publiforge/), version: 1.2 2025-09-08T03:53:01,431 Found link https://files.pythonhosted.org/packages/eb/14/1674e1d4ba9518eaa2e5f6a0a6872e2d069b22819ac554b3a75eaca34b22/PubliForge-2.0.tar.gz (from https://pypi.org/simple/publiforge/), version: 2.0 2025-09-08T03:53:01,431 Found link https://files.pythonhosted.org/packages/ce/99/e78d990cae82141d5f57421395959774c03e3a34d2927996a60732875354/PubliForge-2.1.tar.gz (from https://pypi.org/simple/publiforge/), version: 2.1 2025-09-08T03:53:01,431 Found link https://files.pythonhosted.org/packages/bd/9c/0d22a6f3cc43369284069985bacff0a2eaf355421b58bc6721ac572b2764/PubliForge-2.2.tar.gz (from https://pypi.org/simple/publiforge/), version: 2.2 2025-09-08T03:53:01,431 Fetching project page and analyzing links: https://www.piwheels.org/simple/publiforge/ 2025-09-08T03:53:01,432 Getting page https://www.piwheels.org/simple/publiforge/ 2025-09-08T03:53:01,433 Found index url https://www.piwheels.org/simple/ 2025-09-08T03:53:01,526 Fetched page https://www.piwheels.org/simple/publiforge/ as text/html 2025-09-08T03:53:01,527 Skipping link: not a file: https://www.piwheels.org/simple/publiforge/ 2025-09-08T03:53:01,527 Skipping link: not a file: https://pypi.org/simple/publiforge/ 2025-09-08T03:53:01,553 Given no hashes to check 1 links for project 'publiforge': discarding no candidates 2025-09-08T03:53:01,554 Collecting publiforge==2.0 2025-09-08T03:53:01,555 Created temporary directory: /tmp/pip-unpack-qs8gjq4h 2025-09-08T03:53:01,699 Downloading PubliForge-2.0.tar.gz (9.6 MB) 2025-09-08T03:53:04,581 Added publiforge==2.0 from https://files.pythonhosted.org/packages/eb/14/1674e1d4ba9518eaa2e5f6a0a6872e2d069b22819ac554b3a75eaca34b22/PubliForge-2.0.tar.gz to build tracker '/tmp/pip-build-tracker-0ixscde0' 2025-09-08T03:53:04,582 Running setup.py (path:/tmp/pip-wheel-tbnnfhqc/publiforge_e8b0ae6b644e4753866f56d87c188b85/setup.py) egg_info for package publiforge 2025-09-08T03:53:04,582 Created temporary directory: /tmp/pip-pip-egg-info-cun9_a4g 2025-09-08T03:53:04,583 Preparing metadata (setup.py): started 2025-09-08T03:53:04,583 Running command python setup.py egg_info 2025-09-08T03:53:05,349 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T03:53:05,349 warnings.warn(msg) 2025-09-08T03:53:05,349 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T03:53:05,349 warnings.warn(msg) 2025-09-08T03:53:05,877 running egg_info 2025-09-08T03:53:05,966 creating /tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info 2025-09-08T03:53:05,966 writing /tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info/PKG-INFO 2025-09-08T03:53:05,968 writing dependency_links to /tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info/dependency_links.txt 2025-09-08T03:53:05,969 writing entry points to /tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info/entry_points.txt 2025-09-08T03:53:05,970 writing requirements to /tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info/requires.txt 2025-09-08T03:53:05,970 writing top-level names to /tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info/top_level.txt 2025-09-08T03:53:05,971 writing manifest file '/tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info/SOURCES.txt' 2025-09-08T03:53:06,336 reading manifest file '/tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info/SOURCES.txt' 2025-09-08T03:53:06,337 reading manifest template 'MANIFEST.in' 2025-09-08T03:53:06,339 warning: no files found matching '*.rst' 2025-09-08T03:53:06,901 writing manifest file '/tmp/pip-pip-egg-info-cun9_a4g/PubliForge.egg-info/SOURCES.txt' 2025-09-08T03:53:07,033 Preparing metadata (setup.py): finished with status 'done' 2025-09-08T03:53:07,039 Source in /tmp/pip-wheel-tbnnfhqc/publiforge_e8b0ae6b644e4753866f56d87c188b85 has version 2.0, which satisfies requirement publiforge==2.0 from https://files.pythonhosted.org/packages/eb/14/1674e1d4ba9518eaa2e5f6a0a6872e2d069b22819ac554b3a75eaca34b22/PubliForge-2.0.tar.gz 2025-09-08T03:53:07,039 Removed publiforge==2.0 from https://files.pythonhosted.org/packages/eb/14/1674e1d4ba9518eaa2e5f6a0a6872e2d069b22819ac554b3a75eaca34b22/PubliForge-2.0.tar.gz from build tracker '/tmp/pip-build-tracker-0ixscde0' 2025-09-08T03:53:07,051 Created temporary directory: /tmp/pip-unpack-y50w8loh 2025-09-08T03:53:07,051 Created temporary directory: /tmp/pip-unpack-vbgq6nmc 2025-09-08T03:53:07,052 Building wheels for collected packages: publiforge 2025-09-08T03:53:07,053 Created temporary directory: /tmp/pip-wheel-bzgbjj84 2025-09-08T03:53:07,054 DEPRECATION: Building 'publiforge' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'publiforge'. Discussion can be found at https://github.com/pypa/pip/issues/6334 2025-09-08T03:53:07,055 Building wheel for publiforge (setup.py): started 2025-09-08T03:53:07,056 Destination directory: /tmp/pip-wheel-bzgbjj84 2025-09-08T03:53:07,056 Running command python setup.py bdist_wheel 2025-09-08T03:53:07,824 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T03:53:07,824 warnings.warn(msg) 2025-09-08T03:53:07,825 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T03:53:07,825 warnings.warn(msg) 2025-09-08T03:53:08,269 running bdist_wheel 2025-09-08T03:53:08,711 running build 2025-09-08T03:53:08,711 running build_py 2025-09-08T03:53:08,802 creating build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T03:53:08,803 copying publiforge/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T03:53:08,804 copying publiforge/initialize.py -> build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T03:53:08,805 creating build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,805 copying publiforge/views/job.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,806 copying publiforge/views/file.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,807 copying publiforge/views/build.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,808 copying publiforge/views/maestro.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,809 copying publiforge/views/task.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,809 copying publiforge/views/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,810 copying publiforge/views/group.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,811 copying publiforge/views/role.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,811 copying publiforge/views/selection.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,812 copying publiforge/views/user.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,813 copying publiforge/views/pack.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,814 copying publiforge/views/storage.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,814 copying publiforge/views/security.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,815 copying publiforge/views/indexer.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,816 copying publiforge/views/site.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,816 copying publiforge/views/project.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,817 copying publiforge/views/home.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,818 copying publiforge/views/xmlrpc.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,819 copying publiforge/views/processing.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T03:53:08,820 creating build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,820 copying publiforge/lib/utils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,821 copying publiforge/lib/widget.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,822 copying publiforge/lib/form.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,823 copying publiforge/lib/xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,823 copying publiforge/lib/packutils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,824 copying publiforge/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,825 copying publiforge/lib/viewutils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,825 copying publiforge/lib/handler.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,826 copying publiforge/lib/debug.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T03:53:08,827 creating build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,828 copying publiforge/scripts/pfimage2svg.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,828 copying publiforge/scripts/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,829 copying publiforge/scripts/pfpopulate.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,830 copying publiforge/scripts/pfbuild.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,830 copying publiforge/scripts/pfminify.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,831 copying publiforge/scripts/pftexmath.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,832 copying publiforge/scripts/pfscheduler.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,832 copying publiforge/scripts/pfbackup.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T03:53:08,834 creating build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,834 copying publiforge/models/indexers.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,835 copying publiforge/models/packs.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,835 copying publiforge/models/jobs.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,836 copying publiforge/models/storages.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,837 copying publiforge/models/roles.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,837 copying publiforge/models/users.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,838 copying publiforge/models/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,839 copying publiforge/models/processings.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,839 copying publiforge/models/processors.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,840 copying publiforge/models/tasks.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,841 copying publiforge/models/projects.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,842 copying publiforge/models/groups.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T03:53:08,843 creating build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,843 copying publiforge/tests/test_models_storages.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,844 copying publiforge/tests/test_models_projects.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,844 copying publiforge/tests/test_views_project.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,845 copying publiforge/tests/test_models_processors.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,846 copying publiforge/tests/test_models_groups.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,846 copying publiforge/tests/test_models_users.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,847 copying publiforge/tests/test_scripts_pfbuild.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,848 copying publiforge/tests/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,848 copying publiforge/tests/test_lib_widget.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,849 copying publiforge/tests/test_lib_utils.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,850 copying publiforge/tests/test_lib_form.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,850 copying publiforge/tests/test_lib_xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,851 copying publiforge/tests/test_views_security.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T03:53:08,852 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T03:53:08,852 copying publiforge/lib/rsync/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T03:53:08,853 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T03:53:08,854 copying publiforge/lib/vcs/hgsvn.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T03:53:08,854 copying publiforge/lib/vcs/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T03:53:08,855 copying publiforge/lib/vcs/hg.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T03:53:08,856 copying publiforge/lib/vcs/svn.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T03:53:08,857 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T03:53:08,857 copying publiforge/lib/opener/ini.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T03:53:08,858 copying publiforge/lib/opener/xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T03:53:08,859 copying publiforge/lib/opener/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T03:53:08,860 copying publiforge/lib/opener/image.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T03:53:08,860 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T03:53:08,861 copying publiforge/lib/build/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T03:53:08,861 copying publiforge/lib/build/front.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T03:53:08,862 copying publiforge/lib/build/agent.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T03:53:08,863 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor 2025-09-08T03:53:08,864 copying publiforge/lib/processor/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor 2025-09-08T03:53:08,865 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T03:53:08,865 copying publiforge/lib/processor/leprisme/publiset.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T03:53:08,866 copying publiforge/lib/processor/leprisme/iniscript.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T03:53:08,866 copying publiforge/lib/processor/leprisme/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T03:53:08,867 copying publiforge/lib/processor/leprisme/transform.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T03:53:08,868 copying publiforge/lib/processor/leprisme/containers.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T03:53:08,869 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/generator 2025-09-08T03:53:08,869 copying publiforge/lib/processor/generator/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/generator 2025-09-08T03:53:08,870 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/publiseter 2025-09-08T03:53:08,870 copying publiforge/lib/processor/publiseter/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/publiseter 2025-09-08T03:53:08,871 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/validator 2025-09-08T03:53:08,871 copying publiforge/lib/processor/validator/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/validator 2025-09-08T03:53:08,872 running egg_info 2025-09-08T03:53:08,961 writing PubliForge.egg-info/PKG-INFO 2025-09-08T03:53:08,963 writing dependency_links to PubliForge.egg-info/dependency_links.txt 2025-09-08T03:53:08,964 writing entry points to PubliForge.egg-info/entry_points.txt 2025-09-08T03:53:08,965 writing requirements to PubliForge.egg-info/requires.txt 2025-09-08T03:53:08,965 writing top-level names to PubliForge.egg-info/top_level.txt 2025-09-08T03:53:09,064 reading manifest file 'PubliForge.egg-info/SOURCES.txt' 2025-09-08T03:53:09,108 reading manifest template 'MANIFEST.in' 2025-09-08T03:53:09,110 warning: no files found matching '*.rst' 2025-09-08T03:53:09,679 writing manifest file 'PubliForge.egg-info/SOURCES.txt' 2025-09-08T03:53:09,681 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Locale' is absent from the `packages` configuration. 2025-09-08T03:53:09,681 !! 2025-09-08T03:53:09,681 ******************************************************************************** 2025-09-08T03:53:09,682 ############################ 2025-09-08T03:53:09,682 # Package would be ignored # 2025-09-08T03:53:09,682 ############################ 2025-09-08T03:53:09,682 Python recognizes 'publiforge.Locale' as an importable package[^1], 2025-09-08T03:53:09,682 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,682 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,682 package, please make sure that 'publiforge.Locale' is explicitly added 2025-09-08T03:53:09,682 to the `packages` configuration field. 2025-09-08T03:53:09,683 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,683 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,683 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,683 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,683 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,683 If you don't want 'publiforge.Locale' to be distributed and are 2025-09-08T03:53:09,684 already explicitly excluding 'publiforge.Locale' via 2025-09-08T03:53:09,684 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,684 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,684 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,684 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,684 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,685 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,685 even if it does not contain any `.py` files. 2025-09-08T03:53:09,685 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,685 directory, all directories are treated like packages. 2025-09-08T03:53:09,685 ******************************************************************************** 2025-09-08T03:53:09,685 !! 2025-09-08T03:53:09,685 check.warn(importable) 2025-09-08T03:53:09,685 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Locale.es.LC_MESSAGES' is absent from the `packages` configuration. 2025-09-08T03:53:09,686 !! 2025-09-08T03:53:09,686 ******************************************************************************** 2025-09-08T03:53:09,686 ############################ 2025-09-08T03:53:09,686 # Package would be ignored # 2025-09-08T03:53:09,686 ############################ 2025-09-08T03:53:09,686 Python recognizes 'publiforge.Locale.es.LC_MESSAGES' as an importable package[^1], 2025-09-08T03:53:09,686 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,686 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,687 package, please make sure that 'publiforge.Locale.es.LC_MESSAGES' is explicitly added 2025-09-08T03:53:09,687 to the `packages` configuration field. 2025-09-08T03:53:09,687 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,687 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,687 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,687 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,687 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,688 If you don't want 'publiforge.Locale.es.LC_MESSAGES' to be distributed and are 2025-09-08T03:53:09,688 already explicitly excluding 'publiforge.Locale.es.LC_MESSAGES' via 2025-09-08T03:53:09,688 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,688 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,688 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,688 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,688 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,689 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,689 even if it does not contain any `.py` files. 2025-09-08T03:53:09,689 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,689 directory, all directories are treated like packages. 2025-09-08T03:53:09,689 ******************************************************************************** 2025-09-08T03:53:09,689 !! 2025-09-08T03:53:09,689 check.warn(importable) 2025-09-08T03:53:09,690 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Locale.fr.LC_MESSAGES' is absent from the `packages` configuration. 2025-09-08T03:53:09,690 !! 2025-09-08T03:53:09,690 ******************************************************************************** 2025-09-08T03:53:09,690 ############################ 2025-09-08T03:53:09,690 # Package would be ignored # 2025-09-08T03:53:09,690 ############################ 2025-09-08T03:53:09,690 Python recognizes 'publiforge.Locale.fr.LC_MESSAGES' as an importable package[^1], 2025-09-08T03:53:09,690 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,691 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,691 package, please make sure that 'publiforge.Locale.fr.LC_MESSAGES' is explicitly added 2025-09-08T03:53:09,691 to the `packages` configuration field. 2025-09-08T03:53:09,691 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,691 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,691 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,691 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,691 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,692 If you don't want 'publiforge.Locale.fr.LC_MESSAGES' to be distributed and are 2025-09-08T03:53:09,692 already explicitly excluding 'publiforge.Locale.fr.LC_MESSAGES' via 2025-09-08T03:53:09,692 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,692 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,692 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,692 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,692 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,693 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,693 even if it does not contain any `.py` files. 2025-09-08T03:53:09,693 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,693 directory, all directories are treated like packages. 2025-09-08T03:53:09,693 ******************************************************************************** 2025-09-08T03:53:09,693 !! 2025-09-08T03:53:09,693 check.warn(importable) 2025-09-08T03:53:09,693 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Image' is absent from the `packages` configuration. 2025-09-08T03:53:09,694 !! 2025-09-08T03:53:09,694 ******************************************************************************** 2025-09-08T03:53:09,694 ############################ 2025-09-08T03:53:09,694 # Package would be ignored # 2025-09-08T03:53:09,694 ############################ 2025-09-08T03:53:09,694 Python recognizes 'publiforge.Openers.Image' as an importable package[^1], 2025-09-08T03:53:09,694 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,694 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,694 package, please make sure that 'publiforge.Openers.Image' is explicitly added 2025-09-08T03:53:09,695 to the `packages` configuration field. 2025-09-08T03:53:09,695 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,695 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,695 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,695 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,695 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,695 If you don't want 'publiforge.Openers.Image' to be distributed and are 2025-09-08T03:53:09,696 already explicitly excluding 'publiforge.Openers.Image' via 2025-09-08T03:53:09,696 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,696 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,696 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,696 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,696 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,696 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,696 even if it does not contain any `.py` files. 2025-09-08T03:53:09,697 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,697 directory, all directories are treated like packages. 2025-09-08T03:53:09,697 ******************************************************************************** 2025-09-08T03:53:09,697 !! 2025-09-08T03:53:09,697 check.warn(importable) 2025-09-08T03:53:09,697 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Ini' is absent from the `packages` configuration. 2025-09-08T03:53:09,697 !! 2025-09-08T03:53:09,697 ******************************************************************************** 2025-09-08T03:53:09,697 ############################ 2025-09-08T03:53:09,698 # Package would be ignored # 2025-09-08T03:53:09,698 ############################ 2025-09-08T03:53:09,698 Python recognizes 'publiforge.Openers.Ini' as an importable package[^1], 2025-09-08T03:53:09,698 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,698 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,698 package, please make sure that 'publiforge.Openers.Ini' is explicitly added 2025-09-08T03:53:09,698 to the `packages` configuration field. 2025-09-08T03:53:09,698 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,698 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,699 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,699 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,699 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,699 If you don't want 'publiforge.Openers.Ini' to be distributed and are 2025-09-08T03:53:09,699 already explicitly excluding 'publiforge.Openers.Ini' via 2025-09-08T03:53:09,699 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,699 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,699 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,700 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,700 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,700 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,700 even if it does not contain any `.py` files. 2025-09-08T03:53:09,700 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,701 directory, all directories are treated like packages. 2025-09-08T03:53:09,701 ******************************************************************************** 2025-09-08T03:53:09,701 !! 2025-09-08T03:53:09,701 check.warn(importable) 2025-09-08T03:53:09,701 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.NoMore' is absent from the `packages` configuration. 2025-09-08T03:53:09,701 !! 2025-09-08T03:53:09,701 ******************************************************************************** 2025-09-08T03:53:09,702 ############################ 2025-09-08T03:53:09,702 # Package would be ignored # 2025-09-08T03:53:09,702 ############################ 2025-09-08T03:53:09,702 Python recognizes 'publiforge.Openers.NoMore' as an importable package[^1], 2025-09-08T03:53:09,702 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,702 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,702 package, please make sure that 'publiforge.Openers.NoMore' is explicitly added 2025-09-08T03:53:09,702 to the `packages` configuration field. 2025-09-08T03:53:09,703 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,703 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,703 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,703 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,703 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,703 If you don't want 'publiforge.Openers.NoMore' to be distributed and are 2025-09-08T03:53:09,703 already explicitly excluding 'publiforge.Openers.NoMore' via 2025-09-08T03:53:09,704 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,704 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,704 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,704 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,704 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,704 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,704 even if it does not contain any `.py` files. 2025-09-08T03:53:09,705 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,705 directory, all directories are treated like packages. 2025-09-08T03:53:09,705 ******************************************************************************** 2025-09-08T03:53:09,705 !! 2025-09-08T03:53:09,705 check.warn(importable) 2025-09-08T03:53:09,705 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Plain' is absent from the `packages` configuration. 2025-09-08T03:53:09,705 !! 2025-09-08T03:53:09,705 ******************************************************************************** 2025-09-08T03:53:09,706 ############################ 2025-09-08T03:53:09,706 # Package would be ignored # 2025-09-08T03:53:09,706 ############################ 2025-09-08T03:53:09,706 Python recognizes 'publiforge.Openers.Plain' as an importable package[^1], 2025-09-08T03:53:09,706 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,706 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,706 package, please make sure that 'publiforge.Openers.Plain' is explicitly added 2025-09-08T03:53:09,706 to the `packages` configuration field. 2025-09-08T03:53:09,706 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,707 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,707 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,707 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,707 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,707 If you don't want 'publiforge.Openers.Plain' to be distributed and are 2025-09-08T03:53:09,707 already explicitly excluding 'publiforge.Openers.Plain' via 2025-09-08T03:53:09,707 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,707 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,708 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,708 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,708 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,708 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,708 even if it does not contain any `.py` files. 2025-09-08T03:53:09,708 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,708 directory, all directories are treated like packages. 2025-09-08T03:53:09,709 ******************************************************************************** 2025-09-08T03:53:09,709 !! 2025-09-08T03:53:09,709 check.warn(importable) 2025-09-08T03:53:09,709 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publidoc' is absent from the `packages` configuration. 2025-09-08T03:53:09,709 !! 2025-09-08T03:53:09,709 ******************************************************************************** 2025-09-08T03:53:09,709 ############################ 2025-09-08T03:53:09,709 # Package would be ignored # 2025-09-08T03:53:09,710 ############################ 2025-09-08T03:53:09,710 Python recognizes 'publiforge.Openers.Publidoc' as an importable package[^1], 2025-09-08T03:53:09,710 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,710 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,710 package, please make sure that 'publiforge.Openers.Publidoc' is explicitly added 2025-09-08T03:53:09,710 to the `packages` configuration field. 2025-09-08T03:53:09,710 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,710 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,710 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,711 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,711 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,711 If you don't want 'publiforge.Openers.Publidoc' to be distributed and are 2025-09-08T03:53:09,711 already explicitly excluding 'publiforge.Openers.Publidoc' via 2025-09-08T03:53:09,711 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,711 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,711 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,712 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,712 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,712 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,712 even if it does not contain any `.py` files. 2025-09-08T03:53:09,712 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,712 directory, all directories are treated like packages. 2025-09-08T03:53:09,712 ******************************************************************************** 2025-09-08T03:53:09,713 !! 2025-09-08T03:53:09,713 check.warn(importable) 2025-09-08T03:53:09,713 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publidoc.Maestro' is absent from the `packages` configuration. 2025-09-08T03:53:09,713 !! 2025-09-08T03:53:09,713 ******************************************************************************** 2025-09-08T03:53:09,713 ############################ 2025-09-08T03:53:09,713 # Package would be ignored # 2025-09-08T03:53:09,713 ############################ 2025-09-08T03:53:09,713 Python recognizes 'publiforge.Openers.Publidoc.Maestro' as an importable package[^1], 2025-09-08T03:53:09,714 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,714 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,714 package, please make sure that 'publiforge.Openers.Publidoc.Maestro' is explicitly added 2025-09-08T03:53:09,714 to the `packages` configuration field. 2025-09-08T03:53:09,714 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,714 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,714 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,715 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,715 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,715 If you don't want 'publiforge.Openers.Publidoc.Maestro' to be distributed and are 2025-09-08T03:53:09,715 already explicitly excluding 'publiforge.Openers.Publidoc.Maestro' via 2025-09-08T03:53:09,715 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,715 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,715 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,715 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,716 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,716 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,716 even if it does not contain any `.py` files. 2025-09-08T03:53:09,716 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,716 directory, all directories are treated like packages. 2025-09-08T03:53:09,716 ******************************************************************************** 2025-09-08T03:53:09,717 !! 2025-09-08T03:53:09,717 check.warn(importable) 2025-09-08T03:53:09,717 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publidoc.Regex' is absent from the `packages` configuration. 2025-09-08T03:53:09,717 !! 2025-09-08T03:53:09,717 ******************************************************************************** 2025-09-08T03:53:09,717 ############################ 2025-09-08T03:53:09,717 # Package would be ignored # 2025-09-08T03:53:09,718 ############################ 2025-09-08T03:53:09,718 Python recognizes 'publiforge.Openers.Publidoc.Regex' as an importable package[^1], 2025-09-08T03:53:09,718 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,718 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,718 package, please make sure that 'publiforge.Openers.Publidoc.Regex' is explicitly added 2025-09-08T03:53:09,718 to the `packages` configuration field. 2025-09-08T03:53:09,718 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,719 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,719 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,719 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,719 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,719 If you don't want 'publiforge.Openers.Publidoc.Regex' to be distributed and are 2025-09-08T03:53:09,719 already explicitly excluding 'publiforge.Openers.Publidoc.Regex' via 2025-09-08T03:53:09,719 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,719 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,720 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,720 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,720 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,720 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,720 even if it does not contain any `.py` files. 2025-09-08T03:53:09,720 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,720 directory, all directories are treated like packages. 2025-09-08T03:53:09,721 ******************************************************************************** 2025-09-08T03:53:09,721 !! 2025-09-08T03:53:09,721 check.warn(importable) 2025-09-08T03:53:09,721 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publidoc.Seeds' is absent from the `packages` configuration. 2025-09-08T03:53:09,721 !! 2025-09-08T03:53:09,721 ******************************************************************************** 2025-09-08T03:53:09,721 ############################ 2025-09-08T03:53:09,721 # Package would be ignored # 2025-09-08T03:53:09,721 ############################ 2025-09-08T03:53:09,721 Python recognizes 'publiforge.Openers.Publidoc.Seeds' as an importable package[^1], 2025-09-08T03:53:09,722 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,722 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,722 package, please make sure that 'publiforge.Openers.Publidoc.Seeds' is explicitly added 2025-09-08T03:53:09,722 to the `packages` configuration field. 2025-09-08T03:53:09,722 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,722 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,722 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,722 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,723 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,723 If you don't want 'publiforge.Openers.Publidoc.Seeds' to be distributed and are 2025-09-08T03:53:09,723 already explicitly excluding 'publiforge.Openers.Publidoc.Seeds' via 2025-09-08T03:53:09,723 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,723 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,723 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,723 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,723 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,724 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,724 even if it does not contain any `.py` files. 2025-09-08T03:53:09,724 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,724 directory, all directories are treated like packages. 2025-09-08T03:53:09,724 ******************************************************************************** 2025-09-08T03:53:09,724 !! 2025-09-08T03:53:09,724 check.warn(importable) 2025-09-08T03:53:09,724 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publidoc.Static.Css' is absent from the `packages` configuration. 2025-09-08T03:53:09,725 !! 2025-09-08T03:53:09,725 ******************************************************************************** 2025-09-08T03:53:09,725 ############################ 2025-09-08T03:53:09,725 # Package would be ignored # 2025-09-08T03:53:09,725 ############################ 2025-09-08T03:53:09,725 Python recognizes 'publiforge.Openers.Publidoc.Static.Css' as an importable package[^1], 2025-09-08T03:53:09,725 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,725 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,725 package, please make sure that 'publiforge.Openers.Publidoc.Static.Css' is explicitly added 2025-09-08T03:53:09,726 to the `packages` configuration field. 2025-09-08T03:53:09,726 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,726 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,726 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,726 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,726 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,726 If you don't want 'publiforge.Openers.Publidoc.Static.Css' to be distributed and are 2025-09-08T03:53:09,726 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Css' via 2025-09-08T03:53:09,727 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,727 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,727 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,727 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,727 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,727 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,727 even if it does not contain any `.py` files. 2025-09-08T03:53:09,727 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,728 directory, all directories are treated like packages. 2025-09-08T03:53:09,728 ******************************************************************************** 2025-09-08T03:53:09,728 !! 2025-09-08T03:53:09,728 check.warn(importable) 2025-09-08T03:53:09,728 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publidoc.Static.Js' is absent from the `packages` configuration. 2025-09-08T03:53:09,728 !! 2025-09-08T03:53:09,728 ******************************************************************************** 2025-09-08T03:53:09,728 ############################ 2025-09-08T03:53:09,728 # Package would be ignored # 2025-09-08T03:53:09,729 ############################ 2025-09-08T03:53:09,729 Python recognizes 'publiforge.Openers.Publidoc.Static.Js' as an importable package[^1], 2025-09-08T03:53:09,729 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,729 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,729 package, please make sure that 'publiforge.Openers.Publidoc.Static.Js' is explicitly added 2025-09-08T03:53:09,729 to the `packages` configuration field. 2025-09-08T03:53:09,729 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,729 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,729 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,730 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,730 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,730 If you don't want 'publiforge.Openers.Publidoc.Static.Js' to be distributed and are 2025-09-08T03:53:09,730 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Js' via 2025-09-08T03:53:09,730 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,730 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,730 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,731 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,731 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,731 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,731 even if it does not contain any `.py` files. 2025-09-08T03:53:09,731 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,731 directory, all directories are treated like packages. 2025-09-08T03:53:09,732 ******************************************************************************** 2025-09-08T03:53:09,732 !! 2025-09-08T03:53:09,732 check.warn(importable) 2025-09-08T03:53:09,732 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publidoc.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,732 !! 2025-09-08T03:53:09,732 ******************************************************************************** 2025-09-08T03:53:09,732 ############################ 2025-09-08T03:53:09,732 # Package would be ignored # 2025-09-08T03:53:09,733 ############################ 2025-09-08T03:53:09,733 Python recognizes 'publiforge.Openers.Publidoc.Variables' as an importable package[^1], 2025-09-08T03:53:09,733 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,733 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,733 package, please make sure that 'publiforge.Openers.Publidoc.Variables' is explicitly added 2025-09-08T03:53:09,733 to the `packages` configuration field. 2025-09-08T03:53:09,733 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,733 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,733 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,734 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,734 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,734 If you don't want 'publiforge.Openers.Publidoc.Variables' to be distributed and are 2025-09-08T03:53:09,734 already explicitly excluding 'publiforge.Openers.Publidoc.Variables' via 2025-09-08T03:53:09,734 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,734 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,734 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,734 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,735 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,735 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,735 even if it does not contain any `.py` files. 2025-09-08T03:53:09,735 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,735 directory, all directories are treated like packages. 2025-09-08T03:53:09,735 ******************************************************************************** 2025-09-08T03:53:09,735 !! 2025-09-08T03:53:09,736 check.warn(importable) 2025-09-08T03:53:09,736 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publidoc.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,736 !! 2025-09-08T03:53:09,736 ******************************************************************************** 2025-09-08T03:53:09,736 ############################ 2025-09-08T03:53:09,736 # Package would be ignored # 2025-09-08T03:53:09,736 ############################ 2025-09-08T03:53:09,736 Python recognizes 'publiforge.Openers.Publidoc.Xsl' as an importable package[^1], 2025-09-08T03:53:09,736 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,737 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,737 package, please make sure that 'publiforge.Openers.Publidoc.Xsl' is explicitly added 2025-09-08T03:53:09,737 to the `packages` configuration field. 2025-09-08T03:53:09,737 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,737 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,737 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,737 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,737 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,738 If you don't want 'publiforge.Openers.Publidoc.Xsl' to be distributed and are 2025-09-08T03:53:09,738 already explicitly excluding 'publiforge.Openers.Publidoc.Xsl' via 2025-09-08T03:53:09,738 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,738 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,738 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,738 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,738 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,738 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,739 even if it does not contain any `.py` files. 2025-09-08T03:53:09,739 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,739 directory, all directories are treated like packages. 2025-09-08T03:53:09,739 ******************************************************************************** 2025-09-08T03:53:09,739 !! 2025-09-08T03:53:09,739 check.warn(importable) 2025-09-08T03:53:09,739 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiquiz' is absent from the `packages` configuration. 2025-09-08T03:53:09,739 !! 2025-09-08T03:53:09,739 ******************************************************************************** 2025-09-08T03:53:09,740 ############################ 2025-09-08T03:53:09,740 # Package would be ignored # 2025-09-08T03:53:09,740 ############################ 2025-09-08T03:53:09,740 Python recognizes 'publiforge.Openers.Publiquiz' as an importable package[^1], 2025-09-08T03:53:09,740 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,740 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,740 package, please make sure that 'publiforge.Openers.Publiquiz' is explicitly added 2025-09-08T03:53:09,740 to the `packages` configuration field. 2025-09-08T03:53:09,740 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,740 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,741 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,741 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,741 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,741 If you don't want 'publiforge.Openers.Publiquiz' to be distributed and are 2025-09-08T03:53:09,741 already explicitly excluding 'publiforge.Openers.Publiquiz' via 2025-09-08T03:53:09,741 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,741 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,741 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,742 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,742 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,742 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,742 even if it does not contain any `.py` files. 2025-09-08T03:53:09,742 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,742 directory, all directories are treated like packages. 2025-09-08T03:53:09,742 ******************************************************************************** 2025-09-08T03:53:09,743 !! 2025-09-08T03:53:09,743 check.warn(importable) 2025-09-08T03:53:09,743 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiquiz.Regex' is absent from the `packages` configuration. 2025-09-08T03:53:09,743 !! 2025-09-08T03:53:09,743 ******************************************************************************** 2025-09-08T03:53:09,743 ############################ 2025-09-08T03:53:09,743 # Package would be ignored # 2025-09-08T03:53:09,743 ############################ 2025-09-08T03:53:09,743 Python recognizes 'publiforge.Openers.Publiquiz.Regex' as an importable package[^1], 2025-09-08T03:53:09,744 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,744 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,744 package, please make sure that 'publiforge.Openers.Publiquiz.Regex' is explicitly added 2025-09-08T03:53:09,744 to the `packages` configuration field. 2025-09-08T03:53:09,744 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,744 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,744 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,744 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,745 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,745 If you don't want 'publiforge.Openers.Publiquiz.Regex' to be distributed and are 2025-09-08T03:53:09,745 already explicitly excluding 'publiforge.Openers.Publiquiz.Regex' via 2025-09-08T03:53:09,745 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,745 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,745 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,745 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,746 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,746 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,746 even if it does not contain any `.py` files. 2025-09-08T03:53:09,746 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,746 directory, all directories are treated like packages. 2025-09-08T03:53:09,746 ******************************************************************************** 2025-09-08T03:53:09,747 !! 2025-09-08T03:53:09,747 check.warn(importable) 2025-09-08T03:53:09,747 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiquiz.Seeds' is absent from the `packages` configuration. 2025-09-08T03:53:09,747 !! 2025-09-08T03:53:09,747 ******************************************************************************** 2025-09-08T03:53:09,747 ############################ 2025-09-08T03:53:09,747 # Package would be ignored # 2025-09-08T03:53:09,747 ############################ 2025-09-08T03:53:09,747 Python recognizes 'publiforge.Openers.Publiquiz.Seeds' as an importable package[^1], 2025-09-08T03:53:09,747 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,748 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,748 package, please make sure that 'publiforge.Openers.Publiquiz.Seeds' is explicitly added 2025-09-08T03:53:09,748 to the `packages` configuration field. 2025-09-08T03:53:09,748 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,748 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,748 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,748 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,749 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,749 If you don't want 'publiforge.Openers.Publiquiz.Seeds' to be distributed and are 2025-09-08T03:53:09,749 already explicitly excluding 'publiforge.Openers.Publiquiz.Seeds' via 2025-09-08T03:53:09,749 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,749 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,749 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,749 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,749 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,750 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,750 even if it does not contain any `.py` files. 2025-09-08T03:53:09,750 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,750 directory, all directories are treated like packages. 2025-09-08T03:53:09,750 ******************************************************************************** 2025-09-08T03:53:09,750 !! 2025-09-08T03:53:09,750 check.warn(importable) 2025-09-08T03:53:09,750 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiquiz.Static.Css' is absent from the `packages` configuration. 2025-09-08T03:53:09,750 !! 2025-09-08T03:53:09,751 ******************************************************************************** 2025-09-08T03:53:09,751 ############################ 2025-09-08T03:53:09,751 # Package would be ignored # 2025-09-08T03:53:09,751 ############################ 2025-09-08T03:53:09,751 Python recognizes 'publiforge.Openers.Publiquiz.Static.Css' as an importable package[^1], 2025-09-08T03:53:09,751 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,751 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,751 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Css' is explicitly added 2025-09-08T03:53:09,751 to the `packages` configuration field. 2025-09-08T03:53:09,752 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,752 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,752 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,752 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,752 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,752 If you don't want 'publiforge.Openers.Publiquiz.Static.Css' to be distributed and are 2025-09-08T03:53:09,752 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Css' via 2025-09-08T03:53:09,753 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,753 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,753 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,753 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,753 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,753 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,753 even if it does not contain any `.py` files. 2025-09-08T03:53:09,753 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,754 directory, all directories are treated like packages. 2025-09-08T03:53:09,754 ******************************************************************************** 2025-09-08T03:53:09,754 !! 2025-09-08T03:53:09,754 check.warn(importable) 2025-09-08T03:53:09,754 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiquiz.Static.Js' is absent from the `packages` configuration. 2025-09-08T03:53:09,754 !! 2025-09-08T03:53:09,754 ******************************************************************************** 2025-09-08T03:53:09,754 ############################ 2025-09-08T03:53:09,754 # Package would be ignored # 2025-09-08T03:53:09,755 ############################ 2025-09-08T03:53:09,755 Python recognizes 'publiforge.Openers.Publiquiz.Static.Js' as an importable package[^1], 2025-09-08T03:53:09,755 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,755 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,755 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Js' is explicitly added 2025-09-08T03:53:09,755 to the `packages` configuration field. 2025-09-08T03:53:09,755 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,755 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,755 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,756 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,756 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,756 If you don't want 'publiforge.Openers.Publiquiz.Static.Js' to be distributed and are 2025-09-08T03:53:09,756 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Js' via 2025-09-08T03:53:09,756 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,756 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,756 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,756 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,757 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,757 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,757 even if it does not contain any `.py` files. 2025-09-08T03:53:09,757 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,757 directory, all directories are treated like packages. 2025-09-08T03:53:09,757 ******************************************************************************** 2025-09-08T03:53:09,757 !! 2025-09-08T03:53:09,758 check.warn(importable) 2025-09-08T03:53:09,758 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiquiz.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,758 !! 2025-09-08T03:53:09,758 ******************************************************************************** 2025-09-08T03:53:09,758 ############################ 2025-09-08T03:53:09,758 # Package would be ignored # 2025-09-08T03:53:09,758 ############################ 2025-09-08T03:53:09,758 Python recognizes 'publiforge.Openers.Publiquiz.Variables' as an importable package[^1], 2025-09-08T03:53:09,758 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,758 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,759 package, please make sure that 'publiforge.Openers.Publiquiz.Variables' is explicitly added 2025-09-08T03:53:09,759 to the `packages` configuration field. 2025-09-08T03:53:09,759 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,759 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,759 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,759 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,760 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,760 If you don't want 'publiforge.Openers.Publiquiz.Variables' to be distributed and are 2025-09-08T03:53:09,760 already explicitly excluding 'publiforge.Openers.Publiquiz.Variables' via 2025-09-08T03:53:09,760 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,760 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,760 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,760 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,761 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,761 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,761 even if it does not contain any `.py` files. 2025-09-08T03:53:09,761 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,761 directory, all directories are treated like packages. 2025-09-08T03:53:09,761 ******************************************************************************** 2025-09-08T03:53:09,761 !! 2025-09-08T03:53:09,761 check.warn(importable) 2025-09-08T03:53:09,762 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiquiz.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,762 !! 2025-09-08T03:53:09,762 ******************************************************************************** 2025-09-08T03:53:09,762 ############################ 2025-09-08T03:53:09,762 # Package would be ignored # 2025-09-08T03:53:09,762 ############################ 2025-09-08T03:53:09,762 Python recognizes 'publiforge.Openers.Publiquiz.Xsl' as an importable package[^1], 2025-09-08T03:53:09,762 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,762 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,763 package, please make sure that 'publiforge.Openers.Publiquiz.Xsl' is explicitly added 2025-09-08T03:53:09,763 to the `packages` configuration field. 2025-09-08T03:53:09,763 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,763 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,763 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,763 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,763 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,764 If you don't want 'publiforge.Openers.Publiquiz.Xsl' to be distributed and are 2025-09-08T03:53:09,764 already explicitly excluding 'publiforge.Openers.Publiquiz.Xsl' via 2025-09-08T03:53:09,764 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,764 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,764 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,764 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,764 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,764 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,765 even if it does not contain any `.py` files. 2025-09-08T03:53:09,765 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,765 directory, all directories are treated like packages. 2025-09-08T03:53:09,765 ******************************************************************************** 2025-09-08T03:53:09,765 !! 2025-09-08T03:53:09,765 check.warn(importable) 2025-09-08T03:53:09,765 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiset' is absent from the `packages` configuration. 2025-09-08T03:53:09,765 !! 2025-09-08T03:53:09,765 ******************************************************************************** 2025-09-08T03:53:09,765 ############################ 2025-09-08T03:53:09,766 # Package would be ignored # 2025-09-08T03:53:09,766 ############################ 2025-09-08T03:53:09,766 Python recognizes 'publiforge.Openers.Publiset' as an importable package[^1], 2025-09-08T03:53:09,766 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,766 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,766 package, please make sure that 'publiforge.Openers.Publiset' is explicitly added 2025-09-08T03:53:09,766 to the `packages` configuration field. 2025-09-08T03:53:09,766 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,766 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,767 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,767 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,767 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,767 If you don't want 'publiforge.Openers.Publiset' to be distributed and are 2025-09-08T03:53:09,767 already explicitly excluding 'publiforge.Openers.Publiset' via 2025-09-08T03:53:09,767 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,767 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,767 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,768 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,768 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,768 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,768 even if it does not contain any `.py` files. 2025-09-08T03:53:09,768 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,768 directory, all directories are treated like packages. 2025-09-08T03:53:09,768 ******************************************************************************** 2025-09-08T03:53:09,769 !! 2025-09-08T03:53:09,769 check.warn(importable) 2025-09-08T03:53:09,769 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiset.Regex' is absent from the `packages` configuration. 2025-09-08T03:53:09,769 !! 2025-09-08T03:53:09,769 ******************************************************************************** 2025-09-08T03:53:09,769 ############################ 2025-09-08T03:53:09,769 # Package would be ignored # 2025-09-08T03:53:09,769 ############################ 2025-09-08T03:53:09,769 Python recognizes 'publiforge.Openers.Publiset.Regex' as an importable package[^1], 2025-09-08T03:53:09,769 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,770 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,770 package, please make sure that 'publiforge.Openers.Publiset.Regex' is explicitly added 2025-09-08T03:53:09,770 to the `packages` configuration field. 2025-09-08T03:53:09,770 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,770 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,770 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,770 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,770 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,771 If you don't want 'publiforge.Openers.Publiset.Regex' to be distributed and are 2025-09-08T03:53:09,771 already explicitly excluding 'publiforge.Openers.Publiset.Regex' via 2025-09-08T03:53:09,771 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,771 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,771 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,771 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,771 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,772 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,772 even if it does not contain any `.py` files. 2025-09-08T03:53:09,772 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,772 directory, all directories are treated like packages. 2025-09-08T03:53:09,772 ******************************************************************************** 2025-09-08T03:53:09,772 !! 2025-09-08T03:53:09,772 check.warn(importable) 2025-09-08T03:53:09,772 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiset.Seeds' is absent from the `packages` configuration. 2025-09-08T03:53:09,772 !! 2025-09-08T03:53:09,773 ******************************************************************************** 2025-09-08T03:53:09,773 ############################ 2025-09-08T03:53:09,773 # Package would be ignored # 2025-09-08T03:53:09,773 ############################ 2025-09-08T03:53:09,773 Python recognizes 'publiforge.Openers.Publiset.Seeds' as an importable package[^1], 2025-09-08T03:53:09,773 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,773 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,773 package, please make sure that 'publiforge.Openers.Publiset.Seeds' is explicitly added 2025-09-08T03:53:09,773 to the `packages` configuration field. 2025-09-08T03:53:09,774 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,774 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,774 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,774 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,774 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,774 If you don't want 'publiforge.Openers.Publiset.Seeds' to be distributed and are 2025-09-08T03:53:09,775 already explicitly excluding 'publiforge.Openers.Publiset.Seeds' via 2025-09-08T03:53:09,775 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,775 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,775 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,775 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,775 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,776 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,776 even if it does not contain any `.py` files. 2025-09-08T03:53:09,776 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,776 directory, all directories are treated like packages. 2025-09-08T03:53:09,776 ******************************************************************************** 2025-09-08T03:53:09,776 !! 2025-09-08T03:53:09,776 check.warn(importable) 2025-09-08T03:53:09,776 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiset.Static.Css' is absent from the `packages` configuration. 2025-09-08T03:53:09,776 !! 2025-09-08T03:53:09,776 ******************************************************************************** 2025-09-08T03:53:09,777 ############################ 2025-09-08T03:53:09,777 # Package would be ignored # 2025-09-08T03:53:09,777 ############################ 2025-09-08T03:53:09,777 Python recognizes 'publiforge.Openers.Publiset.Static.Css' as an importable package[^1], 2025-09-08T03:53:09,777 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,777 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,777 package, please make sure that 'publiforge.Openers.Publiset.Static.Css' is explicitly added 2025-09-08T03:53:09,777 to the `packages` configuration field. 2025-09-08T03:53:09,777 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,778 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,778 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,778 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,778 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,778 If you don't want 'publiforge.Openers.Publiset.Static.Css' to be distributed and are 2025-09-08T03:53:09,778 already explicitly excluding 'publiforge.Openers.Publiset.Static.Css' via 2025-09-08T03:53:09,778 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,778 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,778 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,779 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,779 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,779 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,779 even if it does not contain any `.py` files. 2025-09-08T03:53:09,779 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,779 directory, all directories are treated like packages. 2025-09-08T03:53:09,779 ******************************************************************************** 2025-09-08T03:53:09,780 !! 2025-09-08T03:53:09,780 check.warn(importable) 2025-09-08T03:53:09,780 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiset.Static.Images' is absent from the `packages` configuration. 2025-09-08T03:53:09,780 !! 2025-09-08T03:53:09,780 ******************************************************************************** 2025-09-08T03:53:09,780 ############################ 2025-09-08T03:53:09,780 # Package would be ignored # 2025-09-08T03:53:09,780 ############################ 2025-09-08T03:53:09,780 Python recognizes 'publiforge.Openers.Publiset.Static.Images' as an importable package[^1], 2025-09-08T03:53:09,780 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,781 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,781 package, please make sure that 'publiforge.Openers.Publiset.Static.Images' is explicitly added 2025-09-08T03:53:09,781 to the `packages` configuration field. 2025-09-08T03:53:09,781 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,781 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,781 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,781 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,782 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,782 If you don't want 'publiforge.Openers.Publiset.Static.Images' to be distributed and are 2025-09-08T03:53:09,782 already explicitly excluding 'publiforge.Openers.Publiset.Static.Images' via 2025-09-08T03:53:09,782 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,782 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,782 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,782 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,782 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,783 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,783 even if it does not contain any `.py` files. 2025-09-08T03:53:09,783 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,783 directory, all directories are treated like packages. 2025-09-08T03:53:09,783 ******************************************************************************** 2025-09-08T03:53:09,783 !! 2025-09-08T03:53:09,783 check.warn(importable) 2025-09-08T03:53:09,783 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiset.Static.Js' is absent from the `packages` configuration. 2025-09-08T03:53:09,783 !! 2025-09-08T03:53:09,784 ******************************************************************************** 2025-09-08T03:53:09,784 ############################ 2025-09-08T03:53:09,784 # Package would be ignored # 2025-09-08T03:53:09,784 ############################ 2025-09-08T03:53:09,784 Python recognizes 'publiforge.Openers.Publiset.Static.Js' as an importable package[^1], 2025-09-08T03:53:09,784 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,784 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,784 package, please make sure that 'publiforge.Openers.Publiset.Static.Js' is explicitly added 2025-09-08T03:53:09,784 to the `packages` configuration field. 2025-09-08T03:53:09,785 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,785 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,785 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,785 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,785 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,785 If you don't want 'publiforge.Openers.Publiset.Static.Js' to be distributed and are 2025-09-08T03:53:09,785 already explicitly excluding 'publiforge.Openers.Publiset.Static.Js' via 2025-09-08T03:53:09,786 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,786 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,786 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,786 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,786 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,786 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,786 even if it does not contain any `.py` files. 2025-09-08T03:53:09,786 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,787 directory, all directories are treated like packages. 2025-09-08T03:53:09,787 ******************************************************************************** 2025-09-08T03:53:09,787 !! 2025-09-08T03:53:09,787 check.warn(importable) 2025-09-08T03:53:09,787 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiset.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,787 !! 2025-09-08T03:53:09,787 ******************************************************************************** 2025-09-08T03:53:09,787 ############################ 2025-09-08T03:53:09,788 # Package would be ignored # 2025-09-08T03:53:09,788 ############################ 2025-09-08T03:53:09,788 Python recognizes 'publiforge.Openers.Publiset.Variables' as an importable package[^1], 2025-09-08T03:53:09,788 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,788 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,788 package, please make sure that 'publiforge.Openers.Publiset.Variables' is explicitly added 2025-09-08T03:53:09,788 to the `packages` configuration field. 2025-09-08T03:53:09,788 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,789 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,789 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,789 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,789 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,789 If you don't want 'publiforge.Openers.Publiset.Variables' to be distributed and are 2025-09-08T03:53:09,789 already explicitly excluding 'publiforge.Openers.Publiset.Variables' via 2025-09-08T03:53:09,789 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,789 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,790 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,790 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,790 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,790 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,790 even if it does not contain any `.py` files. 2025-09-08T03:53:09,790 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,790 directory, all directories are treated like packages. 2025-09-08T03:53:09,791 ******************************************************************************** 2025-09-08T03:53:09,791 !! 2025-09-08T03:53:09,791 check.warn(importable) 2025-09-08T03:53:09,791 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiset.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,791 !! 2025-09-08T03:53:09,791 ******************************************************************************** 2025-09-08T03:53:09,791 ############################ 2025-09-08T03:53:09,791 # Package would be ignored # 2025-09-08T03:53:09,791 ############################ 2025-09-08T03:53:09,792 Python recognizes 'publiforge.Openers.Publiset.Xsl' as an importable package[^1], 2025-09-08T03:53:09,792 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,792 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,792 package, please make sure that 'publiforge.Openers.Publiset.Xsl' is explicitly added 2025-09-08T03:53:09,792 to the `packages` configuration field. 2025-09-08T03:53:09,792 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,792 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,792 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,793 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,793 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,793 If you don't want 'publiforge.Openers.Publiset.Xsl' to be distributed and are 2025-09-08T03:53:09,793 already explicitly excluding 'publiforge.Openers.Publiset.Xsl' via 2025-09-08T03:53:09,793 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,793 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,793 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,793 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,794 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,794 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,794 even if it does not contain any `.py` files. 2025-09-08T03:53:09,794 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,794 directory, all directories are treated like packages. 2025-09-08T03:53:09,794 ******************************************************************************** 2025-09-08T03:53:09,794 !! 2025-09-08T03:53:09,794 check.warn(importable) 2025-09-08T03:53:09,795 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Xml' is absent from the `packages` configuration. 2025-09-08T03:53:09,795 !! 2025-09-08T03:53:09,795 ******************************************************************************** 2025-09-08T03:53:09,795 ############################ 2025-09-08T03:53:09,795 # Package would be ignored # 2025-09-08T03:53:09,795 ############################ 2025-09-08T03:53:09,795 Python recognizes 'publiforge.Openers.Xml' as an importable package[^1], 2025-09-08T03:53:09,795 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,795 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,795 package, please make sure that 'publiforge.Openers.Xml' is explicitly added 2025-09-08T03:53:09,796 to the `packages` configuration field. 2025-09-08T03:53:09,796 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,796 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,796 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,796 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,796 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,796 If you don't want 'publiforge.Openers.Xml' to be distributed and are 2025-09-08T03:53:09,797 already explicitly excluding 'publiforge.Openers.Xml' via 2025-09-08T03:53:09,797 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,797 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,797 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,797 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,797 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,797 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,797 even if it does not contain any `.py` files. 2025-09-08T03:53:09,798 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,798 directory, all directories are treated like packages. 2025-09-08T03:53:09,798 ******************************************************************************** 2025-09-08T03:53:09,798 !! 2025-09-08T03:53:09,798 check.warn(importable) 2025-09-08T03:53:09,798 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Xml.Static.Css' is absent from the `packages` configuration. 2025-09-08T03:53:09,798 !! 2025-09-08T03:53:09,798 ******************************************************************************** 2025-09-08T03:53:09,798 ############################ 2025-09-08T03:53:09,799 # Package would be ignored # 2025-09-08T03:53:09,799 ############################ 2025-09-08T03:53:09,799 Python recognizes 'publiforge.Openers.Xml.Static.Css' as an importable package[^1], 2025-09-08T03:53:09,799 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,799 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,799 package, please make sure that 'publiforge.Openers.Xml.Static.Css' is explicitly added 2025-09-08T03:53:09,799 to the `packages` configuration field. 2025-09-08T03:53:09,799 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,799 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,799 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,800 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,800 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,800 If you don't want 'publiforge.Openers.Xml.Static.Css' to be distributed and are 2025-09-08T03:53:09,800 already explicitly excluding 'publiforge.Openers.Xml.Static.Css' via 2025-09-08T03:53:09,800 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,800 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,800 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,801 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,801 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,801 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,801 even if it does not contain any `.py` files. 2025-09-08T03:53:09,801 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,801 directory, all directories are treated like packages. 2025-09-08T03:53:09,801 ******************************************************************************** 2025-09-08T03:53:09,802 !! 2025-09-08T03:53:09,802 check.warn(importable) 2025-09-08T03:53:09,802 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Xml.Static.Images' is absent from the `packages` configuration. 2025-09-08T03:53:09,802 !! 2025-09-08T03:53:09,802 ******************************************************************************** 2025-09-08T03:53:09,802 ############################ 2025-09-08T03:53:09,802 # Package would be ignored # 2025-09-08T03:53:09,802 ############################ 2025-09-08T03:53:09,803 Python recognizes 'publiforge.Openers.Xml.Static.Images' as an importable package[^1], 2025-09-08T03:53:09,803 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,803 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,803 package, please make sure that 'publiforge.Openers.Xml.Static.Images' is explicitly added 2025-09-08T03:53:09,803 to the `packages` configuration field. 2025-09-08T03:53:09,803 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,803 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,803 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,804 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,804 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,804 If you don't want 'publiforge.Openers.Xml.Static.Images' to be distributed and are 2025-09-08T03:53:09,804 already explicitly excluding 'publiforge.Openers.Xml.Static.Images' via 2025-09-08T03:53:09,804 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,804 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,804 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,805 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,805 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,805 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,805 even if it does not contain any `.py` files. 2025-09-08T03:53:09,805 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,805 directory, all directories are treated like packages. 2025-09-08T03:53:09,805 ******************************************************************************** 2025-09-08T03:53:09,806 !! 2025-09-08T03:53:09,806 check.warn(importable) 2025-09-08T03:53:09,806 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Xml.Static.Js' is absent from the `packages` configuration. 2025-09-08T03:53:09,806 !! 2025-09-08T03:53:09,806 ******************************************************************************** 2025-09-08T03:53:09,806 ############################ 2025-09-08T03:53:09,806 # Package would be ignored # 2025-09-08T03:53:09,806 ############################ 2025-09-08T03:53:09,806 Python recognizes 'publiforge.Openers.Xml.Static.Js' as an importable package[^1], 2025-09-08T03:53:09,806 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,807 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,807 package, please make sure that 'publiforge.Openers.Xml.Static.Js' is explicitly added 2025-09-08T03:53:09,807 to the `packages` configuration field. 2025-09-08T03:53:09,807 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,807 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,807 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,807 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,807 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,808 If you don't want 'publiforge.Openers.Xml.Static.Js' to be distributed and are 2025-09-08T03:53:09,808 already explicitly excluding 'publiforge.Openers.Xml.Static.Js' via 2025-09-08T03:53:09,808 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,808 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,808 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,808 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,808 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,809 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,809 even if it does not contain any `.py` files. 2025-09-08T03:53:09,809 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,809 directory, all directories are treated like packages. 2025-09-08T03:53:09,809 ******************************************************************************** 2025-09-08T03:53:09,809 !! 2025-09-08T03:53:09,809 check.warn(importable) 2025-09-08T03:53:09,809 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.CharCount' is absent from the `packages` configuration. 2025-09-08T03:53:09,809 !! 2025-09-08T03:53:09,810 ******************************************************************************** 2025-09-08T03:53:09,810 ############################ 2025-09-08T03:53:09,810 # Package would be ignored # 2025-09-08T03:53:09,810 ############################ 2025-09-08T03:53:09,810 Python recognizes 'publiforge.Processors.CharCount' as an importable package[^1], 2025-09-08T03:53:09,810 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,810 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,810 package, please make sure that 'publiforge.Processors.CharCount' is explicitly added 2025-09-08T03:53:09,810 to the `packages` configuration field. 2025-09-08T03:53:09,811 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,811 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,811 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,811 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,811 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,811 If you don't want 'publiforge.Processors.CharCount' to be distributed and are 2025-09-08T03:53:09,811 already explicitly excluding 'publiforge.Processors.CharCount' via 2025-09-08T03:53:09,811 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,812 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,812 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,812 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,812 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,812 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,812 even if it does not contain any `.py` files. 2025-09-08T03:53:09,812 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,812 directory, all directories are treated like packages. 2025-09-08T03:53:09,813 ******************************************************************************** 2025-09-08T03:53:09,813 !! 2025-09-08T03:53:09,813 check.warn(importable) 2025-09-08T03:53:09,813 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.CharCount.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,813 !! 2025-09-08T03:53:09,813 ******************************************************************************** 2025-09-08T03:53:09,813 ############################ 2025-09-08T03:53:09,813 # Package would be ignored # 2025-09-08T03:53:09,813 ############################ 2025-09-08T03:53:09,814 Python recognizes 'publiforge.Processors.CharCount.Xsl' as an importable package[^1], 2025-09-08T03:53:09,814 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,814 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,814 package, please make sure that 'publiforge.Processors.CharCount.Xsl' is explicitly added 2025-09-08T03:53:09,814 to the `packages` configuration field. 2025-09-08T03:53:09,814 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,814 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,814 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,815 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,815 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,815 If you don't want 'publiforge.Processors.CharCount.Xsl' to be distributed and are 2025-09-08T03:53:09,815 already explicitly excluding 'publiforge.Processors.CharCount.Xsl' via 2025-09-08T03:53:09,815 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,815 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,815 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,815 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,816 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,816 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,816 even if it does not contain any `.py` files. 2025-09-08T03:53:09,816 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,816 directory, all directories are treated like packages. 2025-09-08T03:53:09,816 ******************************************************************************** 2025-09-08T03:53:09,817 !! 2025-09-08T03:53:09,817 check.warn(importable) 2025-09-08T03:53:09,817 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.CleanStorage' is absent from the `packages` configuration. 2025-09-08T03:53:09,817 !! 2025-09-08T03:53:09,817 ******************************************************************************** 2025-09-08T03:53:09,817 ############################ 2025-09-08T03:53:09,817 # Package would be ignored # 2025-09-08T03:53:09,817 ############################ 2025-09-08T03:53:09,817 Python recognizes 'publiforge.Processors.CleanStorage' as an importable package[^1], 2025-09-08T03:53:09,818 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,818 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,818 package, please make sure that 'publiforge.Processors.CleanStorage' is explicitly added 2025-09-08T03:53:09,818 to the `packages` configuration field. 2025-09-08T03:53:09,818 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,818 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,818 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,818 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,819 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,819 If you don't want 'publiforge.Processors.CleanStorage' to be distributed and are 2025-09-08T03:53:09,819 already explicitly excluding 'publiforge.Processors.CleanStorage' via 2025-09-08T03:53:09,819 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,819 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,819 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,819 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,820 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,820 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,820 even if it does not contain any `.py` files. 2025-09-08T03:53:09,820 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,820 directory, all directories are treated like packages. 2025-09-08T03:53:09,820 ******************************************************************************** 2025-09-08T03:53:09,820 !! 2025-09-08T03:53:09,820 check.warn(importable) 2025-09-08T03:53:09,820 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.CleanStorage.lib' is absent from the `packages` configuration. 2025-09-08T03:53:09,821 !! 2025-09-08T03:53:09,821 ******************************************************************************** 2025-09-08T03:53:09,821 ############################ 2025-09-08T03:53:09,821 # Package would be ignored # 2025-09-08T03:53:09,821 ############################ 2025-09-08T03:53:09,821 Python recognizes 'publiforge.Processors.CleanStorage.lib' as an importable package[^1], 2025-09-08T03:53:09,821 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,821 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,821 package, please make sure that 'publiforge.Processors.CleanStorage.lib' is explicitly added 2025-09-08T03:53:09,822 to the `packages` configuration field. 2025-09-08T03:53:09,822 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,822 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,822 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,822 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,822 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,822 If you don't want 'publiforge.Processors.CleanStorage.lib' to be distributed and are 2025-09-08T03:53:09,822 already explicitly excluding 'publiforge.Processors.CleanStorage.lib' via 2025-09-08T03:53:09,823 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,823 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,823 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,823 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,823 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,823 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,823 even if it does not contain any `.py` files. 2025-09-08T03:53:09,824 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,824 directory, all directories are treated like packages. 2025-09-08T03:53:09,824 ******************************************************************************** 2025-09-08T03:53:09,824 !! 2025-09-08T03:53:09,824 check.warn(importable) 2025-09-08T03:53:09,824 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.DTBookValid' is absent from the `packages` configuration. 2025-09-08T03:53:09,824 !! 2025-09-08T03:53:09,824 ******************************************************************************** 2025-09-08T03:53:09,824 ############################ 2025-09-08T03:53:09,824 # Package would be ignored # 2025-09-08T03:53:09,825 ############################ 2025-09-08T03:53:09,825 Python recognizes 'publiforge.Processors.DTBookValid' as an importable package[^1], 2025-09-08T03:53:09,825 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,825 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,825 package, please make sure that 'publiforge.Processors.DTBookValid' is explicitly added 2025-09-08T03:53:09,825 to the `packages` configuration field. 2025-09-08T03:53:09,825 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,825 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,825 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,826 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,826 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,826 If you don't want 'publiforge.Processors.DTBookValid' to be distributed and are 2025-09-08T03:53:09,826 already explicitly excluding 'publiforge.Processors.DTBookValid' via 2025-09-08T03:53:09,826 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,826 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,826 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,826 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,827 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,827 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,827 even if it does not contain any `.py` files. 2025-09-08T03:53:09,827 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,827 directory, all directories are treated like packages. 2025-09-08T03:53:09,827 ******************************************************************************** 2025-09-08T03:53:09,827 !! 2025-09-08T03:53:09,828 check.warn(importable) 2025-09-08T03:53:09,828 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.DTBookValid.RelaxNG' is absent from the `packages` configuration. 2025-09-08T03:53:09,828 !! 2025-09-08T03:53:09,828 ******************************************************************************** 2025-09-08T03:53:09,828 ############################ 2025-09-08T03:53:09,828 # Package would be ignored # 2025-09-08T03:53:09,828 ############################ 2025-09-08T03:53:09,828 Python recognizes 'publiforge.Processors.DTBookValid.RelaxNG' as an importable package[^1], 2025-09-08T03:53:09,828 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,828 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,829 package, please make sure that 'publiforge.Processors.DTBookValid.RelaxNG' is explicitly added 2025-09-08T03:53:09,829 to the `packages` configuration field. 2025-09-08T03:53:09,829 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,829 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,829 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,829 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,829 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,830 If you don't want 'publiforge.Processors.DTBookValid.RelaxNG' to be distributed and are 2025-09-08T03:53:09,830 already explicitly excluding 'publiforge.Processors.DTBookValid.RelaxNG' via 2025-09-08T03:53:09,830 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,830 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,830 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,830 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,830 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,831 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,831 even if it does not contain any `.py` files. 2025-09-08T03:53:09,831 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,831 directory, all directories are treated like packages. 2025-09-08T03:53:09,831 ******************************************************************************** 2025-09-08T03:53:09,831 !! 2025-09-08T03:53:09,831 check.warn(importable) 2025-09-08T03:53:09,831 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PackFilling' is absent from the `packages` configuration. 2025-09-08T03:53:09,832 !! 2025-09-08T03:53:09,832 ******************************************************************************** 2025-09-08T03:53:09,832 ############################ 2025-09-08T03:53:09,832 # Package would be ignored # 2025-09-08T03:53:09,832 ############################ 2025-09-08T03:53:09,832 Python recognizes 'publiforge.Processors.PackFilling' as an importable package[^1], 2025-09-08T03:53:09,832 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,832 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,833 package, please make sure that 'publiforge.Processors.PackFilling' is explicitly added 2025-09-08T03:53:09,833 to the `packages` configuration field. 2025-09-08T03:53:09,833 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,833 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,833 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,833 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,833 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,834 If you don't want 'publiforge.Processors.PackFilling' to be distributed and are 2025-09-08T03:53:09,834 already explicitly excluding 'publiforge.Processors.PackFilling' via 2025-09-08T03:53:09,834 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,834 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,834 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,834 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,834 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,834 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,835 even if it does not contain any `.py` files. 2025-09-08T03:53:09,835 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,835 directory, all directories are treated like packages. 2025-09-08T03:53:09,835 ******************************************************************************** 2025-09-08T03:53:09,835 !! 2025-09-08T03:53:09,835 check.warn(importable) 2025-09-08T03:53:09,835 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PackFilling.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,835 !! 2025-09-08T03:53:09,835 ******************************************************************************** 2025-09-08T03:53:09,836 ############################ 2025-09-08T03:53:09,836 # Package would be ignored # 2025-09-08T03:53:09,836 ############################ 2025-09-08T03:53:09,836 Python recognizes 'publiforge.Processors.PackFilling.Variables' as an importable package[^1], 2025-09-08T03:53:09,836 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,836 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,836 package, please make sure that 'publiforge.Processors.PackFilling.Variables' is explicitly added 2025-09-08T03:53:09,836 to the `packages` configuration field. 2025-09-08T03:53:09,836 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,836 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,837 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,837 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,837 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,837 If you don't want 'publiforge.Processors.PackFilling.Variables' to be distributed and are 2025-09-08T03:53:09,837 already explicitly excluding 'publiforge.Processors.PackFilling.Variables' via 2025-09-08T03:53:09,837 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,837 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,837 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,838 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,838 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,838 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,838 even if it does not contain any `.py` files. 2025-09-08T03:53:09,838 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,838 directory, all directories are treated like packages. 2025-09-08T03:53:09,838 ******************************************************************************** 2025-09-08T03:53:09,839 !! 2025-09-08T03:53:09,839 check.warn(importable) 2025-09-08T03:53:09,839 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PackFilling.lib' is absent from the `packages` configuration. 2025-09-08T03:53:09,839 !! 2025-09-08T03:53:09,839 ******************************************************************************** 2025-09-08T03:53:09,839 ############################ 2025-09-08T03:53:09,839 # Package would be ignored # 2025-09-08T03:53:09,839 ############################ 2025-09-08T03:53:09,839 Python recognizes 'publiforge.Processors.PackFilling.lib' as an importable package[^1], 2025-09-08T03:53:09,839 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,840 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,840 package, please make sure that 'publiforge.Processors.PackFilling.lib' is explicitly added 2025-09-08T03:53:09,840 to the `packages` configuration field. 2025-09-08T03:53:09,840 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,840 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,840 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,840 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,840 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,841 If you don't want 'publiforge.Processors.PackFilling.lib' to be distributed and are 2025-09-08T03:53:09,841 already explicitly excluding 'publiforge.Processors.PackFilling.lib' via 2025-09-08T03:53:09,841 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,841 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,841 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,841 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,841 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,842 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,842 even if it does not contain any `.py` files. 2025-09-08T03:53:09,842 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,842 directory, all directories are treated like packages. 2025-09-08T03:53:09,842 ******************************************************************************** 2025-09-08T03:53:09,842 !! 2025-09-08T03:53:09,842 check.warn(importable) 2025-09-08T03:53:09,842 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Parallel' is absent from the `packages` configuration. 2025-09-08T03:53:09,842 !! 2025-09-08T03:53:09,843 ******************************************************************************** 2025-09-08T03:53:09,843 ############################ 2025-09-08T03:53:09,843 # Package would be ignored # 2025-09-08T03:53:09,843 ############################ 2025-09-08T03:53:09,843 Python recognizes 'publiforge.Processors.Parallel' as an importable package[^1], 2025-09-08T03:53:09,843 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,843 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,843 package, please make sure that 'publiforge.Processors.Parallel' is explicitly added 2025-09-08T03:53:09,843 to the `packages` configuration field. 2025-09-08T03:53:09,844 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,844 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,844 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,844 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,844 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,844 If you don't want 'publiforge.Processors.Parallel' to be distributed and are 2025-09-08T03:53:09,845 already explicitly excluding 'publiforge.Processors.Parallel' via 2025-09-08T03:53:09,845 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,845 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,845 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,845 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,845 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,846 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,846 even if it does not contain any `.py` files. 2025-09-08T03:53:09,846 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,846 directory, all directories are treated like packages. 2025-09-08T03:53:09,846 ******************************************************************************** 2025-09-08T03:53:09,846 !! 2025-09-08T03:53:09,846 check.warn(importable) 2025-09-08T03:53:09,846 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Parallel.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,846 !! 2025-09-08T03:53:09,847 ******************************************************************************** 2025-09-08T03:53:09,847 ############################ 2025-09-08T03:53:09,847 # Package would be ignored # 2025-09-08T03:53:09,847 ############################ 2025-09-08T03:53:09,847 Python recognizes 'publiforge.Processors.Parallel.Variables' as an importable package[^1], 2025-09-08T03:53:09,847 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,847 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,847 package, please make sure that 'publiforge.Processors.Parallel.Variables' is explicitly added 2025-09-08T03:53:09,847 to the `packages` configuration field. 2025-09-08T03:53:09,848 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,848 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,848 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,848 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,848 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,848 If you don't want 'publiforge.Processors.Parallel.Variables' to be distributed and are 2025-09-08T03:53:09,848 already explicitly excluding 'publiforge.Processors.Parallel.Variables' via 2025-09-08T03:53:09,849 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,849 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,849 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,849 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,849 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,849 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,849 even if it does not contain any `.py` files. 2025-09-08T03:53:09,849 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,850 directory, all directories are treated like packages. 2025-09-08T03:53:09,850 ******************************************************************************** 2025-09-08T03:53:09,850 !! 2025-09-08T03:53:09,850 check.warn(importable) 2025-09-08T03:53:09,850 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv' is absent from the `packages` configuration. 2025-09-08T03:53:09,850 !! 2025-09-08T03:53:09,850 ******************************************************************************** 2025-09-08T03:53:09,850 ############################ 2025-09-08T03:53:09,850 # Package would be ignored # 2025-09-08T03:53:09,851 ############################ 2025-09-08T03:53:09,851 Python recognizes 'publiforge.Processors.Publidoc2Csv' as an importable package[^1], 2025-09-08T03:53:09,851 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,851 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,851 package, please make sure that 'publiforge.Processors.Publidoc2Csv' is explicitly added 2025-09-08T03:53:09,851 to the `packages` configuration field. 2025-09-08T03:53:09,851 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,851 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,851 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,852 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,852 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,852 If you don't want 'publiforge.Processors.Publidoc2Csv' to be distributed and are 2025-09-08T03:53:09,852 already explicitly excluding 'publiforge.Processors.Publidoc2Csv' via 2025-09-08T03:53:09,852 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,852 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,852 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,853 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,853 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,853 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,853 even if it does not contain any `.py` files. 2025-09-08T03:53:09,853 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,853 directory, all directories are treated like packages. 2025-09-08T03:53:09,853 ******************************************************************************** 2025-09-08T03:53:09,853 !! 2025-09-08T03:53:09,854 check.warn(importable) 2025-09-08T03:53:09,854 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.Regex' is absent from the `packages` configuration. 2025-09-08T03:53:09,854 !! 2025-09-08T03:53:09,854 ******************************************************************************** 2025-09-08T03:53:09,854 ############################ 2025-09-08T03:53:09,854 # Package would be ignored # 2025-09-08T03:53:09,854 ############################ 2025-09-08T03:53:09,854 Python recognizes 'publiforge.Processors.Publidoc2Csv.Regex' as an importable package[^1], 2025-09-08T03:53:09,854 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,855 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,855 package, please make sure that 'publiforge.Processors.Publidoc2Csv.Regex' is explicitly added 2025-09-08T03:53:09,855 to the `packages` configuration field. 2025-09-08T03:53:09,855 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,855 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,855 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,855 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,855 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,856 If you don't want 'publiforge.Processors.Publidoc2Csv.Regex' to be distributed and are 2025-09-08T03:53:09,856 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.Regex' via 2025-09-08T03:53:09,856 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,856 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,856 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,856 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,856 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,857 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,857 even if it does not contain any `.py` files. 2025-09-08T03:53:09,857 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,857 directory, all directories are treated like packages. 2025-09-08T03:53:09,857 ******************************************************************************** 2025-09-08T03:53:09,857 !! 2025-09-08T03:53:09,857 check.warn(importable) 2025-09-08T03:53:09,857 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.Templates' is absent from the `packages` configuration. 2025-09-08T03:53:09,857 !! 2025-09-08T03:53:09,857 ******************************************************************************** 2025-09-08T03:53:09,858 ############################ 2025-09-08T03:53:09,858 # Package would be ignored # 2025-09-08T03:53:09,858 ############################ 2025-09-08T03:53:09,858 Python recognizes 'publiforge.Processors.Publidoc2Csv.Templates' as an importable package[^1], 2025-09-08T03:53:09,858 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,858 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,858 package, please make sure that 'publiforge.Processors.Publidoc2Csv.Templates' is explicitly added 2025-09-08T03:53:09,858 to the `packages` configuration field. 2025-09-08T03:53:09,859 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,859 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,859 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,859 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,859 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,859 If you don't want 'publiforge.Processors.Publidoc2Csv.Templates' to be distributed and are 2025-09-08T03:53:09,860 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.Templates' via 2025-09-08T03:53:09,860 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,860 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,860 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,860 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,860 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,860 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,861 even if it does not contain any `.py` files. 2025-09-08T03:53:09,861 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,861 directory, all directories are treated like packages. 2025-09-08T03:53:09,861 ******************************************************************************** 2025-09-08T03:53:09,861 !! 2025-09-08T03:53:09,861 check.warn(importable) 2025-09-08T03:53:09,861 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,861 !! 2025-09-08T03:53:09,861 ******************************************************************************** 2025-09-08T03:53:09,862 ############################ 2025-09-08T03:53:09,862 # Package would be ignored # 2025-09-08T03:53:09,862 ############################ 2025-09-08T03:53:09,862 Python recognizes 'publiforge.Processors.Publidoc2Csv.Variables' as an importable package[^1], 2025-09-08T03:53:09,862 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,862 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,862 package, please make sure that 'publiforge.Processors.Publidoc2Csv.Variables' is explicitly added 2025-09-08T03:53:09,862 to the `packages` configuration field. 2025-09-08T03:53:09,862 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,863 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,863 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,863 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,863 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,863 If you don't want 'publiforge.Processors.Publidoc2Csv.Variables' to be distributed and are 2025-09-08T03:53:09,863 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.Variables' via 2025-09-08T03:53:09,863 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,863 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,863 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,864 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,864 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,864 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,864 even if it does not contain any `.py` files. 2025-09-08T03:53:09,864 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,864 directory, all directories are treated like packages. 2025-09-08T03:53:09,864 ******************************************************************************** 2025-09-08T03:53:09,865 !! 2025-09-08T03:53:09,865 check.warn(importable) 2025-09-08T03:53:09,865 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,865 !! 2025-09-08T03:53:09,865 ******************************************************************************** 2025-09-08T03:53:09,865 ############################ 2025-09-08T03:53:09,865 # Package would be ignored # 2025-09-08T03:53:09,865 ############################ 2025-09-08T03:53:09,865 Python recognizes 'publiforge.Processors.Publidoc2Csv.Xsl' as an importable package[^1], 2025-09-08T03:53:09,865 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,866 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,866 package, please make sure that 'publiforge.Processors.Publidoc2Csv.Xsl' is explicitly added 2025-09-08T03:53:09,866 to the `packages` configuration field. 2025-09-08T03:53:09,866 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,866 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,866 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,866 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,867 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,867 If you don't want 'publiforge.Processors.Publidoc2Csv.Xsl' to be distributed and are 2025-09-08T03:53:09,867 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.Xsl' via 2025-09-08T03:53:09,867 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,867 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,867 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,867 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,867 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,868 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,868 even if it does not contain any `.py` files. 2025-09-08T03:53:09,868 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,868 directory, all directories are treated like packages. 2025-09-08T03:53:09,868 ******************************************************************************** 2025-09-08T03:53:09,868 !! 2025-09-08T03:53:09,868 check.warn(importable) 2025-09-08T03:53:09,868 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.lib' is absent from the `packages` configuration. 2025-09-08T03:53:09,868 !! 2025-09-08T03:53:09,869 ******************************************************************************** 2025-09-08T03:53:09,869 ############################ 2025-09-08T03:53:09,869 # Package would be ignored # 2025-09-08T03:53:09,869 ############################ 2025-09-08T03:53:09,869 Python recognizes 'publiforge.Processors.Publidoc2Csv.lib' as an importable package[^1], 2025-09-08T03:53:09,869 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,869 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,869 package, please make sure that 'publiforge.Processors.Publidoc2Csv.lib' is explicitly added 2025-09-08T03:53:09,869 to the `packages` configuration field. 2025-09-08T03:53:09,870 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,870 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,870 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,870 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,870 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,870 If you don't want 'publiforge.Processors.Publidoc2Csv.lib' to be distributed and are 2025-09-08T03:53:09,870 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.lib' via 2025-09-08T03:53:09,870 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,870 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,871 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,871 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,871 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,871 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,871 even if it does not contain any `.py` files. 2025-09-08T03:53:09,871 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,871 directory, all directories are treated like packages. 2025-09-08T03:53:09,872 ******************************************************************************** 2025-09-08T03:53:09,872 !! 2025-09-08T03:53:09,872 check.warn(importable) 2025-09-08T03:53:09,872 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2DTBook' is absent from the `packages` configuration. 2025-09-08T03:53:09,872 !! 2025-09-08T03:53:09,872 ******************************************************************************** 2025-09-08T03:53:09,872 ############################ 2025-09-08T03:53:09,873 # Package would be ignored # 2025-09-08T03:53:09,873 ############################ 2025-09-08T03:53:09,873 Python recognizes 'publiforge.Processors.Publidoc2DTBook' as an importable package[^1], 2025-09-08T03:53:09,873 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,873 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,873 package, please make sure that 'publiforge.Processors.Publidoc2DTBook' is explicitly added 2025-09-08T03:53:09,873 to the `packages` configuration field. 2025-09-08T03:53:09,873 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,874 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,874 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,874 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,874 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,874 If you don't want 'publiforge.Processors.Publidoc2DTBook' to be distributed and are 2025-09-08T03:53:09,874 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook' via 2025-09-08T03:53:09,874 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,874 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,875 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,875 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,875 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,875 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,875 even if it does not contain any `.py` files. 2025-09-08T03:53:09,875 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,875 directory, all directories are treated like packages. 2025-09-08T03:53:09,876 ******************************************************************************** 2025-09-08T03:53:09,876 !! 2025-09-08T03:53:09,876 check.warn(importable) 2025-09-08T03:53:09,876 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2DTBook.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,876 !! 2025-09-08T03:53:09,876 ******************************************************************************** 2025-09-08T03:53:09,876 ############################ 2025-09-08T03:53:09,876 # Package would be ignored # 2025-09-08T03:53:09,876 ############################ 2025-09-08T03:53:09,876 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Variables' as an importable package[^1], 2025-09-08T03:53:09,877 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,877 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,877 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Variables' is explicitly added 2025-09-08T03:53:09,877 to the `packages` configuration field. 2025-09-08T03:53:09,877 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,877 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,877 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,877 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,878 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,878 If you don't want 'publiforge.Processors.Publidoc2DTBook.Variables' to be distributed and are 2025-09-08T03:53:09,878 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Variables' via 2025-09-08T03:53:09,878 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,878 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,878 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,878 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,879 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,879 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,879 even if it does not contain any `.py` files. 2025-09-08T03:53:09,879 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,879 directory, all directories are treated like packages. 2025-09-08T03:53:09,879 ******************************************************************************** 2025-09-08T03:53:09,879 !! 2025-09-08T03:53:09,879 check.warn(importable) 2025-09-08T03:53:09,879 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2DTBook.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,880 !! 2025-09-08T03:53:09,880 ******************************************************************************** 2025-09-08T03:53:09,880 ############################ 2025-09-08T03:53:09,880 # Package would be ignored # 2025-09-08T03:53:09,880 ############################ 2025-09-08T03:53:09,880 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Xsl' as an importable package[^1], 2025-09-08T03:53:09,880 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,880 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,880 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Xsl' is explicitly added 2025-09-08T03:53:09,881 to the `packages` configuration field. 2025-09-08T03:53:09,881 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,881 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,881 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,881 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,881 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,881 If you don't want 'publiforge.Processors.Publidoc2DTBook.Xsl' to be distributed and are 2025-09-08T03:53:09,881 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Xsl' via 2025-09-08T03:53:09,882 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,882 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,882 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,882 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,882 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,882 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,882 even if it does not contain any `.py` files. 2025-09-08T03:53:09,883 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,883 directory, all directories are treated like packages. 2025-09-08T03:53:09,883 ******************************************************************************** 2025-09-08T03:53:09,883 !! 2025-09-08T03:53:09,883 check.warn(importable) 2025-09-08T03:53:09,883 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub2' is absent from the `packages` configuration. 2025-09-08T03:53:09,883 !! 2025-09-08T03:53:09,883 ******************************************************************************** 2025-09-08T03:53:09,883 ############################ 2025-09-08T03:53:09,884 # Package would be ignored # 2025-09-08T03:53:09,884 ############################ 2025-09-08T03:53:09,884 Python recognizes 'publiforge.Processors.Publidoc2EPub2' as an importable package[^1], 2025-09-08T03:53:09,884 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,884 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,884 package, please make sure that 'publiforge.Processors.Publidoc2EPub2' is explicitly added 2025-09-08T03:53:09,884 to the `packages` configuration field. 2025-09-08T03:53:09,884 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,884 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,884 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,885 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,885 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,885 If you don't want 'publiforge.Processors.Publidoc2EPub2' to be distributed and are 2025-09-08T03:53:09,885 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2' via 2025-09-08T03:53:09,885 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,885 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,885 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,886 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,886 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,886 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,886 even if it does not contain any `.py` files. 2025-09-08T03:53:09,886 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,886 directory, all directories are treated like packages. 2025-09-08T03:53:09,886 ******************************************************************************** 2025-09-08T03:53:09,887 !! 2025-09-08T03:53:09,887 check.warn(importable) 2025-09-08T03:53:09,887 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.Templates' is absent from the `packages` configuration. 2025-09-08T03:53:09,887 !! 2025-09-08T03:53:09,887 ******************************************************************************** 2025-09-08T03:53:09,887 ############################ 2025-09-08T03:53:09,887 # Package would be ignored # 2025-09-08T03:53:09,887 ############################ 2025-09-08T03:53:09,888 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates' as an importable package[^1], 2025-09-08T03:53:09,888 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,888 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,888 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates' is explicitly added 2025-09-08T03:53:09,888 to the `packages` configuration field. 2025-09-08T03:53:09,888 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,888 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,888 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,889 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,889 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,889 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates' to be distributed and are 2025-09-08T03:53:09,889 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates' via 2025-09-08T03:53:09,889 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,889 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,889 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,889 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,890 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,890 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,890 even if it does not contain any `.py` files. 2025-09-08T03:53:09,890 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,890 directory, all directories are treated like packages. 2025-09-08T03:53:09,890 ******************************************************************************** 2025-09-08T03:53:09,890 !! 2025-09-08T03:53:09,890 check.warn(importable) 2025-09-08T03:53:09,891 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' is absent from the `packages` configuration. 2025-09-08T03:53:09,891 !! 2025-09-08T03:53:09,891 ******************************************************************************** 2025-09-08T03:53:09,891 ############################ 2025-09-08T03:53:09,891 # Package would be ignored # 2025-09-08T03:53:09,891 ############################ 2025-09-08T03:53:09,891 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' as an importable package[^1], 2025-09-08T03:53:09,891 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,891 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,892 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' is explicitly added 2025-09-08T03:53:09,892 to the `packages` configuration field. 2025-09-08T03:53:09,892 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,892 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,892 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,892 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,892 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,893 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' to be distributed and are 2025-09-08T03:53:09,893 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' via 2025-09-08T03:53:09,893 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,893 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,893 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,893 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,893 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,893 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,894 even if it does not contain any `.py` files. 2025-09-08T03:53:09,894 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,894 directory, all directories are treated like packages. 2025-09-08T03:53:09,894 ******************************************************************************** 2025-09-08T03:53:09,894 !! 2025-09-08T03:53:09,894 check.warn(importable) 2025-09-08T03:53:09,894 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,894 !! 2025-09-08T03:53:09,894 ******************************************************************************** 2025-09-08T03:53:09,895 ############################ 2025-09-08T03:53:09,895 # Package would be ignored # 2025-09-08T03:53:09,895 ############################ 2025-09-08T03:53:09,895 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Variables' as an importable package[^1], 2025-09-08T03:53:09,895 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,895 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,895 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Variables' is explicitly added 2025-09-08T03:53:09,895 to the `packages` configuration field. 2025-09-08T03:53:09,895 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,895 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,896 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,896 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,896 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,896 If you don't want 'publiforge.Processors.Publidoc2EPub2.Variables' to be distributed and are 2025-09-08T03:53:09,896 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Variables' via 2025-09-08T03:53:09,896 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,896 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,896 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,897 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,897 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,897 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,897 even if it does not contain any `.py` files. 2025-09-08T03:53:09,897 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,897 directory, all directories are treated like packages. 2025-09-08T03:53:09,897 ******************************************************************************** 2025-09-08T03:53:09,898 !! 2025-09-08T03:53:09,898 check.warn(importable) 2025-09-08T03:53:09,898 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,898 !! 2025-09-08T03:53:09,898 ******************************************************************************** 2025-09-08T03:53:09,898 ############################ 2025-09-08T03:53:09,898 # Package would be ignored # 2025-09-08T03:53:09,898 ############################ 2025-09-08T03:53:09,898 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Xsl' as an importable package[^1], 2025-09-08T03:53:09,898 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,899 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,899 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Xsl' is explicitly added 2025-09-08T03:53:09,899 to the `packages` configuration field. 2025-09-08T03:53:09,899 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,899 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,899 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,899 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,899 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,900 If you don't want 'publiforge.Processors.Publidoc2EPub2.Xsl' to be distributed and are 2025-09-08T03:53:09,900 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Xsl' via 2025-09-08T03:53:09,900 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,900 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,900 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,900 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,901 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,901 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,901 even if it does not contain any `.py` files. 2025-09-08T03:53:09,901 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,901 directory, all directories are treated like packages. 2025-09-08T03:53:09,901 ******************************************************************************** 2025-09-08T03:53:09,901 !! 2025-09-08T03:53:09,902 check.warn(importable) 2025-09-08T03:53:09,902 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.jars' is absent from the `packages` configuration. 2025-09-08T03:53:09,902 !! 2025-09-08T03:53:09,902 ******************************************************************************** 2025-09-08T03:53:09,902 ############################ 2025-09-08T03:53:09,902 # Package would be ignored # 2025-09-08T03:53:09,902 ############################ 2025-09-08T03:53:09,902 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars' as an importable package[^1], 2025-09-08T03:53:09,902 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,903 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,903 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars' is explicitly added 2025-09-08T03:53:09,903 to the `packages` configuration field. 2025-09-08T03:53:09,903 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,903 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,903 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,903 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,904 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,904 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars' to be distributed and are 2025-09-08T03:53:09,904 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars' via 2025-09-08T03:53:09,904 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,904 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,904 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,904 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,904 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,905 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,905 even if it does not contain any `.py` files. 2025-09-08T03:53:09,905 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,905 directory, all directories are treated like packages. 2025-09-08T03:53:09,905 ******************************************************************************** 2025-09-08T03:53:09,905 !! 2025-09-08T03:53:09,905 check.warn(importable) 2025-09-08T03:53:09,905 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.jars.lib' is absent from the `packages` configuration. 2025-09-08T03:53:09,905 !! 2025-09-08T03:53:09,906 ******************************************************************************** 2025-09-08T03:53:09,906 ############################ 2025-09-08T03:53:09,906 # Package would be ignored # 2025-09-08T03:53:09,906 ############################ 2025-09-08T03:53:09,906 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.lib' as an importable package[^1], 2025-09-08T03:53:09,906 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,906 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,906 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.lib' is explicitly added 2025-09-08T03:53:09,906 to the `packages` configuration field. 2025-09-08T03:53:09,907 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,907 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,907 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,907 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,907 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,907 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.lib' to be distributed and are 2025-09-08T03:53:09,907 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.lib' via 2025-09-08T03:53:09,907 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,908 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,908 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,908 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,908 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,908 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,908 even if it does not contain any `.py` files. 2025-09-08T03:53:09,908 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,909 directory, all directories are treated like packages. 2025-09-08T03:53:09,909 ******************************************************************************** 2025-09-08T03:53:09,909 !! 2025-09-08T03:53:09,909 check.warn(importable) 2025-09-08T03:53:09,909 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.jars.licenses' is absent from the `packages` configuration. 2025-09-08T03:53:09,909 !! 2025-09-08T03:53:09,909 ******************************************************************************** 2025-09-08T03:53:09,909 ############################ 2025-09-08T03:53:09,909 # Package would be ignored # 2025-09-08T03:53:09,909 ############################ 2025-09-08T03:53:09,910 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.licenses' as an importable package[^1], 2025-09-08T03:53:09,910 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,910 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,910 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.licenses' is explicitly added 2025-09-08T03:53:09,910 to the `packages` configuration field. 2025-09-08T03:53:09,910 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,910 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,910 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,911 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,911 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,911 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.licenses' to be distributed and are 2025-09-08T03:53:09,911 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.licenses' via 2025-09-08T03:53:09,911 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,911 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,911 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,911 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,912 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,912 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,912 even if it does not contain any `.py` files. 2025-09-08T03:53:09,912 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,912 directory, all directories are treated like packages. 2025-09-08T03:53:09,912 ******************************************************************************** 2025-09-08T03:53:09,912 !! 2025-09-08T03:53:09,912 check.warn(importable) 2025-09-08T03:53:09,913 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub3' is absent from the `packages` configuration. 2025-09-08T03:53:09,913 !! 2025-09-08T03:53:09,913 ******************************************************************************** 2025-09-08T03:53:09,913 ############################ 2025-09-08T03:53:09,913 # Package would be ignored # 2025-09-08T03:53:09,913 ############################ 2025-09-08T03:53:09,913 Python recognizes 'publiforge.Processors.Publidoc2EPub3' as an importable package[^1], 2025-09-08T03:53:09,913 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,913 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,914 package, please make sure that 'publiforge.Processors.Publidoc2EPub3' is explicitly added 2025-09-08T03:53:09,914 to the `packages` configuration field. 2025-09-08T03:53:09,914 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,914 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,914 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,914 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,915 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,915 If you don't want 'publiforge.Processors.Publidoc2EPub3' to be distributed and are 2025-09-08T03:53:09,915 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3' via 2025-09-08T03:53:09,915 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,915 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,915 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,915 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,915 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,916 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,916 even if it does not contain any `.py` files. 2025-09-08T03:53:09,916 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,916 directory, all directories are treated like packages. 2025-09-08T03:53:09,916 ******************************************************************************** 2025-09-08T03:53:09,916 !! 2025-09-08T03:53:09,916 check.warn(importable) 2025-09-08T03:53:09,917 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub3.Templates' is absent from the `packages` configuration. 2025-09-08T03:53:09,917 !! 2025-09-08T03:53:09,917 ******************************************************************************** 2025-09-08T03:53:09,917 ############################ 2025-09-08T03:53:09,917 # Package would be ignored # 2025-09-08T03:53:09,917 ############################ 2025-09-08T03:53:09,917 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates' as an importable package[^1], 2025-09-08T03:53:09,917 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,917 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,918 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates' is explicitly added 2025-09-08T03:53:09,918 to the `packages` configuration field. 2025-09-08T03:53:09,918 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,918 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,918 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,918 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,918 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,918 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates' to be distributed and are 2025-09-08T03:53:09,919 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates' via 2025-09-08T03:53:09,919 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,919 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,919 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,919 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,919 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,919 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,920 even if it does not contain any `.py` files. 2025-09-08T03:53:09,920 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,920 directory, all directories are treated like packages. 2025-09-08T03:53:09,920 ******************************************************************************** 2025-09-08T03:53:09,920 !! 2025-09-08T03:53:09,920 check.warn(importable) 2025-09-08T03:53:09,920 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' is absent from the `packages` configuration. 2025-09-08T03:53:09,920 !! 2025-09-08T03:53:09,920 ******************************************************************************** 2025-09-08T03:53:09,920 ############################ 2025-09-08T03:53:09,921 # Package would be ignored # 2025-09-08T03:53:09,921 ############################ 2025-09-08T03:53:09,921 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' as an importable package[^1], 2025-09-08T03:53:09,921 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,921 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,921 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' is explicitly added 2025-09-08T03:53:09,921 to the `packages` configuration field. 2025-09-08T03:53:09,921 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,921 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,922 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,922 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,922 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,922 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' to be distributed and are 2025-09-08T03:53:09,922 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' via 2025-09-08T03:53:09,922 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,922 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,922 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,923 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,923 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,923 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,923 even if it does not contain any `.py` files. 2025-09-08T03:53:09,923 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,923 directory, all directories are treated like packages. 2025-09-08T03:53:09,923 ******************************************************************************** 2025-09-08T03:53:09,924 !! 2025-09-08T03:53:09,924 check.warn(importable) 2025-09-08T03:53:09,924 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub3.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,924 !! 2025-09-08T03:53:09,924 ******************************************************************************** 2025-09-08T03:53:09,924 ############################ 2025-09-08T03:53:09,924 # Package would be ignored # 2025-09-08T03:53:09,924 ############################ 2025-09-08T03:53:09,924 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Variables' as an importable package[^1], 2025-09-08T03:53:09,924 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,925 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,925 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Variables' is explicitly added 2025-09-08T03:53:09,925 to the `packages` configuration field. 2025-09-08T03:53:09,925 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,925 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,925 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,925 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,925 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,926 If you don't want 'publiforge.Processors.Publidoc2EPub3.Variables' to be distributed and are 2025-09-08T03:53:09,926 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Variables' via 2025-09-08T03:53:09,926 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,926 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,926 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,926 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,926 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,927 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,927 even if it does not contain any `.py` files. 2025-09-08T03:53:09,927 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,927 directory, all directories are treated like packages. 2025-09-08T03:53:09,927 ******************************************************************************** 2025-09-08T03:53:09,927 !! 2025-09-08T03:53:09,927 check.warn(importable) 2025-09-08T03:53:09,927 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2EPub3.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,927 !! 2025-09-08T03:53:09,928 ******************************************************************************** 2025-09-08T03:53:09,928 ############################ 2025-09-08T03:53:09,928 # Package would be ignored # 2025-09-08T03:53:09,928 ############################ 2025-09-08T03:53:09,928 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Xsl' as an importable package[^1], 2025-09-08T03:53:09,928 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,928 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,928 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Xsl' is explicitly added 2025-09-08T03:53:09,929 to the `packages` configuration field. 2025-09-08T03:53:09,929 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,929 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,929 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,929 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,929 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,930 If you don't want 'publiforge.Processors.Publidoc2EPub3.Xsl' to be distributed and are 2025-09-08T03:53:09,930 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Xsl' via 2025-09-08T03:53:09,930 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,930 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,930 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,930 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,930 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,931 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,931 even if it does not contain any `.py` files. 2025-09-08T03:53:09,931 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,931 directory, all directories are treated like packages. 2025-09-08T03:53:09,931 ******************************************************************************** 2025-09-08T03:53:09,931 !! 2025-09-08T03:53:09,931 check.warn(importable) 2025-09-08T03:53:09,931 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Html5' is absent from the `packages` configuration. 2025-09-08T03:53:09,931 !! 2025-09-08T03:53:09,931 ******************************************************************************** 2025-09-08T03:53:09,932 ############################ 2025-09-08T03:53:09,932 # Package would be ignored # 2025-09-08T03:53:09,932 ############################ 2025-09-08T03:53:09,932 Python recognizes 'publiforge.Processors.Publidoc2Html5' as an importable package[^1], 2025-09-08T03:53:09,932 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,932 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,932 package, please make sure that 'publiforge.Processors.Publidoc2Html5' is explicitly added 2025-09-08T03:53:09,932 to the `packages` configuration field. 2025-09-08T03:53:09,932 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,933 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,933 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,933 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,933 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,933 If you don't want 'publiforge.Processors.Publidoc2Html5' to be distributed and are 2025-09-08T03:53:09,933 already explicitly excluding 'publiforge.Processors.Publidoc2Html5' via 2025-09-08T03:53:09,933 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,933 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,934 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,934 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,934 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,934 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,934 even if it does not contain any `.py` files. 2025-09-08T03:53:09,934 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,934 directory, all directories are treated like packages. 2025-09-08T03:53:09,934 ******************************************************************************** 2025-09-08T03:53:09,935 !! 2025-09-08T03:53:09,935 check.warn(importable) 2025-09-08T03:53:09,935 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Templates.Images' is absent from the `packages` configuration. 2025-09-08T03:53:09,935 !! 2025-09-08T03:53:09,935 ******************************************************************************** 2025-09-08T03:53:09,935 ############################ 2025-09-08T03:53:09,935 # Package would be ignored # 2025-09-08T03:53:09,935 ############################ 2025-09-08T03:53:09,935 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Images' as an importable package[^1], 2025-09-08T03:53:09,936 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,936 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,936 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Images' is explicitly added 2025-09-08T03:53:09,936 to the `packages` configuration field. 2025-09-08T03:53:09,936 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,936 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,936 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,936 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,937 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,937 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Images' to be distributed and are 2025-09-08T03:53:09,937 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Images' via 2025-09-08T03:53:09,937 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,937 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,937 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,937 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,937 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,938 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,938 even if it does not contain any `.py` files. 2025-09-08T03:53:09,938 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,938 directory, all directories are treated like packages. 2025-09-08T03:53:09,938 ******************************************************************************** 2025-09-08T03:53:09,938 !! 2025-09-08T03:53:09,938 check.warn(importable) 2025-09-08T03:53:09,938 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Templates.Js' is absent from the `packages` configuration. 2025-09-08T03:53:09,939 !! 2025-09-08T03:53:09,939 ******************************************************************************** 2025-09-08T03:53:09,939 ############################ 2025-09-08T03:53:09,939 # Package would be ignored # 2025-09-08T03:53:09,939 ############################ 2025-09-08T03:53:09,939 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Js' as an importable package[^1], 2025-09-08T03:53:09,939 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,939 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,939 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Js' is explicitly added 2025-09-08T03:53:09,939 to the `packages` configuration field. 2025-09-08T03:53:09,940 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,940 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,940 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,940 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,940 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,940 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Js' to be distributed and are 2025-09-08T03:53:09,940 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Js' via 2025-09-08T03:53:09,941 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,941 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,941 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,941 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,941 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,941 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,941 even if it does not contain any `.py` files. 2025-09-08T03:53:09,942 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,942 directory, all directories are treated like packages. 2025-09-08T03:53:09,942 ******************************************************************************** 2025-09-08T03:53:09,942 !! 2025-09-08T03:53:09,942 check.warn(importable) 2025-09-08T03:53:09,942 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,942 !! 2025-09-08T03:53:09,943 ******************************************************************************** 2025-09-08T03:53:09,943 ############################ 2025-09-08T03:53:09,943 # Package would be ignored # 2025-09-08T03:53:09,943 ############################ 2025-09-08T03:53:09,943 Python recognizes 'publiforge.Processors.Publidoc2Html5.Variables' as an importable package[^1], 2025-09-08T03:53:09,943 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,943 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,943 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Variables' is explicitly added 2025-09-08T03:53:09,943 to the `packages` configuration field. 2025-09-08T03:53:09,944 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,944 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,944 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,944 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,944 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,944 If you don't want 'publiforge.Processors.Publidoc2Html5.Variables' to be distributed and are 2025-09-08T03:53:09,944 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Variables' via 2025-09-08T03:53:09,944 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,945 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,945 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,945 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,945 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,945 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,945 even if it does not contain any `.py` files. 2025-09-08T03:53:09,945 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,946 directory, all directories are treated like packages. 2025-09-08T03:53:09,946 ******************************************************************************** 2025-09-08T03:53:09,946 !! 2025-09-08T03:53:09,946 check.warn(importable) 2025-09-08T03:53:09,946 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,946 !! 2025-09-08T03:53:09,946 ******************************************************************************** 2025-09-08T03:53:09,946 ############################ 2025-09-08T03:53:09,946 # Package would be ignored # 2025-09-08T03:53:09,946 ############################ 2025-09-08T03:53:09,947 Python recognizes 'publiforge.Processors.Publidoc2Html5.Xsl' as an importable package[^1], 2025-09-08T03:53:09,947 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,947 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,947 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Xsl' is explicitly added 2025-09-08T03:53:09,947 to the `packages` configuration field. 2025-09-08T03:53:09,947 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,947 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,947 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,948 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,948 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,948 If you don't want 'publiforge.Processors.Publidoc2Html5.Xsl' to be distributed and are 2025-09-08T03:53:09,948 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Xsl' via 2025-09-08T03:53:09,948 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,948 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,948 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,948 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,949 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,949 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,949 even if it does not contain any `.py` files. 2025-09-08T03:53:09,949 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,949 directory, all directories are treated like packages. 2025-09-08T03:53:09,949 ******************************************************************************** 2025-09-08T03:53:09,949 !! 2025-09-08T03:53:09,949 check.warn(importable) 2025-09-08T03:53:09,950 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Pdf' is absent from the `packages` configuration. 2025-09-08T03:53:09,950 !! 2025-09-08T03:53:09,950 ******************************************************************************** 2025-09-08T03:53:09,950 ############################ 2025-09-08T03:53:09,950 # Package would be ignored # 2025-09-08T03:53:09,950 ############################ 2025-09-08T03:53:09,950 Python recognizes 'publiforge.Processors.Publidoc2Pdf' as an importable package[^1], 2025-09-08T03:53:09,950 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,950 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,951 package, please make sure that 'publiforge.Processors.Publidoc2Pdf' is explicitly added 2025-09-08T03:53:09,951 to the `packages` configuration field. 2025-09-08T03:53:09,951 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,951 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,951 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,951 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,951 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,951 If you don't want 'publiforge.Processors.Publidoc2Pdf' to be distributed and are 2025-09-08T03:53:09,952 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf' via 2025-09-08T03:53:09,952 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,952 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,952 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,952 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,952 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,952 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,953 even if it does not contain any `.py` files. 2025-09-08T03:53:09,953 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,953 directory, all directories are treated like packages. 2025-09-08T03:53:09,953 ******************************************************************************** 2025-09-08T03:53:09,953 !! 2025-09-08T03:53:09,953 check.warn(importable) 2025-09-08T03:53:09,953 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Pdf.Fonts' is absent from the `packages` configuration. 2025-09-08T03:53:09,953 !! 2025-09-08T03:53:09,953 ******************************************************************************** 2025-09-08T03:53:09,954 ############################ 2025-09-08T03:53:09,954 # Package would be ignored # 2025-09-08T03:53:09,954 ############################ 2025-09-08T03:53:09,954 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Fonts' as an importable package[^1], 2025-09-08T03:53:09,954 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,954 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,954 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Fonts' is explicitly added 2025-09-08T03:53:09,954 to the `packages` configuration field. 2025-09-08T03:53:09,954 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,954 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,955 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,955 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,955 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,955 If you don't want 'publiforge.Processors.Publidoc2Pdf.Fonts' to be distributed and are 2025-09-08T03:53:09,955 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Fonts' via 2025-09-08T03:53:09,955 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,955 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,956 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,956 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,956 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,956 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,956 even if it does not contain any `.py` files. 2025-09-08T03:53:09,956 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,957 directory, all directories are treated like packages. 2025-09-08T03:53:09,957 ******************************************************************************** 2025-09-08T03:53:09,957 !! 2025-09-08T03:53:09,957 check.warn(importable) 2025-09-08T03:53:09,957 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Pdf.Regex' is absent from the `packages` configuration. 2025-09-08T03:53:09,957 !! 2025-09-08T03:53:09,957 ******************************************************************************** 2025-09-08T03:53:09,957 ############################ 2025-09-08T03:53:09,957 # Package would be ignored # 2025-09-08T03:53:09,958 ############################ 2025-09-08T03:53:09,958 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Regex' as an importable package[^1], 2025-09-08T03:53:09,958 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,958 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,958 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Regex' is explicitly added 2025-09-08T03:53:09,958 to the `packages` configuration field. 2025-09-08T03:53:09,958 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,958 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,958 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,959 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,959 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,959 If you don't want 'publiforge.Processors.Publidoc2Pdf.Regex' to be distributed and are 2025-09-08T03:53:09,959 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Regex' via 2025-09-08T03:53:09,959 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,959 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,959 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,960 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,960 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,960 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,960 even if it does not contain any `.py` files. 2025-09-08T03:53:09,960 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,960 directory, all directories are treated like packages. 2025-09-08T03:53:09,960 ******************************************************************************** 2025-09-08T03:53:09,960 !! 2025-09-08T03:53:09,961 check.warn(importable) 2025-09-08T03:53:09,961 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Pdf.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,961 !! 2025-09-08T03:53:09,961 ******************************************************************************** 2025-09-08T03:53:09,961 ############################ 2025-09-08T03:53:09,961 # Package would be ignored # 2025-09-08T03:53:09,961 ############################ 2025-09-08T03:53:09,961 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Variables' as an importable package[^1], 2025-09-08T03:53:09,961 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,962 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,962 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Variables' is explicitly added 2025-09-08T03:53:09,962 to the `packages` configuration field. 2025-09-08T03:53:09,962 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,962 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,962 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,962 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,962 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,963 If you don't want 'publiforge.Processors.Publidoc2Pdf.Variables' to be distributed and are 2025-09-08T03:53:09,963 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Variables' via 2025-09-08T03:53:09,963 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,963 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,963 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,963 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,963 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,964 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,964 even if it does not contain any `.py` files. 2025-09-08T03:53:09,964 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,964 directory, all directories are treated like packages. 2025-09-08T03:53:09,964 ******************************************************************************** 2025-09-08T03:53:09,964 !! 2025-09-08T03:53:09,964 check.warn(importable) 2025-09-08T03:53:09,964 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Pdf.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,964 !! 2025-09-08T03:53:09,965 ******************************************************************************** 2025-09-08T03:53:09,965 ############################ 2025-09-08T03:53:09,965 # Package would be ignored # 2025-09-08T03:53:09,965 ############################ 2025-09-08T03:53:09,965 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Xsl' as an importable package[^1], 2025-09-08T03:53:09,965 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,965 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,965 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Xsl' is explicitly added 2025-09-08T03:53:09,965 to the `packages` configuration field. 2025-09-08T03:53:09,965 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,966 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,966 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,966 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,966 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,966 If you don't want 'publiforge.Processors.Publidoc2Pdf.Xsl' to be distributed and are 2025-09-08T03:53:09,966 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Xsl' via 2025-09-08T03:53:09,966 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,966 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,967 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,967 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,967 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,967 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,967 even if it does not contain any `.py` files. 2025-09-08T03:53:09,967 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,967 directory, all directories are treated like packages. 2025-09-08T03:53:09,967 ******************************************************************************** 2025-09-08T03:53:09,968 !! 2025-09-08T03:53:09,968 check.warn(importable) 2025-09-08T03:53:09,968 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2XHtml' is absent from the `packages` configuration. 2025-09-08T03:53:09,968 !! 2025-09-08T03:53:09,968 ******************************************************************************** 2025-09-08T03:53:09,968 ############################ 2025-09-08T03:53:09,968 # Package would be ignored # 2025-09-08T03:53:09,968 ############################ 2025-09-08T03:53:09,968 Python recognizes 'publiforge.Processors.Publidoc2XHtml' as an importable package[^1], 2025-09-08T03:53:09,969 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,969 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,969 package, please make sure that 'publiforge.Processors.Publidoc2XHtml' is explicitly added 2025-09-08T03:53:09,969 to the `packages` configuration field. 2025-09-08T03:53:09,969 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,969 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,969 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,970 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,970 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,970 If you don't want 'publiforge.Processors.Publidoc2XHtml' to be distributed and are 2025-09-08T03:53:09,970 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml' via 2025-09-08T03:53:09,970 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,970 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,970 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,971 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,971 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,971 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,971 even if it does not contain any `.py` files. 2025-09-08T03:53:09,971 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,971 directory, all directories are treated like packages. 2025-09-08T03:53:09,971 ******************************************************************************** 2025-09-08T03:53:09,972 !! 2025-09-08T03:53:09,972 check.warn(importable) 2025-09-08T03:53:09,972 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Regex' is absent from the `packages` configuration. 2025-09-08T03:53:09,972 !! 2025-09-08T03:53:09,972 ******************************************************************************** 2025-09-08T03:53:09,972 ############################ 2025-09-08T03:53:09,972 # Package would be ignored # 2025-09-08T03:53:09,972 ############################ 2025-09-08T03:53:09,972 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Regex' as an importable package[^1], 2025-09-08T03:53:09,973 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,973 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,973 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Regex' is explicitly added 2025-09-08T03:53:09,973 to the `packages` configuration field. 2025-09-08T03:53:09,973 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,973 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,973 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,973 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,974 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,974 If you don't want 'publiforge.Processors.Publidoc2XHtml.Regex' to be distributed and are 2025-09-08T03:53:09,974 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Regex' via 2025-09-08T03:53:09,974 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,974 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,974 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,974 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,975 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,975 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,975 even if it does not contain any `.py` files. 2025-09-08T03:53:09,975 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,975 directory, all directories are treated like packages. 2025-09-08T03:53:09,975 ******************************************************************************** 2025-09-08T03:53:09,975 !! 2025-09-08T03:53:09,975 check.warn(importable) 2025-09-08T03:53:09,976 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Templates.Css' is absent from the `packages` configuration. 2025-09-08T03:53:09,976 !! 2025-09-08T03:53:09,976 ******************************************************************************** 2025-09-08T03:53:09,976 ############################ 2025-09-08T03:53:09,976 # Package would be ignored # 2025-09-08T03:53:09,976 ############################ 2025-09-08T03:53:09,976 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Css' as an importable package[^1], 2025-09-08T03:53:09,976 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,976 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,976 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Css' is explicitly added 2025-09-08T03:53:09,977 to the `packages` configuration field. 2025-09-08T03:53:09,977 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,977 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,977 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,977 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,977 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,977 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Css' to be distributed and are 2025-09-08T03:53:09,978 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Css' via 2025-09-08T03:53:09,978 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,978 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,978 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,978 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,978 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,978 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,978 even if it does not contain any `.py` files. 2025-09-08T03:53:09,979 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,979 directory, all directories are treated like packages. 2025-09-08T03:53:09,979 ******************************************************************************** 2025-09-08T03:53:09,979 !! 2025-09-08T03:53:09,979 check.warn(importable) 2025-09-08T03:53:09,979 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Templates.Images' is absent from the `packages` configuration. 2025-09-08T03:53:09,979 !! 2025-09-08T03:53:09,979 ******************************************************************************** 2025-09-08T03:53:09,979 ############################ 2025-09-08T03:53:09,980 # Package would be ignored # 2025-09-08T03:53:09,980 ############################ 2025-09-08T03:53:09,980 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Images' as an importable package[^1], 2025-09-08T03:53:09,980 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,980 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,980 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Images' is explicitly added 2025-09-08T03:53:09,980 to the `packages` configuration field. 2025-09-08T03:53:09,980 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,980 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,981 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,981 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,981 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,981 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Images' to be distributed and are 2025-09-08T03:53:09,981 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Images' via 2025-09-08T03:53:09,981 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,981 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,981 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,982 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,982 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,982 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,982 even if it does not contain any `.py` files. 2025-09-08T03:53:09,982 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,982 directory, all directories are treated like packages. 2025-09-08T03:53:09,982 ******************************************************************************** 2025-09-08T03:53:09,983 !! 2025-09-08T03:53:09,983 check.warn(importable) 2025-09-08T03:53:09,983 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Templates.Js' is absent from the `packages` configuration. 2025-09-08T03:53:09,983 !! 2025-09-08T03:53:09,983 ******************************************************************************** 2025-09-08T03:53:09,983 ############################ 2025-09-08T03:53:09,983 # Package would be ignored # 2025-09-08T03:53:09,983 ############################ 2025-09-08T03:53:09,983 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Js' as an importable package[^1], 2025-09-08T03:53:09,984 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,984 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,984 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Js' is explicitly added 2025-09-08T03:53:09,984 to the `packages` configuration field. 2025-09-08T03:53:09,984 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,984 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,984 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,985 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,985 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,985 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Js' to be distributed and are 2025-09-08T03:53:09,985 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Js' via 2025-09-08T03:53:09,985 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,985 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,985 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,986 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,986 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,986 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,986 even if it does not contain any `.py` files. 2025-09-08T03:53:09,986 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,986 directory, all directories are treated like packages. 2025-09-08T03:53:09,986 ******************************************************************************** 2025-09-08T03:53:09,986 !! 2025-09-08T03:53:09,987 check.warn(importable) 2025-09-08T03:53:09,987 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:09,987 !! 2025-09-08T03:53:09,987 ******************************************************************************** 2025-09-08T03:53:09,987 ############################ 2025-09-08T03:53:09,987 # Package would be ignored # 2025-09-08T03:53:09,987 ############################ 2025-09-08T03:53:09,987 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Variables' as an importable package[^1], 2025-09-08T03:53:09,987 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,988 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,988 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Variables' is explicitly added 2025-09-08T03:53:09,988 to the `packages` configuration field. 2025-09-08T03:53:09,988 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,988 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,988 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,988 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,988 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,989 If you don't want 'publiforge.Processors.Publidoc2XHtml.Variables' to be distributed and are 2025-09-08T03:53:09,989 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Variables' via 2025-09-08T03:53:09,989 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,989 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,989 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,989 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,989 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,990 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,990 even if it does not contain any `.py` files. 2025-09-08T03:53:09,990 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,990 directory, all directories are treated like packages. 2025-09-08T03:53:09,990 ******************************************************************************** 2025-09-08T03:53:09,990 !! 2025-09-08T03:53:09,990 check.warn(importable) 2025-09-08T03:53:09,990 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:09,990 !! 2025-09-08T03:53:09,991 ******************************************************************************** 2025-09-08T03:53:09,991 ############################ 2025-09-08T03:53:09,991 # Package would be ignored # 2025-09-08T03:53:09,991 ############################ 2025-09-08T03:53:09,991 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Xsl' as an importable package[^1], 2025-09-08T03:53:09,991 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,991 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,991 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Xsl' is explicitly added 2025-09-08T03:53:09,991 to the `packages` configuration field. 2025-09-08T03:53:09,991 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,992 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,992 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,992 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,992 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,992 If you don't want 'publiforge.Processors.Publidoc2XHtml.Xsl' to be distributed and are 2025-09-08T03:53:09,992 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Xsl' via 2025-09-08T03:53:09,992 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,992 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,993 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,993 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,993 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,993 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,993 even if it does not contain any `.py` files. 2025-09-08T03:53:09,993 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,993 directory, all directories are treated like packages. 2025-09-08T03:53:09,994 ******************************************************************************** 2025-09-08T03:53:09,994 !! 2025-09-08T03:53:09,994 check.warn(importable) 2025-09-08T03:53:09,994 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PublidocClean' is absent from the `packages` configuration. 2025-09-08T03:53:09,994 !! 2025-09-08T03:53:09,994 ******************************************************************************** 2025-09-08T03:53:09,994 ############################ 2025-09-08T03:53:09,994 # Package would be ignored # 2025-09-08T03:53:09,994 ############################ 2025-09-08T03:53:09,994 Python recognizes 'publiforge.Processors.PublidocClean' as an importable package[^1], 2025-09-08T03:53:09,995 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,995 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,995 package, please make sure that 'publiforge.Processors.PublidocClean' is explicitly added 2025-09-08T03:53:09,995 to the `packages` configuration field. 2025-09-08T03:53:09,995 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,995 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,995 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,995 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:09,996 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:09,996 If you don't want 'publiforge.Processors.PublidocClean' to be distributed and are 2025-09-08T03:53:09,996 already explicitly excluding 'publiforge.Processors.PublidocClean' via 2025-09-08T03:53:09,996 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:09,996 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:09,996 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:09,996 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:09,997 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:09,997 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:09,997 even if it does not contain any `.py` files. 2025-09-08T03:53:09,997 On the other hand, currently there is no concept of package data 2025-09-08T03:53:09,997 directory, all directories are treated like packages. 2025-09-08T03:53:09,997 ******************************************************************************** 2025-09-08T03:53:09,997 !! 2025-09-08T03:53:09,997 check.warn(importable) 2025-09-08T03:53:09,998 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PublidocClean.Regex' is absent from the `packages` configuration. 2025-09-08T03:53:09,998 !! 2025-09-08T03:53:09,998 ******************************************************************************** 2025-09-08T03:53:09,998 ############################ 2025-09-08T03:53:09,998 # Package would be ignored # 2025-09-08T03:53:09,998 ############################ 2025-09-08T03:53:09,998 Python recognizes 'publiforge.Processors.PublidocClean.Regex' as an importable package[^1], 2025-09-08T03:53:09,998 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:09,999 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:09,999 package, please make sure that 'publiforge.Processors.PublidocClean.Regex' is explicitly added 2025-09-08T03:53:09,999 to the `packages` configuration field. 2025-09-08T03:53:09,999 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:09,999 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:09,999 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:09,999 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,000 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,000 If you don't want 'publiforge.Processors.PublidocClean.Regex' to be distributed and are 2025-09-08T03:53:10,000 already explicitly excluding 'publiforge.Processors.PublidocClean.Regex' via 2025-09-08T03:53:10,000 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,000 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,000 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,000 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,001 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,001 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,001 even if it does not contain any `.py` files. 2025-09-08T03:53:10,001 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,001 directory, all directories are treated like packages. 2025-09-08T03:53:10,001 ******************************************************************************** 2025-09-08T03:53:10,001 !! 2025-09-08T03:53:10,001 check.warn(importable) 2025-09-08T03:53:10,001 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PublidocClean.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:10,002 !! 2025-09-08T03:53:10,002 ******************************************************************************** 2025-09-08T03:53:10,002 ############################ 2025-09-08T03:53:10,002 # Package would be ignored # 2025-09-08T03:53:10,002 ############################ 2025-09-08T03:53:10,002 Python recognizes 'publiforge.Processors.PublidocClean.Variables' as an importable package[^1], 2025-09-08T03:53:10,002 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,002 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,003 package, please make sure that 'publiforge.Processors.PublidocClean.Variables' is explicitly added 2025-09-08T03:53:10,003 to the `packages` configuration field. 2025-09-08T03:53:10,003 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,003 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,003 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,003 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,003 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,003 If you don't want 'publiforge.Processors.PublidocClean.Variables' to be distributed and are 2025-09-08T03:53:10,004 already explicitly excluding 'publiforge.Processors.PublidocClean.Variables' via 2025-09-08T03:53:10,004 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,004 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,004 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,004 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,004 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,004 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,005 even if it does not contain any `.py` files. 2025-09-08T03:53:10,005 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,005 directory, all directories are treated like packages. 2025-09-08T03:53:10,005 ******************************************************************************** 2025-09-08T03:53:10,005 !! 2025-09-08T03:53:10,005 check.warn(importable) 2025-09-08T03:53:10,005 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PublidocClean.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:10,005 !! 2025-09-08T03:53:10,005 ******************************************************************************** 2025-09-08T03:53:10,005 ############################ 2025-09-08T03:53:10,006 # Package would be ignored # 2025-09-08T03:53:10,006 ############################ 2025-09-08T03:53:10,006 Python recognizes 'publiforge.Processors.PublidocClean.Xsl' as an importable package[^1], 2025-09-08T03:53:10,006 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,006 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,006 package, please make sure that 'publiforge.Processors.PublidocClean.Xsl' is explicitly added 2025-09-08T03:53:10,006 to the `packages` configuration field. 2025-09-08T03:53:10,006 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,006 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,007 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,007 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,007 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,007 If you don't want 'publiforge.Processors.PublidocClean.Xsl' to be distributed and are 2025-09-08T03:53:10,007 already explicitly excluding 'publiforge.Processors.PublidocClean.Xsl' via 2025-09-08T03:53:10,007 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,007 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,007 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,008 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,008 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,008 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,008 even if it does not contain any `.py` files. 2025-09-08T03:53:10,008 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,008 directory, all directories are treated like packages. 2025-09-08T03:53:10,008 ******************************************************************************** 2025-09-08T03:53:10,009 !! 2025-09-08T03:53:10,009 check.warn(importable) 2025-09-08T03:53:10,009 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PublidocValid' is absent from the `packages` configuration. 2025-09-08T03:53:10,009 !! 2025-09-08T03:53:10,009 ******************************************************************************** 2025-09-08T03:53:10,009 ############################ 2025-09-08T03:53:10,009 # Package would be ignored # 2025-09-08T03:53:10,009 ############################ 2025-09-08T03:53:10,009 Python recognizes 'publiforge.Processors.PublidocValid' as an importable package[^1], 2025-09-08T03:53:10,009 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,010 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,010 package, please make sure that 'publiforge.Processors.PublidocValid' is explicitly added 2025-09-08T03:53:10,010 to the `packages` configuration field. 2025-09-08T03:53:10,010 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,010 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,010 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,010 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,010 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,011 If you don't want 'publiforge.Processors.PublidocValid' to be distributed and are 2025-09-08T03:53:10,011 already explicitly excluding 'publiforge.Processors.PublidocValid' via 2025-09-08T03:53:10,011 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,011 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,011 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,011 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,011 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,012 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,012 even if it does not contain any `.py` files. 2025-09-08T03:53:10,012 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,012 directory, all directories are treated like packages. 2025-09-08T03:53:10,012 ******************************************************************************** 2025-09-08T03:53:10,012 !! 2025-09-08T03:53:10,013 check.warn(importable) 2025-09-08T03:53:10,013 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.PublidocValid.RelaxNG' is absent from the `packages` configuration. 2025-09-08T03:53:10,013 !! 2025-09-08T03:53:10,013 ******************************************************************************** 2025-09-08T03:53:10,013 ############################ 2025-09-08T03:53:10,013 # Package would be ignored # 2025-09-08T03:53:10,013 ############################ 2025-09-08T03:53:10,013 Python recognizes 'publiforge.Processors.PublidocValid.RelaxNG' as an importable package[^1], 2025-09-08T03:53:10,013 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,014 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,014 package, please make sure that 'publiforge.Processors.PublidocValid.RelaxNG' is explicitly added 2025-09-08T03:53:10,014 to the `packages` configuration field. 2025-09-08T03:53:10,014 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,014 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,014 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,014 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,015 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,015 If you don't want 'publiforge.Processors.PublidocValid.RelaxNG' to be distributed and are 2025-09-08T03:53:10,015 already explicitly excluding 'publiforge.Processors.PublidocValid.RelaxNG' via 2025-09-08T03:53:10,015 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,015 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,015 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,015 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,016 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,016 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,016 even if it does not contain any `.py` files. 2025-09-08T03:53:10,016 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,016 directory, all directories are treated like packages. 2025-09-08T03:53:10,016 ******************************************************************************** 2025-09-08T03:53:10,016 !! 2025-09-08T03:53:10,016 check.warn(importable) 2025-09-08T03:53:10,017 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2EPub3' is absent from the `packages` configuration. 2025-09-08T03:53:10,017 !! 2025-09-08T03:53:10,017 ******************************************************************************** 2025-09-08T03:53:10,017 ############################ 2025-09-08T03:53:10,017 # Package would be ignored # 2025-09-08T03:53:10,017 ############################ 2025-09-08T03:53:10,017 Python recognizes 'publiforge.Processors.Publiquiz2EPub3' as an importable package[^1], 2025-09-08T03:53:10,017 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,017 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,018 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3' is explicitly added 2025-09-08T03:53:10,018 to the `packages` configuration field. 2025-09-08T03:53:10,018 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,018 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,018 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,018 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,018 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,018 If you don't want 'publiforge.Processors.Publiquiz2EPub3' to be distributed and are 2025-09-08T03:53:10,019 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3' via 2025-09-08T03:53:10,019 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,019 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,019 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,019 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,019 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,019 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,020 even if it does not contain any `.py` files. 2025-09-08T03:53:10,020 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,020 directory, all directories are treated like packages. 2025-09-08T03:53:10,020 ******************************************************************************** 2025-09-08T03:53:10,020 !! 2025-09-08T03:53:10,020 check.warn(importable) 2025-09-08T03:53:10,020 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2EPub3.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:10,020 !! 2025-09-08T03:53:10,020 ******************************************************************************** 2025-09-08T03:53:10,021 ############################ 2025-09-08T03:53:10,021 # Package would be ignored # 2025-09-08T03:53:10,021 ############################ 2025-09-08T03:53:10,021 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Variables' as an importable package[^1], 2025-09-08T03:53:10,021 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,021 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,021 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Variables' is explicitly added 2025-09-08T03:53:10,021 to the `packages` configuration field. 2025-09-08T03:53:10,021 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,022 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,022 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,022 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,022 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,022 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Variables' to be distributed and are 2025-09-08T03:53:10,022 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Variables' via 2025-09-08T03:53:10,022 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,022 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,023 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,023 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,023 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,023 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,023 even if it does not contain any `.py` files. 2025-09-08T03:53:10,023 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,023 directory, all directories are treated like packages. 2025-09-08T03:53:10,023 ******************************************************************************** 2025-09-08T03:53:10,024 !! 2025-09-08T03:53:10,024 check.warn(importable) 2025-09-08T03:53:10,024 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2EPub3.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:10,024 !! 2025-09-08T03:53:10,024 ******************************************************************************** 2025-09-08T03:53:10,024 ############################ 2025-09-08T03:53:10,024 # Package would be ignored # 2025-09-08T03:53:10,024 ############################ 2025-09-08T03:53:10,024 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Xsl' as an importable package[^1], 2025-09-08T03:53:10,025 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,025 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,025 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Xsl' is explicitly added 2025-09-08T03:53:10,025 to the `packages` configuration field. 2025-09-08T03:53:10,025 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,025 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,025 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,025 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,026 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,026 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Xsl' to be distributed and are 2025-09-08T03:53:10,026 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Xsl' via 2025-09-08T03:53:10,026 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,026 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,026 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,026 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,027 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,027 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,027 even if it does not contain any `.py` files. 2025-09-08T03:53:10,027 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,027 directory, all directories are treated like packages. 2025-09-08T03:53:10,027 ******************************************************************************** 2025-09-08T03:53:10,028 !! 2025-09-08T03:53:10,028 check.warn(importable) 2025-09-08T03:53:10,028 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5' is absent from the `packages` configuration. 2025-09-08T03:53:10,028 !! 2025-09-08T03:53:10,028 ******************************************************************************** 2025-09-08T03:53:10,028 ############################ 2025-09-08T03:53:10,028 # Package would be ignored # 2025-09-08T03:53:10,028 ############################ 2025-09-08T03:53:10,028 Python recognizes 'publiforge.Processors.Publiquiz2Html5' as an importable package[^1], 2025-09-08T03:53:10,029 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,029 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,029 package, please make sure that 'publiforge.Processors.Publiquiz2Html5' is explicitly added 2025-09-08T03:53:10,029 to the `packages` configuration field. 2025-09-08T03:53:10,029 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,029 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,029 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,029 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,030 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,030 If you don't want 'publiforge.Processors.Publiquiz2Html5' to be distributed and are 2025-09-08T03:53:10,030 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5' via 2025-09-08T03:53:10,030 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,030 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,030 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,030 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,030 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,031 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,031 even if it does not contain any `.py` files. 2025-09-08T03:53:10,031 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,031 directory, all directories are treated like packages. 2025-09-08T03:53:10,031 ******************************************************************************** 2025-09-08T03:53:10,031 !! 2025-09-08T03:53:10,031 check.warn(importable) 2025-09-08T03:53:10,031 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Css' is absent from the `packages` configuration. 2025-09-08T03:53:10,031 !! 2025-09-08T03:53:10,032 ******************************************************************************** 2025-09-08T03:53:10,032 ############################ 2025-09-08T03:53:10,032 # Package would be ignored # 2025-09-08T03:53:10,032 ############################ 2025-09-08T03:53:10,032 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Css' as an importable package[^1], 2025-09-08T03:53:10,032 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,032 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,032 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Css' is explicitly added 2025-09-08T03:53:10,032 to the `packages` configuration field. 2025-09-08T03:53:10,033 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,033 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,033 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,033 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,033 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,033 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Css' to be distributed and are 2025-09-08T03:53:10,033 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Css' via 2025-09-08T03:53:10,034 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,034 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,034 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,034 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,034 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,034 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,034 even if it does not contain any `.py` files. 2025-09-08T03:53:10,034 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,035 directory, all directories are treated like packages. 2025-09-08T03:53:10,035 ******************************************************************************** 2025-09-08T03:53:10,035 !! 2025-09-08T03:53:10,035 check.warn(importable) 2025-09-08T03:53:10,035 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Js' is absent from the `packages` configuration. 2025-09-08T03:53:10,035 !! 2025-09-08T03:53:10,035 ******************************************************************************** 2025-09-08T03:53:10,035 ############################ 2025-09-08T03:53:10,035 # Package would be ignored # 2025-09-08T03:53:10,036 ############################ 2025-09-08T03:53:10,036 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Js' as an importable package[^1], 2025-09-08T03:53:10,036 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,036 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,036 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Js' is explicitly added 2025-09-08T03:53:10,036 to the `packages` configuration field. 2025-09-08T03:53:10,036 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,036 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,036 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,037 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,037 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,037 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Js' to be distributed and are 2025-09-08T03:53:10,037 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Js' via 2025-09-08T03:53:10,037 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,037 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,037 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,037 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,038 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,038 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,038 even if it does not contain any `.py` files. 2025-09-08T03:53:10,038 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,038 directory, all directories are treated like packages. 2025-09-08T03:53:10,038 ******************************************************************************** 2025-09-08T03:53:10,038 !! 2025-09-08T03:53:10,039 check.warn(importable) 2025-09-08T03:53:10,039 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:10,039 !! 2025-09-08T03:53:10,039 ******************************************************************************** 2025-09-08T03:53:10,039 ############################ 2025-09-08T03:53:10,039 # Package would be ignored # 2025-09-08T03:53:10,039 ############################ 2025-09-08T03:53:10,039 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Variables' as an importable package[^1], 2025-09-08T03:53:10,039 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,039 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,040 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Variables' is explicitly added 2025-09-08T03:53:10,040 to the `packages` configuration field. 2025-09-08T03:53:10,040 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,040 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,040 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,040 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,041 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,041 If you don't want 'publiforge.Processors.Publiquiz2Html5.Variables' to be distributed and are 2025-09-08T03:53:10,041 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Variables' via 2025-09-08T03:53:10,041 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,041 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,041 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,041 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,042 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,042 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,042 even if it does not contain any `.py` files. 2025-09-08T03:53:10,042 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,042 directory, all directories are treated like packages. 2025-09-08T03:53:10,042 ******************************************************************************** 2025-09-08T03:53:10,042 !! 2025-09-08T03:53:10,043 check.warn(importable) 2025-09-08T03:53:10,043 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:10,043 !! 2025-09-08T03:53:10,043 ******************************************************************************** 2025-09-08T03:53:10,043 ############################ 2025-09-08T03:53:10,043 # Package would be ignored # 2025-09-08T03:53:10,043 ############################ 2025-09-08T03:53:10,043 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Xsl' as an importable package[^1], 2025-09-08T03:53:10,043 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,044 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,044 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Xsl' is explicitly added 2025-09-08T03:53:10,044 to the `packages` configuration field. 2025-09-08T03:53:10,044 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,044 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,044 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,044 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,044 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,045 If you don't want 'publiforge.Processors.Publiquiz2Html5.Xsl' to be distributed and are 2025-09-08T03:53:10,045 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Xsl' via 2025-09-08T03:53:10,045 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,045 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,045 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,045 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,045 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,046 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,046 even if it does not contain any `.py` files. 2025-09-08T03:53:10,046 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,046 directory, all directories are treated like packages. 2025-09-08T03:53:10,046 ******************************************************************************** 2025-09-08T03:53:10,046 !! 2025-09-08T03:53:10,046 check.warn(importable) 2025-09-08T03:53:10,046 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12' is absent from the `packages` configuration. 2025-09-08T03:53:10,046 !! 2025-09-08T03:53:10,047 ******************************************************************************** 2025-09-08T03:53:10,047 ############################ 2025-09-08T03:53:10,047 # Package would be ignored # 2025-09-08T03:53:10,047 ############################ 2025-09-08T03:53:10,047 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12' as an importable package[^1], 2025-09-08T03:53:10,047 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,047 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,047 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12' is explicitly added 2025-09-08T03:53:10,047 to the `packages` configuration field. 2025-09-08T03:53:10,047 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,048 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,048 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,048 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,048 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,048 If you don't want 'publiforge.Processors.Publiquiz2Scorm12' to be distributed and are 2025-09-08T03:53:10,048 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12' via 2025-09-08T03:53:10,048 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,048 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,049 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,049 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,049 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,049 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,049 even if it does not contain any `.py` files. 2025-09-08T03:53:10,049 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,049 directory, all directories are treated like packages. 2025-09-08T03:53:10,049 ******************************************************************************** 2025-09-08T03:53:10,050 !! 2025-09-08T03:53:10,050 check.warn(importable) 2025-09-08T03:53:10,050 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Templates' is absent from the `packages` configuration. 2025-09-08T03:53:10,050 !! 2025-09-08T03:53:10,050 ******************************************************************************** 2025-09-08T03:53:10,050 ############################ 2025-09-08T03:53:10,050 # Package would be ignored # 2025-09-08T03:53:10,050 ############################ 2025-09-08T03:53:10,050 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates' as an importable package[^1], 2025-09-08T03:53:10,051 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,051 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,051 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates' is explicitly added 2025-09-08T03:53:10,051 to the `packages` configuration field. 2025-09-08T03:53:10,051 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,051 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,051 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,051 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,052 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,052 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates' to be distributed and are 2025-09-08T03:53:10,052 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates' via 2025-09-08T03:53:10,052 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,052 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,052 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,052 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,053 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,053 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,053 even if it does not contain any `.py` files. 2025-09-08T03:53:10,053 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,053 directory, all directories are treated like packages. 2025-09-08T03:53:10,053 ******************************************************************************** 2025-09-08T03:53:10,053 !! 2025-09-08T03:53:10,053 check.warn(importable) 2025-09-08T03:53:10,053 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' is absent from the `packages` configuration. 2025-09-08T03:53:10,054 !! 2025-09-08T03:53:10,054 ******************************************************************************** 2025-09-08T03:53:10,054 ############################ 2025-09-08T03:53:10,054 # Package would be ignored # 2025-09-08T03:53:10,054 ############################ 2025-09-08T03:53:10,054 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' as an importable package[^1], 2025-09-08T03:53:10,054 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,055 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,055 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' is explicitly added 2025-09-08T03:53:10,055 to the `packages` configuration field. 2025-09-08T03:53:10,055 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,055 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,055 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,055 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,056 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,056 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' to be distributed and are 2025-09-08T03:53:10,056 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' via 2025-09-08T03:53:10,056 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,056 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,056 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,056 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,056 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,057 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,057 even if it does not contain any `.py` files. 2025-09-08T03:53:10,057 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,057 directory, all directories are treated like packages. 2025-09-08T03:53:10,057 ******************************************************************************** 2025-09-08T03:53:10,057 !! 2025-09-08T03:53:10,057 check.warn(importable) 2025-09-08T03:53:10,057 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' is absent from the `packages` configuration. 2025-09-08T03:53:10,057 !! 2025-09-08T03:53:10,058 ******************************************************************************** 2025-09-08T03:53:10,058 ############################ 2025-09-08T03:53:10,058 # Package would be ignored # 2025-09-08T03:53:10,058 ############################ 2025-09-08T03:53:10,058 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' as an importable package[^1], 2025-09-08T03:53:10,058 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,058 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,058 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' is explicitly added 2025-09-08T03:53:10,058 to the `packages` configuration field. 2025-09-08T03:53:10,059 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,059 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,059 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,059 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,059 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,059 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' to be distributed and are 2025-09-08T03:53:10,059 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' via 2025-09-08T03:53:10,059 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,060 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,060 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,060 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,060 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,060 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,060 even if it does not contain any `.py` files. 2025-09-08T03:53:10,060 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,061 directory, all directories are treated like packages. 2025-09-08T03:53:10,061 ******************************************************************************** 2025-09-08T03:53:10,061 !! 2025-09-08T03:53:10,061 check.warn(importable) 2025-09-08T03:53:10,061 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' is absent from the `packages` configuration. 2025-09-08T03:53:10,061 !! 2025-09-08T03:53:10,061 ******************************************************************************** 2025-09-08T03:53:10,061 ############################ 2025-09-08T03:53:10,061 # Package would be ignored # 2025-09-08T03:53:10,061 ############################ 2025-09-08T03:53:10,062 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' as an importable package[^1], 2025-09-08T03:53:10,062 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,062 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,062 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' is explicitly added 2025-09-08T03:53:10,062 to the `packages` configuration field. 2025-09-08T03:53:10,062 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,062 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,062 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,063 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,063 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,063 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' to be distributed and are 2025-09-08T03:53:10,063 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' via 2025-09-08T03:53:10,063 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,063 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,063 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,063 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,064 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,064 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,064 even if it does not contain any `.py` files. 2025-09-08T03:53:10,064 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,064 directory, all directories are treated like packages. 2025-09-08T03:53:10,064 ******************************************************************************** 2025-09-08T03:53:10,064 !! 2025-09-08T03:53:10,065 check.warn(importable) 2025-09-08T03:53:10,065 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:10,065 !! 2025-09-08T03:53:10,065 ******************************************************************************** 2025-09-08T03:53:10,065 ############################ 2025-09-08T03:53:10,065 # Package would be ignored # 2025-09-08T03:53:10,065 ############################ 2025-09-08T03:53:10,065 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Variables' as an importable package[^1], 2025-09-08T03:53:10,065 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,065 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,066 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Variables' is explicitly added 2025-09-08T03:53:10,066 to the `packages` configuration field. 2025-09-08T03:53:10,066 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,066 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,066 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,066 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,066 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,067 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Variables' to be distributed and are 2025-09-08T03:53:10,067 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Variables' via 2025-09-08T03:53:10,067 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,067 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,067 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,067 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,067 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,068 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,068 even if it does not contain any `.py` files. 2025-09-08T03:53:10,068 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,068 directory, all directories are treated like packages. 2025-09-08T03:53:10,068 ******************************************************************************** 2025-09-08T03:53:10,068 !! 2025-09-08T03:53:10,068 check.warn(importable) 2025-09-08T03:53:10,069 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:10,069 !! 2025-09-08T03:53:10,069 ******************************************************************************** 2025-09-08T03:53:10,069 ############################ 2025-09-08T03:53:10,069 # Package would be ignored # 2025-09-08T03:53:10,069 ############################ 2025-09-08T03:53:10,069 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Xsl' as an importable package[^1], 2025-09-08T03:53:10,069 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,069 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,070 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Xsl' is explicitly added 2025-09-08T03:53:10,070 to the `packages` configuration field. 2025-09-08T03:53:10,070 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,070 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,070 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,070 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,070 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,070 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Xsl' to be distributed and are 2025-09-08T03:53:10,071 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Xsl' via 2025-09-08T03:53:10,071 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,071 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,071 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,071 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,071 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,071 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,072 even if it does not contain any `.py` files. 2025-09-08T03:53:10,072 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,072 directory, all directories are treated like packages. 2025-09-08T03:53:10,072 ******************************************************************************** 2025-09-08T03:53:10,072 !! 2025-09-08T03:53:10,072 check.warn(importable) 2025-09-08T03:53:10,072 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004' is absent from the `packages` configuration. 2025-09-08T03:53:10,072 !! 2025-09-08T03:53:10,072 ******************************************************************************** 2025-09-08T03:53:10,073 ############################ 2025-09-08T03:53:10,073 # Package would be ignored # 2025-09-08T03:53:10,073 ############################ 2025-09-08T03:53:10,073 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004' as an importable package[^1], 2025-09-08T03:53:10,073 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,073 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,073 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004' is explicitly added 2025-09-08T03:53:10,073 to the `packages` configuration field. 2025-09-08T03:53:10,073 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,073 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,074 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,074 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,074 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,074 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004' to be distributed and are 2025-09-08T03:53:10,074 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004' via 2025-09-08T03:53:10,074 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,074 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,074 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,075 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,075 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,075 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,075 even if it does not contain any `.py` files. 2025-09-08T03:53:10,075 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,075 directory, all directories are treated like packages. 2025-09-08T03:53:10,075 ******************************************************************************** 2025-09-08T03:53:10,076 !! 2025-09-08T03:53:10,076 check.warn(importable) 2025-09-08T03:53:10,076 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates' is absent from the `packages` configuration. 2025-09-08T03:53:10,076 !! 2025-09-08T03:53:10,076 ******************************************************************************** 2025-09-08T03:53:10,076 ############################ 2025-09-08T03:53:10,076 # Package would be ignored # 2025-09-08T03:53:10,076 ############################ 2025-09-08T03:53:10,076 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates' as an importable package[^1], 2025-09-08T03:53:10,076 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,077 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,077 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates' is explicitly added 2025-09-08T03:53:10,077 to the `packages` configuration field. 2025-09-08T03:53:10,077 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,077 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,077 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,077 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,078 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,078 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates' to be distributed and are 2025-09-08T03:53:10,078 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates' via 2025-09-08T03:53:10,078 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,078 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,078 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,078 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,078 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,079 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,079 even if it does not contain any `.py` files. 2025-09-08T03:53:10,079 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,079 directory, all directories are treated like packages. 2025-09-08T03:53:10,079 ******************************************************************************** 2025-09-08T03:53:10,079 !! 2025-09-08T03:53:10,079 check.warn(importable) 2025-09-08T03:53:10,079 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' is absent from the `packages` configuration. 2025-09-08T03:53:10,079 !! 2025-09-08T03:53:10,080 ******************************************************************************** 2025-09-08T03:53:10,080 ############################ 2025-09-08T03:53:10,080 # Package would be ignored # 2025-09-08T03:53:10,080 ############################ 2025-09-08T03:53:10,080 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' as an importable package[^1], 2025-09-08T03:53:10,080 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,080 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,080 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' is explicitly added 2025-09-08T03:53:10,080 to the `packages` configuration field. 2025-09-08T03:53:10,081 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,081 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,081 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,081 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,081 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,081 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' to be distributed and are 2025-09-08T03:53:10,082 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' via 2025-09-08T03:53:10,082 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,082 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,082 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,082 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,082 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,083 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,083 even if it does not contain any `.py` files. 2025-09-08T03:53:10,083 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,083 directory, all directories are treated like packages. 2025-09-08T03:53:10,083 ******************************************************************************** 2025-09-08T03:53:10,083 !! 2025-09-08T03:53:10,083 check.warn(importable) 2025-09-08T03:53:10,083 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' is absent from the `packages` configuration. 2025-09-08T03:53:10,083 !! 2025-09-08T03:53:10,084 ******************************************************************************** 2025-09-08T03:53:10,084 ############################ 2025-09-08T03:53:10,084 # Package would be ignored # 2025-09-08T03:53:10,084 ############################ 2025-09-08T03:53:10,084 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' as an importable package[^1], 2025-09-08T03:53:10,084 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,084 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,084 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' is explicitly added 2025-09-08T03:53:10,085 to the `packages` configuration field. 2025-09-08T03:53:10,085 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,085 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,085 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,085 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,085 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,086 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' to be distributed and are 2025-09-08T03:53:10,086 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' via 2025-09-08T03:53:10,086 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,086 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,086 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,086 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,086 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,087 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,087 even if it does not contain any `.py` files. 2025-09-08T03:53:10,087 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,087 directory, all directories are treated like packages. 2025-09-08T03:53:10,087 ******************************************************************************** 2025-09-08T03:53:10,087 !! 2025-09-08T03:53:10,087 check.warn(importable) 2025-09-08T03:53:10,087 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' is absent from the `packages` configuration. 2025-09-08T03:53:10,087 !! 2025-09-08T03:53:10,088 ******************************************************************************** 2025-09-08T03:53:10,088 ############################ 2025-09-08T03:53:10,088 # Package would be ignored # 2025-09-08T03:53:10,088 ############################ 2025-09-08T03:53:10,088 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' as an importable package[^1], 2025-09-08T03:53:10,088 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,088 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,088 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' is explicitly added 2025-09-08T03:53:10,088 to the `packages` configuration field. 2025-09-08T03:53:10,089 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,089 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,089 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,089 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,089 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,089 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' to be distributed and are 2025-09-08T03:53:10,090 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' via 2025-09-08T03:53:10,090 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,090 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,090 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,090 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,090 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,090 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,091 even if it does not contain any `.py` files. 2025-09-08T03:53:10,091 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,091 directory, all directories are treated like packages. 2025-09-08T03:53:10,091 ******************************************************************************** 2025-09-08T03:53:10,091 !! 2025-09-08T03:53:10,091 check.warn(importable) 2025-09-08T03:53:10,091 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' is absent from the `packages` configuration. 2025-09-08T03:53:10,091 !! 2025-09-08T03:53:10,092 ******************************************************************************** 2025-09-08T03:53:10,092 ############################ 2025-09-08T03:53:10,092 # Package would be ignored # 2025-09-08T03:53:10,092 ############################ 2025-09-08T03:53:10,092 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' as an importable package[^1], 2025-09-08T03:53:10,092 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,092 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,092 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' is explicitly added 2025-09-08T03:53:10,092 to the `packages` configuration field. 2025-09-08T03:53:10,093 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,093 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,093 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,093 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,093 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,093 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' to be distributed and are 2025-09-08T03:53:10,093 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' via 2025-09-08T03:53:10,094 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,094 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,094 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,094 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,094 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,094 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,095 even if it does not contain any `.py` files. 2025-09-08T03:53:10,095 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,095 directory, all directories are treated like packages. 2025-09-08T03:53:10,095 ******************************************************************************** 2025-09-08T03:53:10,095 !! 2025-09-08T03:53:10,095 check.warn(importable) 2025-09-08T03:53:10,095 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' is absent from the `packages` configuration. 2025-09-08T03:53:10,095 !! 2025-09-08T03:53:10,096 ******************************************************************************** 2025-09-08T03:53:10,096 ############################ 2025-09-08T03:53:10,096 # Package would be ignored # 2025-09-08T03:53:10,096 ############################ 2025-09-08T03:53:10,096 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' as an importable package[^1], 2025-09-08T03:53:10,096 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,096 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,096 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' is explicitly added 2025-09-08T03:53:10,096 to the `packages` configuration field. 2025-09-08T03:53:10,097 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,097 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,097 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,097 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,097 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,097 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' to be distributed and are 2025-09-08T03:53:10,098 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' via 2025-09-08T03:53:10,098 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,098 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,098 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,098 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,098 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,098 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,099 even if it does not contain any `.py` files. 2025-09-08T03:53:10,099 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,099 directory, all directories are treated like packages. 2025-09-08T03:53:10,099 ******************************************************************************** 2025-09-08T03:53:10,099 !! 2025-09-08T03:53:10,099 check.warn(importable) 2025-09-08T03:53:10,099 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' is absent from the `packages` configuration. 2025-09-08T03:53:10,099 !! 2025-09-08T03:53:10,100 ******************************************************************************** 2025-09-08T03:53:10,100 ############################ 2025-09-08T03:53:10,100 # Package would be ignored # 2025-09-08T03:53:10,100 ############################ 2025-09-08T03:53:10,100 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' as an importable package[^1], 2025-09-08T03:53:10,100 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,100 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,100 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' is explicitly added 2025-09-08T03:53:10,100 to the `packages` configuration field. 2025-09-08T03:53:10,101 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,101 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,101 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,101 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,101 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,101 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' to be distributed and are 2025-09-08T03:53:10,101 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' via 2025-09-08T03:53:10,102 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,102 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,102 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,102 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,102 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,102 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,103 even if it does not contain any `.py` files. 2025-09-08T03:53:10,103 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,103 directory, all directories are treated like packages. 2025-09-08T03:53:10,103 ******************************************************************************** 2025-09-08T03:53:10,103 !! 2025-09-08T03:53:10,103 check.warn(importable) 2025-09-08T03:53:10,103 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:10,103 !! 2025-09-08T03:53:10,104 ******************************************************************************** 2025-09-08T03:53:10,104 ############################ 2025-09-08T03:53:10,104 # Package would be ignored # 2025-09-08T03:53:10,104 ############################ 2025-09-08T03:53:10,104 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Variables' as an importable package[^1], 2025-09-08T03:53:10,104 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,104 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,104 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Variables' is explicitly added 2025-09-08T03:53:10,104 to the `packages` configuration field. 2025-09-08T03:53:10,105 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,105 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,105 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,105 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,105 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,105 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Variables' to be distributed and are 2025-09-08T03:53:10,105 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Variables' via 2025-09-08T03:53:10,106 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,106 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,106 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,106 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,106 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,106 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,106 even if it does not contain any `.py` files. 2025-09-08T03:53:10,107 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,107 directory, all directories are treated like packages. 2025-09-08T03:53:10,107 ******************************************************************************** 2025-09-08T03:53:10,107 !! 2025-09-08T03:53:10,107 check.warn(importable) 2025-09-08T03:53:10,107 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:10,107 !! 2025-09-08T03:53:10,107 ******************************************************************************** 2025-09-08T03:53:10,107 ############################ 2025-09-08T03:53:10,107 # Package would be ignored # 2025-09-08T03:53:10,108 ############################ 2025-09-08T03:53:10,108 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' as an importable package[^1], 2025-09-08T03:53:10,108 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,108 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,108 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' is explicitly added 2025-09-08T03:53:10,108 to the `packages` configuration field. 2025-09-08T03:53:10,108 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,108 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,108 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,109 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,109 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,109 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' to be distributed and are 2025-09-08T03:53:10,109 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' via 2025-09-08T03:53:10,109 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,109 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,109 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,109 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,110 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,110 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,110 even if it does not contain any `.py` files. 2025-09-08T03:53:10,110 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,110 directory, all directories are treated like packages. 2025-09-08T03:53:10,110 ******************************************************************************** 2025-09-08T03:53:10,111 !! 2025-09-08T03:53:10,111 check.warn(importable) 2025-09-08T03:53:10,111 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiset2Publidoc' is absent from the `packages` configuration. 2025-09-08T03:53:10,111 !! 2025-09-08T03:53:10,111 ******************************************************************************** 2025-09-08T03:53:10,111 ############################ 2025-09-08T03:53:10,111 # Package would be ignored # 2025-09-08T03:53:10,111 ############################ 2025-09-08T03:53:10,112 Python recognizes 'publiforge.Processors.Publiset2Publidoc' as an importable package[^1], 2025-09-08T03:53:10,112 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,112 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,112 package, please make sure that 'publiforge.Processors.Publiset2Publidoc' is explicitly added 2025-09-08T03:53:10,112 to the `packages` configuration field. 2025-09-08T03:53:10,112 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,112 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,112 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,113 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,113 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,113 If you don't want 'publiforge.Processors.Publiset2Publidoc' to be distributed and are 2025-09-08T03:53:10,113 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc' via 2025-09-08T03:53:10,113 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,113 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,113 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,114 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,114 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,114 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,114 even if it does not contain any `.py` files. 2025-09-08T03:53:10,114 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,114 directory, all directories are treated like packages. 2025-09-08T03:53:10,114 ******************************************************************************** 2025-09-08T03:53:10,115 !! 2025-09-08T03:53:10,115 check.warn(importable) 2025-09-08T03:53:10,115 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiset2Publidoc.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:10,115 !! 2025-09-08T03:53:10,115 ******************************************************************************** 2025-09-08T03:53:10,115 ############################ 2025-09-08T03:53:10,115 # Package would be ignored # 2025-09-08T03:53:10,115 ############################ 2025-09-08T03:53:10,115 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Variables' as an importable package[^1], 2025-09-08T03:53:10,115 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,116 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,116 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Variables' is explicitly added 2025-09-08T03:53:10,116 to the `packages` configuration field. 2025-09-08T03:53:10,116 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,116 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,116 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,116 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,117 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,117 If you don't want 'publiforge.Processors.Publiset2Publidoc.Variables' to be distributed and are 2025-09-08T03:53:10,117 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Variables' via 2025-09-08T03:53:10,117 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,117 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,117 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,117 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,117 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,118 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,118 even if it does not contain any `.py` files. 2025-09-08T03:53:10,118 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,118 directory, all directories are treated like packages. 2025-09-08T03:53:10,118 ******************************************************************************** 2025-09-08T03:53:10,118 !! 2025-09-08T03:53:10,118 check.warn(importable) 2025-09-08T03:53:10,119 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiset2Publidoc.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:10,119 !! 2025-09-08T03:53:10,119 ******************************************************************************** 2025-09-08T03:53:10,119 ############################ 2025-09-08T03:53:10,119 # Package would be ignored # 2025-09-08T03:53:10,119 ############################ 2025-09-08T03:53:10,119 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Xsl' as an importable package[^1], 2025-09-08T03:53:10,119 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,119 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,120 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Xsl' is explicitly added 2025-09-08T03:53:10,120 to the `packages` configuration field. 2025-09-08T03:53:10,120 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,120 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,120 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,120 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,120 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,121 If you don't want 'publiforge.Processors.Publiset2Publidoc.Xsl' to be distributed and are 2025-09-08T03:53:10,121 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Xsl' via 2025-09-08T03:53:10,121 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,121 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,121 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,121 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,121 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,122 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,122 even if it does not contain any `.py` files. 2025-09-08T03:53:10,122 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,122 directory, all directories are treated like packages. 2025-09-08T03:53:10,122 ******************************************************************************** 2025-09-08T03:53:10,122 !! 2025-09-08T03:53:10,122 check.warn(importable) 2025-09-08T03:53:10,122 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiset4Publidoc' is absent from the `packages` configuration. 2025-09-08T03:53:10,122 !! 2025-09-08T03:53:10,123 ******************************************************************************** 2025-09-08T03:53:10,123 ############################ 2025-09-08T03:53:10,123 # Package would be ignored # 2025-09-08T03:53:10,123 ############################ 2025-09-08T03:53:10,123 Python recognizes 'publiforge.Processors.Publiset4Publidoc' as an importable package[^1], 2025-09-08T03:53:10,123 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,123 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,123 package, please make sure that 'publiforge.Processors.Publiset4Publidoc' is explicitly added 2025-09-08T03:53:10,123 to the `packages` configuration field. 2025-09-08T03:53:10,124 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,124 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,124 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,124 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,124 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,124 If you don't want 'publiforge.Processors.Publiset4Publidoc' to be distributed and are 2025-09-08T03:53:10,125 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc' via 2025-09-08T03:53:10,125 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,125 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,125 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,125 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,125 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,126 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,126 even if it does not contain any `.py` files. 2025-09-08T03:53:10,126 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,126 directory, all directories are treated like packages. 2025-09-08T03:53:10,126 ******************************************************************************** 2025-09-08T03:53:10,126 !! 2025-09-08T03:53:10,126 check.warn(importable) 2025-09-08T03:53:10,126 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiset4Publidoc.Variables' is absent from the `packages` configuration. 2025-09-08T03:53:10,126 !! 2025-09-08T03:53:10,127 ******************************************************************************** 2025-09-08T03:53:10,127 ############################ 2025-09-08T03:53:10,127 # Package would be ignored # 2025-09-08T03:53:10,127 ############################ 2025-09-08T03:53:10,127 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Variables' as an importable package[^1], 2025-09-08T03:53:10,127 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,127 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,127 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Variables' is explicitly added 2025-09-08T03:53:10,127 to the `packages` configuration field. 2025-09-08T03:53:10,128 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,128 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,128 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,128 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,128 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,128 If you don't want 'publiforge.Processors.Publiset4Publidoc.Variables' to be distributed and are 2025-09-08T03:53:10,128 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Variables' via 2025-09-08T03:53:10,128 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,129 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,129 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,129 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,129 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,129 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,129 even if it does not contain any `.py` files. 2025-09-08T03:53:10,129 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,130 directory, all directories are treated like packages. 2025-09-08T03:53:10,130 ******************************************************************************** 2025-09-08T03:53:10,130 !! 2025-09-08T03:53:10,130 check.warn(importable) 2025-09-08T03:53:10,130 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiset4Publidoc.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:10,130 !! 2025-09-08T03:53:10,130 ******************************************************************************** 2025-09-08T03:53:10,130 ############################ 2025-09-08T03:53:10,131 # Package would be ignored # 2025-09-08T03:53:10,131 ############################ 2025-09-08T03:53:10,131 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Xsl' as an importable package[^1], 2025-09-08T03:53:10,131 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,131 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,131 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Xsl' is explicitly added 2025-09-08T03:53:10,131 to the `packages` configuration field. 2025-09-08T03:53:10,131 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,131 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,132 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,132 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,132 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,132 If you don't want 'publiforge.Processors.Publiset4Publidoc.Xsl' to be distributed and are 2025-09-08T03:53:10,132 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Xsl' via 2025-09-08T03:53:10,132 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,132 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,133 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,133 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,133 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,133 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,133 even if it does not contain any `.py` files. 2025-09-08T03:53:10,133 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,134 directory, all directories are treated like packages. 2025-09-08T03:53:10,134 ******************************************************************************** 2025-09-08T03:53:10,134 !! 2025-09-08T03:53:10,134 check.warn(importable) 2025-09-08T03:53:10,134 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiset4Publiquiz' is absent from the `packages` configuration. 2025-09-08T03:53:10,134 !! 2025-09-08T03:53:10,134 ******************************************************************************** 2025-09-08T03:53:10,134 ############################ 2025-09-08T03:53:10,135 # Package would be ignored # 2025-09-08T03:53:10,135 ############################ 2025-09-08T03:53:10,135 Python recognizes 'publiforge.Processors.Publiset4Publiquiz' as an importable package[^1], 2025-09-08T03:53:10,135 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,135 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,135 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz' is explicitly added 2025-09-08T03:53:10,135 to the `packages` configuration field. 2025-09-08T03:53:10,136 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,136 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,136 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,136 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,136 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,136 If you don't want 'publiforge.Processors.Publiset4Publiquiz' to be distributed and are 2025-09-08T03:53:10,136 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz' via 2025-09-08T03:53:10,137 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,137 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,137 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,137 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,137 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,137 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,138 even if it does not contain any `.py` files. 2025-09-08T03:53:10,138 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,138 directory, all directories are treated like packages. 2025-09-08T03:53:10,138 ******************************************************************************** 2025-09-08T03:53:10,138 !! 2025-09-08T03:53:10,138 check.warn(importable) 2025-09-08T03:53:10,138 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiset4Publiquiz.Xsl' is absent from the `packages` configuration. 2025-09-08T03:53:10,138 !! 2025-09-08T03:53:10,139 ******************************************************************************** 2025-09-08T03:53:10,139 ############################ 2025-09-08T03:53:10,139 # Package would be ignored # 2025-09-08T03:53:10,139 ############################ 2025-09-08T03:53:10,139 Python recognizes 'publiforge.Processors.Publiset4Publiquiz.Xsl' as an importable package[^1], 2025-09-08T03:53:10,139 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,139 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,139 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz.Xsl' is explicitly added 2025-09-08T03:53:10,140 to the `packages` configuration field. 2025-09-08T03:53:10,140 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,140 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,140 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,140 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,140 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,141 If you don't want 'publiforge.Processors.Publiset4Publiquiz.Xsl' to be distributed and are 2025-09-08T03:53:10,141 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz.Xsl' via 2025-09-08T03:53:10,141 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,141 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,141 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,141 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,141 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,142 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,142 even if it does not contain any `.py` files. 2025-09-08T03:53:10,142 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,142 directory, all directories are treated like packages. 2025-09-08T03:53:10,142 ******************************************************************************** 2025-09-08T03:53:10,142 !! 2025-09-08T03:53:10,143 check.warn(importable) 2025-09-08T03:53:10,143 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.RelaxNG' is absent from the `packages` configuration. 2025-09-08T03:53:10,143 !! 2025-09-08T03:53:10,143 ******************************************************************************** 2025-09-08T03:53:10,143 ############################ 2025-09-08T03:53:10,143 # Package would be ignored # 2025-09-08T03:53:10,143 ############################ 2025-09-08T03:53:10,143 Python recognizes 'publiforge.RelaxNG' as an importable package[^1], 2025-09-08T03:53:10,143 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,144 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,144 package, please make sure that 'publiforge.RelaxNG' is explicitly added 2025-09-08T03:53:10,144 to the `packages` configuration field. 2025-09-08T03:53:10,144 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,144 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,144 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,144 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,145 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,145 If you don't want 'publiforge.RelaxNG' to be distributed and are 2025-09-08T03:53:10,145 already explicitly excluding 'publiforge.RelaxNG' via 2025-09-08T03:53:10,145 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,145 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,145 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,146 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,146 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,146 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,146 even if it does not contain any `.py` files. 2025-09-08T03:53:10,146 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,146 directory, all directories are treated like packages. 2025-09-08T03:53:10,146 ******************************************************************************** 2025-09-08T03:53:10,147 !! 2025-09-08T03:53:10,147 check.warn(importable) 2025-09-08T03:53:10,147 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Static' is absent from the `packages` configuration. 2025-09-08T03:53:10,147 !! 2025-09-08T03:53:10,147 ******************************************************************************** 2025-09-08T03:53:10,147 ############################ 2025-09-08T03:53:10,147 # Package would be ignored # 2025-09-08T03:53:10,148 ############################ 2025-09-08T03:53:10,148 Python recognizes 'publiforge.Static' as an importable package[^1], 2025-09-08T03:53:10,148 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,148 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,148 package, please make sure that 'publiforge.Static' is explicitly added 2025-09-08T03:53:10,148 to the `packages` configuration field. 2025-09-08T03:53:10,148 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,148 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,149 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,149 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,149 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,149 If you don't want 'publiforge.Static' to be distributed and are 2025-09-08T03:53:10,149 already explicitly excluding 'publiforge.Static' via 2025-09-08T03:53:10,149 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,149 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,150 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,150 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,150 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,150 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,150 even if it does not contain any `.py` files. 2025-09-08T03:53:10,151 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,151 directory, all directories are treated like packages. 2025-09-08T03:53:10,151 ******************************************************************************** 2025-09-08T03:53:10,151 !! 2025-09-08T03:53:10,151 check.warn(importable) 2025-09-08T03:53:10,151 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Static.Css' is absent from the `packages` configuration. 2025-09-08T03:53:10,151 !! 2025-09-08T03:53:10,151 ******************************************************************************** 2025-09-08T03:53:10,152 ############################ 2025-09-08T03:53:10,152 # Package would be ignored # 2025-09-08T03:53:10,152 ############################ 2025-09-08T03:53:10,152 Python recognizes 'publiforge.Static.Css' as an importable package[^1], 2025-09-08T03:53:10,152 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,152 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,152 package, please make sure that 'publiforge.Static.Css' is explicitly added 2025-09-08T03:53:10,152 to the `packages` configuration field. 2025-09-08T03:53:10,153 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,153 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,153 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,153 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,153 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,154 If you don't want 'publiforge.Static.Css' to be distributed and are 2025-09-08T03:53:10,154 already explicitly excluding 'publiforge.Static.Css' via 2025-09-08T03:53:10,154 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,154 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,154 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,154 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,155 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,155 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,155 even if it does not contain any `.py` files. 2025-09-08T03:53:10,155 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,155 directory, all directories are treated like packages. 2025-09-08T03:53:10,155 ******************************************************************************** 2025-09-08T03:53:10,156 !! 2025-09-08T03:53:10,156 check.warn(importable) 2025-09-08T03:53:10,156 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Static.Images' is absent from the `packages` configuration. 2025-09-08T03:53:10,156 !! 2025-09-08T03:53:10,156 ******************************************************************************** 2025-09-08T03:53:10,156 ############################ 2025-09-08T03:53:10,156 # Package would be ignored # 2025-09-08T03:53:10,157 ############################ 2025-09-08T03:53:10,157 Python recognizes 'publiforge.Static.Images' as an importable package[^1], 2025-09-08T03:53:10,157 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,157 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,157 package, please make sure that 'publiforge.Static.Images' is explicitly added 2025-09-08T03:53:10,157 to the `packages` configuration field. 2025-09-08T03:53:10,158 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,158 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,158 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,158 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,158 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,159 If you don't want 'publiforge.Static.Images' to be distributed and are 2025-09-08T03:53:10,159 already explicitly excluding 'publiforge.Static.Images' via 2025-09-08T03:53:10,159 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,159 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,159 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,159 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,159 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,160 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,160 even if it does not contain any `.py` files. 2025-09-08T03:53:10,160 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,160 directory, all directories are treated like packages. 2025-09-08T03:53:10,160 ******************************************************************************** 2025-09-08T03:53:10,161 !! 2025-09-08T03:53:10,161 check.warn(importable) 2025-09-08T03:53:10,161 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Static.Images.MimeTypes' is absent from the `packages` configuration. 2025-09-08T03:53:10,161 !! 2025-09-08T03:53:10,161 ******************************************************************************** 2025-09-08T03:53:10,161 ############################ 2025-09-08T03:53:10,161 # Package would be ignored # 2025-09-08T03:53:10,161 ############################ 2025-09-08T03:53:10,162 Python recognizes 'publiforge.Static.Images.MimeTypes' as an importable package[^1], 2025-09-08T03:53:10,162 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,162 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,162 package, please make sure that 'publiforge.Static.Images.MimeTypes' is explicitly added 2025-09-08T03:53:10,162 to the `packages` configuration field. 2025-09-08T03:53:10,162 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,163 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,163 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,163 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,163 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,163 If you don't want 'publiforge.Static.Images.MimeTypes' to be distributed and are 2025-09-08T03:53:10,163 already explicitly excluding 'publiforge.Static.Images.MimeTypes' via 2025-09-08T03:53:10,164 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,164 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,164 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,164 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,164 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,165 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,165 even if it does not contain any `.py` files. 2025-09-08T03:53:10,165 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,165 directory, all directories are treated like packages. 2025-09-08T03:53:10,165 ******************************************************************************** 2025-09-08T03:53:10,165 !! 2025-09-08T03:53:10,165 check.warn(importable) 2025-09-08T03:53:10,165 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Static.Js' is absent from the `packages` configuration. 2025-09-08T03:53:10,166 !! 2025-09-08T03:53:10,166 ******************************************************************************** 2025-09-08T03:53:10,166 ############################ 2025-09-08T03:53:10,166 # Package would be ignored # 2025-09-08T03:53:10,166 ############################ 2025-09-08T03:53:10,166 Python recognizes 'publiforge.Static.Js' as an importable package[^1], 2025-09-08T03:53:10,166 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,167 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,167 package, please make sure that 'publiforge.Static.Js' is explicitly added 2025-09-08T03:53:10,167 to the `packages` configuration field. 2025-09-08T03:53:10,167 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,167 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,167 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,168 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,168 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,168 If you don't want 'publiforge.Static.Js' to be distributed and are 2025-09-08T03:53:10,168 already explicitly excluding 'publiforge.Static.Js' via 2025-09-08T03:53:10,168 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,168 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,168 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,169 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,169 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,169 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,169 even if it does not contain any `.py` files. 2025-09-08T03:53:10,169 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,170 directory, all directories are treated like packages. 2025-09-08T03:53:10,170 ******************************************************************************** 2025-09-08T03:53:10,170 !! 2025-09-08T03:53:10,170 check.warn(importable) 2025-09-08T03:53:10,170 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Static.Js.Tests' is absent from the `packages` configuration. 2025-09-08T03:53:10,170 !! 2025-09-08T03:53:10,171 ******************************************************************************** 2025-09-08T03:53:10,171 ############################ 2025-09-08T03:53:10,171 # Package would be ignored # 2025-09-08T03:53:10,171 ############################ 2025-09-08T03:53:10,171 Python recognizes 'publiforge.Static.Js.Tests' as an importable package[^1], 2025-09-08T03:53:10,171 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,171 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,171 package, please make sure that 'publiforge.Static.Js.Tests' is explicitly added 2025-09-08T03:53:10,172 to the `packages` configuration field. 2025-09-08T03:53:10,172 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,172 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,172 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,172 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,172 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,173 If you don't want 'publiforge.Static.Js.Tests' to be distributed and are 2025-09-08T03:53:10,173 already explicitly excluding 'publiforge.Static.Js.Tests' via 2025-09-08T03:53:10,173 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,173 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,173 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,173 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,174 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,174 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,174 even if it does not contain any `.py` files. 2025-09-08T03:53:10,174 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,174 directory, all directories are treated like packages. 2025-09-08T03:53:10,174 ******************************************************************************** 2025-09-08T03:53:10,175 !! 2025-09-08T03:53:10,175 check.warn(importable) 2025-09-08T03:53:10,175 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Templates' is absent from the `packages` configuration. 2025-09-08T03:53:10,175 !! 2025-09-08T03:53:10,175 ******************************************************************************** 2025-09-08T03:53:10,175 ############################ 2025-09-08T03:53:10,175 # Package would be ignored # 2025-09-08T03:53:10,176 ############################ 2025-09-08T03:53:10,176 Python recognizes 'publiforge.Templates' as an importable package[^1], 2025-09-08T03:53:10,176 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,176 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,176 package, please make sure that 'publiforge.Templates' is explicitly added 2025-09-08T03:53:10,176 to the `packages` configuration field. 2025-09-08T03:53:10,177 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,177 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,177 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,177 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,177 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,177 If you don't want 'publiforge.Templates' to be distributed and are 2025-09-08T03:53:10,178 already explicitly excluding 'publiforge.Templates' via 2025-09-08T03:53:10,178 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,178 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,178 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,178 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,178 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,179 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,179 even if it does not contain any `.py` files. 2025-09-08T03:53:10,179 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,179 directory, all directories are treated like packages. 2025-09-08T03:53:10,179 ******************************************************************************** 2025-09-08T03:53:10,179 !! 2025-09-08T03:53:10,180 check.warn(importable) 2025-09-08T03:53:10,180 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.tests.Data' is absent from the `packages` configuration. 2025-09-08T03:53:10,180 !! 2025-09-08T03:53:10,180 ******************************************************************************** 2025-09-08T03:53:10,180 ############################ 2025-09-08T03:53:10,180 # Package would be ignored # 2025-09-08T03:53:10,180 ############################ 2025-09-08T03:53:10,180 Python recognizes 'publiforge.tests.Data' as an importable package[^1], 2025-09-08T03:53:10,181 but it is absent from setuptools' `packages` configuration. 2025-09-08T03:53:10,181 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T03:53:10,181 package, please make sure that 'publiforge.tests.Data' is explicitly added 2025-09-08T03:53:10,181 to the `packages` configuration field. 2025-09-08T03:53:10,181 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T03:53:10,181 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T03:53:10,181 instead of `find_packages(...)`/`find:`). 2025-09-08T03:53:10,182 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T03:53:10,182 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T03:53:10,182 If you don't want 'publiforge.tests.Data' to be distributed and are 2025-09-08T03:53:10,182 already explicitly excluding 'publiforge.tests.Data' via 2025-09-08T03:53:10,182 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T03:53:10,183 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T03:53:10,183 combination with a more fine grained `package-data` configuration. 2025-09-08T03:53:10,183 You can read more about "package data files" on setuptools documentation page: 2025-09-08T03:53:10,183 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T03:53:10,183 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T03:53:10,184 even if it does not contain any `.py` files. 2025-09-08T03:53:10,184 On the other hand, currently there is no concept of package data 2025-09-08T03:53:10,184 directory, all directories are treated like packages. 2025-09-08T03:53:10,184 ******************************************************************************** 2025-09-08T03:53:10,184 !! 2025-09-08T03:53:10,184 check.warn(importable) 2025-09-08T03:53:10,184 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale 2025-09-08T03:53:10,185 copying publiforge/Locale/publiforge.pot -> build/lib.linux-armv7l-cpython-313/publiforge/Locale 2025-09-08T03:53:10,185 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T03:53:10,185 copying publiforge/Locale/es/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T03:53:10,185 copying publiforge/Locale/es/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T03:53:10,185 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T03:53:10,185 copying publiforge/Locale/fr/LC_MESSAGES/colander.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T03:53:10,185 copying publiforge/Locale/fr/LC_MESSAGES/colander.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T03:53:10,185 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T03:53:10,185 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T03:53:10,186 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T03:53:10,186 copying publiforge/Openers/Image/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T03:53:10,186 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T03:53:10,186 copying publiforge/Openers/Ini/ini.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T03:53:10,186 copying publiforge/Openers/Ini/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T03:53:10,186 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/NoMore 2025-09-08T03:53:10,186 copying publiforge/Openers/NoMore/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/NoMore 2025-09-08T03:53:10,186 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Plain 2025-09-08T03:53:10,187 copying publiforge/Openers/Plain/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Plain 2025-09-08T03:53:10,187 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T03:53:10,187 copying publiforge/Openers/Publidoc/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T03:53:10,187 copying publiforge/Openers/Publidoc/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T03:53:10,187 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T03:53:10,187 copying publiforge/Openers/Publidoc/Maestro/publidoc_render4maestro.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T03:53:10,187 copying publiforge/Openers/Publidoc/Maestro/publidoc_xml4maestro.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T03:53:10,187 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Regex 2025-09-08T03:53:10,187 copying publiforge/Openers/Publidoc/Regex/publidoc_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Regex 2025-09-08T03:53:10,188 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T03:53:10,188 copying publiforge/Openers/Publidoc/Seeds/publidoc_document.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T03:53:10,188 copying publiforge/Openers/Publidoc/Seeds/publidoc_topic.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T03:53:10,188 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T03:53:10,188 copying publiforge/Openers/Publidoc/Static/Css/publidoc_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T03:53:10,188 copying publiforge/Openers/Publidoc/Static/Css/publidoc_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T03:53:10,188 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T03:53:10,188 copying publiforge/Openers/Publidoc/Static/Js/codemirror4publidoc_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T03:53:10,188 copying publiforge/Openers/Publidoc/Static/Js/publidoc_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T03:53:10,189 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Variables 2025-09-08T03:53:10,189 copying publiforge/Openers/Publidoc/Variables/publidoc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Variables 2025-09-08T03:53:10,189 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T03:53:10,189 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T03:53:10,189 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T03:53:10,189 copying publiforge/Openers/Publidoc/Xsl/publidoc_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T03:53:10,189 copying publiforge/Openers/Publidoc/Xsl/publidoc_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T03:53:10,190 copying publiforge/Openers/Publidoc/Xsl/publidoc_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T03:53:10,190 copying publiforge/Openers/Publidoc/Xsl/publidoc_save_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T03:53:10,190 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T03:53:10,190 copying publiforge/Openers/Publiquiz/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T03:53:10,190 copying publiforge/Openers/Publiquiz/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T03:53:10,190 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Regex 2025-09-08T03:53:10,190 copying publiforge/Openers/Publiquiz/Regex/publiquiz_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Regex 2025-09-08T03:53:10,190 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,190 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-char.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-fill.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-select.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-check.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_composite.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_matching.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing-categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,191 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,192 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_production.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,192 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_sort.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T03:53:10,192 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T03:53:10,192 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T03:53:10,192 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T03:53:10,192 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T03:53:10,192 copying publiforge/Openers/Publiquiz/Static/Js/codemirror4publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T03:53:10,192 copying publiforge/Openers/Publiquiz/Static/Js/publiquiz_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T03:53:10,193 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Variables 2025-09-08T03:53:10,193 copying publiforge/Openers/Publiquiz/Variables/publiquiz.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Variables 2025-09-08T03:53:10,193 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T03:53:10,193 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T03:53:10,193 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T03:53:10,193 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T03:53:10,193 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T03:53:10,193 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T03:53:10,194 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T03:53:10,194 copying publiforge/Openers/Publiset/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T03:53:10,194 copying publiforge/Openers/Publiset/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T03:53:10,194 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Regex 2025-09-08T03:53:10,194 copying publiforge/Openers/Publiset/Regex/publiset_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Regex 2025-09-08T03:53:10,194 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T03:53:10,194 copying publiforge/Openers/Publiset/Seeds/publiset_composition.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T03:53:10,194 copying publiforge/Openers/Publiset/Seeds/publiset_selection.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T03:53:10,194 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T03:53:10,195 copying publiforge/Openers/Publiset/Static/Css/editor4publiset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T03:53:10,195 copying publiforge/Openers/Publiset/Static/Css/publiset_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T03:53:10,195 copying publiforge/Openers/Publiset/Static/Css/publiset_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T03:53:10,195 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T03:53:10,195 copying publiforge/Openers/Publiset/Static/Images/editor4publiset.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T03:53:10,195 copying publiforge/Openers/Publiset/Static/Images/editor4publiset.xcf -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T03:53:10,195 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T03:53:10,195 copying publiforge/Openers/Publiset/Static/Js/codemirror4publiset_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T03:53:10,196 copying publiforge/Openers/Publiset/Static/Js/editor4publiset.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T03:53:10,196 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_en.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T03:53:10,196 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_fr.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T03:53:10,196 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T03:53:10,197 copying publiforge/Openers/Publiset/Static/Js/publiset_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T03:53:10,198 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Variables 2025-09-08T03:53:10,198 copying publiforge/Openers/Publiset/Variables/publiset.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Variables 2025-09-08T03:53:10,199 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T03:53:10,199 copying publiforge/Openers/Publiset/Xsl/publiset_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T03:53:10,200 copying publiforge/Openers/Publiset/Xsl/publiset_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T03:53:10,201 copying publiforge/Openers/Publiset/Xsl/publiset_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T03:53:10,201 copying publiforge/Openers/Publiset/Xsl/publiset_render_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T03:53:10,202 copying publiforge/Openers/Publiset/Xsl/publiset_render_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T03:53:10,203 copying publiforge/Openers/Publiset/Xsl/publiset_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T03:53:10,204 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T03:53:10,204 copying publiforge/Openers/Xml/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T03:53:10,205 copying publiforge/Openers/Xml/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T03:53:10,205 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Css 2025-09-08T03:53:10,206 copying publiforge/Openers/Xml/Static/Css/editor4xml.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Css 2025-09-08T03:53:10,206 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T03:53:10,207 copying publiforge/Openers/Xml/Static/Images/e4x_folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T03:53:10,207 copying publiforge/Openers/Xml/Static/Images/editor4xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T03:53:10,208 copying publiforge/Openers/Xml/Static/Images/editor4xml.xcf -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T03:53:10,209 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T03:53:10,209 copying publiforge/Openers/Xml/Static/Js/editor4xml.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T03:53:10,210 copying publiforge/Openers/Xml/Static/Js/editor4xml_en.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T03:53:10,211 copying publiforge/Openers/Xml/Static/Js/editor4xml_fr.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T03:53:10,212 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T03:53:10,212 copying publiforge/Processors/CharCount/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T03:53:10,213 copying publiforge/Processors/CharCount/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T03:53:10,213 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount/Xsl 2025-09-08T03:53:10,214 copying publiforge/Processors/CharCount/Xsl/charcount.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount/Xsl 2025-09-08T03:53:10,214 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T03:53:10,215 copying publiforge/Processors/CleanStorage/generator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T03:53:10,215 copying publiforge/Processors/CleanStorage/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T03:53:10,216 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T03:53:10,216 copying publiforge/Processors/CleanStorage/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T03:53:10,217 copying publiforge/Processors/CleanStorage/lib/__init__.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T03:53:10,218 copying publiforge/Processors/CleanStorage/lib/clean_storage.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T03:53:10,218 copying publiforge/Processors/CleanStorage/lib/clean_storage.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T03:53:10,219 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T03:53:10,219 copying publiforge/Processors/DTBookValid/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T03:53:10,220 copying publiforge/Processors/DTBookValid/validator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T03:53:10,221 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid/RelaxNG 2025-09-08T03:53:10,221 copying publiforge/Processors/DTBookValid/RelaxNG/dtbook-2005-3.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid/RelaxNG 2025-09-08T03:53:10,222 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T03:53:10,222 copying publiforge/Processors/PackFilling/generator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T03:53:10,223 copying publiforge/Processors/PackFilling/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T03:53:10,224 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/Variables 2025-09-08T03:53:10,224 copying publiforge/Processors/PackFilling/Variables/packfilling.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/Variables 2025-09-08T03:53:10,225 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T03:53:10,225 copying publiforge/Processors/PackFilling/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T03:53:10,226 copying publiforge/Processors/PackFilling/lib/__init__.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T03:53:10,226 copying publiforge/Processors/PackFilling/lib/packfilling.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T03:53:10,227 copying publiforge/Processors/PackFilling/lib/packfilling.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T03:53:10,228 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel 2025-09-08T03:53:10,228 copying publiforge/Processors/Parallel/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel 2025-09-08T03:53:10,229 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel/Variables 2025-09-08T03:53:10,229 copying publiforge/Processors/Parallel/Variables/parallel.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel/Variables 2025-09-08T03:53:10,230 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv 2025-09-08T03:53:10,230 copying publiforge/Processors/Publidoc2Csv/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv 2025-09-08T03:53:10,230 copying publiforge/Processors/Publidoc2Csv/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv 2025-09-08T03:53:10,231 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T03:53:10,231 copying publiforge/Processors/Publidoc2Csv/Regex/publidoc2csv1_post.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T03:53:10,232 copying publiforge/Processors/Publidoc2Csv/Regex/publidoc2csv1a_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T03:53:10,233 copying publiforge/Processors/Publidoc2Csv/Regex/publidoc2csv1b_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T03:53:10,234 copying publiforge/Processors/Publidoc2Csv/Regex/publidoc2csv2_post.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T03:53:10,234 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Templates 2025-09-08T03:53:10,235 copying publiforge/Processors/Publidoc2Csv/Templates/dummy1.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Templates 2025-09-08T03:53:10,235 copying publiforge/Processors/Publidoc2Csv/Templates/dummy2.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Templates 2025-09-08T03:53:10,236 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Variables 2025-09-08T03:53:10,236 copying publiforge/Processors/Publidoc2Csv/Variables/publidoc2csv.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Variables 2025-09-08T03:53:10,237 copying publiforge/Processors/Publidoc2Csv/Variables/publidoc2csv_unused.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Variables 2025-09-08T03:53:10,238 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Xsl 2025-09-08T03:53:10,238 copying publiforge/Processors/Publidoc2Csv/Xsl/publidoc2csv1.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Xsl 2025-09-08T03:53:10,239 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,239 copying publiforge/Processors/Publidoc2Csv/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,239 copying publiforge/Processors/Publidoc2Csv/lib/__init__.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,240 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv1_post.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,241 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv1_post.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,242 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv1_pre.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,242 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv1_pre.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,243 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv2_post.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,244 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv2_post.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,244 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv_final.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,245 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv_final.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,246 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv_init.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,246 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv_init.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,247 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv_make_id.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,248 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv_make_id.pyc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T03:53:10,248 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T03:53:10,249 copying publiforge/Processors/Publidoc2DTBook/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T03:53:10,249 copying publiforge/Processors/Publidoc2DTBook/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T03:53:10,250 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T03:53:10,250 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T03:53:10,251 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T03:53:10,252 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T03:53:10,252 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T03:53:10,253 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T03:53:10,254 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T03:53:10,254 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T03:53:10,255 copying publiforge/Processors/Publidoc2EPub2/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T03:53:10,255 copying publiforge/Processors/Publidoc2EPub2/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T03:53:10,256 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates 2025-09-08T03:53:10,256 copying publiforge/Processors/Publidoc2EPub2/Templates/mimetype -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates 2025-09-08T03:53:10,257 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2025-09-08T03:53:10,257 copying publiforge/Processors/Publidoc2EPub2/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2025-09-08T03:53:10,258 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2025-09-08T03:53:10,258 copying publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2025-09-08T03:53:10,259 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T03:53:10,259 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T03:53:10,260 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T03:53:10,261 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T03:53:10,261 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T03:53:10,262 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T03:53:10,262 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T03:53:10,263 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T03:53:10,264 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ncx.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T03:53:10,264 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T03:53:10,265 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T03:53:10,266 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T03:53:10,266 copying publiforge/Processors/Publidoc2EPub2/jars/COPYING.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T03:53:10,267 copying publiforge/Processors/Publidoc2EPub2/jars/README.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T03:53:10,268 copying publiforge/Processors/Publidoc2EPub2/jars/THIRD-PARTY.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T03:53:10,268 copying publiforge/Processors/Publidoc2EPub2/jars/epubcheck.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T03:53:10,273 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,273 copying publiforge/Processors/Publidoc2EPub2/jars/lib/Saxon-HE-9.5.1-5.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,313 copying publiforge/Processors/Publidoc2EPub2/jars/lib/common-image-3.1.2.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,314 copying publiforge/Processors/Publidoc2EPub2/jars/lib/common-io-3.1.2.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,315 copying publiforge/Processors/Publidoc2EPub2/jars/lib/common-lang-3.1.2.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,317 copying publiforge/Processors/Publidoc2EPub2/jars/lib/commons-compress-1.5.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,318 copying publiforge/Processors/Publidoc2EPub2/jars/lib/guava-14.0.1.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,327 copying publiforge/Processors/Publidoc2EPub2/jars/lib/imageio-core-3.1.2.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,328 copying publiforge/Processors/Publidoc2EPub2/jars/lib/imageio-jpeg-3.1.2.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,329 copying publiforge/Processors/Publidoc2EPub2/jars/lib/imageio-metadata-3.1.2.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,330 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jackson-core-asl-1.9.12.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,332 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jackson-mapper-asl-1.9.12.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,336 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jing-20120724.0.0.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,339 copying publiforge/Processors/Publidoc2EPub2/jars/lib/sac-1.3.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T03:53:10,340 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T03:53:10,340 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/Apache-2.0.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T03:53:10,341 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/BSD-3-Clause.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T03:53:10,342 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/MPL-1.0.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T03:53:10,343 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/W3C.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T03:53:10,343 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T03:53:10,344 copying publiforge/Processors/Publidoc2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T03:53:10,344 copying publiforge/Processors/Publidoc2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T03:53:10,345 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates 2025-09-08T03:53:10,345 copying publiforge/Processors/Publidoc2EPub3/Templates/mimetype -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates 2025-09-08T03:53:10,346 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2025-09-08T03:53:10,346 copying publiforge/Processors/Publidoc2EPub3/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2025-09-08T03:53:10,347 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2025-09-08T03:53:10,347 copying publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2025-09-08T03:53:10,348 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Variables 2025-09-08T03:53:10,348 copying publiforge/Processors/Publidoc2EPub3/Variables/publidoc2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Variables 2025-09-08T03:53:10,349 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T03:53:10,349 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T03:53:10,350 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_nav.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T03:53:10,351 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T03:53:10,352 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_smil.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T03:53:10,352 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T03:53:10,353 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T03:53:10,353 copying publiforge/Processors/Publidoc2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T03:53:10,354 copying publiforge/Processors/Publidoc2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T03:53:10,355 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T03:53:10,355 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T03:53:10,356 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_play.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T03:53:10,356 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Js 2025-09-08T03:53:10,357 copying publiforge/Processors/Publidoc2Html5/Templates/Js/audio_player.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Js 2025-09-08T03:53:10,358 copying publiforge/Processors/Publidoc2Html5/Templates/Js/publidoc.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Js 2025-09-08T03:53:10,358 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T03:53:10,359 copying publiforge/Processors/Publidoc2Html5/Variables/publidoc2html5_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T03:53:10,359 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T03:53:10,360 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T03:53:10,360 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T03:53:10,361 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_media.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T03:53:10,362 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T03:53:10,362 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T03:53:10,363 copying publiforge/Processors/Publidoc2Pdf/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T03:53:10,363 copying publiforge/Processors/Publidoc2Pdf/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T03:53:10,364 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T03:53:10,364 copying publiforge/Processors/Publidoc2Pdf/Fonts/Mono-Bold.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T03:53:10,366 copying publiforge/Processors/Publidoc2Pdf/Fonts/Mono-BoldItalic.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T03:53:10,367 copying publiforge/Processors/Publidoc2Pdf/Fonts/Mono-Italic.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T03:53:10,369 copying publiforge/Processors/Publidoc2Pdf/Fonts/Mono-Regular.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T03:53:10,370 copying publiforge/Processors/Publidoc2Pdf/Fonts/Script.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T03:53:10,373 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T03:53:10,373 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_post.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T03:53:10,374 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T03:53:10,375 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T03:53:10,375 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_dimension.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T03:53:10,376 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_font.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T03:53:10,377 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T03:53:10,377 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_layout.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T03:53:10,378 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T03:53:10,378 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T03:53:10,379 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T03:53:10,379 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T03:53:10,380 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T03:53:10,381 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T03:53:10,382 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T03:53:10,382 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T03:53:10,383 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T03:53:10,383 copying publiforge/Processors/Publidoc2XHtml/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T03:53:10,384 copying publiforge/Processors/Publidoc2XHtml/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T03:53:10,385 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Regex 2025-09-08T03:53:10,385 copying publiforge/Processors/Publidoc2XHtml/Regex/publidoc2xhtml_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Regex 2025-09-08T03:53:10,386 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T03:53:10,386 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T03:53:10,387 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/publidoc.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T03:53:10,387 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/reset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T03:53:10,388 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,388 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/annotation.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,389 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,390 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/close.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,391 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,391 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_previous.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,392 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,393 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/pulse.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,393 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/video.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T03:53:10,394 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T03:53:10,394 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/jquery.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T03:53:10,395 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/publidoc.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T03:53:10,396 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T03:53:10,396 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T03:53:10,397 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T03:53:10,398 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T03:53:10,399 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T03:53:10,399 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T03:53:10,400 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T03:53:10,400 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T03:53:10,401 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T03:53:10,402 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T03:53:10,403 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T03:53:10,404 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_media.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T03:53:10,404 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T03:53:10,405 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T03:53:10,405 copying publiforge/Processors/PublidocClean/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T03:53:10,406 copying publiforge/Processors/PublidocClean/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T03:53:10,407 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Regex 2025-09-08T03:53:10,407 copying publiforge/Processors/PublidocClean/Regex/publidocclean_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Regex 2025-09-08T03:53:10,408 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Variables 2025-09-08T03:53:10,408 copying publiforge/Processors/PublidocClean/Variables/publidocclean.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Variables 2025-09-08T03:53:10,409 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Xsl 2025-09-08T03:53:10,409 copying publiforge/Processors/PublidocClean/Xsl/publidocclean.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Xsl 2025-09-08T03:53:10,410 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T03:53:10,410 copying publiforge/Processors/PublidocValid/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T03:53:10,411 copying publiforge/Processors/PublidocValid/validator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T03:53:10,411 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T03:53:10,412 copying publiforge/Processors/PublidocValid/RelaxNG/publidoc.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T03:53:10,413 copying publiforge/Processors/PublidocValid/RelaxNG/publiquiz.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T03:53:10,414 copying publiforge/Processors/PublidocValid/RelaxNG/publiset.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T03:53:10,414 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T03:53:10,415 copying publiforge/Processors/Publiquiz2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T03:53:10,415 copying publiforge/Processors/Publiquiz2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T03:53:10,416 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Variables 2025-09-08T03:53:10,416 copying publiforge/Processors/Publiquiz2EPub3/Variables/publiquiz2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Variables 2025-09-08T03:53:10,417 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T03:53:10,417 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T03:53:10,418 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T03:53:10,419 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T03:53:10,419 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T03:53:10,420 copying publiforge/Processors/Publiquiz2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T03:53:10,420 copying publiforge/Processors/Publiquiz2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T03:53:10,421 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T03:53:10,421 copying publiforge/Processors/Publiquiz2Html5/Templates/Css/publiquiz.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T03:53:10,422 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T03:53:10,423 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T03:53:10,424 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_basics.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T03:53:10,425 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_blanks_char.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T03:53:10,426 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T03:53:10,426 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_matching_link.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T03:53:10,427 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_mip.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T03:53:10,428 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T03:53:10,428 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T03:53:10,429 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5_quiz.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T03:53:10,430 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T03:53:10,430 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T03:53:10,431 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T03:53:10,432 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T03:53:10,433 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T03:53:10,433 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T03:53:10,434 copying publiforge/Processors/Publiquiz2Scorm12/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T03:53:10,434 copying publiforge/Processors/Publiquiz2Scorm12/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T03:53:10,435 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T03:53:10,435 copying publiforge/Processors/Publiquiz2Scorm12/Templates/adlcp_rootv1p2.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T03:53:10,436 copying publiforge/Processors/Publiquiz2Scorm12/Templates/ims_xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T03:53:10,437 copying publiforge/Processors/Publiquiz2Scorm12/Templates/imscp_rootv1p1p2.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T03:53:10,437 copying publiforge/Processors/Publiquiz2Scorm12/Templates/imsmd_rootv1p2p1.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T03:53:10,438 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css 2025-09-08T03:53:10,439 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css 2025-09-08T03:53:10,439 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T03:53:10,440 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T03:53:10,440 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images/audio_play.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T03:53:10,441 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T03:53:10,441 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T03:53:10,442 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js/scorm_apiwrapper.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T03:53:10,443 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T03:53:10,443 copying publiforge/Processors/Publiquiz2Scorm12/Variables/publiquiz2scorm12.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T03:53:10,444 copying publiforge/Processors/Publiquiz2Scorm12/Variables/publiquiz2scorm12_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T03:53:10,444 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T03:53:10,445 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T03:53:10,445 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T03:53:10,446 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_ims.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T03:53:10,447 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T03:53:10,447 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T03:53:10,448 copying publiforge/Processors/Publiquiz2Scorm2004/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T03:53:10,449 copying publiforge/Processors/Publiquiz2Scorm2004/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T03:53:10,449 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,450 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/XMLSchema.dtd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,450 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlcp_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,451 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlnav_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,452 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlseq_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,452 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/datatypes.dtd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,453 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/ims_xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,454 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imscp_v1p1.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,455 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,455 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0auxresource.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,456 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0control.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,457 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0delivery.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,457 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0limit.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,458 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0objective.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,459 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0random.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,459 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0rollup.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,460 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0seqrule.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,461 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0util.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,461 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,462 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomCustom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,463 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomLoose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,464 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomStrict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,464 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T03:53:10,465 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css 2025-09-08T03:53:10,465 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css 2025-09-08T03:53:10,466 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T03:53:10,466 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T03:53:10,467 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js/scorm_apiwrapper.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T03:53:10,468 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T03:53:10,468 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/anyElement.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T03:53:10,469 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/dataTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T03:53:10,470 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/elementNames.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T03:53:10,470 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/elementTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T03:53:10,471 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/rootElement.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T03:53:10,472 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/vocabTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T03:53:10,473 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/vocabValues.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T03:53:10,473 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T03:53:10,474 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/extend/custom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T03:53:10,474 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/extend/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T03:53:10,475 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T03:53:10,475 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/unique/loose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T03:53:10,476 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/unique/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T03:53:10,477 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T03:53:10,477 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/custom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T03:53:10,478 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/loose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T03:53:10,478 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T03:53:10,479 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T03:53:10,479 copying publiforge/Processors/Publiquiz2Scorm2004/Variables/publiquiz2scorm2004.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T03:53:10,480 copying publiforge/Processors/Publiquiz2Scorm2004/Variables/publiquiz2scorm2004_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T03:53:10,481 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T03:53:10,481 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T03:53:10,482 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T03:53:10,483 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_ims.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T03:53:10,483 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T03:53:10,484 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T03:53:10,484 copying publiforge/Processors/Publiset2Publidoc/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T03:53:10,485 copying publiforge/Processors/Publiset2Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T03:53:10,486 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T03:53:10,486 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T03:53:10,487 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T03:53:10,487 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T03:53:10,488 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T03:53:10,488 copying publiforge/Processors/Publiset2Publidoc/Xsl/composition.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T03:53:10,489 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T03:53:10,490 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T03:53:10,490 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T03:53:10,491 copying publiforge/Processors/Publiset4Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T03:53:10,491 copying publiforge/Processors/Publiset4Publidoc/publiseter.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T03:53:10,492 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T03:53:10,492 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_meta.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T03:53:10,493 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T03:53:10,494 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_schema.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T03:53:10,494 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Xsl 2025-09-08T03:53:10,495 copying publiforge/Processors/Publiset4Publidoc/Xsl/publiset4publidoc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Xsl 2025-09-08T03:53:10,495 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T03:53:10,496 copying publiforge/Processors/Publiset4Publiquiz/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T03:53:10,496 copying publiforge/Processors/Publiset4Publiquiz/publiseter.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T03:53:10,497 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz/Xsl 2025-09-08T03:53:10,497 copying publiforge/Processors/Publiset4Publiquiz/Xsl/publiset4publiquiz.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz/Xsl 2025-09-08T03:53:10,498 creating build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T03:53:10,498 copying publiforge/RelaxNG/publiforge.rnc -> build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T03:53:10,499 copying publiforge/RelaxNG/publiforge.rng -> build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T03:53:10,500 creating build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T03:53:10,501 copying publiforge/Static/favicon.ico -> build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T03:53:10,501 copying publiforge/Static/robots.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T03:53:10,502 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T03:53:10,502 copying publiforge/Static/Css/base.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T03:53:10,503 copying publiforge/Static/Css/codemirror.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T03:53:10,504 copying publiforge/Static/Css/colors.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T03:53:10,505 copying publiforge/Static/Css/login.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T03:53:10,505 copying publiforge/Static/Css/pygments.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T03:53:10,506 copying publiforge/Static/Css/reset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T03:53:10,507 copying publiforge/Static/Css/reset.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T03:53:10,507 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,508 copying publiforge/Static/Images/action_add.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,508 copying publiforge/Static/Images/action_add_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,509 copying publiforge/Static/Images/action_browse.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,510 copying publiforge/Static/Images/action_browse_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,510 copying publiforge/Static/Images/action_build.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,511 copying publiforge/Static/Images/action_build_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,512 copying publiforge/Static/Images/action_cancel.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,512 copying publiforge/Static/Images/action_create.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,513 copying publiforge/Static/Images/action_dashboard_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,514 copying publiforge/Static/Images/action_delete.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,514 copying publiforge/Static/Images/action_delete_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,515 copying publiforge/Static/Images/action_diff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,516 copying publiforge/Static/Images/action_diff_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,516 copying publiforge/Static/Images/action_display.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,517 copying publiforge/Static/Images/action_display_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,518 copying publiforge/Static/Images/action_down_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,518 copying publiforge/Static/Images/action_download.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,519 copying publiforge/Static/Images/action_download_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,520 copying publiforge/Static/Images/action_duplicate.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,520 copying publiforge/Static/Images/action_edit_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,521 copying publiforge/Static/Images/action_export.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,522 copying publiforge/Static/Images/action_export_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,523 copying publiforge/Static/Images/action_filter.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,523 copying publiforge/Static/Images/action_help_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,524 copying publiforge/Static/Images/action_history_empty.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,525 copying publiforge/Static/Images/action_import.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,525 copying publiforge/Static/Images/action_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,526 copying publiforge/Static/Images/action_info_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,527 copying publiforge/Static/Images/action_log.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,527 copying publiforge/Static/Images/action_log_empty.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,528 copying publiforge/Static/Images/action_log_empty_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,529 copying publiforge/Static/Images/action_mkdir.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,529 copying publiforge/Static/Images/action_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,530 copying publiforge/Static/Images/action_next_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,531 copying publiforge/Static/Images/action_note.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,531 copying publiforge/Static/Images/action_note_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,532 copying publiforge/Static/Images/action_overview_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,533 copying publiforge/Static/Images/action_overview_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,533 copying publiforge/Static/Images/action_pack.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,534 copying publiforge/Static/Images/action_pipe.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,535 copying publiforge/Static/Images/action_progress_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,535 copying publiforge/Static/Images/action_remove.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,536 copying publiforge/Static/Images/action_remove_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,537 copying publiforge/Static/Images/action_rename_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,537 copying publiforge/Static/Images/action_render.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,538 copying publiforge/Static/Images/action_render_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,538 copying publiforge/Static/Images/action_reset_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,539 copying publiforge/Static/Images/action_save.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,540 copying publiforge/Static/Images/action_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,540 copying publiforge/Static/Images/action_select.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,541 copying publiforge/Static/Images/action_select_get.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,542 copying publiforge/Static/Images/action_select_get_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,543 copying publiforge/Static/Images/action_select_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,543 copying publiforge/Static/Images/action_start.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,544 copying publiforge/Static/Images/action_start_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,545 copying publiforge/Static/Images/action_stop.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,545 copying publiforge/Static/Images/action_stop_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,546 copying publiforge/Static/Images/action_synchronize.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,547 copying publiforge/Static/Images/action_synchronize_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,547 copying publiforge/Static/Images/action_take.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,548 copying publiforge/Static/Images/action_take_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,549 copying publiforge/Static/Images/action_up_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,550 copying publiforge/Static/Images/action_upload.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,550 copying publiforge/Static/Images/action_upload_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,551 copying publiforge/Static/Images/action_view.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,551 copying publiforge/Static/Images/action_view_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,552 copying publiforge/Static/Images/admin.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,553 copying publiforge/Static/Images/back.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,554 copying publiforge/Static/Images/breadcrumbs_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,554 copying publiforge/Static/Images/build.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,555 copying publiforge/Static/Images/build22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,556 copying publiforge/Static/Images/build32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,556 copying publiforge/Static/Images/build72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,557 copying publiforge/Static/Images/build72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,558 copying publiforge/Static/Images/build96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,558 copying publiforge/Static/Images/check.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,559 copying publiforge/Static/Images/close_dark.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,560 copying publiforge/Static/Images/close_light.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,560 copying publiforge/Static/Images/collapse_closed.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,561 copying publiforge/Static/Images/collapse_current_closed.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,562 copying publiforge/Static/Images/collapse_current_open.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,563 copying publiforge/Static/Images/collapse_open.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,563 copying publiforge/Static/Images/edit32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,564 copying publiforge/Static/Images/equal.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,565 copying publiforge/Static/Images/extractor.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,566 copying publiforge/Static/Images/extractor22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,566 copying publiforge/Static/Images/extractor32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,567 copying publiforge/Static/Images/flash_alert.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,568 copying publiforge/Static/Images/flash_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,568 copying publiforge/Static/Images/folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,569 copying publiforge/Static/Images/folder22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,570 copying publiforge/Static/Images/folder32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,570 copying publiforge/Static/Images/footer_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,571 copying publiforge/Static/Images/go_first.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,572 copying publiforge/Static/Images/go_last.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,572 copying publiforge/Static/Images/go_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,573 copying publiforge/Static/Images/go_next_file.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,574 copying publiforge/Static/Images/go_next_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,574 copying publiforge/Static/Images/go_previous.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,575 copying publiforge/Static/Images/go_previous_file.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,576 copying publiforge/Static/Images/go_previous_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,576 copying publiforge/Static/Images/go_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,577 copying publiforge/Static/Images/go_top22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,578 copying publiforge/Static/Images/group.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,578 copying publiforge/Static/Images/group22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,579 copying publiforge/Static/Images/group32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,580 copying publiforge/Static/Images/history.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,580 copying publiforge/Static/Images/history22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,581 copying publiforge/Static/Images/history32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,582 copying publiforge/Static/Images/in_menu_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,582 copying publiforge/Static/Images/in_menu_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,583 copying publiforge/Static/Images/indexer.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,584 copying publiforge/Static/Images/indexer22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,585 copying publiforge/Static/Images/indexer32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,585 copying publiforge/Static/Images/info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,586 copying publiforge/Static/Images/info22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,586 copying publiforge/Static/Images/info32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,587 copying publiforge/Static/Images/job.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,588 copying publiforge/Static/Images/job22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,589 copying publiforge/Static/Images/job32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,589 copying publiforge/Static/Images/left_background.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,590 copying publiforge/Static/Images/left_title.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,591 copying publiforge/Static/Images/light_green.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,591 copying publiforge/Static/Images/light_grey.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,592 copying publiforge/Static/Images/light_red.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,593 copying publiforge/Static/Images/light_yellow.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,593 copying publiforge/Static/Images/link.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,594 copying publiforge/Static/Images/link22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,595 copying publiforge/Static/Images/link32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,595 copying publiforge/Static/Images/list_header.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,596 copying publiforge/Static/Images/log_download.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,596 copying publiforge/Static/Images/log_error.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,597 copying publiforge/Static/Images/log_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,598 copying publiforge/Static/Images/log_warning.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,598 copying publiforge/Static/Images/login_bottom_center.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,599 copying publiforge/Static/Images/login_bottom_left.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,600 copying publiforge/Static/Images/login_bottom_right.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,601 copying publiforge/Static/Images/login_middle_left.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,601 copying publiforge/Static/Images/login_middle_right.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,602 copying publiforge/Static/Images/login_top_center.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,603 copying publiforge/Static/Images/login_top_left.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,603 copying publiforge/Static/Images/login_top_right.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,604 copying publiforge/Static/Images/logout.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,605 copying publiforge/Static/Images/notfound.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,606 copying publiforge/Static/Images/open_false.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,606 copying publiforge/Static/Images/open_true.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,607 copying publiforge/Static/Images/opener22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,608 copying publiforge/Static/Images/opener32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,608 copying publiforge/Static/Images/overview_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,609 copying publiforge/Static/Images/overview_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,610 copying publiforge/Static/Images/pack.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,610 copying publiforge/Static/Images/pack22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,611 copying publiforge/Static/Images/pack32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,612 copying publiforge/Static/Images/pack72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,612 copying publiforge/Static/Images/pack72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,613 copying publiforge/Static/Images/pack96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,614 copying publiforge/Static/Images/processing.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,614 copying publiforge/Static/Images/processing22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,615 copying publiforge/Static/Images/processing32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,616 copying publiforge/Static/Images/progress.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,616 copying publiforge/Static/Images/project.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,617 copying publiforge/Static/Images/project22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,618 copying publiforge/Static/Images/project32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,618 copying publiforge/Static/Images/publiforge.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,619 copying publiforge/Static/Images/pyramid.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,620 copying publiforge/Static/Images/role.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,620 copying publiforge/Static/Images/role22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,621 copying publiforge/Static/Images/role32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,622 copying publiforge/Static/Images/search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,622 copying publiforge/Static/Images/search22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,623 copying publiforge/Static/Images/search32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,624 copying publiforge/Static/Images/selection.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,624 copying publiforge/Static/Images/selection_remove_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,625 copying publiforge/Static/Images/selection_remove_sure.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,626 copying publiforge/Static/Images/sort_down.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,626 copying publiforge/Static/Images/sort_down_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,627 copying publiforge/Static/Images/sort_up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,628 copying publiforge/Static/Images/sort_up_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,628 copying publiforge/Static/Images/storage.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,629 copying publiforge/Static/Images/storage22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,630 copying publiforge/Static/Images/storage32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,630 copying publiforge/Static/Images/tab.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,631 copying publiforge/Static/Images/task.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,632 copying publiforge/Static/Images/task22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,632 copying publiforge/Static/Images/task32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,633 copying publiforge/Static/Images/task72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,634 copying publiforge/Static/Images/task72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,635 copying publiforge/Static/Images/task96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,635 copying publiforge/Static/Images/up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,636 copying publiforge/Static/Images/user.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,637 copying publiforge/Static/Images/user22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,638 copying publiforge/Static/Images/user32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,638 copying publiforge/Static/Images/user_pre.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,639 copying publiforge/Static/Images/valid-xhtml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,640 copying publiforge/Static/Images/value.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,640 copying publiforge/Static/Images/value22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,641 copying publiforge/Static/Images/value32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,642 copying publiforge/Static/Images/vcss.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,642 copying publiforge/Static/Images/wait_build.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,643 copying publiforge/Static/Images/wait_slow.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,644 copying publiforge/Static/Images/wait_synchro.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,644 copying publiforge/Static/Images/wcag1aa.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T03:53:10,645 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,645 copying publiforge/Static/Images/MimeTypes/css.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,646 copying publiforge/Static/Images/MimeTypes/csv.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,647 copying publiforge/Static/Images/MimeTypes/epub+zip.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,647 copying publiforge/Static/Images/MimeTypes/folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,648 copying publiforge/Static/Images/MimeTypes/font-woff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,649 copying publiforge/Static/Images/MimeTypes/gif.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,649 copying publiforge/Static/Images/MimeTypes/html.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,650 copying publiforge/Static/Images/MimeTypes/indesign-idml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,651 copying publiforge/Static/Images/MimeTypes/indesign-indd.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,651 copying publiforge/Static/Images/MimeTypes/javascript.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,652 copying publiforge/Static/Images/MimeTypes/jpeg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,653 copying publiforge/Static/Images/MimeTypes/mime.types -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,654 copying publiforge/Static/Images/MimeTypes/mp4.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,654 copying publiforge/Static/Images/MimeTypes/mpeg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,655 copying publiforge/Static/Images/MimeTypes/msword.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,656 copying publiforge/Static/Images/MimeTypes/octet-stream.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,656 copying publiforge/Static/Images/MimeTypes/ogg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,657 copying publiforge/Static/Images/MimeTypes/pdf.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,658 copying publiforge/Static/Images/MimeTypes/plain.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,658 copying publiforge/Static/Images/MimeTypes/png.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,659 copying publiforge/Static/Images/MimeTypes/postscript.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,660 copying publiforge/Static/Images/MimeTypes/relaxng.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,660 copying publiforge/Static/Images/MimeTypes/svg+xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,661 copying publiforge/Static/Images/MimeTypes/tiff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,662 copying publiforge/Static/Images/MimeTypes/unknown.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,662 copying publiforge/Static/Images/MimeTypes/vnd.ms-excel.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,663 copying publiforge/Static/Images/MimeTypes/vnd.ms-opentype.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,664 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.spreadsheet.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,664 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.text.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,665 copying publiforge/Static/Images/MimeTypes/x-msdos-program.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,666 copying publiforge/Static/Images/MimeTypes/x-msvideo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,666 copying publiforge/Static/Images/MimeTypes/x-python.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,667 copying publiforge/Static/Images/MimeTypes/x-shockwave-flash.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,668 copying publiforge/Static/Images/MimeTypes/x-tar.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,668 copying publiforge/Static/Images/MimeTypes/x-wav.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,669 copying publiforge/Static/Images/MimeTypes/xml-dtd.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,670 copying publiforge/Static/Images/MimeTypes/xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,670 copying publiforge/Static/Images/MimeTypes/zip.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T03:53:10,671 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,671 copying publiforge/Static/Js/base.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,672 copying publiforge/Static/Js/bld_progress.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,673 copying publiforge/Static/Js/bld_results.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,674 copying publiforge/Static/Js/bld_view.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,674 copying publiforge/Static/Js/codemirror.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,676 copying publiforge/Static/Js/codemirror4ini.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,676 copying publiforge/Static/Js/codemirror4xml.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,677 copying publiforge/Static/Js/codemirror_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,678 copying publiforge/Static/Js/jquery.cookie.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,678 copying publiforge/Static/Js/jquery.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,679 copying publiforge/Static/Js/prc_edit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,680 copying publiforge/Static/Js/stg_browse.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,681 copying publiforge/Static/Js/stg_edit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,681 copying publiforge/Static/Js/stg_index.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,682 copying publiforge/Static/Js/tsk_index.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T03:53:10,683 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T03:53:10,683 copying publiforge/Static/Js/Tests/index.html -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T03:53:10,684 copying publiforge/Static/Js/Tests/qunit.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T03:53:10,685 copying publiforge/Static/Js/Tests/qunit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T03:53:10,686 copying publiforge/Static/Js/Tests/tests.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T03:53:10,686 creating build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,687 copying publiforge/Templates/base.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,687 copying publiforge/Templates/bld_launch.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,688 copying publiforge/Templates/bld_output.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,689 copying publiforge/Templates/bld_pack.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,689 copying publiforge/Templates/bld_processing.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,690 copying publiforge/Templates/bld_progress.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,691 copying publiforge/Templates/bld_results.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,691 copying publiforge/Templates/bld_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,692 copying publiforge/Templates/error.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,693 copying publiforge/Templates/fil_display.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,693 copying publiforge/Templates/fil_info.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,694 copying publiforge/Templates/fil_modify.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,695 copying publiforge/Templates/fil_search.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,695 copying publiforge/Templates/fil_vcs_params.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,696 copying publiforge/Templates/files_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,697 copying publiforge/Templates/files_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,697 copying publiforge/Templates/flash.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,698 copying publiforge/Templates/grp_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,699 copying publiforge/Templates/grp_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,699 copying publiforge/Templates/grp_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,700 copying publiforge/Templates/home.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,701 copying publiforge/Templates/idx_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,701 copying publiforge/Templates/idx_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,702 copying publiforge/Templates/idx_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,703 copying publiforge/Templates/job_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,704 copying publiforge/Templates/job_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,704 copying publiforge/Templates/job_log.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,705 copying publiforge/Templates/job_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,706 copying publiforge/Templates/login.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,706 copying publiforge/Templates/mbr_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,707 copying publiforge/Templates/mbr_groups_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,708 copying publiforge/Templates/mbr_groups_paging.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,708 copying publiforge/Templates/mbr_groups_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,709 copying publiforge/Templates/mbr_paging.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,710 copying publiforge/Templates/mbr_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,710 copying publiforge/Templates/pck_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,711 copying publiforge/Templates/pck_events.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,712 copying publiforge/Templates/pck_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,712 copying publiforge/Templates/pck_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,713 copying publiforge/Templates/prc_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,714 copying publiforge/Templates/prc_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,714 copying publiforge/Templates/prj_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,715 copying publiforge/Templates/prj_dashboard.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,716 copying publiforge/Templates/prj_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,716 copying publiforge/Templates/prj_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,717 copying publiforge/Templates/prj_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,718 copying publiforge/Templates/rol_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,718 copying publiforge/Templates/rol_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,719 copying publiforge/Templates/sit_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,720 copying publiforge/Templates/stg_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,720 copying publiforge/Templates/stg_browse.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,721 copying publiforge/Templates/stg_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,722 copying publiforge/Templates/stg_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,723 copying publiforge/Templates/stg_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,724 copying publiforge/Templates/tsk_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,724 copying publiforge/Templates/tsk_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,725 copying publiforge/Templates/tsk_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,726 copying publiforge/Templates/usr_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,726 copying publiforge/Templates/usr_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,727 copying publiforge/Templates/usr_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T03:53:10,728 creating build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T03:53:10,728 copying publiforge/tests/Data/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T03:53:10,729 copying publiforge/tests/Data/test.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T03:53:10,729 copying publiforge/lib/rsync/_librsync.c -> build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T03:53:10,735 running build_ext 2025-09-08T03:53:11,090 building 'publiforge.lib.rsync._librsync' extension 2025-09-08T03:53:11,091 creating build/temp.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T03:53:11,091 arm-linux-gnueabihf-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -fPIC -I/usr/include/python3.13 -c publiforge/lib/rsync/_librsync.c -o build/temp.linux-armv7l-cpython-313/publiforge/lib/rsync/_librsync.o 2025-09-08T03:53:11,507 publiforge/lib/rsync/_librsync.c:27:10: fatal error: librsync.h: No such file or directory 2025-09-08T03:53:11,507 27 | #include 2025-09-08T03:53:11,507 | ^~~~~~~~~~~~ 2025-09-08T03:53:11,507 compilation terminated. 2025-09-08T03:53:11,512 error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1 2025-09-08T03:53:11,685 ERROR: python setup.py bdist_wheel exited with 1 2025-09-08T03:53:11,698 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2025-09-08T03:53:11,698 exec(compile('"'"''"'"''"'"' 2025-09-08T03:53:11,698 # This is -- a caller that pip uses to run setup.py 2025-09-08T03:53:11,698 # 2025-09-08T03:53:11,698 # - It imports setuptools before invoking setup.py, to enable projects that directly 2025-09-08T03:53:11,698 # import from `distutils.core` to work with newer packaging standards. 2025-09-08T03:53:11,698 # - It provides a clear error message when setuptools is not installed. 2025-09-08T03:53:11,698 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2025-09-08T03:53:11,698 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2025-09-08T03:53:11,698 # manifest_maker: standard file '"'"'-c'"'"' not found". 2025-09-08T03:53:11,698 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2025-09-08T03:53:11,698 import os, sys, tokenize, traceback 2025-09-08T03:53:11,698 2025-09-08T03:53:11,698 try: 2025-09-08T03:53:11,698 import setuptools 2025-09-08T03:53:11,698 except ImportError: 2025-09-08T03:53:11,698 print( 2025-09-08T03:53:11,698 "ERROR: Can not execute `setup.py` since setuptools failed to import in " 2025-09-08T03:53:11,698 "the build environment with exception:", 2025-09-08T03:53:11,698 file=sys.stderr, 2025-09-08T03:53:11,698 ) 2025-09-08T03:53:11,698 traceback.print_exc() 2025-09-08T03:53:11,698 sys.exit(1) 2025-09-08T03:53:11,698 2025-09-08T03:53:11,698 __file__ = %r 2025-09-08T03:53:11,698 sys.argv[0] = __file__ 2025-09-08T03:53:11,698 2025-09-08T03:53:11,698 if os.path.exists(__file__): 2025-09-08T03:53:11,698 filename = __file__ 2025-09-08T03:53:11,698 with tokenize.open(__file__) as f: 2025-09-08T03:53:11,698 setup_py_code = f.read() 2025-09-08T03:53:11,698 else: 2025-09-08T03:53:11,698 filename = "" 2025-09-08T03:53:11,698 setup_py_code = "from setuptools import setup; setup()" 2025-09-08T03:53:11,698 2025-09-08T03:53:11,698 exec(compile(setup_py_code, filename, "exec")) 2025-09-08T03:53:11,698 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-tbnnfhqc/publiforge_e8b0ae6b644e4753866f56d87c188b85/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-bzgbjj84[/] 2025-09-08T03:53:11,699 [bold magenta]cwd[/]: /tmp/pip-wheel-tbnnfhqc/publiforge_e8b0ae6b644e4753866f56d87c188b85/ 2025-09-08T03:53:11,699 Building wheel for publiforge (setup.py): finished with status 'error' 2025-09-08T03:53:11,700 ERROR: Failed building wheel for publiforge 2025-09-08T03:53:11,701 Running setup.py clean for publiforge 2025-09-08T03:53:11,701 Running command python setup.py clean 2025-09-08T03:53:12,508 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T03:53:12,508 warnings.warn(msg) 2025-09-08T03:53:12,508 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T03:53:12,509 warnings.warn(msg) 2025-09-08T03:53:13,057 running clean 2025-09-08T03:53:13,236 removing 'build/temp.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T03:53:13,236 removing 'build/lib.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T03:53:13,277 'build/bdist.linux-armv7l' does not exist -- can't clean it 2025-09-08T03:53:13,277 'build/scripts-3.13' does not exist -- can't clean it 2025-09-08T03:53:13,277 removing 'build' 2025-09-08T03:53:13,408 Failed to build publiforge 2025-09-08T03:53:13,409 ERROR: Failed to build one or more wheels 2025-09-08T03:53:13,410 Exception information: 2025-09-08T03:53:13,410 Traceback (most recent call last): 2025-09-08T03:53:13,410 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper 2025-09-08T03:53:13,410 status = _inner_run() 2025-09-08T03:53:13,410 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run 2025-09-08T03:53:13,410 return self.run(options, args) 2025-09-08T03:53:13,410 ~~~~~~~~^^^^^^^^^^^^^^^ 2025-09-08T03:53:13,410 File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 68, in wrapper 2025-09-08T03:53:13,410 return func(self, options, args) 2025-09-08T03:53:13,410 File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line 180, in run 2025-09-08T03:53:13,410 raise CommandError("Failed to build one or more wheels") 2025-09-08T03:53:13,410 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2025-09-08T03:53:13,415 Removed build tracker: '/tmp/pip-build-tracker-0ixscde0'