2025-09-08T11:43:15,823 Created temporary directory: /tmp/pip-build-tracker-sibx89z2 2025-09-08T11:43:15,823 Initialized build tracking at /tmp/pip-build-tracker-sibx89z2 2025-09-08T11:43:15,824 Created build tracker: /tmp/pip-build-tracker-sibx89z2 2025-09-08T11:43:15,824 Entered build tracker: /tmp/pip-build-tracker-sibx89z2 2025-09-08T11:43:15,824 Created temporary directory: /tmp/pip-wheel-jzt_t531 2025-09-08T11:43:15,827 Created temporary directory: /tmp/pip-ephem-wheel-cache-gzhzecrd 2025-09-08T11:43:15,885 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-09-08T11:43:15,887 2 location(s) to search for versions of publiforge: 2025-09-08T11:43:15,887 * https://pypi.org/simple/publiforge/ 2025-09-08T11:43:15,887 * https://www.piwheels.org/simple/publiforge/ 2025-09-08T11:43:15,887 Fetching project page and analyzing links: https://pypi.org/simple/publiforge/ 2025-09-08T11:43:15,888 Getting page https://pypi.org/simple/publiforge/ 2025-09-08T11:43:15,889 Found index url https://pypi.org/simple/ 2025-09-08T11:43:15,959 Fetched page https://pypi.org/simple/publiforge/ as application/vnd.pypi.simple.v1+json 2025-09-08T11:43:15,960 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-08T11:43:15,960 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-08T11:43:15,961 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-08T11:43:15,961 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-08T11:43:15,961 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-08T11:43:15,961 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-08T11:43:15,961 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-08T11:43:15,962 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-08T11:43:15,962 Fetching project page and analyzing links: https://www.piwheels.org/simple/publiforge/ 2025-09-08T11:43:15,962 Getting page https://www.piwheels.org/simple/publiforge/ 2025-09-08T11:43:15,963 Found index url https://www.piwheels.org/simple/ 2025-09-08T11:43:16,047 Fetched page https://www.piwheels.org/simple/publiforge/ as text/html 2025-09-08T11:43:16,048 Skipping link: not a file: https://www.piwheels.org/simple/publiforge/ 2025-09-08T11:43:16,048 Skipping link: not a file: https://pypi.org/simple/publiforge/ 2025-09-08T11:43:16,077 Given no hashes to check 1 links for project 'publiforge': discarding no candidates 2025-09-08T11:43:16,079 Collecting publiforge==2.2 2025-09-08T11:43:16,080 Created temporary directory: /tmp/pip-unpack-5ondspm5 2025-09-08T11:43:16,326 Downloading PubliForge-2.2.tar.gz (10.3 MB) 2025-09-08T11:43:18,797 Added publiforge==2.2 from https://files.pythonhosted.org/packages/bd/9c/0d22a6f3cc43369284069985bacff0a2eaf355421b58bc6721ac572b2764/PubliForge-2.2.tar.gz to build tracker '/tmp/pip-build-tracker-sibx89z2' 2025-09-08T11:43:18,798 Running setup.py (path:/tmp/pip-wheel-jzt_t531/publiforge_d2f1bfa7cced42f296db77a69aa94351/setup.py) egg_info for package publiforge 2025-09-08T11:43:18,799 Created temporary directory: /tmp/pip-pip-egg-info-sgxlspp9 2025-09-08T11:43:18,799 Preparing metadata (setup.py): started 2025-09-08T11:43:18,800 Running command python setup.py egg_info 2025-09-08T11:43:19,462 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T11:43:19,462 warnings.warn(msg) 2025-09-08T11:43:19,462 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T11:43:19,463 warnings.warn(msg) 2025-09-08T11:43:19,717 running egg_info 2025-09-08T11:43:19,785 creating /tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info 2025-09-08T11:43:19,785 writing /tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info/PKG-INFO 2025-09-08T11:43:19,791 writing dependency_links to /tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info/dependency_links.txt 2025-09-08T11:43:19,792 writing entry points to /tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info/entry_points.txt 2025-09-08T11:43:19,795 writing requirements to /tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info/requires.txt 2025-09-08T11:43:19,795 writing top-level names to /tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info/top_level.txt 2025-09-08T11:43:19,796 writing manifest file '/tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info/SOURCES.txt' 2025-09-08T11:43:20,254 reading manifest file '/tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info/SOURCES.txt' 2025-09-08T11:43:20,255 reading manifest template 'MANIFEST.in' 2025-09-08T11:43:20,256 warning: no files found matching '*.rst' 2025-09-08T11:43:20,551 warning: no files found matching '*.jinja2' under directory 'publiforge' 2025-09-08T11:43:20,696 warning: no files found matching '*.mak' under directory 'publiforge' 2025-09-08T11:43:20,744 warning: no files found matching '*.mako' under directory 'publiforge' 2025-09-08T11:43:20,995 warning: no files found matching '*.conf' under directory 'publiforge' 2025-09-08T11:43:21,112 writing manifest file '/tmp/pip-pip-egg-info-sgxlspp9/PubliForge.egg-info/SOURCES.txt' 2025-09-08T11:43:21,223 Preparing metadata (setup.py): finished with status 'done' 2025-09-08T11:43:21,228 Source in /tmp/pip-wheel-jzt_t531/publiforge_d2f1bfa7cced42f296db77a69aa94351 has version 2.2, which satisfies requirement publiforge==2.2 from https://files.pythonhosted.org/packages/bd/9c/0d22a6f3cc43369284069985bacff0a2eaf355421b58bc6721ac572b2764/PubliForge-2.2.tar.gz 2025-09-08T11:43:21,228 Removed publiforge==2.2 from https://files.pythonhosted.org/packages/bd/9c/0d22a6f3cc43369284069985bacff0a2eaf355421b58bc6721ac572b2764/PubliForge-2.2.tar.gz from build tracker '/tmp/pip-build-tracker-sibx89z2' 2025-09-08T11:43:21,242 Created temporary directory: /tmp/pip-unpack-l_etufnb 2025-09-08T11:43:21,243 Created temporary directory: /tmp/pip-unpack-kqu6fovi 2025-09-08T11:43:21,243 Building wheels for collected packages: publiforge 2025-09-08T11:43:21,244 Created temporary directory: /tmp/pip-wheel-1emjt0az 2025-09-08T11:43:21,244 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-08T11:43:21,245 Building wheel for publiforge (setup.py): started 2025-09-08T11:43:21,246 Destination directory: /tmp/pip-wheel-1emjt0az 2025-09-08T11:43:21,246 Running command python setup.py bdist_wheel 2025-09-08T11:43:21,915 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T11:43:21,915 warnings.warn(msg) 2025-09-08T11:43:21,915 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T11:43:21,915 warnings.warn(msg) 2025-09-08T11:43:22,102 running bdist_wheel 2025-09-08T11:43:22,615 running build 2025-09-08T11:43:22,615 running build_py 2025-09-08T11:43:22,684 creating build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T11:43:22,684 copying publiforge/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T11:43:22,685 copying publiforge/initialize.py -> build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T11:43:22,686 creating build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,686 copying publiforge/scripts/pfminify.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,687 copying publiforge/scripts/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,687 copying publiforge/scripts/pftexmath.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,688 copying publiforge/scripts/pfimage2svg.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,688 copying publiforge/scripts/pfpopulate.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,689 copying publiforge/scripts/pfbackup.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,689 copying publiforge/scripts/pfbuild.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,690 copying publiforge/scripts/pfscheduler.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T11:43:22,691 creating build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,691 copying publiforge/tests/test_models_projects.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,692 copying publiforge/tests/test_lib_form.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,692 copying publiforge/tests/test_lib_menu.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,693 copying publiforge/tests/test_views_security.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,693 copying publiforge/tests/test_lib_config.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,694 copying publiforge/tests/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,694 copying publiforge/tests/test_models_users.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,695 copying publiforge/tests/test_models_processors.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,695 copying publiforge/tests/test_lib_i18n.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,696 copying publiforge/tests/test_models_storages.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,697 copying publiforge/tests/test_scripts_pfbuild.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,697 copying publiforge/tests/test_models_groups.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,698 copying publiforge/tests/test_lib_utils.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,698 copying publiforge/tests/test_views_project.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,699 copying publiforge/tests/test_lib_xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:22,700 creating build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,700 copying publiforge/models/processings.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,700 copying publiforge/models/packs.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,701 copying publiforge/models/jobs.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,701 copying publiforge/models/storages.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,702 copying publiforge/models/projects.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,703 copying publiforge/models/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,703 copying publiforge/models/users.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,704 copying publiforge/models/roles.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,704 copying publiforge/models/indexers.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,705 copying publiforge/models/tasks.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,705 copying publiforge/models/processors.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,706 copying publiforge/models/groups.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T11:43:22,707 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds 2025-09-08T11:43:22,707 copying publiforge/scaffolds/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds 2025-09-08T11:43:22,708 creating build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,708 copying publiforge/views/home.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,709 copying publiforge/views/job.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,709 copying publiforge/views/site.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,710 copying publiforge/views/file.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,710 copying publiforge/views/xmlrpc.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,711 copying publiforge/views/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,712 copying publiforge/views/processing.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,712 copying publiforge/views/group.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,713 copying publiforge/views/maintenance.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,713 copying publiforge/views/task.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,714 copying publiforge/views/indexer.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,714 copying publiforge/views/security.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,715 copying publiforge/views/user.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,716 copying publiforge/views/pack.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,716 copying publiforge/views/storage.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,717 copying publiforge/views/build.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,717 copying publiforge/views/maestro.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,718 copying publiforge/views/project.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,719 copying publiforge/views/selection.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,719 copying publiforge/views/role.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T11:43:22,720 creating build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,721 copying publiforge/lib/breadcrumbs.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,721 copying publiforge/lib/filter.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,722 copying publiforge/lib/viewutils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,722 copying publiforge/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,723 copying publiforge/lib/menu.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,723 copying publiforge/lib/xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,724 copying publiforge/lib/debug.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,725 copying publiforge/lib/paging.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,725 copying publiforge/lib/config.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,726 copying publiforge/lib/tabset.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,726 copying publiforge/lib/i18n.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,727 copying publiforge/lib/utils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,727 copying publiforge/lib/form.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,728 copying publiforge/lib/handler.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,729 copying publiforge/lib/log.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,729 copying publiforge/lib/packutils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T11:43:22,730 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T11:43:22,730 copying publiforge/lib/build/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T11:43:22,731 copying publiforge/lib/build/front.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T11:43:22,731 copying publiforge/lib/build/agent.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T11:43:22,732 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T11:43:22,733 copying publiforge/lib/rsync/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T11:43:22,733 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor 2025-09-08T11:43:22,734 copying publiforge/lib/processor/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor 2025-09-08T11:43:22,734 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T11:43:22,735 copying publiforge/lib/vcs/hg.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T11:43:22,735 copying publiforge/lib/vcs/hgsvn.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T11:43:22,736 copying publiforge/lib/vcs/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T11:43:22,736 copying publiforge/lib/vcs/svn.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T11:43:22,737 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T11:43:22,737 copying publiforge/lib/opener/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T11:43:22,738 copying publiforge/lib/opener/image.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T11:43:22,739 copying publiforge/lib/opener/ini.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T11:43:22,739 copying publiforge/lib/opener/xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T11:43:22,740 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T11:43:22,740 copying publiforge/lib/processor/leprisme/transform.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T11:43:22,741 copying publiforge/lib/processor/leprisme/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T11:43:22,742 copying publiforge/lib/processor/leprisme/publiset.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T11:43:22,742 copying publiforge/lib/processor/leprisme/containers.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T11:43:22,743 copying publiforge/lib/processor/leprisme/iniscript.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T11:43:22,744 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/publiseter 2025-09-08T11:43:22,744 copying publiforge/lib/processor/publiseter/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/publiseter 2025-09-08T11:43:22,745 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/generator 2025-09-08T11:43:22,745 copying publiforge/lib/processor/generator/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/generator 2025-09-08T11:43:22,746 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/validator 2025-09-08T11:43:22,746 copying publiforge/lib/processor/validator/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/validator 2025-09-08T11:43:22,746 running egg_info 2025-09-08T11:43:22,812 writing PubliForge.egg-info/PKG-INFO 2025-09-08T11:43:22,818 writing dependency_links to PubliForge.egg-info/dependency_links.txt 2025-09-08T11:43:22,819 writing entry points to PubliForge.egg-info/entry_points.txt 2025-09-08T11:43:22,822 writing requirements to PubliForge.egg-info/requires.txt 2025-09-08T11:43:22,822 writing top-level names to PubliForge.egg-info/top_level.txt 2025-09-08T11:43:22,898 reading manifest file 'PubliForge.egg-info/SOURCES.txt' 2025-09-08T11:43:22,945 reading manifest template 'MANIFEST.in' 2025-09-08T11:43:22,946 warning: no files found matching '*.rst' 2025-09-08T11:43:23,238 warning: no files found matching '*.jinja2' under directory 'publiforge' 2025-09-08T11:43:23,383 warning: no files found matching '*.mak' under directory 'publiforge' 2025-09-08T11:43:23,431 warning: no files found matching '*.mako' under directory 'publiforge' 2025-09-08T11:43:23,675 warning: no files found matching '*.conf' under directory 'publiforge' 2025-09-08T11:43:23,803 writing manifest file 'PubliForge.egg-info/SOURCES.txt' 2025-09-08T11:43:23,804 /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-08T11:43:23,805 !! 2025-09-08T11:43:23,805 ******************************************************************************** 2025-09-08T11:43:23,805 ############################ 2025-09-08T11:43:23,805 # Package would be ignored # 2025-09-08T11:43:23,805 ############################ 2025-09-08T11:43:23,805 Python recognizes 'publiforge.Locale' as an importable package[^1], 2025-09-08T11:43:23,805 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,805 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,805 package, please make sure that 'publiforge.Locale' is explicitly added 2025-09-08T11:43:23,806 to the `packages` configuration field. 2025-09-08T11:43:23,806 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,806 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,806 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,806 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,806 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,806 If you don't want 'publiforge.Locale' to be distributed and are 2025-09-08T11:43:23,807 already explicitly excluding 'publiforge.Locale' via 2025-09-08T11:43:23,807 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,807 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,807 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,807 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,807 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,808 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,808 even if it does not contain any `.py` files. 2025-09-08T11:43:23,808 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,808 directory, all directories are treated like packages. 2025-09-08T11:43:23,808 ******************************************************************************** 2025-09-08T11:43:23,808 !! 2025-09-08T11:43:23,808 check.warn(importable) 2025-09-08T11:43:23,808 /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-08T11:43:23,808 !! 2025-09-08T11:43:23,809 ******************************************************************************** 2025-09-08T11:43:23,809 ############################ 2025-09-08T11:43:23,809 # Package would be ignored # 2025-09-08T11:43:23,809 ############################ 2025-09-08T11:43:23,809 Python recognizes 'publiforge.Locale.es.LC_MESSAGES' as an importable package[^1], 2025-09-08T11:43:23,809 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,809 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,809 package, please make sure that 'publiforge.Locale.es.LC_MESSAGES' is explicitly added 2025-09-08T11:43:23,809 to the `packages` configuration field. 2025-09-08T11:43:23,809 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,810 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,810 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,810 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,810 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,810 If you don't want 'publiforge.Locale.es.LC_MESSAGES' to be distributed and are 2025-09-08T11:43:23,810 already explicitly excluding 'publiforge.Locale.es.LC_MESSAGES' via 2025-09-08T11:43:23,810 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,810 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,811 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,811 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,811 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,811 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,811 even if it does not contain any `.py` files. 2025-09-08T11:43:23,811 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,811 directory, all directories are treated like packages. 2025-09-08T11:43:23,811 ******************************************************************************** 2025-09-08T11:43:23,812 !! 2025-09-08T11:43:23,812 check.warn(importable) 2025-09-08T11:43:23,812 /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-08T11:43:23,812 !! 2025-09-08T11:43:23,812 ******************************************************************************** 2025-09-08T11:43:23,812 ############################ 2025-09-08T11:43:23,812 # Package would be ignored # 2025-09-08T11:43:23,812 ############################ 2025-09-08T11:43:23,812 Python recognizes 'publiforge.Locale.fr.LC_MESSAGES' as an importable package[^1], 2025-09-08T11:43:23,813 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,813 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,813 package, please make sure that 'publiforge.Locale.fr.LC_MESSAGES' is explicitly added 2025-09-08T11:43:23,813 to the `packages` configuration field. 2025-09-08T11:43:23,813 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,813 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,813 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,813 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,814 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,814 If you don't want 'publiforge.Locale.fr.LC_MESSAGES' to be distributed and are 2025-09-08T11:43:23,814 already explicitly excluding 'publiforge.Locale.fr.LC_MESSAGES' via 2025-09-08T11:43:23,814 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,814 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,814 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,814 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,814 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,815 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,815 even if it does not contain any `.py` files. 2025-09-08T11:43:23,815 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,815 directory, all directories are treated like packages. 2025-09-08T11:43:23,815 ******************************************************************************** 2025-09-08T11:43:23,815 !! 2025-09-08T11:43:23,815 check.warn(importable) 2025-09-08T11:43:23,815 /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-08T11:43:23,815 !! 2025-09-08T11:43:23,816 ******************************************************************************** 2025-09-08T11:43:23,816 ############################ 2025-09-08T11:43:23,816 # Package would be ignored # 2025-09-08T11:43:23,816 ############################ 2025-09-08T11:43:23,816 Python recognizes 'publiforge.Openers.Image' as an importable package[^1], 2025-09-08T11:43:23,816 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,816 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,816 package, please make sure that 'publiforge.Openers.Image' is explicitly added 2025-09-08T11:43:23,816 to the `packages` configuration field. 2025-09-08T11:43:23,816 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,817 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,817 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,817 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,817 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,817 If you don't want 'publiforge.Openers.Image' to be distributed and are 2025-09-08T11:43:23,817 already explicitly excluding 'publiforge.Openers.Image' via 2025-09-08T11:43:23,817 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,817 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,817 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,818 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,818 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,818 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,818 even if it does not contain any `.py` files. 2025-09-08T11:43:23,818 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,818 directory, all directories are treated like packages. 2025-09-08T11:43:23,818 ******************************************************************************** 2025-09-08T11:43:23,819 !! 2025-09-08T11:43:23,819 check.warn(importable) 2025-09-08T11:43:23,819 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.ImageEdit' is absent from the `packages` configuration. 2025-09-08T11:43:23,819 !! 2025-09-08T11:43:23,819 ******************************************************************************** 2025-09-08T11:43:23,819 ############################ 2025-09-08T11:43:23,819 # Package would be ignored # 2025-09-08T11:43:23,819 ############################ 2025-09-08T11:43:23,819 Python recognizes 'publiforge.Openers.ImageEdit' as an importable package[^1], 2025-09-08T11:43:23,819 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,820 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,820 package, please make sure that 'publiforge.Openers.ImageEdit' is explicitly added 2025-09-08T11:43:23,820 to the `packages` configuration field. 2025-09-08T11:43:23,820 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,820 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,820 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,820 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,820 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,820 If you don't want 'publiforge.Openers.ImageEdit' to be distributed and are 2025-09-08T11:43:23,821 already explicitly excluding 'publiforge.Openers.ImageEdit' via 2025-09-08T11:43:23,821 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,821 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,821 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,821 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,821 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,821 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,821 even if it does not contain any `.py` files. 2025-09-08T11:43:23,822 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,822 directory, all directories are treated like packages. 2025-09-08T11:43:23,822 ******************************************************************************** 2025-09-08T11:43:23,822 !! 2025-09-08T11:43:23,822 check.warn(importable) 2025-09-08T11:43:23,822 /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-08T11:43:23,822 !! 2025-09-08T11:43:23,822 ******************************************************************************** 2025-09-08T11:43:23,823 ############################ 2025-09-08T11:43:23,823 # Package would be ignored # 2025-09-08T11:43:23,823 ############################ 2025-09-08T11:43:23,823 Python recognizes 'publiforge.Openers.Ini' as an importable package[^1], 2025-09-08T11:43:23,823 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,823 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,823 package, please make sure that 'publiforge.Openers.Ini' is explicitly added 2025-09-08T11:43:23,823 to the `packages` configuration field. 2025-09-08T11:43:23,823 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,823 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,824 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,824 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,824 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,824 If you don't want 'publiforge.Openers.Ini' to be distributed and are 2025-09-08T11:43:23,824 already explicitly excluding 'publiforge.Openers.Ini' via 2025-09-08T11:43:23,824 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,824 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,824 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,825 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,825 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,825 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,825 even if it does not contain any `.py` files. 2025-09-08T11:43:23,825 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,825 directory, all directories are treated like packages. 2025-09-08T11:43:23,825 ******************************************************************************** 2025-09-08T11:43:23,825 !! 2025-09-08T11:43:23,825 check.warn(importable) 2025-09-08T11:43:23,826 /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-08T11:43:23,826 !! 2025-09-08T11:43:23,826 ******************************************************************************** 2025-09-08T11:43:23,826 ############################ 2025-09-08T11:43:23,826 # Package would be ignored # 2025-09-08T11:43:23,826 ############################ 2025-09-08T11:43:23,826 Python recognizes 'publiforge.Openers.NoMore' as an importable package[^1], 2025-09-08T11:43:23,826 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,826 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,826 package, please make sure that 'publiforge.Openers.NoMore' is explicitly added 2025-09-08T11:43:23,827 to the `packages` configuration field. 2025-09-08T11:43:23,827 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,827 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,827 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,827 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,827 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,827 If you don't want 'publiforge.Openers.NoMore' to be distributed and are 2025-09-08T11:43:23,827 already explicitly excluding 'publiforge.Openers.NoMore' via 2025-09-08T11:43:23,828 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,828 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,828 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,828 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,828 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,828 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,828 even if it does not contain any `.py` files. 2025-09-08T11:43:23,828 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,829 directory, all directories are treated like packages. 2025-09-08T11:43:23,829 ******************************************************************************** 2025-09-08T11:43:23,829 !! 2025-09-08T11:43:23,829 check.warn(importable) 2025-09-08T11:43:23,829 /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-08T11:43:23,829 !! 2025-09-08T11:43:23,829 ******************************************************************************** 2025-09-08T11:43:23,829 ############################ 2025-09-08T11:43:23,829 # Package would be ignored # 2025-09-08T11:43:23,829 ############################ 2025-09-08T11:43:23,829 Python recognizes 'publiforge.Openers.Plain' as an importable package[^1], 2025-09-08T11:43:23,830 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,830 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,830 package, please make sure that 'publiforge.Openers.Plain' is explicitly added 2025-09-08T11:43:23,830 to the `packages` configuration field. 2025-09-08T11:43:23,830 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,830 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,830 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,830 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,831 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,831 If you don't want 'publiforge.Openers.Plain' to be distributed and are 2025-09-08T11:43:23,831 already explicitly excluding 'publiforge.Openers.Plain' via 2025-09-08T11:43:23,831 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,831 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,831 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,831 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,831 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,832 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,832 even if it does not contain any `.py` files. 2025-09-08T11:43:23,832 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,832 directory, all directories are treated like packages. 2025-09-08T11:43:23,832 ******************************************************************************** 2025-09-08T11:43:23,832 !! 2025-09-08T11:43:23,832 check.warn(importable) 2025-09-08T11:43:23,832 /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-08T11:43:23,832 !! 2025-09-08T11:43:23,833 ******************************************************************************** 2025-09-08T11:43:23,833 ############################ 2025-09-08T11:43:23,833 # Package would be ignored # 2025-09-08T11:43:23,833 ############################ 2025-09-08T11:43:23,833 Python recognizes 'publiforge.Openers.Publidoc' as an importable package[^1], 2025-09-08T11:43:23,833 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,833 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,833 package, please make sure that 'publiforge.Openers.Publidoc' is explicitly added 2025-09-08T11:43:23,833 to the `packages` configuration field. 2025-09-08T11:43:23,833 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,833 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,834 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,834 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,834 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,834 If you don't want 'publiforge.Openers.Publidoc' to be distributed and are 2025-09-08T11:43:23,834 already explicitly excluding 'publiforge.Openers.Publidoc' via 2025-09-08T11:43:23,834 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,834 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,834 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,835 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,835 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,835 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,835 even if it does not contain any `.py` files. 2025-09-08T11:43:23,835 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,835 directory, all directories are treated like packages. 2025-09-08T11:43:23,835 ******************************************************************************** 2025-09-08T11:43:23,836 !! 2025-09-08T11:43:23,836 check.warn(importable) 2025-09-08T11:43:23,836 /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-08T11:43:23,836 !! 2025-09-08T11:43:23,836 ******************************************************************************** 2025-09-08T11:43:23,836 ############################ 2025-09-08T11:43:23,836 # Package would be ignored # 2025-09-08T11:43:23,836 ############################ 2025-09-08T11:43:23,836 Python recognizes 'publiforge.Openers.Publidoc.Maestro' as an importable package[^1], 2025-09-08T11:43:23,836 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,837 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,837 package, please make sure that 'publiforge.Openers.Publidoc.Maestro' is explicitly added 2025-09-08T11:43:23,837 to the `packages` configuration field. 2025-09-08T11:43:23,837 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,837 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,837 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,837 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,837 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,838 If you don't want 'publiforge.Openers.Publidoc.Maestro' to be distributed and are 2025-09-08T11:43:23,838 already explicitly excluding 'publiforge.Openers.Publidoc.Maestro' via 2025-09-08T11:43:23,838 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,838 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,838 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,838 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,838 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,838 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,839 even if it does not contain any `.py` files. 2025-09-08T11:43:23,839 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,839 directory, all directories are treated like packages. 2025-09-08T11:43:23,839 ******************************************************************************** 2025-09-08T11:43:23,839 !! 2025-09-08T11:43:23,839 check.warn(importable) 2025-09-08T11:43:23,839 /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-08T11:43:23,839 !! 2025-09-08T11:43:23,839 ******************************************************************************** 2025-09-08T11:43:23,839 ############################ 2025-09-08T11:43:23,840 # Package would be ignored # 2025-09-08T11:43:23,840 ############################ 2025-09-08T11:43:23,840 Python recognizes 'publiforge.Openers.Publidoc.Regex' as an importable package[^1], 2025-09-08T11:43:23,840 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,840 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,840 package, please make sure that 'publiforge.Openers.Publidoc.Regex' is explicitly added 2025-09-08T11:43:23,840 to the `packages` configuration field. 2025-09-08T11:43:23,840 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,840 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,840 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,841 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,841 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,841 If you don't want 'publiforge.Openers.Publidoc.Regex' to be distributed and are 2025-09-08T11:43:23,841 already explicitly excluding 'publiforge.Openers.Publidoc.Regex' via 2025-09-08T11:43:23,841 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,841 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,841 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,841 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,842 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,842 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,842 even if it does not contain any `.py` files. 2025-09-08T11:43:23,842 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,842 directory, all directories are treated like packages. 2025-09-08T11:43:23,842 ******************************************************************************** 2025-09-08T11:43:23,842 !! 2025-09-08T11:43:23,842 check.warn(importable) 2025-09-08T11:43:23,842 /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-08T11:43:23,843 !! 2025-09-08T11:43:23,843 ******************************************************************************** 2025-09-08T11:43:23,843 ############################ 2025-09-08T11:43:23,843 # Package would be ignored # 2025-09-08T11:43:23,843 ############################ 2025-09-08T11:43:23,843 Python recognizes 'publiforge.Openers.Publidoc.Seeds' as an importable package[^1], 2025-09-08T11:43:23,843 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,843 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,843 package, please make sure that 'publiforge.Openers.Publidoc.Seeds' is explicitly added 2025-09-08T11:43:23,843 to the `packages` configuration field. 2025-09-08T11:43:23,844 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,844 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,844 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,844 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,844 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,844 If you don't want 'publiforge.Openers.Publidoc.Seeds' to be distributed and are 2025-09-08T11:43:23,844 already explicitly excluding 'publiforge.Openers.Publidoc.Seeds' via 2025-09-08T11:43:23,844 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,845 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,845 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,845 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,845 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,845 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,845 even if it does not contain any `.py` files. 2025-09-08T11:43:23,845 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,845 directory, all directories are treated like packages. 2025-09-08T11:43:23,845 ******************************************************************************** 2025-09-08T11:43:23,846 !! 2025-09-08T11:43:23,846 check.warn(importable) 2025-09-08T11:43:23,846 /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-08T11:43:23,846 !! 2025-09-08T11:43:23,846 ******************************************************************************** 2025-09-08T11:43:23,846 ############################ 2025-09-08T11:43:23,846 # Package would be ignored # 2025-09-08T11:43:23,846 ############################ 2025-09-08T11:43:23,846 Python recognizes 'publiforge.Openers.Publidoc.Static.Css' as an importable package[^1], 2025-09-08T11:43:23,846 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,847 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,847 package, please make sure that 'publiforge.Openers.Publidoc.Static.Css' is explicitly added 2025-09-08T11:43:23,847 to the `packages` configuration field. 2025-09-08T11:43:23,847 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,847 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,847 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,847 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,847 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,848 If you don't want 'publiforge.Openers.Publidoc.Static.Css' to be distributed and are 2025-09-08T11:43:23,848 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Css' via 2025-09-08T11:43:23,848 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,848 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,848 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,848 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,848 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,849 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,849 even if it does not contain any `.py` files. 2025-09-08T11:43:23,849 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,849 directory, all directories are treated like packages. 2025-09-08T11:43:23,849 ******************************************************************************** 2025-09-08T11:43:23,849 !! 2025-09-08T11:43:23,849 check.warn(importable) 2025-09-08T11:43:23,849 /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-08T11:43:23,849 !! 2025-09-08T11:43:23,850 ******************************************************************************** 2025-09-08T11:43:23,850 ############################ 2025-09-08T11:43:23,850 # Package would be ignored # 2025-09-08T11:43:23,850 ############################ 2025-09-08T11:43:23,850 Python recognizes 'publiforge.Openers.Publidoc.Static.Js' as an importable package[^1], 2025-09-08T11:43:23,850 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,850 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,850 package, please make sure that 'publiforge.Openers.Publidoc.Static.Js' is explicitly added 2025-09-08T11:43:23,850 to the `packages` configuration field. 2025-09-08T11:43:23,850 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,851 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,851 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,851 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,851 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,851 If you don't want 'publiforge.Openers.Publidoc.Static.Js' to be distributed and are 2025-09-08T11:43:23,851 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Js' via 2025-09-08T11:43:23,851 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,851 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,851 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,852 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,852 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,852 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,852 even if it does not contain any `.py` files. 2025-09-08T11:43:23,852 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,852 directory, all directories are treated like packages. 2025-09-08T11:43:23,852 ******************************************************************************** 2025-09-08T11:43:23,852 !! 2025-09-08T11:43:23,853 check.warn(importable) 2025-09-08T11:43:23,853 /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-08T11:43:23,853 !! 2025-09-08T11:43:23,853 ******************************************************************************** 2025-09-08T11:43:23,853 ############################ 2025-09-08T11:43:23,853 # Package would be ignored # 2025-09-08T11:43:23,853 ############################ 2025-09-08T11:43:23,853 Python recognizes 'publiforge.Openers.Publidoc.Variables' as an importable package[^1], 2025-09-08T11:43:23,853 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,853 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,854 package, please make sure that 'publiforge.Openers.Publidoc.Variables' is explicitly added 2025-09-08T11:43:23,854 to the `packages` configuration field. 2025-09-08T11:43:23,854 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,854 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,854 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,854 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,854 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,854 If you don't want 'publiforge.Openers.Publidoc.Variables' to be distributed and are 2025-09-08T11:43:23,855 already explicitly excluding 'publiforge.Openers.Publidoc.Variables' via 2025-09-08T11:43:23,855 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,855 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,855 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,855 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,855 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,855 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,855 even if it does not contain any `.py` files. 2025-09-08T11:43:23,856 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,856 directory, all directories are treated like packages. 2025-09-08T11:43:23,856 ******************************************************************************** 2025-09-08T11:43:23,856 !! 2025-09-08T11:43:23,856 check.warn(importable) 2025-09-08T11:43:23,856 /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-08T11:43:23,856 !! 2025-09-08T11:43:23,856 ******************************************************************************** 2025-09-08T11:43:23,856 ############################ 2025-09-08T11:43:23,856 # Package would be ignored # 2025-09-08T11:43:23,857 ############################ 2025-09-08T11:43:23,857 Python recognizes 'publiforge.Openers.Publidoc.Xsl' as an importable package[^1], 2025-09-08T11:43:23,857 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,857 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,857 package, please make sure that 'publiforge.Openers.Publidoc.Xsl' is explicitly added 2025-09-08T11:43:23,857 to the `packages` configuration field. 2025-09-08T11:43:23,857 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,857 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,857 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,858 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,858 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,858 If you don't want 'publiforge.Openers.Publidoc.Xsl' to be distributed and are 2025-09-08T11:43:23,858 already explicitly excluding 'publiforge.Openers.Publidoc.Xsl' via 2025-09-08T11:43:23,858 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,858 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,858 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,858 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,859 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,859 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,859 even if it does not contain any `.py` files. 2025-09-08T11:43:23,859 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,859 directory, all directories are treated like packages. 2025-09-08T11:43:23,859 ******************************************************************************** 2025-09-08T11:43:23,859 !! 2025-09-08T11:43:23,859 check.warn(importable) 2025-09-08T11:43:23,859 /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-08T11:43:23,860 !! 2025-09-08T11:43:23,860 ******************************************************************************** 2025-09-08T11:43:23,860 ############################ 2025-09-08T11:43:23,860 # Package would be ignored # 2025-09-08T11:43:23,860 ############################ 2025-09-08T11:43:23,860 Python recognizes 'publiforge.Openers.Publiquiz' as an importable package[^1], 2025-09-08T11:43:23,860 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,860 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,860 package, please make sure that 'publiforge.Openers.Publiquiz' is explicitly added 2025-09-08T11:43:23,860 to the `packages` configuration field. 2025-09-08T11:43:23,861 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,861 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,861 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,861 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,861 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,861 If you don't want 'publiforge.Openers.Publiquiz' to be distributed and are 2025-09-08T11:43:23,861 already explicitly excluding 'publiforge.Openers.Publiquiz' via 2025-09-08T11:43:23,862 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,862 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,862 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,862 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,862 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,862 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,862 even if it does not contain any `.py` files. 2025-09-08T11:43:23,862 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,863 directory, all directories are treated like packages. 2025-09-08T11:43:23,863 ******************************************************************************** 2025-09-08T11:43:23,863 !! 2025-09-08T11:43:23,863 check.warn(importable) 2025-09-08T11:43:23,863 /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-08T11:43:23,863 !! 2025-09-08T11:43:23,863 ******************************************************************************** 2025-09-08T11:43:23,863 ############################ 2025-09-08T11:43:23,863 # Package would be ignored # 2025-09-08T11:43:23,863 ############################ 2025-09-08T11:43:23,864 Python recognizes 'publiforge.Openers.Publiquiz.Regex' as an importable package[^1], 2025-09-08T11:43:23,864 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,864 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,864 package, please make sure that 'publiforge.Openers.Publiquiz.Regex' is explicitly added 2025-09-08T11:43:23,864 to the `packages` configuration field. 2025-09-08T11:43:23,864 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,864 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,864 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,864 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,865 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,865 If you don't want 'publiforge.Openers.Publiquiz.Regex' to be distributed and are 2025-09-08T11:43:23,865 already explicitly excluding 'publiforge.Openers.Publiquiz.Regex' via 2025-09-08T11:43:23,865 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,865 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,865 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,865 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,865 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,866 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,866 even if it does not contain any `.py` files. 2025-09-08T11:43:23,866 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,866 directory, all directories are treated like packages. 2025-09-08T11:43:23,866 ******************************************************************************** 2025-09-08T11:43:23,866 !! 2025-09-08T11:43:23,866 check.warn(importable) 2025-09-08T11:43:23,866 /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-08T11:43:23,866 !! 2025-09-08T11:43:23,867 ******************************************************************************** 2025-09-08T11:43:23,867 ############################ 2025-09-08T11:43:23,867 # Package would be ignored # 2025-09-08T11:43:23,867 ############################ 2025-09-08T11:43:23,867 Python recognizes 'publiforge.Openers.Publiquiz.Seeds' as an importable package[^1], 2025-09-08T11:43:23,867 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,867 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,867 package, please make sure that 'publiforge.Openers.Publiquiz.Seeds' is explicitly added 2025-09-08T11:43:23,867 to the `packages` configuration field. 2025-09-08T11:43:23,868 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,868 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,868 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,868 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,868 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,868 If you don't want 'publiforge.Openers.Publiquiz.Seeds' to be distributed and are 2025-09-08T11:43:23,868 already explicitly excluding 'publiforge.Openers.Publiquiz.Seeds' via 2025-09-08T11:43:23,868 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,868 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,869 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,869 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,869 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,869 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,869 even if it does not contain any `.py` files. 2025-09-08T11:43:23,869 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,869 directory, all directories are treated like packages. 2025-09-08T11:43:23,869 ******************************************************************************** 2025-09-08T11:43:23,870 !! 2025-09-08T11:43:23,870 check.warn(importable) 2025-09-08T11:43:23,870 /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-08T11:43:23,870 !! 2025-09-08T11:43:23,870 ******************************************************************************** 2025-09-08T11:43:23,870 ############################ 2025-09-08T11:43:23,870 # Package would be ignored # 2025-09-08T11:43:23,870 ############################ 2025-09-08T11:43:23,870 Python recognizes 'publiforge.Openers.Publiquiz.Static.Css' as an importable package[^1], 2025-09-08T11:43:23,870 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,871 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,871 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Css' is explicitly added 2025-09-08T11:43:23,871 to the `packages` configuration field. 2025-09-08T11:43:23,871 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,871 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,871 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,871 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,871 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,872 If you don't want 'publiforge.Openers.Publiquiz.Static.Css' to be distributed and are 2025-09-08T11:43:23,872 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Css' via 2025-09-08T11:43:23,872 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,872 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,872 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,872 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,872 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,872 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,873 even if it does not contain any `.py` files. 2025-09-08T11:43:23,873 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,873 directory, all directories are treated like packages. 2025-09-08T11:43:23,873 ******************************************************************************** 2025-09-08T11:43:23,873 !! 2025-09-08T11:43:23,873 check.warn(importable) 2025-09-08T11:43:23,873 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Openers.Publiquiz.Static.Fonts' is absent from the `packages` configuration. 2025-09-08T11:43:23,873 !! 2025-09-08T11:43:23,873 ******************************************************************************** 2025-09-08T11:43:23,873 ############################ 2025-09-08T11:43:23,873 # Package would be ignored # 2025-09-08T11:43:23,874 ############################ 2025-09-08T11:43:23,874 Python recognizes 'publiforge.Openers.Publiquiz.Static.Fonts' as an importable package[^1], 2025-09-08T11:43:23,874 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,874 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,874 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Fonts' is explicitly added 2025-09-08T11:43:23,874 to the `packages` configuration field. 2025-09-08T11:43:23,874 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,874 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,875 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,875 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,875 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,875 If you don't want 'publiforge.Openers.Publiquiz.Static.Fonts' to be distributed and are 2025-09-08T11:43:23,875 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Fonts' via 2025-09-08T11:43:23,875 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,875 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,875 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,876 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,876 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,876 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,876 even if it does not contain any `.py` files. 2025-09-08T11:43:23,876 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,876 directory, all directories are treated like packages. 2025-09-08T11:43:23,876 ******************************************************************************** 2025-09-08T11:43:23,876 !! 2025-09-08T11:43:23,877 check.warn(importable) 2025-09-08T11:43:23,877 /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-08T11:43:23,877 !! 2025-09-08T11:43:23,877 ******************************************************************************** 2025-09-08T11:43:23,877 ############################ 2025-09-08T11:43:23,877 # Package would be ignored # 2025-09-08T11:43:23,877 ############################ 2025-09-08T11:43:23,877 Python recognizes 'publiforge.Openers.Publiquiz.Static.Js' as an importable package[^1], 2025-09-08T11:43:23,877 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,877 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,878 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Js' is explicitly added 2025-09-08T11:43:23,878 to the `packages` configuration field. 2025-09-08T11:43:23,878 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,878 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,878 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,878 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,878 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,878 If you don't want 'publiforge.Openers.Publiquiz.Static.Js' to be distributed and are 2025-09-08T11:43:23,879 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Js' via 2025-09-08T11:43:23,879 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,879 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,879 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,879 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,879 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,879 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,879 even if it does not contain any `.py` files. 2025-09-08T11:43:23,880 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,880 directory, all directories are treated like packages. 2025-09-08T11:43:23,880 ******************************************************************************** 2025-09-08T11:43:23,880 !! 2025-09-08T11:43:23,880 check.warn(importable) 2025-09-08T11:43:23,880 /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-08T11:43:23,880 !! 2025-09-08T11:43:23,880 ******************************************************************************** 2025-09-08T11:43:23,880 ############################ 2025-09-08T11:43:23,880 # Package would be ignored # 2025-09-08T11:43:23,880 ############################ 2025-09-08T11:43:23,881 Python recognizes 'publiforge.Openers.Publiquiz.Variables' as an importable package[^1], 2025-09-08T11:43:23,881 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,881 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,881 package, please make sure that 'publiforge.Openers.Publiquiz.Variables' is explicitly added 2025-09-08T11:43:23,881 to the `packages` configuration field. 2025-09-08T11:43:23,881 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,881 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,881 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,881 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,882 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,882 If you don't want 'publiforge.Openers.Publiquiz.Variables' to be distributed and are 2025-09-08T11:43:23,882 already explicitly excluding 'publiforge.Openers.Publiquiz.Variables' via 2025-09-08T11:43:23,882 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,882 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,882 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,882 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,882 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,883 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,883 even if it does not contain any `.py` files. 2025-09-08T11:43:23,883 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,883 directory, all directories are treated like packages. 2025-09-08T11:43:23,883 ******************************************************************************** 2025-09-08T11:43:23,883 !! 2025-09-08T11:43:23,883 check.warn(importable) 2025-09-08T11:43:23,883 /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-08T11:43:23,883 !! 2025-09-08T11:43:23,884 ******************************************************************************** 2025-09-08T11:43:23,884 ############################ 2025-09-08T11:43:23,884 # Package would be ignored # 2025-09-08T11:43:23,884 ############################ 2025-09-08T11:43:23,884 Python recognizes 'publiforge.Openers.Publiquiz.Xsl' as an importable package[^1], 2025-09-08T11:43:23,884 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,884 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,884 package, please make sure that 'publiforge.Openers.Publiquiz.Xsl' is explicitly added 2025-09-08T11:43:23,884 to the `packages` configuration field. 2025-09-08T11:43:23,884 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,885 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,885 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,885 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,885 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,885 If you don't want 'publiforge.Openers.Publiquiz.Xsl' to be distributed and are 2025-09-08T11:43:23,885 already explicitly excluding 'publiforge.Openers.Publiquiz.Xsl' via 2025-09-08T11:43:23,885 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,885 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,885 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,886 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,886 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,886 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,886 even if it does not contain any `.py` files. 2025-09-08T11:43:23,886 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,886 directory, all directories are treated like packages. 2025-09-08T11:43:23,886 ******************************************************************************** 2025-09-08T11:43:23,887 !! 2025-09-08T11:43:23,887 check.warn(importable) 2025-09-08T11:43:23,887 /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-08T11:43:23,887 !! 2025-09-08T11:43:23,887 ******************************************************************************** 2025-09-08T11:43:23,887 ############################ 2025-09-08T11:43:23,887 # Package would be ignored # 2025-09-08T11:43:23,887 ############################ 2025-09-08T11:43:23,887 Python recognizes 'publiforge.Openers.Publiset' as an importable package[^1], 2025-09-08T11:43:23,887 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,888 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,888 package, please make sure that 'publiforge.Openers.Publiset' is explicitly added 2025-09-08T11:43:23,888 to the `packages` configuration field. 2025-09-08T11:43:23,888 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,888 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,888 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,888 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,888 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,889 If you don't want 'publiforge.Openers.Publiset' to be distributed and are 2025-09-08T11:43:23,889 already explicitly excluding 'publiforge.Openers.Publiset' via 2025-09-08T11:43:23,889 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,889 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,889 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,889 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,889 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,890 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,890 even if it does not contain any `.py` files. 2025-09-08T11:43:23,890 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,890 directory, all directories are treated like packages. 2025-09-08T11:43:23,890 ******************************************************************************** 2025-09-08T11:43:23,890 !! 2025-09-08T11:43:23,890 check.warn(importable) 2025-09-08T11:43:23,890 /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-08T11:43:23,890 !! 2025-09-08T11:43:23,890 ******************************************************************************** 2025-09-08T11:43:23,890 ############################ 2025-09-08T11:43:23,891 # Package would be ignored # 2025-09-08T11:43:23,891 ############################ 2025-09-08T11:43:23,891 Python recognizes 'publiforge.Openers.Publiset.Regex' as an importable package[^1], 2025-09-08T11:43:23,891 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,891 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,891 package, please make sure that 'publiforge.Openers.Publiset.Regex' is explicitly added 2025-09-08T11:43:23,891 to the `packages` configuration field. 2025-09-08T11:43:23,891 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,891 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,891 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,892 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,892 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,892 If you don't want 'publiforge.Openers.Publiset.Regex' to be distributed and are 2025-09-08T11:43:23,892 already explicitly excluding 'publiforge.Openers.Publiset.Regex' via 2025-09-08T11:43:23,892 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,892 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,892 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,892 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,893 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,893 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,893 even if it does not contain any `.py` files. 2025-09-08T11:43:23,893 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,893 directory, all directories are treated like packages. 2025-09-08T11:43:23,893 ******************************************************************************** 2025-09-08T11:43:23,893 !! 2025-09-08T11:43:23,893 check.warn(importable) 2025-09-08T11:43:23,894 /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-08T11:43:23,894 !! 2025-09-08T11:43:23,894 ******************************************************************************** 2025-09-08T11:43:23,894 ############################ 2025-09-08T11:43:23,894 # Package would be ignored # 2025-09-08T11:43:23,894 ############################ 2025-09-08T11:43:23,894 Python recognizes 'publiforge.Openers.Publiset.Seeds' as an importable package[^1], 2025-09-08T11:43:23,894 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,894 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,894 package, please make sure that 'publiforge.Openers.Publiset.Seeds' is explicitly added 2025-09-08T11:43:23,895 to the `packages` configuration field. 2025-09-08T11:43:23,895 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,895 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,895 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,895 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,895 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,895 If you don't want 'publiforge.Openers.Publiset.Seeds' to be distributed and are 2025-09-08T11:43:23,895 already explicitly excluding 'publiforge.Openers.Publiset.Seeds' via 2025-09-08T11:43:23,895 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,896 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,896 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,896 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,896 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,896 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,896 even if it does not contain any `.py` files. 2025-09-08T11:43:23,896 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,896 directory, all directories are treated like packages. 2025-09-08T11:43:23,897 ******************************************************************************** 2025-09-08T11:43:23,897 !! 2025-09-08T11:43:23,897 check.warn(importable) 2025-09-08T11:43:23,897 /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-08T11:43:23,897 !! 2025-09-08T11:43:23,897 ******************************************************************************** 2025-09-08T11:43:23,897 ############################ 2025-09-08T11:43:23,897 # Package would be ignored # 2025-09-08T11:43:23,897 ############################ 2025-09-08T11:43:23,897 Python recognizes 'publiforge.Openers.Publiset.Static.Css' as an importable package[^1], 2025-09-08T11:43:23,898 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,898 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,898 package, please make sure that 'publiforge.Openers.Publiset.Static.Css' is explicitly added 2025-09-08T11:43:23,898 to the `packages` configuration field. 2025-09-08T11:43:23,898 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,898 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,898 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,898 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,898 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,899 If you don't want 'publiforge.Openers.Publiset.Static.Css' to be distributed and are 2025-09-08T11:43:23,899 already explicitly excluding 'publiforge.Openers.Publiset.Static.Css' via 2025-09-08T11:43:23,899 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,899 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,899 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,899 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,899 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,900 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,900 even if it does not contain any `.py` files. 2025-09-08T11:43:23,900 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,900 directory, all directories are treated like packages. 2025-09-08T11:43:23,900 ******************************************************************************** 2025-09-08T11:43:23,900 !! 2025-09-08T11:43:23,900 check.warn(importable) 2025-09-08T11:43:23,900 /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-08T11:43:23,900 !! 2025-09-08T11:43:23,901 ******************************************************************************** 2025-09-08T11:43:23,901 ############################ 2025-09-08T11:43:23,901 # Package would be ignored # 2025-09-08T11:43:23,901 ############################ 2025-09-08T11:43:23,901 Python recognizes 'publiforge.Openers.Publiset.Static.Images' as an importable package[^1], 2025-09-08T11:43:23,901 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,901 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,901 package, please make sure that 'publiforge.Openers.Publiset.Static.Images' is explicitly added 2025-09-08T11:43:23,901 to the `packages` configuration field. 2025-09-08T11:43:23,901 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,902 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,902 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,902 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,902 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,902 If you don't want 'publiforge.Openers.Publiset.Static.Images' to be distributed and are 2025-09-08T11:43:23,902 already explicitly excluding 'publiforge.Openers.Publiset.Static.Images' via 2025-09-08T11:43:23,902 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,902 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,902 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,903 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,903 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,903 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,903 even if it does not contain any `.py` files. 2025-09-08T11:43:23,903 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,903 directory, all directories are treated like packages. 2025-09-08T11:43:23,903 ******************************************************************************** 2025-09-08T11:43:23,904 !! 2025-09-08T11:43:23,904 check.warn(importable) 2025-09-08T11:43:23,904 /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-08T11:43:23,904 !! 2025-09-08T11:43:23,904 ******************************************************************************** 2025-09-08T11:43:23,904 ############################ 2025-09-08T11:43:23,904 # Package would be ignored # 2025-09-08T11:43:23,904 ############################ 2025-09-08T11:43:23,904 Python recognizes 'publiforge.Openers.Publiset.Static.Js' as an importable package[^1], 2025-09-08T11:43:23,904 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,905 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,905 package, please make sure that 'publiforge.Openers.Publiset.Static.Js' is explicitly added 2025-09-08T11:43:23,905 to the `packages` configuration field. 2025-09-08T11:43:23,905 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,905 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,905 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,905 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,905 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,905 If you don't want 'publiforge.Openers.Publiset.Static.Js' to be distributed and are 2025-09-08T11:43:23,906 already explicitly excluding 'publiforge.Openers.Publiset.Static.Js' via 2025-09-08T11:43:23,906 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,906 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,906 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,906 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,906 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,906 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,906 even if it does not contain any `.py` files. 2025-09-08T11:43:23,907 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,907 directory, all directories are treated like packages. 2025-09-08T11:43:23,907 ******************************************************************************** 2025-09-08T11:43:23,907 !! 2025-09-08T11:43:23,907 check.warn(importable) 2025-09-08T11:43:23,907 /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-08T11:43:23,907 !! 2025-09-08T11:43:23,907 ******************************************************************************** 2025-09-08T11:43:23,907 ############################ 2025-09-08T11:43:23,908 # Package would be ignored # 2025-09-08T11:43:23,908 ############################ 2025-09-08T11:43:23,908 Python recognizes 'publiforge.Openers.Publiset.Variables' as an importable package[^1], 2025-09-08T11:43:23,908 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,908 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,908 package, please make sure that 'publiforge.Openers.Publiset.Variables' is explicitly added 2025-09-08T11:43:23,908 to the `packages` configuration field. 2025-09-08T11:43:23,908 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,908 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,908 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,909 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,909 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,909 If you don't want 'publiforge.Openers.Publiset.Variables' to be distributed and are 2025-09-08T11:43:23,909 already explicitly excluding 'publiforge.Openers.Publiset.Variables' via 2025-09-08T11:43:23,909 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,909 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,909 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,909 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,910 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,910 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,910 even if it does not contain any `.py` files. 2025-09-08T11:43:23,910 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,910 directory, all directories are treated like packages. 2025-09-08T11:43:23,910 ******************************************************************************** 2025-09-08T11:43:23,910 !! 2025-09-08T11:43:23,910 check.warn(importable) 2025-09-08T11:43:23,910 /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-08T11:43:23,911 !! 2025-09-08T11:43:23,911 ******************************************************************************** 2025-09-08T11:43:23,911 ############################ 2025-09-08T11:43:23,911 # Package would be ignored # 2025-09-08T11:43:23,911 ############################ 2025-09-08T11:43:23,911 Python recognizes 'publiforge.Openers.Publiset.Xsl' as an importable package[^1], 2025-09-08T11:43:23,911 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,911 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,911 package, please make sure that 'publiforge.Openers.Publiset.Xsl' is explicitly added 2025-09-08T11:43:23,911 to the `packages` configuration field. 2025-09-08T11:43:23,912 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,912 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,912 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,912 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,912 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,912 If you don't want 'publiforge.Openers.Publiset.Xsl' to be distributed and are 2025-09-08T11:43:23,912 already explicitly excluding 'publiforge.Openers.Publiset.Xsl' via 2025-09-08T11:43:23,912 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,912 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,913 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,913 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,913 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,913 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,913 even if it does not contain any `.py` files. 2025-09-08T11:43:23,913 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,913 directory, all directories are treated like packages. 2025-09-08T11:43:23,914 ******************************************************************************** 2025-09-08T11:43:23,914 !! 2025-09-08T11:43:23,914 check.warn(importable) 2025-09-08T11:43:23,914 /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-08T11:43:23,914 !! 2025-09-08T11:43:23,914 ******************************************************************************** 2025-09-08T11:43:23,914 ############################ 2025-09-08T11:43:23,914 # Package would be ignored # 2025-09-08T11:43:23,914 ############################ 2025-09-08T11:43:23,915 Python recognizes 'publiforge.Openers.Xml' as an importable package[^1], 2025-09-08T11:43:23,915 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,915 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,915 package, please make sure that 'publiforge.Openers.Xml' is explicitly added 2025-09-08T11:43:23,915 to the `packages` configuration field. 2025-09-08T11:43:23,915 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,915 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,915 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,915 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,916 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,916 If you don't want 'publiforge.Openers.Xml' to be distributed and are 2025-09-08T11:43:23,916 already explicitly excluding 'publiforge.Openers.Xml' via 2025-09-08T11:43:23,916 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,916 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,916 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,916 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,916 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,917 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,917 even if it does not contain any `.py` files. 2025-09-08T11:43:23,917 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,917 directory, all directories are treated like packages. 2025-09-08T11:43:23,917 ******************************************************************************** 2025-09-08T11:43:23,917 !! 2025-09-08T11:43:23,917 check.warn(importable) 2025-09-08T11:43:23,917 /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-08T11:43:23,917 !! 2025-09-08T11:43:23,918 ******************************************************************************** 2025-09-08T11:43:23,918 ############################ 2025-09-08T11:43:23,918 # Package would be ignored # 2025-09-08T11:43:23,918 ############################ 2025-09-08T11:43:23,918 Python recognizes 'publiforge.Openers.Xml.Static.Css' as an importable package[^1], 2025-09-08T11:43:23,918 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,918 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,918 package, please make sure that 'publiforge.Openers.Xml.Static.Css' is explicitly added 2025-09-08T11:43:23,918 to the `packages` configuration field. 2025-09-08T11:43:23,918 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,919 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,919 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,919 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,919 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,919 If you don't want 'publiforge.Openers.Xml.Static.Css' to be distributed and are 2025-09-08T11:43:23,919 already explicitly excluding 'publiforge.Openers.Xml.Static.Css' via 2025-09-08T11:43:23,919 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,919 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,919 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,920 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,920 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,920 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,920 even if it does not contain any `.py` files. 2025-09-08T11:43:23,920 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,920 directory, all directories are treated like packages. 2025-09-08T11:43:23,920 ******************************************************************************** 2025-09-08T11:43:23,920 !! 2025-09-08T11:43:23,921 check.warn(importable) 2025-09-08T11:43:23,921 /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-08T11:43:23,921 !! 2025-09-08T11:43:23,921 ******************************************************************************** 2025-09-08T11:43:23,921 ############################ 2025-09-08T11:43:23,921 # Package would be ignored # 2025-09-08T11:43:23,921 ############################ 2025-09-08T11:43:23,921 Python recognizes 'publiforge.Openers.Xml.Static.Images' as an importable package[^1], 2025-09-08T11:43:23,921 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,921 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,922 package, please make sure that 'publiforge.Openers.Xml.Static.Images' is explicitly added 2025-09-08T11:43:23,922 to the `packages` configuration field. 2025-09-08T11:43:23,922 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,922 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,922 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,922 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,922 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,922 If you don't want 'publiforge.Openers.Xml.Static.Images' to be distributed and are 2025-09-08T11:43:23,922 already explicitly excluding 'publiforge.Openers.Xml.Static.Images' via 2025-09-08T11:43:23,923 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,923 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,923 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,923 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,923 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,923 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,923 even if it does not contain any `.py` files. 2025-09-08T11:43:23,923 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,924 directory, all directories are treated like packages. 2025-09-08T11:43:23,924 ******************************************************************************** 2025-09-08T11:43:23,924 !! 2025-09-08T11:43:23,924 check.warn(importable) 2025-09-08T11:43:23,924 /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-08T11:43:23,924 !! 2025-09-08T11:43:23,924 ******************************************************************************** 2025-09-08T11:43:23,924 ############################ 2025-09-08T11:43:23,924 # Package would be ignored # 2025-09-08T11:43:23,924 ############################ 2025-09-08T11:43:23,925 Python recognizes 'publiforge.Openers.Xml.Static.Js' as an importable package[^1], 2025-09-08T11:43:23,925 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,925 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,925 package, please make sure that 'publiforge.Openers.Xml.Static.Js' is explicitly added 2025-09-08T11:43:23,925 to the `packages` configuration field. 2025-09-08T11:43:23,925 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,925 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,925 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,925 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,926 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,926 If you don't want 'publiforge.Openers.Xml.Static.Js' to be distributed and are 2025-09-08T11:43:23,926 already explicitly excluding 'publiforge.Openers.Xml.Static.Js' via 2025-09-08T11:43:23,926 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,926 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,926 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,926 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,927 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,927 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,927 even if it does not contain any `.py` files. 2025-09-08T11:43:23,927 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,927 directory, all directories are treated like packages. 2025-09-08T11:43:23,927 ******************************************************************************** 2025-09-08T11:43:23,927 !! 2025-09-08T11:43:23,927 check.warn(importable) 2025-09-08T11:43:23,928 /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-08T11:43:23,928 !! 2025-09-08T11:43:23,928 ******************************************************************************** 2025-09-08T11:43:23,928 ############################ 2025-09-08T11:43:23,928 # Package would be ignored # 2025-09-08T11:43:23,928 ############################ 2025-09-08T11:43:23,928 Python recognizes 'publiforge.Processors.CharCount' as an importable package[^1], 2025-09-08T11:43:23,928 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,928 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,928 package, please make sure that 'publiforge.Processors.CharCount' is explicitly added 2025-09-08T11:43:23,929 to the `packages` configuration field. 2025-09-08T11:43:23,929 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,929 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,929 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,929 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,929 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,929 If you don't want 'publiforge.Processors.CharCount' to be distributed and are 2025-09-08T11:43:23,929 already explicitly excluding 'publiforge.Processors.CharCount' via 2025-09-08T11:43:23,929 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,930 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,930 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,930 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,930 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,930 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,930 even if it does not contain any `.py` files. 2025-09-08T11:43:23,930 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,930 directory, all directories are treated like packages. 2025-09-08T11:43:23,931 ******************************************************************************** 2025-09-08T11:43:23,931 !! 2025-09-08T11:43:23,931 check.warn(importable) 2025-09-08T11:43:23,931 /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-08T11:43:23,931 !! 2025-09-08T11:43:23,931 ******************************************************************************** 2025-09-08T11:43:23,931 ############################ 2025-09-08T11:43:23,931 # Package would be ignored # 2025-09-08T11:43:23,931 ############################ 2025-09-08T11:43:23,931 Python recognizes 'publiforge.Processors.CharCount.Xsl' as an importable package[^1], 2025-09-08T11:43:23,932 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,932 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,932 package, please make sure that 'publiforge.Processors.CharCount.Xsl' is explicitly added 2025-09-08T11:43:23,932 to the `packages` configuration field. 2025-09-08T11:43:23,932 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,932 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,932 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,932 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,933 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,933 If you don't want 'publiforge.Processors.CharCount.Xsl' to be distributed and are 2025-09-08T11:43:23,933 already explicitly excluding 'publiforge.Processors.CharCount.Xsl' via 2025-09-08T11:43:23,933 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,933 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,933 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,933 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,933 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,934 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,934 even if it does not contain any `.py` files. 2025-09-08T11:43:23,934 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,934 directory, all directories are treated like packages. 2025-09-08T11:43:23,934 ******************************************************************************** 2025-09-08T11:43:23,934 !! 2025-09-08T11:43:23,934 check.warn(importable) 2025-09-08T11:43:23,934 /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-08T11:43:23,934 !! 2025-09-08T11:43:23,934 ******************************************************************************** 2025-09-08T11:43:23,935 ############################ 2025-09-08T11:43:23,935 # Package would be ignored # 2025-09-08T11:43:23,935 ############################ 2025-09-08T11:43:23,935 Python recognizes 'publiforge.Processors.CleanStorage' as an importable package[^1], 2025-09-08T11:43:23,935 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,935 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,935 package, please make sure that 'publiforge.Processors.CleanStorage' is explicitly added 2025-09-08T11:43:23,935 to the `packages` configuration field. 2025-09-08T11:43:23,935 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,935 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,936 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,936 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,936 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,936 If you don't want 'publiforge.Processors.CleanStorage' to be distributed and are 2025-09-08T11:43:23,936 already explicitly excluding 'publiforge.Processors.CleanStorage' via 2025-09-08T11:43:23,936 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,936 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,936 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,937 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,937 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,937 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,937 even if it does not contain any `.py` files. 2025-09-08T11:43:23,937 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,937 directory, all directories are treated like packages. 2025-09-08T11:43:23,937 ******************************************************************************** 2025-09-08T11:43:23,937 !! 2025-09-08T11:43:23,937 check.warn(importable) 2025-09-08T11:43:23,938 /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-08T11:43:23,938 !! 2025-09-08T11:43:23,938 ******************************************************************************** 2025-09-08T11:43:23,938 ############################ 2025-09-08T11:43:23,938 # Package would be ignored # 2025-09-08T11:43:23,938 ############################ 2025-09-08T11:43:23,938 Python recognizes 'publiforge.Processors.CleanStorage.lib' as an importable package[^1], 2025-09-08T11:43:23,938 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,938 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,938 package, please make sure that 'publiforge.Processors.CleanStorage.lib' is explicitly added 2025-09-08T11:43:23,939 to the `packages` configuration field. 2025-09-08T11:43:23,939 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,939 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,939 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,939 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,939 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,939 If you don't want 'publiforge.Processors.CleanStorage.lib' to be distributed and are 2025-09-08T11:43:23,939 already explicitly excluding 'publiforge.Processors.CleanStorage.lib' via 2025-09-08T11:43:23,940 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,940 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,940 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,940 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,940 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,940 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,940 even if it does not contain any `.py` files. 2025-09-08T11:43:23,941 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,941 directory, all directories are treated like packages. 2025-09-08T11:43:23,941 ******************************************************************************** 2025-09-08T11:43:23,941 !! 2025-09-08T11:43:23,941 check.warn(importable) 2025-09-08T11:43:23,941 /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-08T11:43:23,941 !! 2025-09-08T11:43:23,941 ******************************************************************************** 2025-09-08T11:43:23,941 ############################ 2025-09-08T11:43:23,941 # Package would be ignored # 2025-09-08T11:43:23,942 ############################ 2025-09-08T11:43:23,942 Python recognizes 'publiforge.Processors.DTBookValid' as an importable package[^1], 2025-09-08T11:43:23,942 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,942 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,942 package, please make sure that 'publiforge.Processors.DTBookValid' is explicitly added 2025-09-08T11:43:23,942 to the `packages` configuration field. 2025-09-08T11:43:23,942 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,942 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,942 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,943 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,943 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,943 If you don't want 'publiforge.Processors.DTBookValid' to be distributed and are 2025-09-08T11:43:23,943 already explicitly excluding 'publiforge.Processors.DTBookValid' via 2025-09-08T11:43:23,943 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,943 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,943 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,943 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,944 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,944 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,944 even if it does not contain any `.py` files. 2025-09-08T11:43:23,944 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,944 directory, all directories are treated like packages. 2025-09-08T11:43:23,944 ******************************************************************************** 2025-09-08T11:43:23,944 !! 2025-09-08T11:43:23,944 check.warn(importable) 2025-09-08T11:43:23,944 /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-08T11:43:23,945 !! 2025-09-08T11:43:23,945 ******************************************************************************** 2025-09-08T11:43:23,945 ############################ 2025-09-08T11:43:23,945 # Package would be ignored # 2025-09-08T11:43:23,945 ############################ 2025-09-08T11:43:23,945 Python recognizes 'publiforge.Processors.DTBookValid.RelaxNG' as an importable package[^1], 2025-09-08T11:43:23,945 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,945 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,945 package, please make sure that 'publiforge.Processors.DTBookValid.RelaxNG' is explicitly added 2025-09-08T11:43:23,945 to the `packages` configuration field. 2025-09-08T11:43:23,946 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,946 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,946 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,946 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,946 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,946 If you don't want 'publiforge.Processors.DTBookValid.RelaxNG' to be distributed and are 2025-09-08T11:43:23,946 already explicitly excluding 'publiforge.Processors.DTBookValid.RelaxNG' via 2025-09-08T11:43:23,946 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,946 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,947 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,947 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,947 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,947 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,947 even if it does not contain any `.py` files. 2025-09-08T11:43:23,947 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,947 directory, all directories are treated like packages. 2025-09-08T11:43:23,947 ******************************************************************************** 2025-09-08T11:43:23,948 !! 2025-09-08T11:43:23,948 check.warn(importable) 2025-09-08T11:43:23,948 /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-08T11:43:23,948 !! 2025-09-08T11:43:23,948 ******************************************************************************** 2025-09-08T11:43:23,948 ############################ 2025-09-08T11:43:23,948 # Package would be ignored # 2025-09-08T11:43:23,948 ############################ 2025-09-08T11:43:23,948 Python recognizes 'publiforge.Processors.PackFilling' as an importable package[^1], 2025-09-08T11:43:23,948 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,949 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,949 package, please make sure that 'publiforge.Processors.PackFilling' is explicitly added 2025-09-08T11:43:23,949 to the `packages` configuration field. 2025-09-08T11:43:23,949 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,949 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,949 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,949 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,949 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,950 If you don't want 'publiforge.Processors.PackFilling' to be distributed and are 2025-09-08T11:43:23,950 already explicitly excluding 'publiforge.Processors.PackFilling' via 2025-09-08T11:43:23,950 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,950 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,950 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,950 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,950 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,950 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,951 even if it does not contain any `.py` files. 2025-09-08T11:43:23,951 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,951 directory, all directories are treated like packages. 2025-09-08T11:43:23,951 ******************************************************************************** 2025-09-08T11:43:23,951 !! 2025-09-08T11:43:23,951 check.warn(importable) 2025-09-08T11:43:23,951 /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-08T11:43:23,951 !! 2025-09-08T11:43:23,951 ******************************************************************************** 2025-09-08T11:43:23,951 ############################ 2025-09-08T11:43:23,952 # Package would be ignored # 2025-09-08T11:43:23,952 ############################ 2025-09-08T11:43:23,952 Python recognizes 'publiforge.Processors.PackFilling.Variables' as an importable package[^1], 2025-09-08T11:43:23,952 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,952 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,952 package, please make sure that 'publiforge.Processors.PackFilling.Variables' is explicitly added 2025-09-08T11:43:23,952 to the `packages` configuration field. 2025-09-08T11:43:23,952 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,952 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,952 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,953 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,953 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,953 If you don't want 'publiforge.Processors.PackFilling.Variables' to be distributed and are 2025-09-08T11:43:23,953 already explicitly excluding 'publiforge.Processors.PackFilling.Variables' via 2025-09-08T11:43:23,953 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,953 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,953 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,954 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,954 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,954 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,954 even if it does not contain any `.py` files. 2025-09-08T11:43:23,954 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,954 directory, all directories are treated like packages. 2025-09-08T11:43:23,954 ******************************************************************************** 2025-09-08T11:43:23,954 !! 2025-09-08T11:43:23,955 check.warn(importable) 2025-09-08T11:43:23,955 /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-08T11:43:23,955 !! 2025-09-08T11:43:23,955 ******************************************************************************** 2025-09-08T11:43:23,955 ############################ 2025-09-08T11:43:23,955 # Package would be ignored # 2025-09-08T11:43:23,955 ############################ 2025-09-08T11:43:23,955 Python recognizes 'publiforge.Processors.PackFilling.lib' as an importable package[^1], 2025-09-08T11:43:23,955 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,956 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,956 package, please make sure that 'publiforge.Processors.PackFilling.lib' is explicitly added 2025-09-08T11:43:23,956 to the `packages` configuration field. 2025-09-08T11:43:23,956 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,956 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,956 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,956 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,956 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,957 If you don't want 'publiforge.Processors.PackFilling.lib' to be distributed and are 2025-09-08T11:43:23,957 already explicitly excluding 'publiforge.Processors.PackFilling.lib' via 2025-09-08T11:43:23,957 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,957 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,957 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,957 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,957 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,957 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,958 even if it does not contain any `.py` files. 2025-09-08T11:43:23,958 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,958 directory, all directories are treated like packages. 2025-09-08T11:43:23,958 ******************************************************************************** 2025-09-08T11:43:23,958 !! 2025-09-08T11:43:23,958 check.warn(importable) 2025-09-08T11:43:23,958 /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-08T11:43:23,958 !! 2025-09-08T11:43:23,958 ******************************************************************************** 2025-09-08T11:43:23,958 ############################ 2025-09-08T11:43:23,959 # Package would be ignored # 2025-09-08T11:43:23,959 ############################ 2025-09-08T11:43:23,959 Python recognizes 'publiforge.Processors.Parallel' as an importable package[^1], 2025-09-08T11:43:23,959 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,959 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,959 package, please make sure that 'publiforge.Processors.Parallel' is explicitly added 2025-09-08T11:43:23,959 to the `packages` configuration field. 2025-09-08T11:43:23,959 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,959 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,959 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,960 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,960 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,960 If you don't want 'publiforge.Processors.Parallel' to be distributed and are 2025-09-08T11:43:23,960 already explicitly excluding 'publiforge.Processors.Parallel' via 2025-09-08T11:43:23,960 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,960 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,960 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,960 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,961 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,961 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,961 even if it does not contain any `.py` files. 2025-09-08T11:43:23,961 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,961 directory, all directories are treated like packages. 2025-09-08T11:43:23,961 ******************************************************************************** 2025-09-08T11:43:23,961 !! 2025-09-08T11:43:23,961 check.warn(importable) 2025-09-08T11:43:23,961 /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-08T11:43:23,962 !! 2025-09-08T11:43:23,962 ******************************************************************************** 2025-09-08T11:43:23,962 ############################ 2025-09-08T11:43:23,962 # Package would be ignored # 2025-09-08T11:43:23,962 ############################ 2025-09-08T11:43:23,962 Python recognizes 'publiforge.Processors.Parallel.Variables' as an importable package[^1], 2025-09-08T11:43:23,962 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,962 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,962 package, please make sure that 'publiforge.Processors.Parallel.Variables' is explicitly added 2025-09-08T11:43:23,962 to the `packages` configuration field. 2025-09-08T11:43:23,963 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,963 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,963 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,963 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,963 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,963 If you don't want 'publiforge.Processors.Parallel.Variables' to be distributed and are 2025-09-08T11:43:23,963 already explicitly excluding 'publiforge.Processors.Parallel.Variables' via 2025-09-08T11:43:23,963 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,964 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,964 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,964 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,964 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,964 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,964 even if it does not contain any `.py` files. 2025-09-08T11:43:23,964 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,964 directory, all directories are treated like packages. 2025-09-08T11:43:23,965 ******************************************************************************** 2025-09-08T11:43:23,965 !! 2025-09-08T11:43:23,965 check.warn(importable) 2025-09-08T11:43:23,965 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publianim2Html5' is absent from the `packages` configuration. 2025-09-08T11:43:23,965 !! 2025-09-08T11:43:23,965 ******************************************************************************** 2025-09-08T11:43:23,965 ############################ 2025-09-08T11:43:23,965 # Package would be ignored # 2025-09-08T11:43:23,965 ############################ 2025-09-08T11:43:23,965 Python recognizes 'publiforge.Processors.Publianim2Html5' as an importable package[^1], 2025-09-08T11:43:23,965 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,966 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,966 package, please make sure that 'publiforge.Processors.Publianim2Html5' is explicitly added 2025-09-08T11:43:23,966 to the `packages` configuration field. 2025-09-08T11:43:23,966 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,966 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,966 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,966 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,967 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,967 If you don't want 'publiforge.Processors.Publianim2Html5' to be distributed and are 2025-09-08T11:43:23,967 already explicitly excluding 'publiforge.Processors.Publianim2Html5' via 2025-09-08T11:43:23,967 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,967 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,967 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,967 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,967 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,968 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,968 even if it does not contain any `.py` files. 2025-09-08T11:43:23,968 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,968 directory, all directories are treated like packages. 2025-09-08T11:43:23,968 ******************************************************************************** 2025-09-08T11:43:23,968 !! 2025-09-08T11:43:23,968 check.warn(importable) 2025-09-08T11:43:23,968 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publianim2Html5.Variables' is absent from the `packages` configuration. 2025-09-08T11:43:23,968 !! 2025-09-08T11:43:23,969 ******************************************************************************** 2025-09-08T11:43:23,969 ############################ 2025-09-08T11:43:23,969 # Package would be ignored # 2025-09-08T11:43:23,969 ############################ 2025-09-08T11:43:23,969 Python recognizes 'publiforge.Processors.Publianim2Html5.Variables' as an importable package[^1], 2025-09-08T11:43:23,969 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,969 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,969 package, please make sure that 'publiforge.Processors.Publianim2Html5.Variables' is explicitly added 2025-09-08T11:43:23,969 to the `packages` configuration field. 2025-09-08T11:43:23,970 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,970 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,970 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,970 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,970 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,970 If you don't want 'publiforge.Processors.Publianim2Html5.Variables' to be distributed and are 2025-09-08T11:43:23,970 already explicitly excluding 'publiforge.Processors.Publianim2Html5.Variables' via 2025-09-08T11:43:23,970 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,970 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,971 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,971 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,971 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,971 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,971 even if it does not contain any `.py` files. 2025-09-08T11:43:23,971 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,971 directory, all directories are treated like packages. 2025-09-08T11:43:23,971 ******************************************************************************** 2025-09-08T11:43:23,972 !! 2025-09-08T11:43:23,972 check.warn(importable) 2025-09-08T11:43:23,972 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publianim2Html5.Xsl' is absent from the `packages` configuration. 2025-09-08T11:43:23,972 !! 2025-09-08T11:43:23,972 ******************************************************************************** 2025-09-08T11:43:23,972 ############################ 2025-09-08T11:43:23,972 # Package would be ignored # 2025-09-08T11:43:23,972 ############################ 2025-09-08T11:43:23,972 Python recognizes 'publiforge.Processors.Publianim2Html5.Xsl' as an importable package[^1], 2025-09-08T11:43:23,972 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,973 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,973 package, please make sure that 'publiforge.Processors.Publianim2Html5.Xsl' is explicitly added 2025-09-08T11:43:23,973 to the `packages` configuration field. 2025-09-08T11:43:23,973 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,973 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,973 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,973 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,973 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,974 If you don't want 'publiforge.Processors.Publianim2Html5.Xsl' to be distributed and are 2025-09-08T11:43:23,974 already explicitly excluding 'publiforge.Processors.Publianim2Html5.Xsl' via 2025-09-08T11:43:23,974 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,974 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,974 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,974 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,974 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,974 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,975 even if it does not contain any `.py` files. 2025-09-08T11:43:23,975 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,975 directory, all directories are treated like packages. 2025-09-08T11:43:23,975 ******************************************************************************** 2025-09-08T11:43:23,975 !! 2025-09-08T11:43:23,975 check.warn(importable) 2025-09-08T11:43:23,975 /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-08T11:43:23,975 !! 2025-09-08T11:43:23,975 ******************************************************************************** 2025-09-08T11:43:23,975 ############################ 2025-09-08T11:43:23,976 # Package would be ignored # 2025-09-08T11:43:23,976 ############################ 2025-09-08T11:43:23,976 Python recognizes 'publiforge.Processors.Publidoc2DTBook' as an importable package[^1], 2025-09-08T11:43:23,976 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,976 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,976 package, please make sure that 'publiforge.Processors.Publidoc2DTBook' is explicitly added 2025-09-08T11:43:23,976 to the `packages` configuration field. 2025-09-08T11:43:23,976 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,976 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,976 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,977 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,977 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,977 If you don't want 'publiforge.Processors.Publidoc2DTBook' to be distributed and are 2025-09-08T11:43:23,977 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook' via 2025-09-08T11:43:23,977 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,977 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,977 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,977 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,978 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,978 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,978 even if it does not contain any `.py` files. 2025-09-08T11:43:23,978 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,978 directory, all directories are treated like packages. 2025-09-08T11:43:23,978 ******************************************************************************** 2025-09-08T11:43:23,978 !! 2025-09-08T11:43:23,978 check.warn(importable) 2025-09-08T11:43:23,978 /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-08T11:43:23,979 !! 2025-09-08T11:43:23,979 ******************************************************************************** 2025-09-08T11:43:23,979 ############################ 2025-09-08T11:43:23,979 # Package would be ignored # 2025-09-08T11:43:23,979 ############################ 2025-09-08T11:43:23,979 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Variables' as an importable package[^1], 2025-09-08T11:43:23,979 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,979 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,979 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Variables' is explicitly added 2025-09-08T11:43:23,980 to the `packages` configuration field. 2025-09-08T11:43:23,980 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,980 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,980 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,980 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,980 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,980 If you don't want 'publiforge.Processors.Publidoc2DTBook.Variables' to be distributed and are 2025-09-08T11:43:23,980 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Variables' via 2025-09-08T11:43:23,981 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,981 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,981 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,981 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,981 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,981 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,981 even if it does not contain any `.py` files. 2025-09-08T11:43:23,981 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,982 directory, all directories are treated like packages. 2025-09-08T11:43:23,982 ******************************************************************************** 2025-09-08T11:43:23,982 !! 2025-09-08T11:43:23,982 check.warn(importable) 2025-09-08T11:43:23,982 /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-08T11:43:23,982 !! 2025-09-08T11:43:23,982 ******************************************************************************** 2025-09-08T11:43:23,982 ############################ 2025-09-08T11:43:23,982 # Package would be ignored # 2025-09-08T11:43:23,982 ############################ 2025-09-08T11:43:23,983 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Xsl' as an importable package[^1], 2025-09-08T11:43:23,983 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,983 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,983 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Xsl' is explicitly added 2025-09-08T11:43:23,983 to the `packages` configuration field. 2025-09-08T11:43:23,983 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,983 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,983 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,983 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,984 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,984 If you don't want 'publiforge.Processors.Publidoc2DTBook.Xsl' to be distributed and are 2025-09-08T11:43:23,984 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Xsl' via 2025-09-08T11:43:23,984 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,984 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,984 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,984 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,984 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,985 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,985 even if it does not contain any `.py` files. 2025-09-08T11:43:23,985 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,985 directory, all directories are treated like packages. 2025-09-08T11:43:23,985 ******************************************************************************** 2025-09-08T11:43:23,985 !! 2025-09-08T11:43:23,985 check.warn(importable) 2025-09-08T11:43:23,985 /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-08T11:43:23,985 !! 2025-09-08T11:43:23,986 ******************************************************************************** 2025-09-08T11:43:23,986 ############################ 2025-09-08T11:43:23,986 # Package would be ignored # 2025-09-08T11:43:23,986 ############################ 2025-09-08T11:43:23,986 Python recognizes 'publiforge.Processors.Publidoc2EPub2' as an importable package[^1], 2025-09-08T11:43:23,986 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,986 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,986 package, please make sure that 'publiforge.Processors.Publidoc2EPub2' is explicitly added 2025-09-08T11:43:23,986 to the `packages` configuration field. 2025-09-08T11:43:23,986 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,987 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,987 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,987 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,987 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,987 If you don't want 'publiforge.Processors.Publidoc2EPub2' to be distributed and are 2025-09-08T11:43:23,987 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2' via 2025-09-08T11:43:23,987 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,987 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,987 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,988 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,988 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,988 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,988 even if it does not contain any `.py` files. 2025-09-08T11:43:23,988 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,988 directory, all directories are treated like packages. 2025-09-08T11:43:23,988 ******************************************************************************** 2025-09-08T11:43:23,988 !! 2025-09-08T11:43:23,989 check.warn(importable) 2025-09-08T11:43:23,989 /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-08T11:43:23,989 !! 2025-09-08T11:43:23,989 ******************************************************************************** 2025-09-08T11:43:23,989 ############################ 2025-09-08T11:43:23,989 # Package would be ignored # 2025-09-08T11:43:23,989 ############################ 2025-09-08T11:43:23,989 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates' as an importable package[^1], 2025-09-08T11:43:23,989 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,989 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,990 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates' is explicitly added 2025-09-08T11:43:23,990 to the `packages` configuration field. 2025-09-08T11:43:23,990 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,990 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,990 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,990 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,990 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,990 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates' to be distributed and are 2025-09-08T11:43:23,991 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates' via 2025-09-08T11:43:23,991 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,991 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,991 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,991 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,991 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,991 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,991 even if it does not contain any `.py` files. 2025-09-08T11:43:23,992 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,992 directory, all directories are treated like packages. 2025-09-08T11:43:23,992 ******************************************************************************** 2025-09-08T11:43:23,992 !! 2025-09-08T11:43:23,992 check.warn(importable) 2025-09-08T11:43:23,992 /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-08T11:43:23,992 !! 2025-09-08T11:43:23,992 ******************************************************************************** 2025-09-08T11:43:23,992 ############################ 2025-09-08T11:43:23,993 # Package would be ignored # 2025-09-08T11:43:23,993 ############################ 2025-09-08T11:43:23,993 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' as an importable package[^1], 2025-09-08T11:43:23,993 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,993 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,993 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' is explicitly added 2025-09-08T11:43:23,993 to the `packages` configuration field. 2025-09-08T11:43:23,993 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,993 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,993 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,994 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,994 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,994 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' to be distributed and are 2025-09-08T11:43:23,994 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' via 2025-09-08T11:43:23,994 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,994 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,994 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,994 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,995 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,995 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,995 even if it does not contain any `.py` files. 2025-09-08T11:43:23,995 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,995 directory, all directories are treated like packages. 2025-09-08T11:43:23,995 ******************************************************************************** 2025-09-08T11:43:23,995 !! 2025-09-08T11:43:23,995 check.warn(importable) 2025-09-08T11:43:23,996 /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-08T11:43:23,996 !! 2025-09-08T11:43:23,996 ******************************************************************************** 2025-09-08T11:43:23,996 ############################ 2025-09-08T11:43:23,996 # Package would be ignored # 2025-09-08T11:43:23,996 ############################ 2025-09-08T11:43:23,996 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Variables' as an importable package[^1], 2025-09-08T11:43:23,996 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:23,996 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:23,996 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Variables' is explicitly added 2025-09-08T11:43:23,996 to the `packages` configuration field. 2025-09-08T11:43:23,997 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:23,997 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:23,997 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:23,997 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:23,997 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:23,997 If you don't want 'publiforge.Processors.Publidoc2EPub2.Variables' to be distributed and are 2025-09-08T11:43:23,997 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Variables' via 2025-09-08T11:43:23,997 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:23,998 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:23,998 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:23,998 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:23,998 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:23,998 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:23,998 even if it does not contain any `.py` files. 2025-09-08T11:43:23,998 On the other hand, currently there is no concept of package data 2025-09-08T11:43:23,998 directory, all directories are treated like packages. 2025-09-08T11:43:23,999 ******************************************************************************** 2025-09-08T11:43:23,999 !! 2025-09-08T11:43:23,999 check.warn(importable) 2025-09-08T11:43:23,999 /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-08T11:43:23,999 !! 2025-09-08T11:43:23,999 ******************************************************************************** 2025-09-08T11:43:23,999 ############################ 2025-09-08T11:43:23,999 # Package would be ignored # 2025-09-08T11:43:23,999 ############################ 2025-09-08T11:43:23,999 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Xsl' as an importable package[^1], 2025-09-08T11:43:24,000 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,000 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,000 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Xsl' is explicitly added 2025-09-08T11:43:24,000 to the `packages` configuration field. 2025-09-08T11:43:24,000 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,000 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,000 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,000 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,001 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,001 If you don't want 'publiforge.Processors.Publidoc2EPub2.Xsl' to be distributed and are 2025-09-08T11:43:24,001 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Xsl' via 2025-09-08T11:43:24,001 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,001 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,001 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,001 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,001 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,002 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,002 even if it does not contain any `.py` files. 2025-09-08T11:43:24,002 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,002 directory, all directories are treated like packages. 2025-09-08T11:43:24,002 ******************************************************************************** 2025-09-08T11:43:24,002 !! 2025-09-08T11:43:24,002 check.warn(importable) 2025-09-08T11:43:24,002 /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-08T11:43:24,002 !! 2025-09-08T11:43:24,002 ******************************************************************************** 2025-09-08T11:43:24,003 ############################ 2025-09-08T11:43:24,003 # Package would be ignored # 2025-09-08T11:43:24,003 ############################ 2025-09-08T11:43:24,003 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars' as an importable package[^1], 2025-09-08T11:43:24,003 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,003 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,003 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars' is explicitly added 2025-09-08T11:43:24,003 to the `packages` configuration field. 2025-09-08T11:43:24,003 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,003 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,004 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,004 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,004 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,004 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars' to be distributed and are 2025-09-08T11:43:24,004 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars' via 2025-09-08T11:43:24,004 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,004 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,004 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,005 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,005 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,005 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,005 even if it does not contain any `.py` files. 2025-09-08T11:43:24,005 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,005 directory, all directories are treated like packages. 2025-09-08T11:43:24,005 ******************************************************************************** 2025-09-08T11:43:24,006 !! 2025-09-08T11:43:24,006 check.warn(importable) 2025-09-08T11:43:24,006 /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-08T11:43:24,006 !! 2025-09-08T11:43:24,006 ******************************************************************************** 2025-09-08T11:43:24,006 ############################ 2025-09-08T11:43:24,006 # Package would be ignored # 2025-09-08T11:43:24,006 ############################ 2025-09-08T11:43:24,006 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.lib' as an importable package[^1], 2025-09-08T11:43:24,006 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,007 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,007 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.lib' is explicitly added 2025-09-08T11:43:24,007 to the `packages` configuration field. 2025-09-08T11:43:24,007 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,007 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,007 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,007 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,007 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,008 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.lib' to be distributed and are 2025-09-08T11:43:24,008 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.lib' via 2025-09-08T11:43:24,008 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,008 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,008 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,008 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,008 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,009 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,009 even if it does not contain any `.py` files. 2025-09-08T11:43:24,009 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,009 directory, all directories are treated like packages. 2025-09-08T11:43:24,009 ******************************************************************************** 2025-09-08T11:43:24,009 !! 2025-09-08T11:43:24,009 check.warn(importable) 2025-09-08T11:43:24,009 /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-08T11:43:24,009 !! 2025-09-08T11:43:24,009 ******************************************************************************** 2025-09-08T11:43:24,010 ############################ 2025-09-08T11:43:24,010 # Package would be ignored # 2025-09-08T11:43:24,010 ############################ 2025-09-08T11:43:24,010 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.licenses' as an importable package[^1], 2025-09-08T11:43:24,010 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,010 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,010 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.licenses' is explicitly added 2025-09-08T11:43:24,010 to the `packages` configuration field. 2025-09-08T11:43:24,010 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,010 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,010 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,011 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,011 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,011 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.licenses' to be distributed and are 2025-09-08T11:43:24,011 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.licenses' via 2025-09-08T11:43:24,011 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,011 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,011 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,011 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,012 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,012 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,012 even if it does not contain any `.py` files. 2025-09-08T11:43:24,012 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,012 directory, all directories are treated like packages. 2025-09-08T11:43:24,012 ******************************************************************************** 2025-09-08T11:43:24,012 !! 2025-09-08T11:43:24,012 check.warn(importable) 2025-09-08T11:43:24,013 /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-08T11:43:24,013 !! 2025-09-08T11:43:24,013 ******************************************************************************** 2025-09-08T11:43:24,013 ############################ 2025-09-08T11:43:24,013 # Package would be ignored # 2025-09-08T11:43:24,013 ############################ 2025-09-08T11:43:24,013 Python recognizes 'publiforge.Processors.Publidoc2EPub3' as an importable package[^1], 2025-09-08T11:43:24,013 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,013 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,013 package, please make sure that 'publiforge.Processors.Publidoc2EPub3' is explicitly added 2025-09-08T11:43:24,014 to the `packages` configuration field. 2025-09-08T11:43:24,014 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,014 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,014 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,014 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,014 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,014 If you don't want 'publiforge.Processors.Publidoc2EPub3' to be distributed and are 2025-09-08T11:43:24,014 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3' via 2025-09-08T11:43:24,015 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,015 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,015 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,015 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,015 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,015 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,015 even if it does not contain any `.py` files. 2025-09-08T11:43:24,015 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,016 directory, all directories are treated like packages. 2025-09-08T11:43:24,016 ******************************************************************************** 2025-09-08T11:43:24,016 !! 2025-09-08T11:43:24,016 check.warn(importable) 2025-09-08T11:43:24,016 /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-08T11:43:24,016 !! 2025-09-08T11:43:24,016 ******************************************************************************** 2025-09-08T11:43:24,016 ############################ 2025-09-08T11:43:24,016 # Package would be ignored # 2025-09-08T11:43:24,016 ############################ 2025-09-08T11:43:24,017 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates' as an importable package[^1], 2025-09-08T11:43:24,017 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,017 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,017 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates' is explicitly added 2025-09-08T11:43:24,017 to the `packages` configuration field. 2025-09-08T11:43:24,017 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,017 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,017 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,018 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,018 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,018 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates' to be distributed and are 2025-09-08T11:43:24,018 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates' via 2025-09-08T11:43:24,018 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,018 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,018 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,018 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,019 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,019 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,019 even if it does not contain any `.py` files. 2025-09-08T11:43:24,019 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,019 directory, all directories are treated like packages. 2025-09-08T11:43:24,019 ******************************************************************************** 2025-09-08T11:43:24,019 !! 2025-09-08T11:43:24,019 check.warn(importable) 2025-09-08T11:43:24,019 /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-08T11:43:24,020 !! 2025-09-08T11:43:24,020 ******************************************************************************** 2025-09-08T11:43:24,020 ############################ 2025-09-08T11:43:24,020 # Package would be ignored # 2025-09-08T11:43:24,020 ############################ 2025-09-08T11:43:24,020 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' as an importable package[^1], 2025-09-08T11:43:24,020 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,020 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,020 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' is explicitly added 2025-09-08T11:43:24,020 to the `packages` configuration field. 2025-09-08T11:43:24,021 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,021 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,021 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,021 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,021 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,021 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' to be distributed and are 2025-09-08T11:43:24,021 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' via 2025-09-08T11:43:24,021 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,022 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,022 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,022 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,022 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,022 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,022 even if it does not contain any `.py` files. 2025-09-08T11:43:24,022 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,022 directory, all directories are treated like packages. 2025-09-08T11:43:24,023 ******************************************************************************** 2025-09-08T11:43:24,023 !! 2025-09-08T11:43:24,023 check.warn(importable) 2025-09-08T11:43:24,023 /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-08T11:43:24,023 !! 2025-09-08T11:43:24,023 ******************************************************************************** 2025-09-08T11:43:24,023 ############################ 2025-09-08T11:43:24,023 # Package would be ignored # 2025-09-08T11:43:24,023 ############################ 2025-09-08T11:43:24,023 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Variables' as an importable package[^1], 2025-09-08T11:43:24,024 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,024 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,024 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Variables' is explicitly added 2025-09-08T11:43:24,024 to the `packages` configuration field. 2025-09-08T11:43:24,024 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,024 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,024 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,024 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,025 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,025 If you don't want 'publiforge.Processors.Publidoc2EPub3.Variables' to be distributed and are 2025-09-08T11:43:24,025 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Variables' via 2025-09-08T11:43:24,025 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,025 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,025 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,025 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,025 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,026 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,026 even if it does not contain any `.py` files. 2025-09-08T11:43:24,026 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,026 directory, all directories are treated like packages. 2025-09-08T11:43:24,026 ******************************************************************************** 2025-09-08T11:43:24,026 !! 2025-09-08T11:43:24,026 check.warn(importable) 2025-09-08T11:43:24,026 /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-08T11:43:24,026 !! 2025-09-08T11:43:24,026 ******************************************************************************** 2025-09-08T11:43:24,027 ############################ 2025-09-08T11:43:24,027 # Package would be ignored # 2025-09-08T11:43:24,027 ############################ 2025-09-08T11:43:24,027 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Xsl' as an importable package[^1], 2025-09-08T11:43:24,027 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,027 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,027 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Xsl' is explicitly added 2025-09-08T11:43:24,027 to the `packages` configuration field. 2025-09-08T11:43:24,027 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,027 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,028 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,028 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,028 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,028 If you don't want 'publiforge.Processors.Publidoc2EPub3.Xsl' to be distributed and are 2025-09-08T11:43:24,028 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Xsl' via 2025-09-08T11:43:24,028 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,028 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,028 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,029 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,029 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,029 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,029 even if it does not contain any `.py` files. 2025-09-08T11:43:24,029 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,029 directory, all directories are treated like packages. 2025-09-08T11:43:24,029 ******************************************************************************** 2025-09-08T11:43:24,029 !! 2025-09-08T11:43:24,030 check.warn(importable) 2025-09-08T11:43:24,030 /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-08T11:43:24,030 !! 2025-09-08T11:43:24,030 ******************************************************************************** 2025-09-08T11:43:24,030 ############################ 2025-09-08T11:43:24,030 # Package would be ignored # 2025-09-08T11:43:24,030 ############################ 2025-09-08T11:43:24,030 Python recognizes 'publiforge.Processors.Publidoc2Html5' as an importable package[^1], 2025-09-08T11:43:24,030 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,031 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,031 package, please make sure that 'publiforge.Processors.Publidoc2Html5' is explicitly added 2025-09-08T11:43:24,031 to the `packages` configuration field. 2025-09-08T11:43:24,031 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,031 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,031 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,031 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,031 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,032 If you don't want 'publiforge.Processors.Publidoc2Html5' to be distributed and are 2025-09-08T11:43:24,032 already explicitly excluding 'publiforge.Processors.Publidoc2Html5' via 2025-09-08T11:43:24,032 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,032 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,032 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,032 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,032 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,032 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,033 even if it does not contain any `.py` files. 2025-09-08T11:43:24,033 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,033 directory, all directories are treated like packages. 2025-09-08T11:43:24,033 ******************************************************************************** 2025-09-08T11:43:24,033 !! 2025-09-08T11:43:24,033 check.warn(importable) 2025-09-08T11:43:24,033 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Templates.Css' is absent from the `packages` configuration. 2025-09-08T11:43:24,033 !! 2025-09-08T11:43:24,033 ******************************************************************************** 2025-09-08T11:43:24,033 ############################ 2025-09-08T11:43:24,034 # Package would be ignored # 2025-09-08T11:43:24,034 ############################ 2025-09-08T11:43:24,034 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Css' as an importable package[^1], 2025-09-08T11:43:24,034 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,034 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,034 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Css' is explicitly added 2025-09-08T11:43:24,034 to the `packages` configuration field. 2025-09-08T11:43:24,034 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,034 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,035 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,035 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,035 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,035 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Css' to be distributed and are 2025-09-08T11:43:24,035 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Css' via 2025-09-08T11:43:24,035 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,035 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,035 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,036 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,036 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,036 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,036 even if it does not contain any `.py` files. 2025-09-08T11:43:24,036 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,036 directory, all directories are treated like packages. 2025-09-08T11:43:24,036 ******************************************************************************** 2025-09-08T11:43:24,036 !! 2025-09-08T11:43:24,036 check.warn(importable) 2025-09-08T11:43:24,037 /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-08T11:43:24,037 !! 2025-09-08T11:43:24,037 ******************************************************************************** 2025-09-08T11:43:24,037 ############################ 2025-09-08T11:43:24,037 # Package would be ignored # 2025-09-08T11:43:24,037 ############################ 2025-09-08T11:43:24,037 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Images' as an importable package[^1], 2025-09-08T11:43:24,037 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,037 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,037 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Images' is explicitly added 2025-09-08T11:43:24,038 to the `packages` configuration field. 2025-09-08T11:43:24,038 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,038 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,038 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,038 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,038 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,038 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Images' to be distributed and are 2025-09-08T11:43:24,038 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Images' via 2025-09-08T11:43:24,039 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,039 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,039 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,039 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,039 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,039 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,039 even if it does not contain any `.py` files. 2025-09-08T11:43:24,039 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,039 directory, all directories are treated like packages. 2025-09-08T11:43:24,040 ******************************************************************************** 2025-09-08T11:43:24,040 !! 2025-09-08T11:43:24,040 check.warn(importable) 2025-09-08T11:43:24,040 /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-08T11:43:24,040 !! 2025-09-08T11:43:24,040 ******************************************************************************** 2025-09-08T11:43:24,040 ############################ 2025-09-08T11:43:24,040 # Package would be ignored # 2025-09-08T11:43:24,040 ############################ 2025-09-08T11:43:24,040 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Js' as an importable package[^1], 2025-09-08T11:43:24,041 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,041 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,041 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Js' is explicitly added 2025-09-08T11:43:24,041 to the `packages` configuration field. 2025-09-08T11:43:24,041 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,041 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,041 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,041 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,042 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,042 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Js' to be distributed and are 2025-09-08T11:43:24,042 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Js' via 2025-09-08T11:43:24,042 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,042 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,042 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,042 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,042 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,043 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,043 even if it does not contain any `.py` files. 2025-09-08T11:43:24,043 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,043 directory, all directories are treated like packages. 2025-09-08T11:43:24,043 ******************************************************************************** 2025-09-08T11:43:24,043 !! 2025-09-08T11:43:24,043 check.warn(importable) 2025-09-08T11:43:24,043 /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-08T11:43:24,043 !! 2025-09-08T11:43:24,044 ******************************************************************************** 2025-09-08T11:43:24,044 ############################ 2025-09-08T11:43:24,044 # Package would be ignored # 2025-09-08T11:43:24,044 ############################ 2025-09-08T11:43:24,044 Python recognizes 'publiforge.Processors.Publidoc2Html5.Variables' as an importable package[^1], 2025-09-08T11:43:24,044 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,044 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,044 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Variables' is explicitly added 2025-09-08T11:43:24,044 to the `packages` configuration field. 2025-09-08T11:43:24,045 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,045 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,045 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,045 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,045 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,045 If you don't want 'publiforge.Processors.Publidoc2Html5.Variables' to be distributed and are 2025-09-08T11:43:24,045 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Variables' via 2025-09-08T11:43:24,045 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,045 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,046 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,046 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,046 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,046 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,046 even if it does not contain any `.py` files. 2025-09-08T11:43:24,046 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,046 directory, all directories are treated like packages. 2025-09-08T11:43:24,046 ******************************************************************************** 2025-09-08T11:43:24,047 !! 2025-09-08T11:43:24,047 check.warn(importable) 2025-09-08T11:43:24,047 /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-08T11:43:24,047 !! 2025-09-08T11:43:24,047 ******************************************************************************** 2025-09-08T11:43:24,047 ############################ 2025-09-08T11:43:24,047 # Package would be ignored # 2025-09-08T11:43:24,047 ############################ 2025-09-08T11:43:24,047 Python recognizes 'publiforge.Processors.Publidoc2Html5.Xsl' as an importable package[^1], 2025-09-08T11:43:24,047 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,048 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,048 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Xsl' is explicitly added 2025-09-08T11:43:24,048 to the `packages` configuration field. 2025-09-08T11:43:24,048 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,048 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,048 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,048 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,048 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,049 If you don't want 'publiforge.Processors.Publidoc2Html5.Xsl' to be distributed and are 2025-09-08T11:43:24,049 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Xsl' via 2025-09-08T11:43:24,049 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,049 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,049 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,049 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,049 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,049 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,050 even if it does not contain any `.py` files. 2025-09-08T11:43:24,050 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,050 directory, all directories are treated like packages. 2025-09-08T11:43:24,050 ******************************************************************************** 2025-09-08T11:43:24,050 !! 2025-09-08T11:43:24,050 check.warn(importable) 2025-09-08T11:43:24,050 /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-08T11:43:24,050 !! 2025-09-08T11:43:24,050 ******************************************************************************** 2025-09-08T11:43:24,050 ############################ 2025-09-08T11:43:24,051 # Package would be ignored # 2025-09-08T11:43:24,051 ############################ 2025-09-08T11:43:24,051 Python recognizes 'publiforge.Processors.Publidoc2Pdf' as an importable package[^1], 2025-09-08T11:43:24,051 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,051 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,051 package, please make sure that 'publiforge.Processors.Publidoc2Pdf' is explicitly added 2025-09-08T11:43:24,051 to the `packages` configuration field. 2025-09-08T11:43:24,051 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,051 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,051 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,052 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,052 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,052 If you don't want 'publiforge.Processors.Publidoc2Pdf' to be distributed and are 2025-09-08T11:43:24,052 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf' via 2025-09-08T11:43:24,052 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,052 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,052 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,052 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,053 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,053 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,053 even if it does not contain any `.py` files. 2025-09-08T11:43:24,053 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,053 directory, all directories are treated like packages. 2025-09-08T11:43:24,053 ******************************************************************************** 2025-09-08T11:43:24,053 !! 2025-09-08T11:43:24,053 check.warn(importable) 2025-09-08T11:43:24,053 /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-08T11:43:24,054 !! 2025-09-08T11:43:24,054 ******************************************************************************** 2025-09-08T11:43:24,054 ############################ 2025-09-08T11:43:24,054 # Package would be ignored # 2025-09-08T11:43:24,054 ############################ 2025-09-08T11:43:24,054 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Fonts' as an importable package[^1], 2025-09-08T11:43:24,054 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,054 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,054 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Fonts' is explicitly added 2025-09-08T11:43:24,054 to the `packages` configuration field. 2025-09-08T11:43:24,055 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,055 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,055 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,055 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,055 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,055 If you don't want 'publiforge.Processors.Publidoc2Pdf.Fonts' to be distributed and are 2025-09-08T11:43:24,055 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Fonts' via 2025-09-08T11:43:24,056 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,056 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,056 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,056 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,056 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,056 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,056 even if it does not contain any `.py` files. 2025-09-08T11:43:24,056 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,057 directory, all directories are treated like packages. 2025-09-08T11:43:24,057 ******************************************************************************** 2025-09-08T11:43:24,057 !! 2025-09-08T11:43:24,057 check.warn(importable) 2025-09-08T11:43:24,057 /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-08T11:43:24,057 !! 2025-09-08T11:43:24,057 ******************************************************************************** 2025-09-08T11:43:24,057 ############################ 2025-09-08T11:43:24,058 # Package would be ignored # 2025-09-08T11:43:24,058 ############################ 2025-09-08T11:43:24,058 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Regex' as an importable package[^1], 2025-09-08T11:43:24,058 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,058 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,058 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Regex' is explicitly added 2025-09-08T11:43:24,058 to the `packages` configuration field. 2025-09-08T11:43:24,058 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,058 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,058 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,059 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,059 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,059 If you don't want 'publiforge.Processors.Publidoc2Pdf.Regex' to be distributed and are 2025-09-08T11:43:24,059 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Regex' via 2025-09-08T11:43:24,059 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,059 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,059 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,059 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,060 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,060 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,060 even if it does not contain any `.py` files. 2025-09-08T11:43:24,060 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,060 directory, all directories are treated like packages. 2025-09-08T11:43:24,060 ******************************************************************************** 2025-09-08T11:43:24,060 !! 2025-09-08T11:43:24,060 check.warn(importable) 2025-09-08T11:43:24,060 /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-08T11:43:24,061 !! 2025-09-08T11:43:24,061 ******************************************************************************** 2025-09-08T11:43:24,061 ############################ 2025-09-08T11:43:24,061 # Package would be ignored # 2025-09-08T11:43:24,061 ############################ 2025-09-08T11:43:24,061 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Variables' as an importable package[^1], 2025-09-08T11:43:24,061 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,061 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,061 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Variables' is explicitly added 2025-09-08T11:43:24,061 to the `packages` configuration field. 2025-09-08T11:43:24,062 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,062 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,062 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,062 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,062 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,062 If you don't want 'publiforge.Processors.Publidoc2Pdf.Variables' to be distributed and are 2025-09-08T11:43:24,062 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Variables' via 2025-09-08T11:43:24,062 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,062 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,063 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,063 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,063 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,063 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,063 even if it does not contain any `.py` files. 2025-09-08T11:43:24,063 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,063 directory, all directories are treated like packages. 2025-09-08T11:43:24,063 ******************************************************************************** 2025-09-08T11:43:24,064 !! 2025-09-08T11:43:24,064 check.warn(importable) 2025-09-08T11:43:24,064 /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-08T11:43:24,064 !! 2025-09-08T11:43:24,064 ******************************************************************************** 2025-09-08T11:43:24,064 ############################ 2025-09-08T11:43:24,064 # Package would be ignored # 2025-09-08T11:43:24,064 ############################ 2025-09-08T11:43:24,064 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Xsl' as an importable package[^1], 2025-09-08T11:43:24,064 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,065 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,065 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Xsl' is explicitly added 2025-09-08T11:43:24,065 to the `packages` configuration field. 2025-09-08T11:43:24,065 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,065 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,065 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,065 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,065 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,066 If you don't want 'publiforge.Processors.Publidoc2Pdf.Xsl' to be distributed and are 2025-09-08T11:43:24,066 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Xsl' via 2025-09-08T11:43:24,066 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,066 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,066 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,066 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,066 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,067 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,067 even if it does not contain any `.py` files. 2025-09-08T11:43:24,067 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,067 directory, all directories are treated like packages. 2025-09-08T11:43:24,067 ******************************************************************************** 2025-09-08T11:43:24,067 !! 2025-09-08T11:43:24,067 check.warn(importable) 2025-09-08T11:43:24,067 /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-08T11:43:24,067 !! 2025-09-08T11:43:24,067 ******************************************************************************** 2025-09-08T11:43:24,068 ############################ 2025-09-08T11:43:24,068 # Package would be ignored # 2025-09-08T11:43:24,068 ############################ 2025-09-08T11:43:24,068 Python recognizes 'publiforge.Processors.Publidoc2XHtml' as an importable package[^1], 2025-09-08T11:43:24,068 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,068 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,068 package, please make sure that 'publiforge.Processors.Publidoc2XHtml' is explicitly added 2025-09-08T11:43:24,068 to the `packages` configuration field. 2025-09-08T11:43:24,068 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,068 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,069 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,069 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,069 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,069 If you don't want 'publiforge.Processors.Publidoc2XHtml' to be distributed and are 2025-09-08T11:43:24,069 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml' via 2025-09-08T11:43:24,069 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,069 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,069 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,070 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,070 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,070 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,070 even if it does not contain any `.py` files. 2025-09-08T11:43:24,070 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,070 directory, all directories are treated like packages. 2025-09-08T11:43:24,070 ******************************************************************************** 2025-09-08T11:43:24,071 !! 2025-09-08T11:43:24,071 check.warn(importable) 2025-09-08T11:43:24,071 /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-08T11:43:24,071 !! 2025-09-08T11:43:24,071 ******************************************************************************** 2025-09-08T11:43:24,071 ############################ 2025-09-08T11:43:24,071 # Package would be ignored # 2025-09-08T11:43:24,071 ############################ 2025-09-08T11:43:24,071 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Regex' as an importable package[^1], 2025-09-08T11:43:24,071 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,072 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,072 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Regex' is explicitly added 2025-09-08T11:43:24,072 to the `packages` configuration field. 2025-09-08T11:43:24,072 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,072 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,072 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,072 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,072 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,073 If you don't want 'publiforge.Processors.Publidoc2XHtml.Regex' to be distributed and are 2025-09-08T11:43:24,073 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Regex' via 2025-09-08T11:43:24,073 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,073 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,073 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,073 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,073 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,073 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,074 even if it does not contain any `.py` files. 2025-09-08T11:43:24,074 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,074 directory, all directories are treated like packages. 2025-09-08T11:43:24,074 ******************************************************************************** 2025-09-08T11:43:24,074 !! 2025-09-08T11:43:24,074 check.warn(importable) 2025-09-08T11:43:24,074 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Scss' is absent from the `packages` configuration. 2025-09-08T11:43:24,074 !! 2025-09-08T11:43:24,074 ******************************************************************************** 2025-09-08T11:43:24,074 ############################ 2025-09-08T11:43:24,075 # Package would be ignored # 2025-09-08T11:43:24,075 ############################ 2025-09-08T11:43:24,075 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Scss' as an importable package[^1], 2025-09-08T11:43:24,075 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,075 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,075 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Scss' is explicitly added 2025-09-08T11:43:24,075 to the `packages` configuration field. 2025-09-08T11:43:24,075 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,075 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,075 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,076 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,076 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,076 If you don't want 'publiforge.Processors.Publidoc2XHtml.Scss' to be distributed and are 2025-09-08T11:43:24,076 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Scss' via 2025-09-08T11:43:24,076 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,076 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,076 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,076 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,077 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,077 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,077 even if it does not contain any `.py` files. 2025-09-08T11:43:24,077 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,077 directory, all directories are treated like packages. 2025-09-08T11:43:24,077 ******************************************************************************** 2025-09-08T11:43:24,077 !! 2025-09-08T11:43:24,077 check.warn(importable) 2025-09-08T11:43:24,077 /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-08T11:43:24,078 !! 2025-09-08T11:43:24,078 ******************************************************************************** 2025-09-08T11:43:24,078 ############################ 2025-09-08T11:43:24,078 # Package would be ignored # 2025-09-08T11:43:24,078 ############################ 2025-09-08T11:43:24,078 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Css' as an importable package[^1], 2025-09-08T11:43:24,078 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,078 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,078 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Css' is explicitly added 2025-09-08T11:43:24,078 to the `packages` configuration field. 2025-09-08T11:43:24,079 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,079 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,079 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,079 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,079 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,079 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Css' to be distributed and are 2025-09-08T11:43:24,079 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Css' via 2025-09-08T11:43:24,079 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,079 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,080 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,080 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,080 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,080 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,080 even if it does not contain any `.py` files. 2025-09-08T11:43:24,080 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,080 directory, all directories are treated like packages. 2025-09-08T11:43:24,080 ******************************************************************************** 2025-09-08T11:43:24,081 !! 2025-09-08T11:43:24,081 check.warn(importable) 2025-09-08T11:43:24,081 /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-08T11:43:24,081 !! 2025-09-08T11:43:24,081 ******************************************************************************** 2025-09-08T11:43:24,081 ############################ 2025-09-08T11:43:24,081 # Package would be ignored # 2025-09-08T11:43:24,081 ############################ 2025-09-08T11:43:24,081 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Images' as an importable package[^1], 2025-09-08T11:43:24,082 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,082 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,082 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Images' is explicitly added 2025-09-08T11:43:24,082 to the `packages` configuration field. 2025-09-08T11:43:24,082 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,082 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,082 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,082 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,083 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,083 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Images' to be distributed and are 2025-09-08T11:43:24,083 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Images' via 2025-09-08T11:43:24,083 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,083 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,083 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,083 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,083 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,084 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,084 even if it does not contain any `.py` files. 2025-09-08T11:43:24,084 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,084 directory, all directories are treated like packages. 2025-09-08T11:43:24,084 ******************************************************************************** 2025-09-08T11:43:24,084 !! 2025-09-08T11:43:24,084 check.warn(importable) 2025-09-08T11:43:24,084 /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-08T11:43:24,084 !! 2025-09-08T11:43:24,085 ******************************************************************************** 2025-09-08T11:43:24,085 ############################ 2025-09-08T11:43:24,085 # Package would be ignored # 2025-09-08T11:43:24,085 ############################ 2025-09-08T11:43:24,085 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Js' as an importable package[^1], 2025-09-08T11:43:24,085 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,085 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,085 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Js' is explicitly added 2025-09-08T11:43:24,085 to the `packages` configuration field. 2025-09-08T11:43:24,085 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,086 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,086 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,086 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,086 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,086 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Js' to be distributed and are 2025-09-08T11:43:24,086 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Js' via 2025-09-08T11:43:24,086 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,086 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,086 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,087 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,087 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,087 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,087 even if it does not contain any `.py` files. 2025-09-08T11:43:24,087 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,087 directory, all directories are treated like packages. 2025-09-08T11:43:24,087 ******************************************************************************** 2025-09-08T11:43:24,087 !! 2025-09-08T11:43:24,088 check.warn(importable) 2025-09-08T11:43:24,088 /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-08T11:43:24,088 !! 2025-09-08T11:43:24,088 ******************************************************************************** 2025-09-08T11:43:24,088 ############################ 2025-09-08T11:43:24,088 # Package would be ignored # 2025-09-08T11:43:24,088 ############################ 2025-09-08T11:43:24,088 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Variables' as an importable package[^1], 2025-09-08T11:43:24,088 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,088 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,089 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Variables' is explicitly added 2025-09-08T11:43:24,089 to the `packages` configuration field. 2025-09-08T11:43:24,089 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,089 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,089 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,089 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,089 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,089 If you don't want 'publiforge.Processors.Publidoc2XHtml.Variables' to be distributed and are 2025-09-08T11:43:24,090 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Variables' via 2025-09-08T11:43:24,090 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,090 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,090 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,090 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,090 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,090 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,090 even if it does not contain any `.py` files. 2025-09-08T11:43:24,090 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,091 directory, all directories are treated like packages. 2025-09-08T11:43:24,091 ******************************************************************************** 2025-09-08T11:43:24,091 !! 2025-09-08T11:43:24,091 check.warn(importable) 2025-09-08T11:43:24,091 /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-08T11:43:24,091 !! 2025-09-08T11:43:24,091 ******************************************************************************** 2025-09-08T11:43:24,091 ############################ 2025-09-08T11:43:24,091 # Package would be ignored # 2025-09-08T11:43:24,091 ############################ 2025-09-08T11:43:24,092 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Xsl' as an importable package[^1], 2025-09-08T11:43:24,092 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,092 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,092 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Xsl' is explicitly added 2025-09-08T11:43:24,092 to the `packages` configuration field. 2025-09-08T11:43:24,092 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,092 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,092 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,092 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,093 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,093 If you don't want 'publiforge.Processors.Publidoc2XHtml.Xsl' to be distributed and are 2025-09-08T11:43:24,093 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Xsl' via 2025-09-08T11:43:24,093 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,093 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,093 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,093 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,093 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,094 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,094 even if it does not contain any `.py` files. 2025-09-08T11:43:24,094 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,094 directory, all directories are treated like packages. 2025-09-08T11:43:24,094 ******************************************************************************** 2025-09-08T11:43:24,094 !! 2025-09-08T11:43:24,094 check.warn(importable) 2025-09-08T11:43:24,094 /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-08T11:43:24,095 !! 2025-09-08T11:43:24,095 ******************************************************************************** 2025-09-08T11:43:24,095 ############################ 2025-09-08T11:43:24,095 # Package would be ignored # 2025-09-08T11:43:24,095 ############################ 2025-09-08T11:43:24,095 Python recognizes 'publiforge.Processors.PublidocClean' as an importable package[^1], 2025-09-08T11:43:24,095 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,095 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,095 package, please make sure that 'publiforge.Processors.PublidocClean' is explicitly added 2025-09-08T11:43:24,095 to the `packages` configuration field. 2025-09-08T11:43:24,096 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,096 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,096 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,096 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,096 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,096 If you don't want 'publiforge.Processors.PublidocClean' to be distributed and are 2025-09-08T11:43:24,096 already explicitly excluding 'publiforge.Processors.PublidocClean' via 2025-09-08T11:43:24,096 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,097 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,097 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,097 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,097 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,097 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,097 even if it does not contain any `.py` files. 2025-09-08T11:43:24,097 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,097 directory, all directories are treated like packages. 2025-09-08T11:43:24,098 ******************************************************************************** 2025-09-08T11:43:24,098 !! 2025-09-08T11:43:24,098 check.warn(importable) 2025-09-08T11:43:24,098 /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-08T11:43:24,098 !! 2025-09-08T11:43:24,098 ******************************************************************************** 2025-09-08T11:43:24,098 ############################ 2025-09-08T11:43:24,098 # Package would be ignored # 2025-09-08T11:43:24,098 ############################ 2025-09-08T11:43:24,098 Python recognizes 'publiforge.Processors.PublidocClean.Regex' as an importable package[^1], 2025-09-08T11:43:24,099 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,099 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,099 package, please make sure that 'publiforge.Processors.PublidocClean.Regex' is explicitly added 2025-09-08T11:43:24,099 to the `packages` configuration field. 2025-09-08T11:43:24,099 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,099 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,099 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,099 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,100 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,100 If you don't want 'publiforge.Processors.PublidocClean.Regex' to be distributed and are 2025-09-08T11:43:24,100 already explicitly excluding 'publiforge.Processors.PublidocClean.Regex' via 2025-09-08T11:43:24,100 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,100 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,100 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,100 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,100 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,101 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,101 even if it does not contain any `.py` files. 2025-09-08T11:43:24,101 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,101 directory, all directories are treated like packages. 2025-09-08T11:43:24,101 ******************************************************************************** 2025-09-08T11:43:24,101 !! 2025-09-08T11:43:24,101 check.warn(importable) 2025-09-08T11:43:24,101 /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-08T11:43:24,101 !! 2025-09-08T11:43:24,101 ******************************************************************************** 2025-09-08T11:43:24,102 ############################ 2025-09-08T11:43:24,102 # Package would be ignored # 2025-09-08T11:43:24,102 ############################ 2025-09-08T11:43:24,102 Python recognizes 'publiforge.Processors.PublidocClean.Variables' as an importable package[^1], 2025-09-08T11:43:24,102 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,102 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,102 package, please make sure that 'publiforge.Processors.PublidocClean.Variables' is explicitly added 2025-09-08T11:43:24,102 to the `packages` configuration field. 2025-09-08T11:43:24,102 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,102 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,103 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,103 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,103 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,103 If you don't want 'publiforge.Processors.PublidocClean.Variables' to be distributed and are 2025-09-08T11:43:24,103 already explicitly excluding 'publiforge.Processors.PublidocClean.Variables' via 2025-09-08T11:43:24,103 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,103 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,103 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,104 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,104 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,104 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,104 even if it does not contain any `.py` files. 2025-09-08T11:43:24,104 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,104 directory, all directories are treated like packages. 2025-09-08T11:43:24,104 ******************************************************************************** 2025-09-08T11:43:24,104 !! 2025-09-08T11:43:24,105 check.warn(importable) 2025-09-08T11:43:24,105 /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-08T11:43:24,105 !! 2025-09-08T11:43:24,105 ******************************************************************************** 2025-09-08T11:43:24,105 ############################ 2025-09-08T11:43:24,105 # Package would be ignored # 2025-09-08T11:43:24,105 ############################ 2025-09-08T11:43:24,105 Python recognizes 'publiforge.Processors.PublidocClean.Xsl' as an importable package[^1], 2025-09-08T11:43:24,105 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,105 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,105 package, please make sure that 'publiforge.Processors.PublidocClean.Xsl' is explicitly added 2025-09-08T11:43:24,106 to the `packages` configuration field. 2025-09-08T11:43:24,106 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,106 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,106 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,106 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,106 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,106 If you don't want 'publiforge.Processors.PublidocClean.Xsl' to be distributed and are 2025-09-08T11:43:24,106 already explicitly excluding 'publiforge.Processors.PublidocClean.Xsl' via 2025-09-08T11:43:24,107 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,107 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,107 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,107 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,107 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,107 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,108 even if it does not contain any `.py` files. 2025-09-08T11:43:24,108 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,108 directory, all directories are treated like packages. 2025-09-08T11:43:24,108 ******************************************************************************** 2025-09-08T11:43:24,108 !! 2025-09-08T11:43:24,108 check.warn(importable) 2025-09-08T11:43:24,108 /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-08T11:43:24,108 !! 2025-09-08T11:43:24,108 ******************************************************************************** 2025-09-08T11:43:24,109 ############################ 2025-09-08T11:43:24,109 # Package would be ignored # 2025-09-08T11:43:24,109 ############################ 2025-09-08T11:43:24,109 Python recognizes 'publiforge.Processors.PublidocValid' as an importable package[^1], 2025-09-08T11:43:24,109 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,109 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,109 package, please make sure that 'publiforge.Processors.PublidocValid' is explicitly added 2025-09-08T11:43:24,109 to the `packages` configuration field. 2025-09-08T11:43:24,109 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,109 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,109 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,110 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,110 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,110 If you don't want 'publiforge.Processors.PublidocValid' to be distributed and are 2025-09-08T11:43:24,110 already explicitly excluding 'publiforge.Processors.PublidocValid' via 2025-09-08T11:43:24,110 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,110 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,110 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,110 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,111 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,111 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,111 even if it does not contain any `.py` files. 2025-09-08T11:43:24,111 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,111 directory, all directories are treated like packages. 2025-09-08T11:43:24,111 ******************************************************************************** 2025-09-08T11:43:24,111 !! 2025-09-08T11:43:24,111 check.warn(importable) 2025-09-08T11:43:24,112 /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-08T11:43:24,112 !! 2025-09-08T11:43:24,112 ******************************************************************************** 2025-09-08T11:43:24,112 ############################ 2025-09-08T11:43:24,112 # Package would be ignored # 2025-09-08T11:43:24,112 ############################ 2025-09-08T11:43:24,112 Python recognizes 'publiforge.Processors.PublidocValid.RelaxNG' as an importable package[^1], 2025-09-08T11:43:24,112 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,112 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,112 package, please make sure that 'publiforge.Processors.PublidocValid.RelaxNG' is explicitly added 2025-09-08T11:43:24,112 to the `packages` configuration field. 2025-09-08T11:43:24,113 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,113 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,113 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,113 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,113 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,113 If you don't want 'publiforge.Processors.PublidocValid.RelaxNG' to be distributed and are 2025-09-08T11:43:24,113 already explicitly excluding 'publiforge.Processors.PublidocValid.RelaxNG' via 2025-09-08T11:43:24,113 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,114 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,114 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,114 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,114 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,114 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,114 even if it does not contain any `.py` files. 2025-09-08T11:43:24,114 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,114 directory, all directories are treated like packages. 2025-09-08T11:43:24,115 ******************************************************************************** 2025-09-08T11:43:24,115 !! 2025-09-08T11:43:24,115 check.warn(importable) 2025-09-08T11:43:24,115 /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-08T11:43:24,115 !! 2025-09-08T11:43:24,115 ******************************************************************************** 2025-09-08T11:43:24,115 ############################ 2025-09-08T11:43:24,115 # Package would be ignored # 2025-09-08T11:43:24,115 ############################ 2025-09-08T11:43:24,115 Python recognizes 'publiforge.Processors.Publiquiz2EPub3' as an importable package[^1], 2025-09-08T11:43:24,116 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,116 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,116 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3' is explicitly added 2025-09-08T11:43:24,116 to the `packages` configuration field. 2025-09-08T11:43:24,116 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,116 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,116 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,116 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,116 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,117 If you don't want 'publiforge.Processors.Publiquiz2EPub3' to be distributed and are 2025-09-08T11:43:24,117 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3' via 2025-09-08T11:43:24,117 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,117 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,117 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,117 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,117 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,118 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,118 even if it does not contain any `.py` files. 2025-09-08T11:43:24,118 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,118 directory, all directories are treated like packages. 2025-09-08T11:43:24,118 ******************************************************************************** 2025-09-08T11:43:24,118 !! 2025-09-08T11:43:24,118 check.warn(importable) 2025-09-08T11:43:24,118 /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-08T11:43:24,118 !! 2025-09-08T11:43:24,118 ******************************************************************************** 2025-09-08T11:43:24,119 ############################ 2025-09-08T11:43:24,119 # Package would be ignored # 2025-09-08T11:43:24,119 ############################ 2025-09-08T11:43:24,119 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Variables' as an importable package[^1], 2025-09-08T11:43:24,119 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,119 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,119 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Variables' is explicitly added 2025-09-08T11:43:24,119 to the `packages` configuration field. 2025-09-08T11:43:24,119 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,119 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,119 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,120 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,120 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,120 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Variables' to be distributed and are 2025-09-08T11:43:24,120 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Variables' via 2025-09-08T11:43:24,120 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,120 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,120 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,121 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,121 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,121 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,121 even if it does not contain any `.py` files. 2025-09-08T11:43:24,121 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,121 directory, all directories are treated like packages. 2025-09-08T11:43:24,121 ******************************************************************************** 2025-09-08T11:43:24,122 !! 2025-09-08T11:43:24,122 check.warn(importable) 2025-09-08T11:43:24,122 /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-08T11:43:24,122 !! 2025-09-08T11:43:24,122 ******************************************************************************** 2025-09-08T11:43:24,122 ############################ 2025-09-08T11:43:24,122 # Package would be ignored # 2025-09-08T11:43:24,122 ############################ 2025-09-08T11:43:24,122 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Xsl' as an importable package[^1], 2025-09-08T11:43:24,122 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,123 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,123 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Xsl' is explicitly added 2025-09-08T11:43:24,123 to the `packages` configuration field. 2025-09-08T11:43:24,123 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,123 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,123 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,123 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,123 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,124 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Xsl' to be distributed and are 2025-09-08T11:43:24,124 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Xsl' via 2025-09-08T11:43:24,124 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,124 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,124 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,124 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,124 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,124 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,125 even if it does not contain any `.py` files. 2025-09-08T11:43:24,125 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,125 directory, all directories are treated like packages. 2025-09-08T11:43:24,125 ******************************************************************************** 2025-09-08T11:43:24,125 !! 2025-09-08T11:43:24,125 check.warn(importable) 2025-09-08T11:43:24,125 /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-08T11:43:24,125 !! 2025-09-08T11:43:24,125 ******************************************************************************** 2025-09-08T11:43:24,125 ############################ 2025-09-08T11:43:24,126 # Package would be ignored # 2025-09-08T11:43:24,126 ############################ 2025-09-08T11:43:24,126 Python recognizes 'publiforge.Processors.Publiquiz2Html5' as an importable package[^1], 2025-09-08T11:43:24,126 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,126 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,126 package, please make sure that 'publiforge.Processors.Publiquiz2Html5' is explicitly added 2025-09-08T11:43:24,126 to the `packages` configuration field. 2025-09-08T11:43:24,126 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,126 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,126 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,127 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,127 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,127 If you don't want 'publiforge.Processors.Publiquiz2Html5' to be distributed and are 2025-09-08T11:43:24,127 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5' via 2025-09-08T11:43:24,127 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,127 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,127 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,127 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,128 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,128 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,128 even if it does not contain any `.py` files. 2025-09-08T11:43:24,128 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,128 directory, all directories are treated like packages. 2025-09-08T11:43:24,128 ******************************************************************************** 2025-09-08T11:43:24,128 !! 2025-09-08T11:43:24,128 check.warn(importable) 2025-09-08T11:43:24,128 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Scss' is absent from the `packages` configuration. 2025-09-08T11:43:24,129 !! 2025-09-08T11:43:24,129 ******************************************************************************** 2025-09-08T11:43:24,129 ############################ 2025-09-08T11:43:24,129 # Package would be ignored # 2025-09-08T11:43:24,129 ############################ 2025-09-08T11:43:24,129 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Scss' as an importable package[^1], 2025-09-08T11:43:24,129 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,129 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,129 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Scss' is explicitly added 2025-09-08T11:43:24,129 to the `packages` configuration field. 2025-09-08T11:43:24,130 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,130 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,130 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,130 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,130 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,130 If you don't want 'publiforge.Processors.Publiquiz2Html5.Scss' to be distributed and are 2025-09-08T11:43:24,130 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Scss' via 2025-09-08T11:43:24,130 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,131 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,131 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,131 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,131 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,131 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,131 even if it does not contain any `.py` files. 2025-09-08T11:43:24,131 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,131 directory, all directories are treated like packages. 2025-09-08T11:43:24,131 ******************************************************************************** 2025-09-08T11:43:24,132 !! 2025-09-08T11:43:24,132 check.warn(importable) 2025-09-08T11:43:24,132 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' is absent from the `packages` configuration. 2025-09-08T11:43:24,132 !! 2025-09-08T11:43:24,132 ******************************************************************************** 2025-09-08T11:43:24,132 ############################ 2025-09-08T11:43:24,132 # Package would be ignored # 2025-09-08T11:43:24,132 ############################ 2025-09-08T11:43:24,132 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' as an importable package[^1], 2025-09-08T11:43:24,132 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,133 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,133 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' is explicitly added 2025-09-08T11:43:24,133 to the `packages` configuration field. 2025-09-08T11:43:24,133 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,133 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,133 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,133 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,134 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,134 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' to be distributed and are 2025-09-08T11:43:24,134 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' via 2025-09-08T11:43:24,134 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,134 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,134 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,134 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,134 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,135 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,135 even if it does not contain any `.py` files. 2025-09-08T11:43:24,135 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,135 directory, all directories are treated like packages. 2025-09-08T11:43:24,135 ******************************************************************************** 2025-09-08T11:43:24,135 !! 2025-09-08T11:43:24,135 check.warn(importable) 2025-09-08T11:43:24,135 /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-08T11:43:24,135 !! 2025-09-08T11:43:24,136 ******************************************************************************** 2025-09-08T11:43:24,136 ############################ 2025-09-08T11:43:24,136 # Package would be ignored # 2025-09-08T11:43:24,136 ############################ 2025-09-08T11:43:24,136 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Css' as an importable package[^1], 2025-09-08T11:43:24,136 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,136 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,136 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Css' is explicitly added 2025-09-08T11:43:24,136 to the `packages` configuration field. 2025-09-08T11:43:24,136 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,137 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,137 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,137 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,137 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,137 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Css' to be distributed and are 2025-09-08T11:43:24,137 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Css' via 2025-09-08T11:43:24,137 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,137 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,137 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,138 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,138 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,138 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,138 even if it does not contain any `.py` files. 2025-09-08T11:43:24,138 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,138 directory, all directories are treated like packages. 2025-09-08T11:43:24,138 ******************************************************************************** 2025-09-08T11:43:24,138 !! 2025-09-08T11:43:24,139 check.warn(importable) 2025-09-08T11:43:24,139 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' is absent from the `packages` configuration. 2025-09-08T11:43:24,139 !! 2025-09-08T11:43:24,139 ******************************************************************************** 2025-09-08T11:43:24,139 ############################ 2025-09-08T11:43:24,139 # Package would be ignored # 2025-09-08T11:43:24,139 ############################ 2025-09-08T11:43:24,139 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' as an importable package[^1], 2025-09-08T11:43:24,139 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,139 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,140 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' is explicitly added 2025-09-08T11:43:24,140 to the `packages` configuration field. 2025-09-08T11:43:24,140 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,140 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,140 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,140 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,140 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,140 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' to be distributed and are 2025-09-08T11:43:24,140 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' via 2025-09-08T11:43:24,141 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,141 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,141 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,141 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,141 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,141 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,141 even if it does not contain any `.py` files. 2025-09-08T11:43:24,141 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,142 directory, all directories are treated like packages. 2025-09-08T11:43:24,142 ******************************************************************************** 2025-09-08T11:43:24,142 !! 2025-09-08T11:43:24,142 check.warn(importable) 2025-09-08T11:43:24,142 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Images' is absent from the `packages` configuration. 2025-09-08T11:43:24,142 !! 2025-09-08T11:43:24,142 ******************************************************************************** 2025-09-08T11:43:24,142 ############################ 2025-09-08T11:43:24,142 # Package would be ignored # 2025-09-08T11:43:24,142 ############################ 2025-09-08T11:43:24,143 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Images' as an importable package[^1], 2025-09-08T11:43:24,143 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,143 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,143 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Images' is explicitly added 2025-09-08T11:43:24,143 to the `packages` configuration field. 2025-09-08T11:43:24,143 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,143 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,143 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,143 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,144 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,144 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Images' to be distributed and are 2025-09-08T11:43:24,144 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Images' via 2025-09-08T11:43:24,144 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,144 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,144 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,144 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,144 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,145 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,145 even if it does not contain any `.py` files. 2025-09-08T11:43:24,145 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,145 directory, all directories are treated like packages. 2025-09-08T11:43:24,145 ******************************************************************************** 2025-09-08T11:43:24,145 !! 2025-09-08T11:43:24,145 check.warn(importable) 2025-09-08T11:43:24,145 /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-08T11:43:24,145 !! 2025-09-08T11:43:24,146 ******************************************************************************** 2025-09-08T11:43:24,146 ############################ 2025-09-08T11:43:24,146 # Package would be ignored # 2025-09-08T11:43:24,146 ############################ 2025-09-08T11:43:24,146 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Js' as an importable package[^1], 2025-09-08T11:43:24,146 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,146 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,146 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Js' is explicitly added 2025-09-08T11:43:24,146 to the `packages` configuration field. 2025-09-08T11:43:24,147 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,147 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,147 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,147 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,147 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,147 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Js' to be distributed and are 2025-09-08T11:43:24,147 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Js' via 2025-09-08T11:43:24,147 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,147 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,148 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,148 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,148 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,148 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,148 even if it does not contain any `.py` files. 2025-09-08T11:43:24,148 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,148 directory, all directories are treated like packages. 2025-09-08T11:43:24,148 ******************************************************************************** 2025-09-08T11:43:24,149 !! 2025-09-08T11:43:24,149 check.warn(importable) 2025-09-08T11:43:24,149 /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-08T11:43:24,149 !! 2025-09-08T11:43:24,149 ******************************************************************************** 2025-09-08T11:43:24,149 ############################ 2025-09-08T11:43:24,149 # Package would be ignored # 2025-09-08T11:43:24,149 ############################ 2025-09-08T11:43:24,149 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Variables' as an importable package[^1], 2025-09-08T11:43:24,149 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,150 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,150 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Variables' is explicitly added 2025-09-08T11:43:24,150 to the `packages` configuration field. 2025-09-08T11:43:24,150 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,150 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,150 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,150 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,150 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,151 If you don't want 'publiforge.Processors.Publiquiz2Html5.Variables' to be distributed and are 2025-09-08T11:43:24,151 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Variables' via 2025-09-08T11:43:24,151 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,151 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,151 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,151 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,151 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,151 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,152 even if it does not contain any `.py` files. 2025-09-08T11:43:24,152 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,152 directory, all directories are treated like packages. 2025-09-08T11:43:24,152 ******************************************************************************** 2025-09-08T11:43:24,152 !! 2025-09-08T11:43:24,152 check.warn(importable) 2025-09-08T11:43:24,152 /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-08T11:43:24,152 !! 2025-09-08T11:43:24,152 ******************************************************************************** 2025-09-08T11:43:24,152 ############################ 2025-09-08T11:43:24,153 # Package would be ignored # 2025-09-08T11:43:24,153 ############################ 2025-09-08T11:43:24,153 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Xsl' as an importable package[^1], 2025-09-08T11:43:24,153 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,153 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,153 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Xsl' is explicitly added 2025-09-08T11:43:24,153 to the `packages` configuration field. 2025-09-08T11:43:24,153 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,153 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,153 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,154 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,154 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,154 If you don't want 'publiforge.Processors.Publiquiz2Html5.Xsl' to be distributed and are 2025-09-08T11:43:24,154 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Xsl' via 2025-09-08T11:43:24,154 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,154 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,154 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,154 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,155 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,155 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,155 even if it does not contain any `.py` files. 2025-09-08T11:43:24,155 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,155 directory, all directories are treated like packages. 2025-09-08T11:43:24,155 ******************************************************************************** 2025-09-08T11:43:24,155 !! 2025-09-08T11:43:24,155 check.warn(importable) 2025-09-08T11:43:24,156 /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-08T11:43:24,156 !! 2025-09-08T11:43:24,156 ******************************************************************************** 2025-09-08T11:43:24,156 ############################ 2025-09-08T11:43:24,156 # Package would be ignored # 2025-09-08T11:43:24,156 ############################ 2025-09-08T11:43:24,156 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12' as an importable package[^1], 2025-09-08T11:43:24,156 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,156 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,156 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12' is explicitly added 2025-09-08T11:43:24,156 to the `packages` configuration field. 2025-09-08T11:43:24,157 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,157 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,157 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,157 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,157 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,157 If you don't want 'publiforge.Processors.Publiquiz2Scorm12' to be distributed and are 2025-09-08T11:43:24,157 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12' via 2025-09-08T11:43:24,158 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,158 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,158 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,158 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,158 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,158 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,158 even if it does not contain any `.py` files. 2025-09-08T11:43:24,159 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,159 directory, all directories are treated like packages. 2025-09-08T11:43:24,159 ******************************************************************************** 2025-09-08T11:43:24,159 !! 2025-09-08T11:43:24,159 check.warn(importable) 2025-09-08T11:43:24,159 /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-08T11:43:24,159 !! 2025-09-08T11:43:24,159 ******************************************************************************** 2025-09-08T11:43:24,159 ############################ 2025-09-08T11:43:24,159 # Package would be ignored # 2025-09-08T11:43:24,160 ############################ 2025-09-08T11:43:24,160 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates' as an importable package[^1], 2025-09-08T11:43:24,160 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,160 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,160 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates' is explicitly added 2025-09-08T11:43:24,160 to the `packages` configuration field. 2025-09-08T11:43:24,160 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,160 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,160 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,161 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,161 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,161 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates' to be distributed and are 2025-09-08T11:43:24,161 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates' via 2025-09-08T11:43:24,161 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,161 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,161 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,161 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,162 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,162 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,162 even if it does not contain any `.py` files. 2025-09-08T11:43:24,162 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,162 directory, all directories are treated like packages. 2025-09-08T11:43:24,162 ******************************************************************************** 2025-09-08T11:43:24,162 !! 2025-09-08T11:43:24,162 check.warn(importable) 2025-09-08T11:43:24,162 /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-08T11:43:24,163 !! 2025-09-08T11:43:24,163 ******************************************************************************** 2025-09-08T11:43:24,163 ############################ 2025-09-08T11:43:24,163 # Package would be ignored # 2025-09-08T11:43:24,163 ############################ 2025-09-08T11:43:24,163 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' as an importable package[^1], 2025-09-08T11:43:24,163 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,163 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,163 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' is explicitly added 2025-09-08T11:43:24,163 to the `packages` configuration field. 2025-09-08T11:43:24,164 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,164 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,164 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,164 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,164 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,164 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' to be distributed and are 2025-09-08T11:43:24,164 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' via 2025-09-08T11:43:24,164 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,165 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,165 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,165 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,165 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,165 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,165 even if it does not contain any `.py` files. 2025-09-08T11:43:24,165 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,165 directory, all directories are treated like packages. 2025-09-08T11:43:24,165 ******************************************************************************** 2025-09-08T11:43:24,166 !! 2025-09-08T11:43:24,166 check.warn(importable) 2025-09-08T11:43:24,166 /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-08T11:43:24,166 !! 2025-09-08T11:43:24,166 ******************************************************************************** 2025-09-08T11:43:24,166 ############################ 2025-09-08T11:43:24,166 # Package would be ignored # 2025-09-08T11:43:24,166 ############################ 2025-09-08T11:43:24,166 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' as an importable package[^1], 2025-09-08T11:43:24,166 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,167 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,167 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' is explicitly added 2025-09-08T11:43:24,167 to the `packages` configuration field. 2025-09-08T11:43:24,167 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,167 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,167 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,167 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,167 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,168 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' to be distributed and are 2025-09-08T11:43:24,168 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' via 2025-09-08T11:43:24,168 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,168 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,168 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,168 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,168 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,168 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,169 even if it does not contain any `.py` files. 2025-09-08T11:43:24,169 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,169 directory, all directories are treated like packages. 2025-09-08T11:43:24,169 ******************************************************************************** 2025-09-08T11:43:24,169 !! 2025-09-08T11:43:24,169 check.warn(importable) 2025-09-08T11:43:24,169 /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-08T11:43:24,169 !! 2025-09-08T11:43:24,169 ******************************************************************************** 2025-09-08T11:43:24,169 ############################ 2025-09-08T11:43:24,170 # Package would be ignored # 2025-09-08T11:43:24,170 ############################ 2025-09-08T11:43:24,170 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' as an importable package[^1], 2025-09-08T11:43:24,170 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,170 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,170 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' is explicitly added 2025-09-08T11:43:24,170 to the `packages` configuration field. 2025-09-08T11:43:24,170 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,170 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,171 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,171 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,171 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,171 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' to be distributed and are 2025-09-08T11:43:24,171 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' via 2025-09-08T11:43:24,171 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,171 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,171 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,172 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,172 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,172 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,172 even if it does not contain any `.py` files. 2025-09-08T11:43:24,172 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,172 directory, all directories are treated like packages. 2025-09-08T11:43:24,172 ******************************************************************************** 2025-09-08T11:43:24,172 !! 2025-09-08T11:43:24,173 check.warn(importable) 2025-09-08T11:43:24,173 /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-08T11:43:24,173 !! 2025-09-08T11:43:24,173 ******************************************************************************** 2025-09-08T11:43:24,173 ############################ 2025-09-08T11:43:24,173 # Package would be ignored # 2025-09-08T11:43:24,173 ############################ 2025-09-08T11:43:24,173 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Variables' as an importable package[^1], 2025-09-08T11:43:24,173 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,173 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,174 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Variables' is explicitly added 2025-09-08T11:43:24,174 to the `packages` configuration field. 2025-09-08T11:43:24,174 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,174 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,174 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,174 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,174 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,174 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Variables' to be distributed and are 2025-09-08T11:43:24,175 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Variables' via 2025-09-08T11:43:24,175 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,175 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,175 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,175 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,175 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,175 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,175 even if it does not contain any `.py` files. 2025-09-08T11:43:24,176 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,176 directory, all directories are treated like packages. 2025-09-08T11:43:24,176 ******************************************************************************** 2025-09-08T11:43:24,176 !! 2025-09-08T11:43:24,176 check.warn(importable) 2025-09-08T11:43:24,176 /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-08T11:43:24,176 !! 2025-09-08T11:43:24,176 ******************************************************************************** 2025-09-08T11:43:24,176 ############################ 2025-09-08T11:43:24,176 # Package would be ignored # 2025-09-08T11:43:24,176 ############################ 2025-09-08T11:43:24,177 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Xsl' as an importable package[^1], 2025-09-08T11:43:24,177 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,177 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,177 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Xsl' is explicitly added 2025-09-08T11:43:24,177 to the `packages` configuration field. 2025-09-08T11:43:24,177 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,177 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,177 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,177 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,178 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,178 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Xsl' to be distributed and are 2025-09-08T11:43:24,178 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Xsl' via 2025-09-08T11:43:24,178 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,178 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,178 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,178 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,178 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,179 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,179 even if it does not contain any `.py` files. 2025-09-08T11:43:24,179 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,179 directory, all directories are treated like packages. 2025-09-08T11:43:24,179 ******************************************************************************** 2025-09-08T11:43:24,179 !! 2025-09-08T11:43:24,179 check.warn(importable) 2025-09-08T11:43:24,179 /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-08T11:43:24,179 !! 2025-09-08T11:43:24,180 ******************************************************************************** 2025-09-08T11:43:24,180 ############################ 2025-09-08T11:43:24,180 # Package would be ignored # 2025-09-08T11:43:24,180 ############################ 2025-09-08T11:43:24,180 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004' as an importable package[^1], 2025-09-08T11:43:24,180 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,180 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,180 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004' is explicitly added 2025-09-08T11:43:24,180 to the `packages` configuration field. 2025-09-08T11:43:24,180 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,181 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,181 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,181 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,181 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,181 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004' to be distributed and are 2025-09-08T11:43:24,181 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004' via 2025-09-08T11:43:24,181 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,181 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,181 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,182 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,182 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,182 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,182 even if it does not contain any `.py` files. 2025-09-08T11:43:24,182 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,182 directory, all directories are treated like packages. 2025-09-08T11:43:24,182 ******************************************************************************** 2025-09-08T11:43:24,182 !! 2025-09-08T11:43:24,183 check.warn(importable) 2025-09-08T11:43:24,183 /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-08T11:43:24,183 !! 2025-09-08T11:43:24,183 ******************************************************************************** 2025-09-08T11:43:24,183 ############################ 2025-09-08T11:43:24,183 # Package would be ignored # 2025-09-08T11:43:24,183 ############################ 2025-09-08T11:43:24,183 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates' as an importable package[^1], 2025-09-08T11:43:24,183 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,184 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,184 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates' is explicitly added 2025-09-08T11:43:24,184 to the `packages` configuration field. 2025-09-08T11:43:24,184 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,184 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,184 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,184 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,184 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,185 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates' to be distributed and are 2025-09-08T11:43:24,185 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates' via 2025-09-08T11:43:24,185 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,185 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,185 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,185 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,185 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,186 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,186 even if it does not contain any `.py` files. 2025-09-08T11:43:24,186 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,186 directory, all directories are treated like packages. 2025-09-08T11:43:24,186 ******************************************************************************** 2025-09-08T11:43:24,186 !! 2025-09-08T11:43:24,186 check.warn(importable) 2025-09-08T11:43:24,186 /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-08T11:43:24,186 !! 2025-09-08T11:43:24,186 ******************************************************************************** 2025-09-08T11:43:24,187 ############################ 2025-09-08T11:43:24,187 # Package would be ignored # 2025-09-08T11:43:24,187 ############################ 2025-09-08T11:43:24,187 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' as an importable package[^1], 2025-09-08T11:43:24,187 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,187 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,187 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' is explicitly added 2025-09-08T11:43:24,187 to the `packages` configuration field. 2025-09-08T11:43:24,187 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,187 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,188 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,188 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,188 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,188 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' to be distributed and are 2025-09-08T11:43:24,188 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' via 2025-09-08T11:43:24,188 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,188 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,188 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,188 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,189 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,189 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,189 even if it does not contain any `.py` files. 2025-09-08T11:43:24,189 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,189 directory, all directories are treated like packages. 2025-09-08T11:43:24,189 ******************************************************************************** 2025-09-08T11:43:24,189 !! 2025-09-08T11:43:24,189 check.warn(importable) 2025-09-08T11:43:24,190 /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-08T11:43:24,190 !! 2025-09-08T11:43:24,190 ******************************************************************************** 2025-09-08T11:43:24,190 ############################ 2025-09-08T11:43:24,190 # Package would be ignored # 2025-09-08T11:43:24,190 ############################ 2025-09-08T11:43:24,190 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' as an importable package[^1], 2025-09-08T11:43:24,190 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,190 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,190 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' is explicitly added 2025-09-08T11:43:24,191 to the `packages` configuration field. 2025-09-08T11:43:24,191 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,191 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,191 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,191 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,191 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,191 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' to be distributed and are 2025-09-08T11:43:24,191 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' via 2025-09-08T11:43:24,191 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,192 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,192 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,192 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,192 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,192 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,192 even if it does not contain any `.py` files. 2025-09-08T11:43:24,192 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,192 directory, all directories are treated like packages. 2025-09-08T11:43:24,193 ******************************************************************************** 2025-09-08T11:43:24,193 !! 2025-09-08T11:43:24,193 check.warn(importable) 2025-09-08T11:43:24,193 /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-08T11:43:24,193 !! 2025-09-08T11:43:24,193 ******************************************************************************** 2025-09-08T11:43:24,193 ############################ 2025-09-08T11:43:24,193 # Package would be ignored # 2025-09-08T11:43:24,193 ############################ 2025-09-08T11:43:24,193 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' as an importable package[^1], 2025-09-08T11:43:24,194 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,194 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,194 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' is explicitly added 2025-09-08T11:43:24,194 to the `packages` configuration field. 2025-09-08T11:43:24,194 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,194 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,194 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,194 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,195 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,195 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' to be distributed and are 2025-09-08T11:43:24,195 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' via 2025-09-08T11:43:24,195 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,195 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,195 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,195 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,195 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,196 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,196 even if it does not contain any `.py` files. 2025-09-08T11:43:24,196 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,196 directory, all directories are treated like packages. 2025-09-08T11:43:24,196 ******************************************************************************** 2025-09-08T11:43:24,196 !! 2025-09-08T11:43:24,196 check.warn(importable) 2025-09-08T11:43:24,196 /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-08T11:43:24,196 !! 2025-09-08T11:43:24,197 ******************************************************************************** 2025-09-08T11:43:24,197 ############################ 2025-09-08T11:43:24,197 # Package would be ignored # 2025-09-08T11:43:24,197 ############################ 2025-09-08T11:43:24,197 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' as an importable package[^1], 2025-09-08T11:43:24,197 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,197 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,197 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' is explicitly added 2025-09-08T11:43:24,197 to the `packages` configuration field. 2025-09-08T11:43:24,198 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,198 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,198 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,198 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,198 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,198 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' to be distributed and are 2025-09-08T11:43:24,198 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' via 2025-09-08T11:43:24,198 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,198 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,199 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,199 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,199 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,199 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,199 even if it does not contain any `.py` files. 2025-09-08T11:43:24,199 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,199 directory, all directories are treated like packages. 2025-09-08T11:43:24,200 ******************************************************************************** 2025-09-08T11:43:24,200 !! 2025-09-08T11:43:24,200 check.warn(importable) 2025-09-08T11:43:24,200 /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-08T11:43:24,200 !! 2025-09-08T11:43:24,200 ******************************************************************************** 2025-09-08T11:43:24,200 ############################ 2025-09-08T11:43:24,200 # Package would be ignored # 2025-09-08T11:43:24,200 ############################ 2025-09-08T11:43:24,200 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' as an importable package[^1], 2025-09-08T11:43:24,201 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,201 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,201 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' is explicitly added 2025-09-08T11:43:24,201 to the `packages` configuration field. 2025-09-08T11:43:24,201 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,201 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,201 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,201 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,202 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,202 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' to be distributed and are 2025-09-08T11:43:24,202 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' via 2025-09-08T11:43:24,202 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,202 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,202 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,202 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,202 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,203 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,203 even if it does not contain any `.py` files. 2025-09-08T11:43:24,203 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,203 directory, all directories are treated like packages. 2025-09-08T11:43:24,203 ******************************************************************************** 2025-09-08T11:43:24,203 !! 2025-09-08T11:43:24,203 check.warn(importable) 2025-09-08T11:43:24,203 /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-08T11:43:24,203 !! 2025-09-08T11:43:24,204 ******************************************************************************** 2025-09-08T11:43:24,204 ############################ 2025-09-08T11:43:24,204 # Package would be ignored # 2025-09-08T11:43:24,204 ############################ 2025-09-08T11:43:24,204 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' as an importable package[^1], 2025-09-08T11:43:24,204 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,204 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,204 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' is explicitly added 2025-09-08T11:43:24,204 to the `packages` configuration field. 2025-09-08T11:43:24,205 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,205 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,205 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,205 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,205 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,205 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' to be distributed and are 2025-09-08T11:43:24,205 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' via 2025-09-08T11:43:24,205 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,206 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,206 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,206 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,206 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,206 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,206 even if it does not contain any `.py` files. 2025-09-08T11:43:24,206 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,206 directory, all directories are treated like packages. 2025-09-08T11:43:24,207 ******************************************************************************** 2025-09-08T11:43:24,207 !! 2025-09-08T11:43:24,207 check.warn(importable) 2025-09-08T11:43:24,207 /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-08T11:43:24,207 !! 2025-09-08T11:43:24,207 ******************************************************************************** 2025-09-08T11:43:24,207 ############################ 2025-09-08T11:43:24,207 # Package would be ignored # 2025-09-08T11:43:24,207 ############################ 2025-09-08T11:43:24,208 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Variables' as an importable package[^1], 2025-09-08T11:43:24,208 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,208 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,208 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Variables' is explicitly added 2025-09-08T11:43:24,208 to the `packages` configuration field. 2025-09-08T11:43:24,208 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,208 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,208 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,209 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,209 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,209 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Variables' to be distributed and are 2025-09-08T11:43:24,209 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Variables' via 2025-09-08T11:43:24,209 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,209 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,209 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,209 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,210 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,210 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,210 even if it does not contain any `.py` files. 2025-09-08T11:43:24,210 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,210 directory, all directories are treated like packages. 2025-09-08T11:43:24,210 ******************************************************************************** 2025-09-08T11:43:24,210 !! 2025-09-08T11:43:24,210 check.warn(importable) 2025-09-08T11:43:24,211 /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-08T11:43:24,211 !! 2025-09-08T11:43:24,211 ******************************************************************************** 2025-09-08T11:43:24,211 ############################ 2025-09-08T11:43:24,211 # Package would be ignored # 2025-09-08T11:43:24,211 ############################ 2025-09-08T11:43:24,211 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' as an importable package[^1], 2025-09-08T11:43:24,211 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,211 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,211 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' is explicitly added 2025-09-08T11:43:24,212 to the `packages` configuration field. 2025-09-08T11:43:24,212 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,212 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,212 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,212 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,212 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,212 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' to be distributed and are 2025-09-08T11:43:24,212 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' via 2025-09-08T11:43:24,213 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,213 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,213 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,213 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,213 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,213 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,213 even if it does not contain any `.py` files. 2025-09-08T11:43:24,214 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,214 directory, all directories are treated like packages. 2025-09-08T11:43:24,214 ******************************************************************************** 2025-09-08T11:43:24,214 !! 2025-09-08T11:43:24,214 check.warn(importable) 2025-09-08T11:43:24,214 /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-08T11:43:24,214 !! 2025-09-08T11:43:24,214 ******************************************************************************** 2025-09-08T11:43:24,214 ############################ 2025-09-08T11:43:24,214 # Package would be ignored # 2025-09-08T11:43:24,215 ############################ 2025-09-08T11:43:24,215 Python recognizes 'publiforge.Processors.Publiset2Publidoc' as an importable package[^1], 2025-09-08T11:43:24,215 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,215 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,215 package, please make sure that 'publiforge.Processors.Publiset2Publidoc' is explicitly added 2025-09-08T11:43:24,215 to the `packages` configuration field. 2025-09-08T11:43:24,215 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,215 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,215 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,216 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,216 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,216 If you don't want 'publiforge.Processors.Publiset2Publidoc' to be distributed and are 2025-09-08T11:43:24,216 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc' via 2025-09-08T11:43:24,216 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,216 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,216 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,216 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,217 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,217 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,217 even if it does not contain any `.py` files. 2025-09-08T11:43:24,217 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,217 directory, all directories are treated like packages. 2025-09-08T11:43:24,217 ******************************************************************************** 2025-09-08T11:43:24,217 !! 2025-09-08T11:43:24,217 check.warn(importable) 2025-09-08T11:43:24,218 /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-08T11:43:24,218 !! 2025-09-08T11:43:24,218 ******************************************************************************** 2025-09-08T11:43:24,218 ############################ 2025-09-08T11:43:24,218 # Package would be ignored # 2025-09-08T11:43:24,218 ############################ 2025-09-08T11:43:24,218 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Variables' as an importable package[^1], 2025-09-08T11:43:24,218 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,218 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,218 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Variables' is explicitly added 2025-09-08T11:43:24,219 to the `packages` configuration field. 2025-09-08T11:43:24,219 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,219 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,219 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,219 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,219 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,219 If you don't want 'publiforge.Processors.Publiset2Publidoc.Variables' to be distributed and are 2025-09-08T11:43:24,219 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Variables' via 2025-09-08T11:43:24,220 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,220 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,220 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,220 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,220 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,220 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,220 even if it does not contain any `.py` files. 2025-09-08T11:43:24,220 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,220 directory, all directories are treated like packages. 2025-09-08T11:43:24,221 ******************************************************************************** 2025-09-08T11:43:24,221 !! 2025-09-08T11:43:24,221 check.warn(importable) 2025-09-08T11:43:24,221 /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-08T11:43:24,221 !! 2025-09-08T11:43:24,221 ******************************************************************************** 2025-09-08T11:43:24,221 ############################ 2025-09-08T11:43:24,221 # Package would be ignored # 2025-09-08T11:43:24,221 ############################ 2025-09-08T11:43:24,221 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Xsl' as an importable package[^1], 2025-09-08T11:43:24,222 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,222 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,222 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Xsl' is explicitly added 2025-09-08T11:43:24,222 to the `packages` configuration field. 2025-09-08T11:43:24,222 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,222 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,222 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,222 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,223 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,223 If you don't want 'publiforge.Processors.Publiset2Publidoc.Xsl' to be distributed and are 2025-09-08T11:43:24,223 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Xsl' via 2025-09-08T11:43:24,223 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,223 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,223 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,223 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,223 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,224 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,224 even if it does not contain any `.py` files. 2025-09-08T11:43:24,224 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,224 directory, all directories are treated like packages. 2025-09-08T11:43:24,224 ******************************************************************************** 2025-09-08T11:43:24,224 !! 2025-09-08T11:43:24,224 check.warn(importable) 2025-09-08T11:43:24,224 /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-08T11:43:24,224 !! 2025-09-08T11:43:24,225 ******************************************************************************** 2025-09-08T11:43:24,225 ############################ 2025-09-08T11:43:24,225 # Package would be ignored # 2025-09-08T11:43:24,225 ############################ 2025-09-08T11:43:24,225 Python recognizes 'publiforge.Processors.Publiset4Publidoc' as an importable package[^1], 2025-09-08T11:43:24,225 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,225 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,225 package, please make sure that 'publiforge.Processors.Publiset4Publidoc' is explicitly added 2025-09-08T11:43:24,225 to the `packages` configuration field. 2025-09-08T11:43:24,226 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,226 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,226 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,226 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,226 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,226 If you don't want 'publiforge.Processors.Publiset4Publidoc' to be distributed and are 2025-09-08T11:43:24,226 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc' via 2025-09-08T11:43:24,226 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,226 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,227 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,227 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,227 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,227 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,227 even if it does not contain any `.py` files. 2025-09-08T11:43:24,227 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,227 directory, all directories are treated like packages. 2025-09-08T11:43:24,227 ******************************************************************************** 2025-09-08T11:43:24,228 !! 2025-09-08T11:43:24,228 check.warn(importable) 2025-09-08T11:43:24,228 /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-08T11:43:24,228 !! 2025-09-08T11:43:24,228 ******************************************************************************** 2025-09-08T11:43:24,228 ############################ 2025-09-08T11:43:24,228 # Package would be ignored # 2025-09-08T11:43:24,228 ############################ 2025-09-08T11:43:24,228 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Variables' as an importable package[^1], 2025-09-08T11:43:24,228 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,229 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,229 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Variables' is explicitly added 2025-09-08T11:43:24,229 to the `packages` configuration field. 2025-09-08T11:43:24,229 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,229 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,229 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,229 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,229 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,230 If you don't want 'publiforge.Processors.Publiset4Publidoc.Variables' to be distributed and are 2025-09-08T11:43:24,230 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Variables' via 2025-09-08T11:43:24,230 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,230 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,230 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,230 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,230 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,230 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,231 even if it does not contain any `.py` files. 2025-09-08T11:43:24,231 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,231 directory, all directories are treated like packages. 2025-09-08T11:43:24,231 ******************************************************************************** 2025-09-08T11:43:24,231 !! 2025-09-08T11:43:24,231 check.warn(importable) 2025-09-08T11:43:24,231 /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-08T11:43:24,231 !! 2025-09-08T11:43:24,231 ******************************************************************************** 2025-09-08T11:43:24,231 ############################ 2025-09-08T11:43:24,231 # Package would be ignored # 2025-09-08T11:43:24,232 ############################ 2025-09-08T11:43:24,232 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Xsl' as an importable package[^1], 2025-09-08T11:43:24,232 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,232 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,232 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Xsl' is explicitly added 2025-09-08T11:43:24,232 to the `packages` configuration field. 2025-09-08T11:43:24,232 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,232 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,232 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,233 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,233 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,233 If you don't want 'publiforge.Processors.Publiset4Publidoc.Xsl' to be distributed and are 2025-09-08T11:43:24,233 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Xsl' via 2025-09-08T11:43:24,233 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,233 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,233 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,233 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,233 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,234 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,234 even if it does not contain any `.py` files. 2025-09-08T11:43:24,234 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,234 directory, all directories are treated like packages. 2025-09-08T11:43:24,234 ******************************************************************************** 2025-09-08T11:43:24,234 !! 2025-09-08T11:43:24,234 check.warn(importable) 2025-09-08T11:43:24,234 /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-08T11:43:24,235 !! 2025-09-08T11:43:24,235 ******************************************************************************** 2025-09-08T11:43:24,235 ############################ 2025-09-08T11:43:24,235 # Package would be ignored # 2025-09-08T11:43:24,235 ############################ 2025-09-08T11:43:24,235 Python recognizes 'publiforge.Processors.Publiset4Publiquiz' as an importable package[^1], 2025-09-08T11:43:24,235 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,235 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,235 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz' is explicitly added 2025-09-08T11:43:24,235 to the `packages` configuration field. 2025-09-08T11:43:24,236 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,236 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,236 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,236 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,236 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,236 If you don't want 'publiforge.Processors.Publiset4Publiquiz' to be distributed and are 2025-09-08T11:43:24,236 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz' via 2025-09-08T11:43:24,236 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,237 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,237 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,237 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,237 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,237 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,237 even if it does not contain any `.py` files. 2025-09-08T11:43:24,237 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,237 directory, all directories are treated like packages. 2025-09-08T11:43:24,237 ******************************************************************************** 2025-09-08T11:43:24,238 !! 2025-09-08T11:43:24,238 check.warn(importable) 2025-09-08T11:43:24,238 /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-08T11:43:24,238 !! 2025-09-08T11:43:24,238 ******************************************************************************** 2025-09-08T11:43:24,238 ############################ 2025-09-08T11:43:24,238 # Package would be ignored # 2025-09-08T11:43:24,238 ############################ 2025-09-08T11:43:24,238 Python recognizes 'publiforge.Processors.Publiset4Publiquiz.Xsl' as an importable package[^1], 2025-09-08T11:43:24,238 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,239 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,239 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz.Xsl' is explicitly added 2025-09-08T11:43:24,239 to the `packages` configuration field. 2025-09-08T11:43:24,239 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,239 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,239 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,239 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,239 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,240 If you don't want 'publiforge.Processors.Publiset4Publiquiz.Xsl' to be distributed and are 2025-09-08T11:43:24,240 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz.Xsl' via 2025-09-08T11:43:24,240 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,240 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,240 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,240 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,240 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,240 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,241 even if it does not contain any `.py` files. 2025-09-08T11:43:24,241 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,241 directory, all directories are treated like packages. 2025-09-08T11:43:24,241 ******************************************************************************** 2025-09-08T11:43:24,241 !! 2025-09-08T11:43:24,241 check.warn(importable) 2025-09-08T11:43:24,241 /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-08T11:43:24,241 !! 2025-09-08T11:43:24,241 ******************************************************************************** 2025-09-08T11:43:24,241 ############################ 2025-09-08T11:43:24,242 # Package would be ignored # 2025-09-08T11:43:24,242 ############################ 2025-09-08T11:43:24,242 Python recognizes 'publiforge.RelaxNG' as an importable package[^1], 2025-09-08T11:43:24,242 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,242 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,242 package, please make sure that 'publiforge.RelaxNG' is explicitly added 2025-09-08T11:43:24,242 to the `packages` configuration field. 2025-09-08T11:43:24,242 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,242 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,242 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,243 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,243 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,243 If you don't want 'publiforge.RelaxNG' to be distributed and are 2025-09-08T11:43:24,243 already explicitly excluding 'publiforge.RelaxNG' via 2025-09-08T11:43:24,243 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,243 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,243 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,243 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,244 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,244 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,244 even if it does not contain any `.py` files. 2025-09-08T11:43:24,244 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,244 directory, all directories are treated like packages. 2025-09-08T11:43:24,244 ******************************************************************************** 2025-09-08T11:43:24,244 !! 2025-09-08T11:43:24,244 check.warn(importable) 2025-09-08T11:43:24,245 /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-08T11:43:24,245 !! 2025-09-08T11:43:24,245 ******************************************************************************** 2025-09-08T11:43:24,245 ############################ 2025-09-08T11:43:24,245 # Package would be ignored # 2025-09-08T11:43:24,245 ############################ 2025-09-08T11:43:24,245 Python recognizes 'publiforge.Static' as an importable package[^1], 2025-09-08T11:43:24,245 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,245 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,245 package, please make sure that 'publiforge.Static' is explicitly added 2025-09-08T11:43:24,245 to the `packages` configuration field. 2025-09-08T11:43:24,246 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,246 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,246 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,246 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,246 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,246 If you don't want 'publiforge.Static' to be distributed and are 2025-09-08T11:43:24,246 already explicitly excluding 'publiforge.Static' via 2025-09-08T11:43:24,246 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,247 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,247 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,247 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,247 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,247 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,247 even if it does not contain any `.py` files. 2025-09-08T11:43:24,247 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,247 directory, all directories are treated like packages. 2025-09-08T11:43:24,248 ******************************************************************************** 2025-09-08T11:43:24,248 !! 2025-09-08T11:43:24,248 check.warn(importable) 2025-09-08T11:43:24,248 /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-08T11:43:24,248 !! 2025-09-08T11:43:24,248 ******************************************************************************** 2025-09-08T11:43:24,248 ############################ 2025-09-08T11:43:24,248 # Package would be ignored # 2025-09-08T11:43:24,248 ############################ 2025-09-08T11:43:24,249 Python recognizes 'publiforge.Static.Css' as an importable package[^1], 2025-09-08T11:43:24,249 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,249 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,249 package, please make sure that 'publiforge.Static.Css' is explicitly added 2025-09-08T11:43:24,249 to the `packages` configuration field. 2025-09-08T11:43:24,249 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,249 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,249 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,249 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,250 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,250 If you don't want 'publiforge.Static.Css' to be distributed and are 2025-09-08T11:43:24,250 already explicitly excluding 'publiforge.Static.Css' via 2025-09-08T11:43:24,250 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,250 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,250 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,250 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,250 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,251 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,251 even if it does not contain any `.py` files. 2025-09-08T11:43:24,251 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,251 directory, all directories are treated like packages. 2025-09-08T11:43:24,251 ******************************************************************************** 2025-09-08T11:43:24,251 !! 2025-09-08T11:43:24,251 check.warn(importable) 2025-09-08T11:43:24,251 /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-08T11:43:24,251 !! 2025-09-08T11:43:24,252 ******************************************************************************** 2025-09-08T11:43:24,252 ############################ 2025-09-08T11:43:24,252 # Package would be ignored # 2025-09-08T11:43:24,252 ############################ 2025-09-08T11:43:24,252 Python recognizes 'publiforge.Static.Images' as an importable package[^1], 2025-09-08T11:43:24,252 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,252 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,252 package, please make sure that 'publiforge.Static.Images' is explicitly added 2025-09-08T11:43:24,252 to the `packages` configuration field. 2025-09-08T11:43:24,252 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,252 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,253 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,253 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,253 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,253 If you don't want 'publiforge.Static.Images' to be distributed and are 2025-09-08T11:43:24,253 already explicitly excluding 'publiforge.Static.Images' via 2025-09-08T11:43:24,253 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,253 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,253 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,254 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,254 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,254 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,254 even if it does not contain any `.py` files. 2025-09-08T11:43:24,254 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,254 directory, all directories are treated like packages. 2025-09-08T11:43:24,254 ******************************************************************************** 2025-09-08T11:43:24,254 !! 2025-09-08T11:43:24,255 check.warn(importable) 2025-09-08T11:43:24,255 /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-08T11:43:24,255 !! 2025-09-08T11:43:24,255 ******************************************************************************** 2025-09-08T11:43:24,255 ############################ 2025-09-08T11:43:24,255 # Package would be ignored # 2025-09-08T11:43:24,255 ############################ 2025-09-08T11:43:24,255 Python recognizes 'publiforge.Static.Images.MimeTypes' as an importable package[^1], 2025-09-08T11:43:24,255 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,255 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,256 package, please make sure that 'publiforge.Static.Images.MimeTypes' is explicitly added 2025-09-08T11:43:24,256 to the `packages` configuration field. 2025-09-08T11:43:24,256 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,256 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,256 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,256 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,256 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,256 If you don't want 'publiforge.Static.Images.MimeTypes' to be distributed and are 2025-09-08T11:43:24,257 already explicitly excluding 'publiforge.Static.Images.MimeTypes' via 2025-09-08T11:43:24,257 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,257 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,257 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,257 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,257 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,257 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,257 even if it does not contain any `.py` files. 2025-09-08T11:43:24,257 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,258 directory, all directories are treated like packages. 2025-09-08T11:43:24,258 ******************************************************************************** 2025-09-08T11:43:24,258 !! 2025-09-08T11:43:24,258 check.warn(importable) 2025-09-08T11:43:24,258 /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-08T11:43:24,258 !! 2025-09-08T11:43:24,258 ******************************************************************************** 2025-09-08T11:43:24,258 ############################ 2025-09-08T11:43:24,259 # Package would be ignored # 2025-09-08T11:43:24,259 ############################ 2025-09-08T11:43:24,259 Python recognizes 'publiforge.Static.Js' as an importable package[^1], 2025-09-08T11:43:24,259 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,259 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,259 package, please make sure that 'publiforge.Static.Js' is explicitly added 2025-09-08T11:43:24,259 to the `packages` configuration field. 2025-09-08T11:43:24,259 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,259 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,259 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,260 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,260 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,260 If you don't want 'publiforge.Static.Js' to be distributed and are 2025-09-08T11:43:24,260 already explicitly excluding 'publiforge.Static.Js' via 2025-09-08T11:43:24,260 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,260 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,260 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,260 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,261 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,261 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,261 even if it does not contain any `.py` files. 2025-09-08T11:43:24,261 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,261 directory, all directories are treated like packages. 2025-09-08T11:43:24,261 ******************************************************************************** 2025-09-08T11:43:24,261 !! 2025-09-08T11:43:24,262 check.warn(importable) 2025-09-08T11:43:24,262 /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-08T11:43:24,262 !! 2025-09-08T11:43:24,262 ******************************************************************************** 2025-09-08T11:43:24,262 ############################ 2025-09-08T11:43:24,262 # Package would be ignored # 2025-09-08T11:43:24,262 ############################ 2025-09-08T11:43:24,262 Python recognizes 'publiforge.Static.Js.Tests' as an importable package[^1], 2025-09-08T11:43:24,262 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,262 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,263 package, please make sure that 'publiforge.Static.Js.Tests' is explicitly added 2025-09-08T11:43:24,263 to the `packages` configuration field. 2025-09-08T11:43:24,263 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,263 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,263 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,263 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,263 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,263 If you don't want 'publiforge.Static.Js.Tests' to be distributed and are 2025-09-08T11:43:24,264 already explicitly excluding 'publiforge.Static.Js.Tests' via 2025-09-08T11:43:24,264 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,264 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,264 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,264 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,264 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,264 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,265 even if it does not contain any `.py` files. 2025-09-08T11:43:24,265 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,265 directory, all directories are treated like packages. 2025-09-08T11:43:24,265 ******************************************************************************** 2025-09-08T11:43:24,265 !! 2025-09-08T11:43:24,265 check.warn(importable) 2025-09-08T11:43:24,265 /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-08T11:43:24,265 !! 2025-09-08T11:43:24,265 ******************************************************************************** 2025-09-08T11:43:24,265 ############################ 2025-09-08T11:43:24,266 # Package would be ignored # 2025-09-08T11:43:24,266 ############################ 2025-09-08T11:43:24,266 Python recognizes 'publiforge.Templates' as an importable package[^1], 2025-09-08T11:43:24,266 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,266 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,266 package, please make sure that 'publiforge.Templates' is explicitly added 2025-09-08T11:43:24,266 to the `packages` configuration field. 2025-09-08T11:43:24,266 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,266 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,266 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,267 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,267 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,267 If you don't want 'publiforge.Templates' to be distributed and are 2025-09-08T11:43:24,267 already explicitly excluding 'publiforge.Templates' via 2025-09-08T11:43:24,267 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,267 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,267 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,267 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,268 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,268 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,268 even if it does not contain any `.py` files. 2025-09-08T11:43:24,268 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,268 directory, all directories are treated like packages. 2025-09-08T11:43:24,268 ******************************************************************************** 2025-09-08T11:43:24,268 !! 2025-09-08T11:43:24,268 check.warn(importable) 2025-09-08T11:43:24,269 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge' is absent from the `packages` configuration. 2025-09-08T11:43:24,269 !! 2025-09-08T11:43:24,269 ******************************************************************************** 2025-09-08T11:43:24,269 ############################ 2025-09-08T11:43:24,269 # Package would be ignored # 2025-09-08T11:43:24,269 ############################ 2025-09-08T11:43:24,269 Python recognizes 'publiforge.scaffolds.Front.PubliForge' as an importable package[^1], 2025-09-08T11:43:24,269 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,269 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,269 package, please make sure that 'publiforge.scaffolds.Front.PubliForge' is explicitly added 2025-09-08T11:43:24,270 to the `packages` configuration field. 2025-09-08T11:43:24,270 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,270 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,270 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,270 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,270 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,270 If you don't want 'publiforge.scaffolds.Front.PubliForge' to be distributed and are 2025-09-08T11:43:24,270 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge' via 2025-09-08T11:43:24,271 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,271 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,271 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,271 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,271 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,271 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,271 even if it does not contain any `.py` files. 2025-09-08T11:43:24,271 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,272 directory, all directories are treated like packages. 2025-09-08T11:43:24,272 ******************************************************************************** 2025-09-08T11:43:24,272 !! 2025-09-08T11:43:24,272 check.warn(importable) 2025-09-08T11:43:24,272 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' is absent from the `packages` configuration. 2025-09-08T11:43:24,272 !! 2025-09-08T11:43:24,272 ******************************************************************************** 2025-09-08T11:43:24,272 ############################ 2025-09-08T11:43:24,272 # Package would be ignored # 2025-09-08T11:43:24,272 ############################ 2025-09-08T11:43:24,273 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' as an importable package[^1], 2025-09-08T11:43:24,273 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,273 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,273 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' is explicitly added 2025-09-08T11:43:24,273 to the `packages` configuration field. 2025-09-08T11:43:24,273 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,273 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,273 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,273 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,274 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,274 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' to be distributed and are 2025-09-08T11:43:24,274 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' via 2025-09-08T11:43:24,274 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,274 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,274 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,274 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,275 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,275 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,275 even if it does not contain any `.py` files. 2025-09-08T11:43:24,275 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,275 directory, all directories are treated like packages. 2025-09-08T11:43:24,275 ******************************************************************************** 2025-09-08T11:43:24,275 !! 2025-09-08T11:43:24,275 check.warn(importable) 2025-09-08T11:43:24,275 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' is absent from the `packages` configuration. 2025-09-08T11:43:24,276 !! 2025-09-08T11:43:24,276 ******************************************************************************** 2025-09-08T11:43:24,276 ############################ 2025-09-08T11:43:24,276 # Package would be ignored # 2025-09-08T11:43:24,276 ############################ 2025-09-08T11:43:24,276 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' as an importable package[^1], 2025-09-08T11:43:24,276 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,276 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,276 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' is explicitly added 2025-09-08T11:43:24,276 to the `packages` configuration field. 2025-09-08T11:43:24,277 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,277 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,277 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,277 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,277 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,277 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' to be distributed and are 2025-09-08T11:43:24,277 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' via 2025-09-08T11:43:24,277 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,278 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,278 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,278 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,278 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,278 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,278 even if it does not contain any `.py` files. 2025-09-08T11:43:24,278 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,278 directory, all directories are treated like packages. 2025-09-08T11:43:24,279 ******************************************************************************** 2025-09-08T11:43:24,279 !! 2025-09-08T11:43:24,279 check.warn(importable) 2025-09-08T11:43:24,279 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' is absent from the `packages` configuration. 2025-09-08T11:43:24,279 !! 2025-09-08T11:43:24,279 ******************************************************************************** 2025-09-08T11:43:24,279 ############################ 2025-09-08T11:43:24,279 # Package would be ignored # 2025-09-08T11:43:24,279 ############################ 2025-09-08T11:43:24,279 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' as an importable package[^1], 2025-09-08T11:43:24,280 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,280 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,280 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' is explicitly added 2025-09-08T11:43:24,280 to the `packages` configuration field. 2025-09-08T11:43:24,280 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,280 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,280 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,280 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,281 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,281 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' to be distributed and are 2025-09-08T11:43:24,281 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' via 2025-09-08T11:43:24,281 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,281 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,281 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,281 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,281 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,282 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,282 even if it does not contain any `.py` files. 2025-09-08T11:43:24,282 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,282 directory, all directories are treated like packages. 2025-09-08T11:43:24,282 ******************************************************************************** 2025-09-08T11:43:24,282 !! 2025-09-08T11:43:24,282 check.warn(importable) 2025-09-08T11:43:24,282 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' is absent from the `packages` configuration. 2025-09-08T11:43:24,282 !! 2025-09-08T11:43:24,283 ******************************************************************************** 2025-09-08T11:43:24,283 ############################ 2025-09-08T11:43:24,283 # Package would be ignored # 2025-09-08T11:43:24,283 ############################ 2025-09-08T11:43:24,283 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' as an importable package[^1], 2025-09-08T11:43:24,283 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,283 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,283 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' is explicitly added 2025-09-08T11:43:24,283 to the `packages` configuration field. 2025-09-08T11:43:24,283 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,284 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,284 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,284 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,284 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,284 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' to be distributed and are 2025-09-08T11:43:24,284 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' via 2025-09-08T11:43:24,284 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,284 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,285 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,285 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,285 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,285 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,285 even if it does not contain any `.py` files. 2025-09-08T11:43:24,285 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,285 directory, all directories are treated like packages. 2025-09-08T11:43:24,286 ******************************************************************************** 2025-09-08T11:43:24,286 !! 2025-09-08T11:43:24,286 check.warn(importable) 2025-09-08T11:43:24,286 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' is absent from the `packages` configuration. 2025-09-08T11:43:24,286 !! 2025-09-08T11:43:24,286 ******************************************************************************** 2025-09-08T11:43:24,286 ############################ 2025-09-08T11:43:24,286 # Package would be ignored # 2025-09-08T11:43:24,286 ############################ 2025-09-08T11:43:24,286 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' as an importable package[^1], 2025-09-08T11:43:24,287 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,287 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,287 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' is explicitly added 2025-09-08T11:43:24,287 to the `packages` configuration field. 2025-09-08T11:43:24,287 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,287 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,287 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,288 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,288 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,288 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' to be distributed and are 2025-09-08T11:43:24,288 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' via 2025-09-08T11:43:24,288 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,288 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,288 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,288 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,289 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,289 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,289 even if it does not contain any `.py` files. 2025-09-08T11:43:24,289 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,289 directory, all directories are treated like packages. 2025-09-08T11:43:24,289 ******************************************************************************** 2025-09-08T11:43:24,289 !! 2025-09-08T11:43:24,289 check.warn(importable) 2025-09-08T11:43:24,290 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Static' is absent from the `packages` configuration. 2025-09-08T11:43:24,290 !! 2025-09-08T11:43:24,290 ******************************************************************************** 2025-09-08T11:43:24,290 ############################ 2025-09-08T11:43:24,290 # Package would be ignored # 2025-09-08T11:43:24,290 ############################ 2025-09-08T11:43:24,290 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static' as an importable package[^1], 2025-09-08T11:43:24,290 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,290 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,290 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static' is explicitly added 2025-09-08T11:43:24,291 to the `packages` configuration field. 2025-09-08T11:43:24,291 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,291 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,291 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,291 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,291 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,291 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static' to be distributed and are 2025-09-08T11:43:24,292 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static' via 2025-09-08T11:43:24,292 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,292 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,292 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,292 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,292 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,293 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,293 even if it does not contain any `.py` files. 2025-09-08T11:43:24,293 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,293 directory, all directories are treated like packages. 2025-09-08T11:43:24,293 ******************************************************************************** 2025-09-08T11:43:24,294 !! 2025-09-08T11:43:24,294 check.warn(importable) 2025-09-08T11:43:24,294 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Static.Css' is absent from the `packages` configuration. 2025-09-08T11:43:24,294 !! 2025-09-08T11:43:24,294 ******************************************************************************** 2025-09-08T11:43:24,294 ############################ 2025-09-08T11:43:24,294 # Package would be ignored # 2025-09-08T11:43:24,294 ############################ 2025-09-08T11:43:24,295 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static.Css' as an importable package[^1], 2025-09-08T11:43:24,295 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,295 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,295 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static.Css' is explicitly added 2025-09-08T11:43:24,295 to the `packages` configuration field. 2025-09-08T11:43:24,295 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,295 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,295 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,296 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,296 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,296 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static.Css' to be distributed and are 2025-09-08T11:43:24,296 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static.Css' via 2025-09-08T11:43:24,296 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,296 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,296 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,297 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,297 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,297 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,297 even if it does not contain any `.py` files. 2025-09-08T11:43:24,297 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,297 directory, all directories are treated like packages. 2025-09-08T11:43:24,297 ******************************************************************************** 2025-09-08T11:43:24,298 !! 2025-09-08T11:43:24,298 check.warn(importable) 2025-09-08T11:43:24,298 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Static.Images' is absent from the `packages` configuration. 2025-09-08T11:43:24,298 !! 2025-09-08T11:43:24,298 ******************************************************************************** 2025-09-08T11:43:24,298 ############################ 2025-09-08T11:43:24,298 # Package would be ignored # 2025-09-08T11:43:24,298 ############################ 2025-09-08T11:43:24,298 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static.Images' as an importable package[^1], 2025-09-08T11:43:24,298 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,299 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,299 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static.Images' is explicitly added 2025-09-08T11:43:24,299 to the `packages` configuration field. 2025-09-08T11:43:24,299 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,299 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,299 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,299 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,299 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,300 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static.Images' to be distributed and are 2025-09-08T11:43:24,300 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static.Images' via 2025-09-08T11:43:24,300 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,300 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,300 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,300 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,300 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,301 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,301 even if it does not contain any `.py` files. 2025-09-08T11:43:24,301 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,301 directory, all directories are treated like packages. 2025-09-08T11:43:24,301 ******************************************************************************** 2025-09-08T11:43:24,301 !! 2025-09-08T11:43:24,301 check.warn(importable) 2025-09-08T11:43:24,302 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.LePrisme' is absent from the `packages` configuration. 2025-09-08T11:43:24,302 !! 2025-09-08T11:43:24,302 ******************************************************************************** 2025-09-08T11:43:24,302 ############################ 2025-09-08T11:43:24,302 # Package would be ignored # 2025-09-08T11:43:24,302 ############################ 2025-09-08T11:43:24,302 Python recognizes 'publiforge.scaffolds.LePrisme' as an importable package[^1], 2025-09-08T11:43:24,302 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,302 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,303 package, please make sure that 'publiforge.scaffolds.LePrisme' is explicitly added 2025-09-08T11:43:24,303 to the `packages` configuration field. 2025-09-08T11:43:24,303 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,303 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,303 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,303 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,303 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,303 If you don't want 'publiforge.scaffolds.LePrisme' to be distributed and are 2025-09-08T11:43:24,304 already explicitly excluding 'publiforge.scaffolds.LePrisme' via 2025-09-08T11:43:24,304 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,304 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,304 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,304 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,304 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,305 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,305 even if it does not contain any `.py` files. 2025-09-08T11:43:24,305 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,305 directory, all directories are treated like packages. 2025-09-08T11:43:24,305 ******************************************************************************** 2025-09-08T11:43:24,305 !! 2025-09-08T11:43:24,305 check.warn(importable) 2025-09-08T11:43:24,305 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.LePrisme.Templates' is absent from the `packages` configuration. 2025-09-08T11:43:24,305 !! 2025-09-08T11:43:24,306 ******************************************************************************** 2025-09-08T11:43:24,306 ############################ 2025-09-08T11:43:24,306 # Package would be ignored # 2025-09-08T11:43:24,306 ############################ 2025-09-08T11:43:24,306 Python recognizes 'publiforge.scaffolds.LePrisme.Templates' as an importable package[^1], 2025-09-08T11:43:24,306 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,306 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,306 package, please make sure that 'publiforge.scaffolds.LePrisme.Templates' is explicitly added 2025-09-08T11:43:24,306 to the `packages` configuration field. 2025-09-08T11:43:24,306 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,307 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,307 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,307 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,307 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,307 If you don't want 'publiforge.scaffolds.LePrisme.Templates' to be distributed and are 2025-09-08T11:43:24,307 already explicitly excluding 'publiforge.scaffolds.LePrisme.Templates' via 2025-09-08T11:43:24,307 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,307 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,308 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,308 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,308 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,308 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,308 even if it does not contain any `.py` files. 2025-09-08T11:43:24,308 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,309 directory, all directories are treated like packages. 2025-09-08T11:43:24,309 ******************************************************************************** 2025-09-08T11:43:24,309 !! 2025-09-08T11:43:24,309 check.warn(importable) 2025-09-08T11:43:24,309 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.LePrisme.Variables' is absent from the `packages` configuration. 2025-09-08T11:43:24,309 !! 2025-09-08T11:43:24,309 ******************************************************************************** 2025-09-08T11:43:24,309 ############################ 2025-09-08T11:43:24,309 # Package would be ignored # 2025-09-08T11:43:24,310 ############################ 2025-09-08T11:43:24,310 Python recognizes 'publiforge.scaffolds.LePrisme.Variables' as an importable package[^1], 2025-09-08T11:43:24,310 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,310 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,310 package, please make sure that 'publiforge.scaffolds.LePrisme.Variables' is explicitly added 2025-09-08T11:43:24,310 to the `packages` configuration field. 2025-09-08T11:43:24,310 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,310 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,310 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,311 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,311 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,311 If you don't want 'publiforge.scaffolds.LePrisme.Variables' to be distributed and are 2025-09-08T11:43:24,311 already explicitly excluding 'publiforge.scaffolds.LePrisme.Variables' via 2025-09-08T11:43:24,311 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,311 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,311 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,311 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,312 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,312 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,312 even if it does not contain any `.py` files. 2025-09-08T11:43:24,312 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,312 directory, all directories are treated like packages. 2025-09-08T11:43:24,312 ******************************************************************************** 2025-09-08T11:43:24,312 !! 2025-09-08T11:43:24,313 check.warn(importable) 2025-09-08T11:43:24,313 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.scaffolds.LePrisme.lib' is absent from the `packages` configuration. 2025-09-08T11:43:24,313 !! 2025-09-08T11:43:24,313 ******************************************************************************** 2025-09-08T11:43:24,313 ############################ 2025-09-08T11:43:24,313 # Package would be ignored # 2025-09-08T11:43:24,313 ############################ 2025-09-08T11:43:24,313 Python recognizes 'publiforge.scaffolds.LePrisme.lib' as an importable package[^1], 2025-09-08T11:43:24,313 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,314 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,314 package, please make sure that 'publiforge.scaffolds.LePrisme.lib' is explicitly added 2025-09-08T11:43:24,314 to the `packages` configuration field. 2025-09-08T11:43:24,314 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,314 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,314 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,314 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,314 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,315 If you don't want 'publiforge.scaffolds.LePrisme.lib' to be distributed and are 2025-09-08T11:43:24,315 already explicitly excluding 'publiforge.scaffolds.LePrisme.lib' via 2025-09-08T11:43:24,315 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,315 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,315 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,315 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,315 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,316 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,316 even if it does not contain any `.py` files. 2025-09-08T11:43:24,316 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,316 directory, all directories are treated like packages. 2025-09-08T11:43:24,316 ******************************************************************************** 2025-09-08T11:43:24,316 !! 2025-09-08T11:43:24,316 check.warn(importable) 2025-09-08T11:43:24,316 /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-08T11:43:24,317 !! 2025-09-08T11:43:24,317 ******************************************************************************** 2025-09-08T11:43:24,317 ############################ 2025-09-08T11:43:24,317 # Package would be ignored # 2025-09-08T11:43:24,317 ############################ 2025-09-08T11:43:24,317 Python recognizes 'publiforge.tests.Data' as an importable package[^1], 2025-09-08T11:43:24,317 but it is absent from setuptools' `packages` configuration. 2025-09-08T11:43:24,317 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T11:43:24,317 package, please make sure that 'publiforge.tests.Data' is explicitly added 2025-09-08T11:43:24,318 to the `packages` configuration field. 2025-09-08T11:43:24,318 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T11:43:24,318 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T11:43:24,318 instead of `find_packages(...)`/`find:`). 2025-09-08T11:43:24,318 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T11:43:24,318 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T11:43:24,318 If you don't want 'publiforge.tests.Data' to be distributed and are 2025-09-08T11:43:24,318 already explicitly excluding 'publiforge.tests.Data' via 2025-09-08T11:43:24,319 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T11:43:24,319 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T11:43:24,319 combination with a more fine grained `package-data` configuration. 2025-09-08T11:43:24,319 You can read more about "package data files" on setuptools documentation page: 2025-09-08T11:43:24,319 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T11:43:24,319 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T11:43:24,319 even if it does not contain any `.py` files. 2025-09-08T11:43:24,320 On the other hand, currently there is no concept of package data 2025-09-08T11:43:24,320 directory, all directories are treated like packages. 2025-09-08T11:43:24,320 ******************************************************************************** 2025-09-08T11:43:24,320 !! 2025-09-08T11:43:24,320 check.warn(importable) 2025-09-08T11:43:24,320 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale 2025-09-08T11:43:24,320 copying publiforge/Locale/publiforge.pot -> build/lib.linux-armv7l-cpython-313/publiforge/Locale 2025-09-08T11:43:24,320 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T11:43:24,320 copying publiforge/Locale/es/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T11:43:24,320 copying publiforge/Locale/es/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T11:43:24,321 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T11:43:24,321 copying publiforge/Locale/fr/LC_MESSAGES/colander.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T11:43:24,321 copying publiforge/Locale/fr/LC_MESSAGES/colander.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T11:43:24,321 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T11:43:24,321 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T11:43:24,321 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T11:43:24,321 copying publiforge/Openers/Image/image.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T11:43:24,321 copying publiforge/Openers/Image/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T11:43:24,321 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/ImageEdit 2025-09-08T11:43:24,321 copying publiforge/Openers/ImageEdit/image.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/ImageEdit 2025-09-08T11:43:24,321 copying publiforge/Openers/ImageEdit/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/ImageEdit 2025-09-08T11:43:24,322 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T11:43:24,322 copying publiforge/Openers/Ini/ini.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T11:43:24,322 copying publiforge/Openers/Ini/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T11:43:24,322 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/NoMore 2025-09-08T11:43:24,322 copying publiforge/Openers/NoMore/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/NoMore 2025-09-08T11:43:24,322 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Plain 2025-09-08T11:43:24,322 copying publiforge/Openers/Plain/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Plain 2025-09-08T11:43:24,322 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T11:43:24,322 copying publiforge/Openers/Publidoc/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T11:43:24,322 copying publiforge/Openers/Publidoc/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T11:43:24,322 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T11:43:24,323 copying publiforge/Openers/Publidoc/Maestro/publidoc_render4maestro.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T11:43:24,323 copying publiforge/Openers/Publidoc/Maestro/publidoc_xml4maestro.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T11:43:24,323 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Regex 2025-09-08T11:43:24,323 copying publiforge/Openers/Publidoc/Regex/publidoc_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Regex 2025-09-08T11:43:24,323 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T11:43:24,323 copying publiforge/Openers/Publidoc/Seeds/publidoc_document.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T11:43:24,323 copying publiforge/Openers/Publidoc/Seeds/publidoc_glossary.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T11:43:24,323 copying publiforge/Openers/Publidoc/Seeds/publidoc_topic.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T11:43:24,323 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T11:43:24,323 copying publiforge/Openers/Publidoc/Static/Css/publidoc_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T11:43:24,323 copying publiforge/Openers/Publidoc/Static/Css/publidoc_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T11:43:24,324 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T11:43:24,324 copying publiforge/Openers/Publidoc/Static/Js/codemirror4publidoc_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T11:43:24,324 copying publiforge/Openers/Publidoc/Static/Js/publidoc_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T11:43:24,324 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Variables 2025-09-08T11:43:24,324 copying publiforge/Openers/Publidoc/Variables/publidoc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Variables 2025-09-08T11:43:24,324 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T11:43:24,324 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T11:43:24,324 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T11:43:24,324 copying publiforge/Openers/Publidoc/Xsl/publidoc_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T11:43:24,325 copying publiforge/Openers/Publidoc/Xsl/publidoc_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T11:43:24,325 copying publiforge/Openers/Publidoc/Xsl/publidoc_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T11:43:24,325 copying publiforge/Openers/Publidoc/Xsl/publidoc_save_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T11:43:24,325 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T11:43:24,325 copying publiforge/Openers/Publiquiz/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T11:43:24,325 copying publiforge/Openers/Publiquiz/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T11:43:24,325 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Regex 2025-09-08T11:43:24,325 copying publiforge/Openers/Publiquiz/Regex/publiquiz_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Regex 2025-09-08T11:43:24,325 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,325 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-fill.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,325 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-media.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-select.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-check.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_coloring.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_composite.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_correct-line.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_blanks-fill.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_blanks-select.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_choices-check.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,326 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_choices-radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,327 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_matching.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,327 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing-categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,327 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,327 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_production.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,327 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_sort.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,327 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_wordsearch.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T11:43:24,327 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T11:43:24,327 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T11:43:24,327 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T11:43:24,328 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Fonts 2025-09-08T11:43:24,328 copying publiforge/Openers/Publiquiz/Static/Fonts/FontAwesome.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Fonts 2025-09-08T11:43:24,329 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T11:43:24,329 copying publiforge/Openers/Publiquiz/Static/Js/codemirror4publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T11:43:24,330 copying publiforge/Openers/Publiquiz/Static/Js/publiquiz_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T11:43:24,330 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Variables 2025-09-08T11:43:24,331 copying publiforge/Openers/Publiquiz/Variables/publiquiz.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Variables 2025-09-08T11:43:24,331 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T11:43:24,332 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T11:43:24,332 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T11:43:24,333 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T11:43:24,333 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T11:43:24,334 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T11:43:24,334 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T11:43:24,335 copying publiforge/Openers/Publiset/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T11:43:24,335 copying publiforge/Openers/Publiset/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T11:43:24,336 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Regex 2025-09-08T11:43:24,336 copying publiforge/Openers/Publiset/Regex/publiset_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Regex 2025-09-08T11:43:24,336 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T11:43:24,337 copying publiforge/Openers/Publiset/Seeds/publiset_composition.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T11:43:24,337 copying publiforge/Openers/Publiset/Seeds/publiset_selection.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T11:43:24,338 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T11:43:24,338 copying publiforge/Openers/Publiset/Static/Css/editor4publiset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T11:43:24,339 copying publiforge/Openers/Publiset/Static/Css/publiset_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T11:43:24,339 copying publiforge/Openers/Publiset/Static/Css/publiset_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T11:43:24,340 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T11:43:24,340 copying publiforge/Openers/Publiset/Static/Images/editor4publiset.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T11:43:24,340 copying publiforge/Openers/Publiset/Static/Images/editor4publiset.xcf -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T11:43:24,341 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T11:43:24,341 copying publiforge/Openers/Publiset/Static/Js/codemirror4publiset_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T11:43:24,342 copying publiforge/Openers/Publiset/Static/Js/editor4publiset.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T11:43:24,342 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_en.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T11:43:24,343 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_fr.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T11:43:24,343 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T11:43:24,344 copying publiforge/Openers/Publiset/Static/Js/publiset_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T11:43:24,345 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Variables 2025-09-08T11:43:24,345 copying publiforge/Openers/Publiset/Variables/publiset.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Variables 2025-09-08T11:43:24,345 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T11:43:24,346 copying publiforge/Openers/Publiset/Xsl/publiset_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T11:43:24,346 copying publiforge/Openers/Publiset/Xsl/publiset_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T11:43:24,347 copying publiforge/Openers/Publiset/Xsl/publiset_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T11:43:24,347 copying publiforge/Openers/Publiset/Xsl/publiset_render_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T11:43:24,348 copying publiforge/Openers/Publiset/Xsl/publiset_render_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T11:43:24,348 copying publiforge/Openers/Publiset/Xsl/publiset_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T11:43:24,349 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T11:43:24,349 copying publiforge/Openers/Xml/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T11:43:24,350 copying publiforge/Openers/Xml/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T11:43:24,350 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Css 2025-09-08T11:43:24,351 copying publiforge/Openers/Xml/Static/Css/editor4xml.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Css 2025-09-08T11:43:24,351 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T11:43:24,351 copying publiforge/Openers/Xml/Static/Images/e4x_folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T11:43:24,352 copying publiforge/Openers/Xml/Static/Images/editor4xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T11:43:24,353 copying publiforge/Openers/Xml/Static/Images/editor4xml.xcf -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T11:43:24,353 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T11:43:24,353 copying publiforge/Openers/Xml/Static/Js/editor4xml.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T11:43:24,355 copying publiforge/Openers/Xml/Static/Js/editor4xml_en.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T11:43:24,355 copying publiforge/Openers/Xml/Static/Js/editor4xml_fr.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T11:43:24,356 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T11:43:24,356 copying publiforge/Processors/CharCount/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T11:43:24,357 copying publiforge/Processors/CharCount/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T11:43:24,357 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount/Xsl 2025-09-08T11:43:24,357 copying publiforge/Processors/CharCount/Xsl/charcount.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount/Xsl 2025-09-08T11:43:24,358 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T11:43:24,358 copying publiforge/Processors/CleanStorage/generator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T11:43:24,359 copying publiforge/Processors/CleanStorage/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T11:43:24,359 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T11:43:24,359 copying publiforge/Processors/CleanStorage/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T11:43:24,360 copying publiforge/Processors/CleanStorage/lib/clean_storage.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T11:43:24,360 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T11:43:24,361 copying publiforge/Processors/DTBookValid/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T11:43:24,361 copying publiforge/Processors/DTBookValid/validator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T11:43:24,362 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid/RelaxNG 2025-09-08T11:43:24,362 copying publiforge/Processors/DTBookValid/RelaxNG/dtbook-2005-3.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid/RelaxNG 2025-09-08T11:43:24,363 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T11:43:24,363 copying publiforge/Processors/PackFilling/generator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T11:43:24,364 copying publiforge/Processors/PackFilling/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T11:43:24,364 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/Variables 2025-09-08T11:43:24,364 copying publiforge/Processors/PackFilling/Variables/packfilling.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/Variables 2025-09-08T11:43:24,365 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T11:43:24,365 copying publiforge/Processors/PackFilling/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T11:43:24,366 copying publiforge/Processors/PackFilling/lib/packfilling.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T11:43:24,366 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel 2025-09-08T11:43:24,366 copying publiforge/Processors/Parallel/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel 2025-09-08T11:43:24,367 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel/Variables 2025-09-08T11:43:24,367 copying publiforge/Processors/Parallel/Variables/parallel.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel/Variables 2025-09-08T11:43:24,368 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5 2025-09-08T11:43:24,368 copying publiforge/Processors/Publianim2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5 2025-09-08T11:43:24,368 copying publiforge/Processors/Publianim2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5 2025-09-08T11:43:24,369 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5/Variables 2025-09-08T11:43:24,369 copying publiforge/Processors/Publianim2Html5/Variables/publianim2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5/Variables 2025-09-08T11:43:24,370 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5/Xsl 2025-09-08T11:43:24,370 copying publiforge/Processors/Publianim2Html5/Xsl/publianim2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5/Xsl 2025-09-08T11:43:24,370 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T11:43:24,371 copying publiforge/Processors/Publidoc2DTBook/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T11:43:24,371 copying publiforge/Processors/Publidoc2DTBook/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T11:43:24,372 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T11:43:24,372 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T11:43:24,373 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T11:43:24,373 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T11:43:24,373 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T11:43:24,374 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T11:43:24,375 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T11:43:24,375 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T11:43:24,375 copying publiforge/Processors/Publidoc2EPub2/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T11:43:24,376 copying publiforge/Processors/Publidoc2EPub2/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T11:43:24,376 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates 2025-09-08T11:43:24,377 copying publiforge/Processors/Publidoc2EPub2/Templates/mimetype -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates 2025-09-08T11:43:24,377 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2025-09-08T11:43:24,377 copying publiforge/Processors/Publidoc2EPub2/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2025-09-08T11:43:24,378 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2025-09-08T11:43:24,378 copying publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2025-09-08T11:43:24,379 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T11:43:24,379 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T11:43:24,380 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T11:43:24,380 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T11:43:24,380 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T11:43:24,381 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T11:43:24,381 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T11:43:24,382 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T11:43:24,382 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ncx.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T11:43:24,383 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T11:43:24,384 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T11:43:24,384 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T11:43:24,385 copying publiforge/Processors/Publidoc2EPub2/jars/COPYING.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T11:43:24,385 copying publiforge/Processors/Publidoc2EPub2/jars/README.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T11:43:24,386 copying publiforge/Processors/Publidoc2EPub2/jars/THIRD-PARTY.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T11:43:24,386 copying publiforge/Processors/Publidoc2EPub2/jars/epubcheck.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T11:43:24,391 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T11:43:24,391 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-08T11:43:24,427 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-08T11:43:24,428 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-08T11:43:24,429 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-08T11:43:24,430 copying publiforge/Processors/Publidoc2EPub2/jars/lib/commons-compress-1.5.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T11:43:24,432 copying publiforge/Processors/Publidoc2EPub2/jars/lib/guava-14.0.1.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T11:43:24,440 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-08T11:43:24,441 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-08T11:43:24,442 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-08T11:43:24,443 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-08T11:43:24,444 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-08T11:43:24,447 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jing-20120724.0.0.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T11:43:24,451 copying publiforge/Processors/Publidoc2EPub2/jars/lib/sac-1.3.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T11:43:24,451 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T11:43:24,452 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/Apache-2.0.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T11:43:24,452 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/BSD-3-Clause.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T11:43:24,453 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/MPL-1.0.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T11:43:24,453 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/W3C.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T11:43:24,454 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T11:43:24,454 copying publiforge/Processors/Publidoc2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T11:43:24,455 copying publiforge/Processors/Publidoc2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T11:43:24,455 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates 2025-09-08T11:43:24,456 copying publiforge/Processors/Publidoc2EPub3/Templates/mimetype -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates 2025-09-08T11:43:24,456 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2025-09-08T11:43:24,456 copying publiforge/Processors/Publidoc2EPub3/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2025-09-08T11:43:24,457 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2025-09-08T11:43:24,457 copying publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2025-09-08T11:43:24,458 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Variables 2025-09-08T11:43:24,458 copying publiforge/Processors/Publidoc2EPub3/Variables/publidoc2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Variables 2025-09-08T11:43:24,459 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T11:43:24,459 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T11:43:24,459 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_nav.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T11:43:24,460 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T11:43:24,461 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_smil.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T11:43:24,461 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T11:43:24,462 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T11:43:24,462 copying publiforge/Processors/Publidoc2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T11:43:24,463 copying publiforge/Processors/Publidoc2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T11:43:24,463 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Css 2025-09-08T11:43:24,463 copying publiforge/Processors/Publidoc2Html5/Templates/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Css 2025-09-08T11:43:24,464 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T11:43:24,464 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_en.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T11:43:24,465 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_fr.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T11:43:24,465 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T11:43:24,466 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_play.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T11:43:24,466 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Js 2025-09-08T11:43:24,467 copying publiforge/Processors/Publidoc2Html5/Templates/Js/audio_player.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Js 2025-09-08T11:43:24,467 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T11:43:24,468 copying publiforge/Processors/Publidoc2Html5/Variables/publidoc2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T11:43:24,468 copying publiforge/Processors/Publidoc2Html5/Variables/publidoc2html5_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T11:43:24,469 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T11:43:24,469 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T11:43:24,469 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T11:43:24,470 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_media.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T11:43:24,471 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T11:43:24,471 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T11:43:24,471 copying publiforge/Processors/Publidoc2Pdf/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T11:43:24,472 copying publiforge/Processors/Publidoc2Pdf/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T11:43:24,472 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T11:43:24,473 copying publiforge/Processors/Publidoc2Pdf/Fonts/Script.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T11:43:24,476 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T11:43:24,476 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_post.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T11:43:24,476 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T11:43:24,477 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T11:43:24,477 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_dimension.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T11:43:24,478 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_font.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T11:43:24,478 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T11:43:24,479 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_layout.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T11:43:24,479 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T11:43:24,480 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T11:43:24,480 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T11:43:24,481 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T11:43:24,481 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T11:43:24,482 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T11:43:24,482 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T11:43:24,483 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T11:43:24,483 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T11:43:24,484 copying publiforge/Processors/Publidoc2XHtml/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T11:43:24,484 copying publiforge/Processors/Publidoc2XHtml/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T11:43:24,485 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Regex 2025-09-08T11:43:24,485 copying publiforge/Processors/Publidoc2XHtml/Regex/publidoc2xhtml_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Regex 2025-09-08T11:43:24,486 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,486 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_block.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,487 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_component.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,487 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_division.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,488 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_head.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,488 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_inline.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,489 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_section.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,489 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_top.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,490 copying publiforge/Processors/Publidoc2XHtml/Scss/publidoc.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T11:43:24,490 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T11:43:24,491 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T11:43:24,491 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/publidoc.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T11:43:24,492 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/publidoc.css.map -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T11:43:24,492 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/reset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T11:43:24,493 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,493 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/annotation.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,494 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,494 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,495 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio_play.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,495 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,496 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_previous.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,496 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,497 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/pulse.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,497 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/video.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T11:43:24,498 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T11:43:24,498 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/jquery.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T11:43:24,499 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/publidoc.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T11:43:24,499 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T11:43:24,500 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T11:43:24,500 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_html.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T11:43:24,501 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T11:43:24,501 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T11:43:24,502 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T11:43:24,502 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T11:43:24,503 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T11:43:24,503 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T11:43:24,504 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T11:43:24,505 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T11:43:24,505 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T11:43:24,506 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_media.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T11:43:24,507 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T11:43:24,507 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T11:43:24,507 copying publiforge/Processors/PublidocClean/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T11:43:24,508 copying publiforge/Processors/PublidocClean/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T11:43:24,509 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Regex 2025-09-08T11:43:24,509 copying publiforge/Processors/PublidocClean/Regex/publidocclean_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Regex 2025-09-08T11:43:24,509 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Variables 2025-09-08T11:43:24,510 copying publiforge/Processors/PublidocClean/Variables/publidocclean.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Variables 2025-09-08T11:43:24,510 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Xsl 2025-09-08T11:43:24,510 copying publiforge/Processors/PublidocClean/Xsl/publidocclean.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Xsl 2025-09-08T11:43:24,511 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T11:43:24,511 copying publiforge/Processors/PublidocValid/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T11:43:24,512 copying publiforge/Processors/PublidocValid/validator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T11:43:24,512 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T11:43:24,512 copying publiforge/Processors/PublidocValid/RelaxNG/publianim.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T11:43:24,513 copying publiforge/Processors/PublidocValid/RelaxNG/publidoc.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T11:43:24,514 copying publiforge/Processors/PublidocValid/RelaxNG/publiquiz.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T11:43:24,515 copying publiforge/Processors/PublidocValid/RelaxNG/publiset.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T11:43:24,515 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T11:43:24,516 copying publiforge/Processors/Publiquiz2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T11:43:24,516 copying publiforge/Processors/Publiquiz2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T11:43:24,517 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Variables 2025-09-08T11:43:24,517 copying publiforge/Processors/Publiquiz2EPub3/Variables/publiquiz2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Variables 2025-09-08T11:43:24,517 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T11:43:24,518 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T11:43:24,518 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T11:43:24,519 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T11:43:24,519 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T11:43:24,520 copying publiforge/Processors/Publiquiz2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T11:43:24,520 copying publiforge/Processors/Publiquiz2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T11:43:24,521 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,521 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_block.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,522 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_buttons.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,522 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_categories.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,523 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_choices.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,524 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_coloring.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,524 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_flashcard.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,525 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_matching.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,525 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_memory.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,526 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_pointing.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,527 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_production.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,527 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_wordsearch.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,528 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_inline.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,529 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_section.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,529 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_top.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,530 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/publiquiz.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2025-09-08T11:43:24,530 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,531 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_block.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,531 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_buttons.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,532 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_categories.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,532 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_choices.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,533 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_coloring.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,533 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_flashcard.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,534 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_matching.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,534 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_memory.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,535 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_pointing.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,535 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_production.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,536 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_wordsearch.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,537 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_inline.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,537 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_section.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,538 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_top.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,538 copying publiforge/Processors/Publiquiz2Html5/Scss/publiquiz.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T11:43:24,539 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2025-09-08T11:43:24,539 copying publiforge/Processors/Publiquiz2Html5/Templates/Audios/right.mp3 -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2025-09-08T11:43:24,540 copying publiforge/Processors/Publiquiz2Html5/Templates/Audios/right.ogg -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2025-09-08T11:43:24,540 copying publiforge/Processors/Publiquiz2Html5/Templates/Audios/wrong.mp3 -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2025-09-08T11:43:24,541 copying publiforge/Processors/Publiquiz2Html5/Templates/Audios/wrong.ogg -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2025-09-08T11:43:24,541 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T11:43:24,541 copying publiforge/Processors/Publiquiz2Html5/Templates/Css/publiquiz.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T11:43:24,542 copying publiforge/Processors/Publiquiz2Html5/Templates/Css/publiquiz.css.map -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T11:43:24,543 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2025-09-08T11:43:24,543 copying publiforge/Processors/Publiquiz2Html5/Templates/Fonts/FontAwesome.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2025-09-08T11:43:24,544 copying publiforge/Processors/Publiquiz2Html5/Templates/Fonts/FontAwesome.ttf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2025-09-08T11:43:24,545 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T11:43:24,546 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/back_card.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T11:43:24,548 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/brush.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T11:43:24,549 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/bucket.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T11:43:24,550 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/close.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T11:43:24,550 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/eraser.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T11:43:24,551 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/highlighter.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T11:43:24,551 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/loading.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T11:43:24,552 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,552 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/code.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,553 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/memory.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,553 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/memory_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,554 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publianim_drawing.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,555 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,556 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_basics.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,557 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_coloring.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,558 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_correct_line.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,558 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_flashcard.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,559 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,560 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_matching_link.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,560 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_wordsearch.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T11:43:24,561 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T11:43:24,561 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T11:43:24,562 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5_quiz.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T11:43:24,562 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T11:43:24,563 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T11:43:24,563 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T11:43:24,564 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T11:43:24,565 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T11:43:24,566 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T11:43:24,566 copying publiforge/Processors/Publiquiz2Scorm12/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T11:43:24,567 copying publiforge/Processors/Publiquiz2Scorm12/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T11:43:24,567 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T11:43:24,567 copying publiforge/Processors/Publiquiz2Scorm12/Templates/adlcp_rootv1p2.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T11:43:24,568 copying publiforge/Processors/Publiquiz2Scorm12/Templates/ims_xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T11:43:24,568 copying publiforge/Processors/Publiquiz2Scorm12/Templates/imscp_rootv1p1p2.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T11:43:24,569 copying publiforge/Processors/Publiquiz2Scorm12/Templates/imsmd_rootv1p2p1.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T11:43:24,570 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css 2025-09-08T11:43:24,570 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css 2025-09-08T11:43:24,570 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T11:43:24,571 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T11:43:24,571 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images/audio_play.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T11:43:24,572 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T11:43:24,572 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T11:43:24,573 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js/scorm_apiwrapper.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T11:43:24,573 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T11:43:24,573 copying publiforge/Processors/Publiquiz2Scorm12/Variables/publiquiz2scorm12.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T11:43:24,574 copying publiforge/Processors/Publiquiz2Scorm12/Variables/publiquiz2scorm12_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T11:43:24,574 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T11:43:24,575 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T11:43:24,575 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T11:43:24,576 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_ims.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T11:43:24,576 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T11:43:24,577 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T11:43:24,577 copying publiforge/Processors/Publiquiz2Scorm2004/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T11:43:24,578 copying publiforge/Processors/Publiquiz2Scorm2004/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T11:43:24,578 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,578 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/XMLSchema.dtd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,579 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlcp_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,579 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlnav_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,580 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlseq_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,581 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/datatypes.dtd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,581 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/ims_xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,582 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imscp_v1p1.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,582 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,583 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0auxresource.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,583 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0control.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,584 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0delivery.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,584 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0limit.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,585 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0objective.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,585 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0random.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,586 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0rollup.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,587 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0seqrule.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,587 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0util.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,588 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,588 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomCustom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,589 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomLoose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,589 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomStrict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,590 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T11:43:24,590 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css 2025-09-08T11:43:24,590 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css 2025-09-08T11:43:24,591 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T11:43:24,591 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T11:43:24,592 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js/scorm_apiwrapper.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T11:43:24,592 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T11:43:24,593 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/anyElement.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T11:43:24,593 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/dataTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T11:43:24,594 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/elementNames.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T11:43:24,594 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/elementTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T11:43:24,595 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/rootElement.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T11:43:24,596 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/vocabTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T11:43:24,596 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/vocabValues.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T11:43:24,597 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T11:43:24,597 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/extend/custom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T11:43:24,598 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/extend/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T11:43:24,598 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T11:43:24,598 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/unique/loose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T11:43:24,599 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/unique/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T11:43:24,599 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T11:43:24,600 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/custom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T11:43:24,600 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/loose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T11:43:24,601 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T11:43:24,601 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T11:43:24,602 copying publiforge/Processors/Publiquiz2Scorm2004/Variables/publiquiz2scorm2004.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T11:43:24,602 copying publiforge/Processors/Publiquiz2Scorm2004/Variables/publiquiz2scorm2004_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T11:43:24,603 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T11:43:24,603 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T11:43:24,603 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T11:43:24,604 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_ims.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T11:43:24,605 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T11:43:24,605 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T11:43:24,605 copying publiforge/Processors/Publiset2Publidoc/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T11:43:24,606 copying publiforge/Processors/Publiset2Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T11:43:24,606 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T11:43:24,607 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T11:43:24,607 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T11:43:24,608 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T11:43:24,608 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T11:43:24,608 copying publiforge/Processors/Publiset2Publidoc/Xsl/composition.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T11:43:24,609 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T11:43:24,610 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T11:43:24,610 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T11:43:24,611 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T11:43:24,611 copying publiforge/Processors/Publiset4Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T11:43:24,611 copying publiforge/Processors/Publiset4Publidoc/publiseter.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T11:43:24,612 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T11:43:24,612 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_meta.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T11:43:24,613 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T11:43:24,613 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_schema.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T11:43:24,614 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Xsl 2025-09-08T11:43:24,614 copying publiforge/Processors/Publiset4Publidoc/Xsl/publiset4publidoc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Xsl 2025-09-08T11:43:24,615 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T11:43:24,615 copying publiforge/Processors/Publiset4Publiquiz/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T11:43:24,615 copying publiforge/Processors/Publiset4Publiquiz/publiseter.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T11:43:24,616 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz/Xsl 2025-09-08T11:43:24,616 copying publiforge/Processors/Publiset4Publiquiz/Xsl/publiset4publiquiz.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz/Xsl 2025-09-08T11:43:24,617 creating build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T11:43:24,617 copying publiforge/RelaxNG/publiforge.rnc -> build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T11:43:24,617 copying publiforge/RelaxNG/publiforge.rng -> build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T11:43:24,618 creating build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T11:43:24,618 copying publiforge/Static/favicon.ico -> build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T11:43:24,619 copying publiforge/Static/robots.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T11:43:24,619 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T11:43:24,620 copying publiforge/Static/Css/base.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T11:43:24,620 copying publiforge/Static/Css/codemirror.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T11:43:24,621 copying publiforge/Static/Css/login.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T11:43:24,622 copying publiforge/Static/Css/pygments.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T11:43:24,622 copying publiforge/Static/Css/reset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T11:43:24,623 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,623 copying publiforge/Static/Images/action_add.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,623 copying publiforge/Static/Images/action_add_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,624 copying publiforge/Static/Images/action_browse.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,625 copying publiforge/Static/Images/action_browse_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,625 copying publiforge/Static/Images/action_build.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,626 copying publiforge/Static/Images/action_build_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,626 copying publiforge/Static/Images/action_cancel.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,627 copying publiforge/Static/Images/action_create.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,627 copying publiforge/Static/Images/action_dashboard_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,628 copying publiforge/Static/Images/action_delete.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,628 copying publiforge/Static/Images/action_delete_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,629 copying publiforge/Static/Images/action_diff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,629 copying publiforge/Static/Images/action_diff_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,630 copying publiforge/Static/Images/action_display.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,630 copying publiforge/Static/Images/action_display_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,631 copying publiforge/Static/Images/action_down_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,631 copying publiforge/Static/Images/action_download.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,632 copying publiforge/Static/Images/action_download_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,632 copying publiforge/Static/Images/action_duplicate.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,633 copying publiforge/Static/Images/action_edit_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,633 copying publiforge/Static/Images/action_export.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,634 copying publiforge/Static/Images/action_export_csv.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,634 copying publiforge/Static/Images/action_export_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,635 copying publiforge/Static/Images/action_filter.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,635 copying publiforge/Static/Images/action_help_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,636 copying publiforge/Static/Images/action_history_empty.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,636 copying publiforge/Static/Images/action_import.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,637 copying publiforge/Static/Images/action_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,637 copying publiforge/Static/Images/action_info_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,638 copying publiforge/Static/Images/action_log.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,638 copying publiforge/Static/Images/action_log_empty.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,639 copying publiforge/Static/Images/action_log_empty_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,640 copying publiforge/Static/Images/action_mkdir.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,640 copying publiforge/Static/Images/action_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,641 copying publiforge/Static/Images/action_next_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,641 copying publiforge/Static/Images/action_note.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,642 copying publiforge/Static/Images/action_note_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,642 copying publiforge/Static/Images/action_overview_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,643 copying publiforge/Static/Images/action_overview_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,643 copying publiforge/Static/Images/action_pack.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,644 copying publiforge/Static/Images/action_pipe.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,644 copying publiforge/Static/Images/action_progress_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,645 copying publiforge/Static/Images/action_remove.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,645 copying publiforge/Static/Images/action_remove_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,646 copying publiforge/Static/Images/action_rename_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,646 copying publiforge/Static/Images/action_render.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,647 copying publiforge/Static/Images/action_render_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,647 copying publiforge/Static/Images/action_reset_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,648 copying publiforge/Static/Images/action_save.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,648 copying publiforge/Static/Images/action_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,649 copying publiforge/Static/Images/action_select.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,649 copying publiforge/Static/Images/action_select_get.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,650 copying publiforge/Static/Images/action_select_get_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,650 copying publiforge/Static/Images/action_select_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,651 copying publiforge/Static/Images/action_start.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,651 copying publiforge/Static/Images/action_start_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,652 copying publiforge/Static/Images/action_stop.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,652 copying publiforge/Static/Images/action_stop_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,653 copying publiforge/Static/Images/action_synchronize.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,653 copying publiforge/Static/Images/action_synchronize_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,654 copying publiforge/Static/Images/action_take.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,654 copying publiforge/Static/Images/action_take_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,655 copying publiforge/Static/Images/action_up_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,655 copying publiforge/Static/Images/action_upload.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,656 copying publiforge/Static/Images/action_upload_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,656 copying publiforge/Static/Images/action_view.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,657 copying publiforge/Static/Images/action_view_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,658 copying publiforge/Static/Images/admin.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,658 copying publiforge/Static/Images/back.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,659 copying publiforge/Static/Images/breadcrumbs_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,659 copying publiforge/Static/Images/build.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,660 copying publiforge/Static/Images/build22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,660 copying publiforge/Static/Images/build32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,661 copying publiforge/Static/Images/build72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,661 copying publiforge/Static/Images/build72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,662 copying publiforge/Static/Images/build96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,662 copying publiforge/Static/Images/check.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,663 copying publiforge/Static/Images/close_dark.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,663 copying publiforge/Static/Images/close_light.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,664 copying publiforge/Static/Images/collapse_closed.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,665 copying publiforge/Static/Images/collapse_current_closed.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,665 copying publiforge/Static/Images/collapse_current_open.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,666 copying publiforge/Static/Images/collapse_open.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,666 copying publiforge/Static/Images/edit32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,667 copying publiforge/Static/Images/equal.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,667 copying publiforge/Static/Images/extractor.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,668 copying publiforge/Static/Images/extractor22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,668 copying publiforge/Static/Images/extractor32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,669 copying publiforge/Static/Images/flash_alert.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,669 copying publiforge/Static/Images/flash_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,670 copying publiforge/Static/Images/folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,670 copying publiforge/Static/Images/folder22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,671 copying publiforge/Static/Images/folder32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,671 copying publiforge/Static/Images/footer_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,672 copying publiforge/Static/Images/go_first.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,673 copying publiforge/Static/Images/go_first_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,673 copying publiforge/Static/Images/go_last.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,674 copying publiforge/Static/Images/go_last_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,674 copying publiforge/Static/Images/go_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,675 copying publiforge/Static/Images/go_next_file.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,675 copying publiforge/Static/Images/go_next_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,676 copying publiforge/Static/Images/go_next_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,676 copying publiforge/Static/Images/go_previous.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,677 copying publiforge/Static/Images/go_previous_file.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,677 copying publiforge/Static/Images/go_previous_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,678 copying publiforge/Static/Images/go_previous_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,678 copying publiforge/Static/Images/go_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,679 copying publiforge/Static/Images/go_top22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,679 copying publiforge/Static/Images/group.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,680 copying publiforge/Static/Images/group22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,680 copying publiforge/Static/Images/group32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,681 copying publiforge/Static/Images/history.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,681 copying publiforge/Static/Images/history22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,682 copying publiforge/Static/Images/history32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,682 copying publiforge/Static/Images/in_menu_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,683 copying publiforge/Static/Images/in_menu_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,683 copying publiforge/Static/Images/indexer.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,684 copying publiforge/Static/Images/indexer22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,684 copying publiforge/Static/Images/indexer32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,685 copying publiforge/Static/Images/info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,685 copying publiforge/Static/Images/info22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,686 copying publiforge/Static/Images/info32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,687 copying publiforge/Static/Images/job.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,687 copying publiforge/Static/Images/job22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,688 copying publiforge/Static/Images/job32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,688 copying publiforge/Static/Images/left_title.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,689 copying publiforge/Static/Images/light_green.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,689 copying publiforge/Static/Images/light_grey.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,690 copying publiforge/Static/Images/light_red.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,690 copying publiforge/Static/Images/light_yellow.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,691 copying publiforge/Static/Images/link.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,691 copying publiforge/Static/Images/link22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,692 copying publiforge/Static/Images/link32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,692 copying publiforge/Static/Images/list_header.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,693 copying publiforge/Static/Images/log_download.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,693 copying publiforge/Static/Images/log_error.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,694 copying publiforge/Static/Images/log_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,694 copying publiforge/Static/Images/log_warning.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,695 copying publiforge/Static/Images/logout.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,695 copying publiforge/Static/Images/notfound.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,696 copying publiforge/Static/Images/open_false.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,697 copying publiforge/Static/Images/open_true.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,697 copying publiforge/Static/Images/opener22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,698 copying publiforge/Static/Images/opener32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,698 copying publiforge/Static/Images/overview_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,699 copying publiforge/Static/Images/overview_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,699 copying publiforge/Static/Images/pack.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,700 copying publiforge/Static/Images/pack22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,700 copying publiforge/Static/Images/pack32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,701 copying publiforge/Static/Images/pack72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,701 copying publiforge/Static/Images/pack72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,702 copying publiforge/Static/Images/pack96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,702 copying publiforge/Static/Images/processing.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,703 copying publiforge/Static/Images/processing22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,703 copying publiforge/Static/Images/processing32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,704 copying publiforge/Static/Images/progress.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,705 copying publiforge/Static/Images/project.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,705 copying publiforge/Static/Images/project22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,706 copying publiforge/Static/Images/project32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,706 copying publiforge/Static/Images/publiforge.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,707 copying publiforge/Static/Images/pyramid.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,708 copying publiforge/Static/Images/role.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,708 copying publiforge/Static/Images/role22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,709 copying publiforge/Static/Images/role32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,709 copying publiforge/Static/Images/search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,710 copying publiforge/Static/Images/search22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,710 copying publiforge/Static/Images/search32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,711 copying publiforge/Static/Images/selection.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,711 copying publiforge/Static/Images/selection_remove_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,712 copying publiforge/Static/Images/selection_remove_sure.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,712 copying publiforge/Static/Images/sort_asc.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,713 copying publiforge/Static/Images/sort_desc.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,713 copying publiforge/Static/Images/sort_down.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,714 copying publiforge/Static/Images/sort_down_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,714 copying publiforge/Static/Images/sort_up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,715 copying publiforge/Static/Images/sort_up_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,715 copying publiforge/Static/Images/storage.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,716 copying publiforge/Static/Images/storage22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,716 copying publiforge/Static/Images/storage32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,717 copying publiforge/Static/Images/tab.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,717 copying publiforge/Static/Images/task.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,718 copying publiforge/Static/Images/task22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,718 copying publiforge/Static/Images/task32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,719 copying publiforge/Static/Images/task72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,719 copying publiforge/Static/Images/task72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,720 copying publiforge/Static/Images/task96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,720 copying publiforge/Static/Images/up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,721 copying publiforge/Static/Images/user.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,721 copying publiforge/Static/Images/user22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,722 copying publiforge/Static/Images/user32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,723 copying publiforge/Static/Images/user_pre.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,723 copying publiforge/Static/Images/valid-xhtml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,724 copying publiforge/Static/Images/value.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,724 copying publiforge/Static/Images/value22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,725 copying publiforge/Static/Images/value32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,725 copying publiforge/Static/Images/vcss.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,726 copying publiforge/Static/Images/wait_build.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,726 copying publiforge/Static/Images/wait_slow.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,727 copying publiforge/Static/Images/wait_synchro.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,727 copying publiforge/Static/Images/wcag1aa.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T11:43:24,728 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,728 copying publiforge/Static/Images/MimeTypes/css.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,728 copying publiforge/Static/Images/MimeTypes/csv.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,729 copying publiforge/Static/Images/MimeTypes/epub+zip.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,729 copying publiforge/Static/Images/MimeTypes/folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,730 copying publiforge/Static/Images/MimeTypes/font-woff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,731 copying publiforge/Static/Images/MimeTypes/gif.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,731 copying publiforge/Static/Images/MimeTypes/html.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,732 copying publiforge/Static/Images/MimeTypes/indesign-idml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,732 copying publiforge/Static/Images/MimeTypes/indesign-indd.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,733 copying publiforge/Static/Images/MimeTypes/javascript.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,733 copying publiforge/Static/Images/MimeTypes/jpeg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,734 copying publiforge/Static/Images/MimeTypes/mp4.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,734 copying publiforge/Static/Images/MimeTypes/mpeg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,735 copying publiforge/Static/Images/MimeTypes/msword.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,735 copying publiforge/Static/Images/MimeTypes/octet-stream.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,736 copying publiforge/Static/Images/MimeTypes/ogg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,736 copying publiforge/Static/Images/MimeTypes/pdf.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,737 copying publiforge/Static/Images/MimeTypes/plain.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,737 copying publiforge/Static/Images/MimeTypes/png.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,738 copying publiforge/Static/Images/MimeTypes/postscript.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,738 copying publiforge/Static/Images/MimeTypes/relaxng.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,739 copying publiforge/Static/Images/MimeTypes/svg+xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,739 copying publiforge/Static/Images/MimeTypes/tiff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,740 copying publiforge/Static/Images/MimeTypes/unknown.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,740 copying publiforge/Static/Images/MimeTypes/vnd.ms-excel.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,741 copying publiforge/Static/Images/MimeTypes/vnd.ms-opentype.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,741 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.spreadsheet.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,742 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.text.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,742 copying publiforge/Static/Images/MimeTypes/x-msdos-program.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,743 copying publiforge/Static/Images/MimeTypes/x-msvideo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,743 copying publiforge/Static/Images/MimeTypes/x-python.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,744 copying publiforge/Static/Images/MimeTypes/x-shockwave-flash.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,745 copying publiforge/Static/Images/MimeTypes/x-tar.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,745 copying publiforge/Static/Images/MimeTypes/x-wav.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,746 copying publiforge/Static/Images/MimeTypes/xml-dtd.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,746 copying publiforge/Static/Images/MimeTypes/xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,747 copying publiforge/Static/Images/MimeTypes/zip.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T11:43:24,747 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,748 copying publiforge/Static/Js/base.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,748 copying publiforge/Static/Js/bld_progress.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,749 copying publiforge/Static/Js/bld_results.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,749 copying publiforge/Static/Js/bld_view.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,750 copying publiforge/Static/Js/codemirror.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,751 copying publiforge/Static/Js/codemirror4ini.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,752 copying publiforge/Static/Js/codemirror4xml.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,752 copying publiforge/Static/Js/codemirror_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,753 copying publiforge/Static/Js/jquery.cookie.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,753 copying publiforge/Static/Js/jquery.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,754 copying publiforge/Static/Js/prc_edit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,755 copying publiforge/Static/Js/stg_browse.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,755 copying publiforge/Static/Js/stg_edit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,756 copying publiforge/Static/Js/stg_index.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,756 copying publiforge/Static/Js/tsk_index.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T11:43:24,757 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T11:43:24,757 copying publiforge/Static/Js/Tests/index.html -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T11:43:24,758 copying publiforge/Static/Js/Tests/qunit.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T11:43:24,758 copying publiforge/Static/Js/Tests/qunit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T11:43:24,759 copying publiforge/Static/Js/Tests/tests.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T11:43:24,760 creating build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,760 copying publiforge/Templates/base.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,761 copying publiforge/Templates/bld_launch.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,761 copying publiforge/Templates/bld_output.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,762 copying publiforge/Templates/bld_pack.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,762 copying publiforge/Templates/bld_processing.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,763 copying publiforge/Templates/bld_progress.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,763 copying publiforge/Templates/bld_results.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,764 copying publiforge/Templates/bld_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,764 copying publiforge/Templates/error.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,765 copying publiforge/Templates/fil_display.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,765 copying publiforge/Templates/fil_info.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,766 copying publiforge/Templates/fil_modify.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,766 copying publiforge/Templates/fil_search.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,767 copying publiforge/Templates/fil_vcs_params.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,767 copying publiforge/Templates/files_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,768 copying publiforge/Templates/files_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,769 copying publiforge/Templates/flash.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,769 copying publiforge/Templates/grp_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,770 copying publiforge/Templates/grp_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,770 copying publiforge/Templates/grp_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,771 copying publiforge/Templates/home.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,771 copying publiforge/Templates/idx_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,772 copying publiforge/Templates/idx_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,772 copying publiforge/Templates/idx_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,773 copying publiforge/Templates/job_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,773 copying publiforge/Templates/job_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,774 copying publiforge/Templates/job_log.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,774 copying publiforge/Templates/job_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,775 copying publiforge/Templates/login.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,775 copying publiforge/Templates/maintenance.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,776 copying publiforge/Templates/mbr_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,776 copying publiforge/Templates/mbr_groups_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,777 copying publiforge/Templates/mbr_groups_paging.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,777 copying publiforge/Templates/mbr_groups_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,778 copying publiforge/Templates/mbr_paging.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,778 copying publiforge/Templates/mbr_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,779 copying publiforge/Templates/pck_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,779 copying publiforge/Templates/pck_events.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,780 copying publiforge/Templates/pck_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,781 copying publiforge/Templates/pck_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,781 copying publiforge/Templates/prc_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,782 copying publiforge/Templates/prc_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,782 copying publiforge/Templates/prj_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,783 copying publiforge/Templates/prj_dashboard.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,783 copying publiforge/Templates/prj_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,784 copying publiforge/Templates/prj_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,785 copying publiforge/Templates/prj_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,785 copying publiforge/Templates/rol_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,786 copying publiforge/Templates/rol_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,786 copying publiforge/Templates/sit_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,787 copying publiforge/Templates/stg_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,787 copying publiforge/Templates/stg_browse.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,788 copying publiforge/Templates/stg_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,789 copying publiforge/Templates/stg_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,789 copying publiforge/Templates/stg_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,790 copying publiforge/Templates/tsk_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,790 copying publiforge/Templates/tsk_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,791 copying publiforge/Templates/tsk_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,791 copying publiforge/Templates/usr_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,792 copying publiforge/Templates/usr_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,792 copying publiforge/Templates/usr_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T11:43:24,793 copying publiforge/tests/test.ini -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T11:43:24,793 creating build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T11:43:24,794 copying publiforge/tests/Data/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T11:43:24,794 copying publiforge/tests/Data/test.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T11:43:24,795 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge 2025-09-08T11:43:24,795 copying publiforge/scaffolds/Front/PubliForge/development.ini_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge 2025-09-08T11:43:24,796 copying publiforge/scaffolds/Front/PubliForge/pf+package+.ini_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge 2025-09-08T11:43:24,796 copying publiforge/scaffolds/Front/PubliForge/pf+package+.wsgi_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge 2025-09-08T11:43:24,797 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Apache 2025-09-08T11:43:24,797 copying publiforge/scaffolds/Front/PubliForge/Configuration/Apache/+package+.publiforge.conf_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Apache 2025-09-08T11:43:24,797 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2025-09-08T11:43:24,798 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/hgwebdir.conf_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2025-09-08T11:43:24,798 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/hgwebdir.wsgi_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2025-09-08T11:43:24,799 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/users_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2025-09-08T11:43:24,799 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Projects 2025-09-08T11:43:24,800 copying publiforge/scaffolds/Front/PubliForge/Configuration/Projects/+pfproject_id+.pfprj.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Projects 2025-09-08T11:43:24,800 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2025-09-08T11:43:24,800 copying publiforge/scaffolds/Front/PubliForge/Configuration/Storages/+storage+.hg.pfstg.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2025-09-08T11:43:24,801 copying publiforge/scaffolds/Front/PubliForge/Configuration/Storages/+storage+.local.pfstg.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2025-09-08T11:43:24,801 copying publiforge/scaffolds/Front/PubliForge/Configuration/Storages/result.pfstg.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2025-09-08T11:43:24,802 copying publiforge/scaffolds/Front/PubliForge/Configuration/Storages/sandbox.pfstg.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2025-09-08T11:43:24,802 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Users 2025-09-08T11:43:24,803 copying publiforge/scaffolds/Front/PubliForge/Configuration/Users/+package+.pfusr.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Users 2025-09-08T11:43:24,803 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static 2025-09-08T11:43:24,803 copying publiforge/scaffolds/Front/PubliForge/Static/favicon.ico -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static 2025-09-08T11:43:24,804 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static/Css 2025-09-08T11:43:24,804 copying publiforge/scaffolds/Front/PubliForge/Static/Css/+package+.css_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static/Css 2025-09-08T11:43:24,805 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static/Images 2025-09-08T11:43:24,805 copying publiforge/scaffolds/Front/PubliForge/Static/Images/+package+.png -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static/Images 2025-09-08T11:43:24,806 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme 2025-09-08T11:43:24,806 copying publiforge/scaffolds/LePrisme/+package+.pfprc.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme 2025-09-08T11:43:24,807 copying publiforge/scaffolds/LePrisme/leprisme.ini_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme 2025-09-08T11:43:24,807 copying publiforge/scaffolds/LePrisme/processor.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme 2025-09-08T11:43:24,808 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Templates 2025-09-08T11:43:24,808 copying publiforge/scaffolds/LePrisme/Templates/dummy1.txt -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Templates 2025-09-08T11:43:24,808 copying publiforge/scaffolds/LePrisme/Templates/dummy2.txt -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Templates 2025-09-08T11:43:24,809 copying publiforge/scaffolds/LePrisme/Templates/dummy3.txt -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Templates 2025-09-08T11:43:24,809 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Variables 2025-09-08T11:43:24,810 copying publiforge/scaffolds/LePrisme/Variables/+package+.pfvar.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Variables 2025-09-08T11:43:24,810 copying publiforge/scaffolds/LePrisme/Variables/+package+_available.pfvar.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Variables 2025-09-08T11:43:24,811 copying publiforge/scaffolds/LePrisme/Variables/+package+_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Variables 2025-09-08T11:43:24,811 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/lib 2025-09-08T11:43:24,811 copying publiforge/scaffolds/LePrisme/lib/__init__.py_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/lib 2025-09-08T11:43:24,812 copying publiforge/lib/rsync/_librsync.c -> build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T11:43:24,818 running build_ext 2025-09-08T11:43:25,155 building 'publiforge.lib.rsync._librsync' extension 2025-09-08T11:43:25,156 creating build/temp.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T11:43:25,156 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-08T11:43:25,511 publiforge/lib/rsync/_librsync.c:26:10: fatal error: librsync.h: No such file or directory 2025-09-08T11:43:25,511 26 | #include 2025-09-08T11:43:25,512 | ^~~~~~~~~~~~ 2025-09-08T11:43:25,512 compilation terminated. 2025-09-08T11:43:25,515 error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1 2025-09-08T11:43:25,665 ERROR: python setup.py bdist_wheel exited with 1 2025-09-08T11:43:25,677 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2025-09-08T11:43:25,677 exec(compile('"'"''"'"''"'"' 2025-09-08T11:43:25,677 # This is -- a caller that pip uses to run setup.py 2025-09-08T11:43:25,677 # 2025-09-08T11:43:25,677 # - It imports setuptools before invoking setup.py, to enable projects that directly 2025-09-08T11:43:25,677 # import from `distutils.core` to work with newer packaging standards. 2025-09-08T11:43:25,677 # - It provides a clear error message when setuptools is not installed. 2025-09-08T11:43:25,677 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2025-09-08T11:43:25,677 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2025-09-08T11:43:25,677 # manifest_maker: standard file '"'"'-c'"'"' not found". 2025-09-08T11:43:25,677 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2025-09-08T11:43:25,677 import os, sys, tokenize, traceback 2025-09-08T11:43:25,677 2025-09-08T11:43:25,677 try: 2025-09-08T11:43:25,677 import setuptools 2025-09-08T11:43:25,677 except ImportError: 2025-09-08T11:43:25,677 print( 2025-09-08T11:43:25,677 "ERROR: Can not execute `setup.py` since setuptools failed to import in " 2025-09-08T11:43:25,677 "the build environment with exception:", 2025-09-08T11:43:25,677 file=sys.stderr, 2025-09-08T11:43:25,677 ) 2025-09-08T11:43:25,677 traceback.print_exc() 2025-09-08T11:43:25,677 sys.exit(1) 2025-09-08T11:43:25,677 2025-09-08T11:43:25,677 __file__ = %r 2025-09-08T11:43:25,677 sys.argv[0] = __file__ 2025-09-08T11:43:25,677 2025-09-08T11:43:25,677 if os.path.exists(__file__): 2025-09-08T11:43:25,677 filename = __file__ 2025-09-08T11:43:25,677 with tokenize.open(__file__) as f: 2025-09-08T11:43:25,677 setup_py_code = f.read() 2025-09-08T11:43:25,677 else: 2025-09-08T11:43:25,677 filename = "" 2025-09-08T11:43:25,677 setup_py_code = "from setuptools import setup; setup()" 2025-09-08T11:43:25,677 2025-09-08T11:43:25,677 exec(compile(setup_py_code, filename, "exec")) 2025-09-08T11:43:25,677 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-jzt_t531/publiforge_d2f1bfa7cced42f296db77a69aa94351/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-1emjt0az[/] 2025-09-08T11:43:25,677 [bold magenta]cwd[/]: /tmp/pip-wheel-jzt_t531/publiforge_d2f1bfa7cced42f296db77a69aa94351/ 2025-09-08T11:43:25,677 Building wheel for publiforge (setup.py): finished with status 'error' 2025-09-08T11:43:25,678 ERROR: Failed building wheel for publiforge 2025-09-08T11:43:25,679 Running setup.py clean for publiforge 2025-09-08T11:43:25,680 Running command python setup.py clean 2025-09-08T11:43:26,367 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T11:43:26,367 warnings.warn(msg) 2025-09-08T11:43:26,367 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T11:43:26,367 warnings.warn(msg) 2025-09-08T11:43:26,589 running clean 2025-09-08T11:43:26,733 removing 'build/temp.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T11:43:26,734 removing 'build/lib.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T11:43:26,777 'build/bdist.linux-armv7l' does not exist -- can't clean it 2025-09-08T11:43:26,777 'build/scripts-3.13' does not exist -- can't clean it 2025-09-08T11:43:26,777 removing 'build' 2025-09-08T11:43:26,869 Failed to build publiforge 2025-09-08T11:43:26,870 ERROR: Failed to build one or more wheels 2025-09-08T11:43:26,871 Exception information: 2025-09-08T11:43:26,871 Traceback (most recent call last): 2025-09-08T11:43:26,871 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper 2025-09-08T11:43:26,871 status = _inner_run() 2025-09-08T11:43:26,871 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run 2025-09-08T11:43:26,871 return self.run(options, args) 2025-09-08T11:43:26,871 ~~~~~~~~^^^^^^^^^^^^^^^ 2025-09-08T11:43:26,871 File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 68, in wrapper 2025-09-08T11:43:26,871 return func(self, options, args) 2025-09-08T11:43:26,871 File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line 180, in run 2025-09-08T11:43:26,871 raise CommandError("Failed to build one or more wheels") 2025-09-08T11:43:26,871 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2025-09-08T11:43:26,875 Removed build tracker: '/tmp/pip-build-tracker-sibx89z2'