2025-09-08T10:44:06,229 Created temporary directory: /tmp/pip-build-tracker-0z8u64i3 2025-09-08T10:44:06,229 Initialized build tracking at /tmp/pip-build-tracker-0z8u64i3 2025-09-08T10:44:06,229 Created build tracker: /tmp/pip-build-tracker-0z8u64i3 2025-09-08T10:44:06,229 Entered build tracker: /tmp/pip-build-tracker-0z8u64i3 2025-09-08T10:44:06,230 Created temporary directory: /tmp/pip-wheel-6497a9jw 2025-09-08T10:44:06,233 Created temporary directory: /tmp/pip-ephem-wheel-cache-1xls04zb 2025-09-08T10:44:06,291 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-09-08T10:44:06,294 2 location(s) to search for versions of publiforge: 2025-09-08T10:44:06,294 * https://pypi.org/simple/publiforge/ 2025-09-08T10:44:06,294 * https://www.piwheels.org/simple/publiforge/ 2025-09-08T10:44:06,294 Fetching project page and analyzing links: https://pypi.org/simple/publiforge/ 2025-09-08T10:44:06,294 Getting page https://pypi.org/simple/publiforge/ 2025-09-08T10:44:06,296 Found index url https://pypi.org/simple/ 2025-09-08T10:44:06,366 Fetched page https://pypi.org/simple/publiforge/ as application/vnd.pypi.simple.v1+json 2025-09-08T10:44:06,368 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-08T10:44:06,368 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-08T10:44:06,368 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-08T10:44:06,368 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-08T10:44:06,369 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-08T10:44:06,369 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-08T10:44:06,369 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-08T10:44:06,369 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-08T10:44:06,370 Fetching project page and analyzing links: https://www.piwheels.org/simple/publiforge/ 2025-09-08T10:44:06,370 Getting page https://www.piwheels.org/simple/publiforge/ 2025-09-08T10:44:06,371 Found index url https://www.piwheels.org/simple/ 2025-09-08T10:44:06,467 Fetched page https://www.piwheels.org/simple/publiforge/ as text/html 2025-09-08T10:44:06,468 Skipping link: not a file: https://www.piwheels.org/simple/publiforge/ 2025-09-08T10:44:06,468 Skipping link: not a file: https://pypi.org/simple/publiforge/ 2025-09-08T10:44:06,494 Given no hashes to check 1 links for project 'publiforge': discarding no candidates 2025-09-08T10:44:06,495 Collecting publiforge==2.1 2025-09-08T10:44:06,496 Created temporary directory: /tmp/pip-unpack-yrxscfnb 2025-09-08T10:44:06,874 Downloading PubliForge-2.1.tar.gz (34.5 MB) 2025-09-08T10:44:13,485 Added publiforge==2.1 from https://files.pythonhosted.org/packages/ce/99/e78d990cae82141d5f57421395959774c03e3a34d2927996a60732875354/PubliForge-2.1.tar.gz to build tracker '/tmp/pip-build-tracker-0z8u64i3' 2025-09-08T10:44:13,486 Running setup.py (path:/tmp/pip-wheel-6497a9jw/publiforge_cea0ad06fe8c4cb7916f9d8b29a21eb4/setup.py) egg_info for package publiforge 2025-09-08T10:44:13,486 Created temporary directory: /tmp/pip-pip-egg-info-d28988md 2025-09-08T10:44:13,487 Preparing metadata (setup.py): started 2025-09-08T10:44:13,487 Running command python setup.py egg_info 2025-09-08T10:44:14,195 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T10:44:14,195 warnings.warn(msg) 2025-09-08T10:44:14,195 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T10:44:14,195 warnings.warn(msg) 2025-09-08T10:44:14,682 running egg_info 2025-09-08T10:44:14,758 creating /tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info 2025-09-08T10:44:14,758 writing /tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info/PKG-INFO 2025-09-08T10:44:14,764 writing dependency_links to /tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info/dependency_links.txt 2025-09-08T10:44:14,765 writing entry points to /tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info/entry_points.txt 2025-09-08T10:44:14,768 writing requirements to /tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info/requires.txt 2025-09-08T10:44:14,769 writing top-level names to /tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info/top_level.txt 2025-09-08T10:44:14,769 writing manifest file '/tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info/SOURCES.txt' 2025-09-08T10:44:15,079 reading manifest file '/tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info/SOURCES.txt' 2025-09-08T10:44:15,080 reading manifest template 'MANIFEST.in' 2025-09-08T10:44:15,082 warning: no files found matching '*.rst' 2025-09-08T10:44:15,460 warning: no files found matching '*.jinja2' under directory 'publiforge' 2025-09-08T10:44:15,647 warning: no files found matching '*.mak' under directory 'publiforge' 2025-09-08T10:44:15,709 warning: no files found matching '*.mako' under directory 'publiforge' 2025-09-08T10:44:16,024 warning: no files found matching '*.conf' under directory 'publiforge' 2025-09-08T10:44:16,162 writing manifest file '/tmp/pip-pip-egg-info-d28988md/PubliForge.egg-info/SOURCES.txt' 2025-09-08T10:44:16,275 Preparing metadata (setup.py): finished with status 'done' 2025-09-08T10:44:16,280 Source in /tmp/pip-wheel-6497a9jw/publiforge_cea0ad06fe8c4cb7916f9d8b29a21eb4 has version 2.1, which satisfies requirement publiforge==2.1 from https://files.pythonhosted.org/packages/ce/99/e78d990cae82141d5f57421395959774c03e3a34d2927996a60732875354/PubliForge-2.1.tar.gz 2025-09-08T10:44:16,280 Removed publiforge==2.1 from https://files.pythonhosted.org/packages/ce/99/e78d990cae82141d5f57421395959774c03e3a34d2927996a60732875354/PubliForge-2.1.tar.gz from build tracker '/tmp/pip-build-tracker-0z8u64i3' 2025-09-08T10:44:16,297 Created temporary directory: /tmp/pip-unpack-uy5haqn6 2025-09-08T10:44:16,298 Created temporary directory: /tmp/pip-unpack-em9lh7jo 2025-09-08T10:44:16,298 Building wheels for collected packages: publiforge 2025-09-08T10:44:16,299 Created temporary directory: /tmp/pip-wheel-s16mzo7w 2025-09-08T10:44:16,300 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-08T10:44:16,301 Building wheel for publiforge (setup.py): started 2025-09-08T10:44:16,302 Destination directory: /tmp/pip-wheel-s16mzo7w 2025-09-08T10:44:16,302 Running command python setup.py bdist_wheel 2025-09-08T10:44:16,985 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T10:44:16,986 warnings.warn(msg) 2025-09-08T10:44:16,986 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T10:44:16,986 warnings.warn(msg) 2025-09-08T10:44:17,386 running bdist_wheel 2025-09-08T10:44:17,754 running build 2025-09-08T10:44:17,754 running build_py 2025-09-08T10:44:17,832 creating build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T10:44:17,832 copying publiforge/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T10:44:17,833 copying publiforge/initialize.py -> build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T10:44:17,834 creating build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,834 copying publiforge/views/job.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,835 copying publiforge/views/file.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,836 copying publiforge/views/build.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,836 copying publiforge/views/maestro.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,837 copying publiforge/views/task.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,837 copying publiforge/views/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,838 copying publiforge/views/group.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,839 copying publiforge/views/role.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,839 copying publiforge/views/selection.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,840 copying publiforge/views/user.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,840 copying publiforge/views/pack.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,841 copying publiforge/views/storage.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,842 copying publiforge/views/security.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,842 copying publiforge/views/indexer.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,843 copying publiforge/views/site.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,843 copying publiforge/views/project.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,844 copying publiforge/views/home.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,844 copying publiforge/views/maintenance.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,845 copying publiforge/views/xmlrpc.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,845 copying publiforge/views/processing.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T10:44:17,847 creating build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,847 copying publiforge/lib/paging.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,847 copying publiforge/lib/utils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,848 copying publiforge/lib/tabset.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,848 copying publiforge/lib/form.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,849 copying publiforge/lib/xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,850 copying publiforge/lib/log.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,850 copying publiforge/lib/packutils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,851 copying publiforge/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,851 copying publiforge/lib/config.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,852 copying publiforge/lib/breadcrumbs.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,852 copying publiforge/lib/menu.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,853 copying publiforge/lib/filter.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,853 copying publiforge/lib/viewutils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,854 copying publiforge/lib/handler.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,855 copying publiforge/lib/i18n.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,855 copying publiforge/lib/debug.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T10:44:17,856 creating build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,856 copying publiforge/scripts/pfimage2svg.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,857 copying publiforge/scripts/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,857 copying publiforge/scripts/pfpopulate.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,858 copying publiforge/scripts/pfbuild.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,859 copying publiforge/scripts/pfminify.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,859 copying publiforge/scripts/pftexmath.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,860 copying publiforge/scripts/pfscheduler.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,860 copying publiforge/scripts/pfbackup.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T10:44:17,861 creating build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,861 copying publiforge/models/indexers.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,862 copying publiforge/models/packs.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,863 copying publiforge/models/jobs.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,863 copying publiforge/models/storages.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,864 copying publiforge/models/roles.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,864 copying publiforge/models/users.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,865 copying publiforge/models/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,865 copying publiforge/models/processings.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,866 copying publiforge/models/processors.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,866 copying publiforge/models/tasks.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,867 copying publiforge/models/projects.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,867 copying publiforge/models/groups.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T10:44:17,868 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds 2025-09-08T10:44:17,868 copying publiforge/scaffolds/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds 2025-09-08T10:44:17,869 creating build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,870 copying publiforge/tests/test_models_storages.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,870 copying publiforge/tests/test_models_projects.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,871 copying publiforge/tests/test_views_project.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,871 copying publiforge/tests/test_models_processors.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,872 copying publiforge/tests/test_models_groups.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,872 copying publiforge/tests/test_lib_menu.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,873 copying publiforge/tests/test_models_users.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,873 copying publiforge/tests/test_lib_i18n.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,874 copying publiforge/tests/test_lib_config.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,874 copying publiforge/tests/test_scripts_pfbuild.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,875 copying publiforge/tests/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,875 copying publiforge/tests/test_lib_utils.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,876 copying publiforge/tests/test_lib_form.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,876 copying publiforge/tests/test_lib_xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,877 copying publiforge/tests/test_views_security.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:17,878 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T10:44:17,878 copying publiforge/lib/rsync/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T10:44:17,879 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T10:44:17,879 copying publiforge/lib/vcs/hgsvn.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T10:44:17,879 copying publiforge/lib/vcs/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T10:44:17,880 copying publiforge/lib/vcs/hg.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T10:44:17,881 copying publiforge/lib/vcs/svn.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T10:44:17,881 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T10:44:17,882 copying publiforge/lib/opener/ini.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T10:44:17,882 copying publiforge/lib/opener/xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T10:44:17,883 copying publiforge/lib/opener/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T10:44:17,884 copying publiforge/lib/opener/image.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T10:44:17,884 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T10:44:17,885 copying publiforge/lib/build/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T10:44:17,885 copying publiforge/lib/build/front.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T10:44:17,886 copying publiforge/lib/build/agent.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T10:44:17,887 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor 2025-09-08T10:44:17,887 copying publiforge/lib/processor/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor 2025-09-08T10:44:17,888 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T10:44:17,888 copying publiforge/lib/processor/leprisme/publiset.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T10:44:17,889 copying publiforge/lib/processor/leprisme/iniscript.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T10:44:17,889 copying publiforge/lib/processor/leprisme/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T10:44:17,890 copying publiforge/lib/processor/leprisme/transform.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T10:44:17,890 copying publiforge/lib/processor/leprisme/containers.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T10:44:17,891 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/generator 2025-09-08T10:44:17,891 copying publiforge/lib/processor/generator/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/generator 2025-09-08T10:44:17,892 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/publiseter 2025-09-08T10:44:17,892 copying publiforge/lib/processor/publiseter/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/publiseter 2025-09-08T10:44:17,893 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/validator 2025-09-08T10:44:17,893 copying publiforge/lib/processor/validator/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/validator 2025-09-08T10:44:17,894 running egg_info 2025-09-08T10:44:17,968 writing PubliForge.egg-info/PKG-INFO 2025-09-08T10:44:17,974 writing dependency_links to PubliForge.egg-info/dependency_links.txt 2025-09-08T10:44:17,974 writing entry points to PubliForge.egg-info/entry_points.txt 2025-09-08T10:44:17,978 writing requirements to PubliForge.egg-info/requires.txt 2025-09-08T10:44:17,978 writing top-level names to PubliForge.egg-info/top_level.txt 2025-09-08T10:44:18,061 reading manifest file 'PubliForge.egg-info/SOURCES.txt' 2025-09-08T10:44:18,120 reading manifest template 'MANIFEST.in' 2025-09-08T10:44:18,122 warning: no files found matching '*.rst' 2025-09-08T10:44:18,498 warning: no files found matching '*.jinja2' under directory 'publiforge' 2025-09-08T10:44:18,686 warning: no files found matching '*.mak' under directory 'publiforge' 2025-09-08T10:44:18,747 warning: no files found matching '*.mako' under directory 'publiforge' 2025-09-08T10:44:19,061 warning: no files found matching '*.conf' under directory 'publiforge' 2025-09-08T10:44:19,212 writing manifest file 'PubliForge.egg-info/SOURCES.txt' 2025-09-08T10:44:19,214 /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-08T10:44:19,214 !! 2025-09-08T10:44:19,215 ******************************************************************************** 2025-09-08T10:44:19,215 ############################ 2025-09-08T10:44:19,215 # Package would be ignored # 2025-09-08T10:44:19,215 ############################ 2025-09-08T10:44:19,215 Python recognizes 'publiforge.Locale' as an importable package[^1], 2025-09-08T10:44:19,215 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,215 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,215 package, please make sure that 'publiforge.Locale' is explicitly added 2025-09-08T10:44:19,215 to the `packages` configuration field. 2025-09-08T10:44:19,216 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,216 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,216 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,216 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,216 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,216 If you don't want 'publiforge.Locale' to be distributed and are 2025-09-08T10:44:19,216 already explicitly excluding 'publiforge.Locale' via 2025-09-08T10:44:19,216 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,217 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,217 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,217 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,217 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,217 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,217 even if it does not contain any `.py` files. 2025-09-08T10:44:19,217 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,218 directory, all directories are treated like packages. 2025-09-08T10:44:19,218 ******************************************************************************** 2025-09-08T10:44:19,218 !! 2025-09-08T10:44:19,218 check.warn(importable) 2025-09-08T10:44:19,218 /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-08T10:44:19,218 !! 2025-09-08T10:44:19,218 ******************************************************************************** 2025-09-08T10:44:19,218 ############################ 2025-09-08T10:44:19,218 # Package would be ignored # 2025-09-08T10:44:19,219 ############################ 2025-09-08T10:44:19,219 Python recognizes 'publiforge.Locale.es.LC_MESSAGES' as an importable package[^1], 2025-09-08T10:44:19,219 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,219 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,219 package, please make sure that 'publiforge.Locale.es.LC_MESSAGES' is explicitly added 2025-09-08T10:44:19,219 to the `packages` configuration field. 2025-09-08T10:44:19,219 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,219 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,219 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,220 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,220 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,220 If you don't want 'publiforge.Locale.es.LC_MESSAGES' to be distributed and are 2025-09-08T10:44:19,220 already explicitly excluding 'publiforge.Locale.es.LC_MESSAGES' via 2025-09-08T10:44:19,220 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,220 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,220 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,220 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,221 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,221 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,221 even if it does not contain any `.py` files. 2025-09-08T10:44:19,221 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,221 directory, all directories are treated like packages. 2025-09-08T10:44:19,221 ******************************************************************************** 2025-09-08T10:44:19,221 !! 2025-09-08T10:44:19,221 check.warn(importable) 2025-09-08T10:44:19,222 /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-08T10:44:19,222 !! 2025-09-08T10:44:19,222 ******************************************************************************** 2025-09-08T10:44:19,222 ############################ 2025-09-08T10:44:19,222 # Package would be ignored # 2025-09-08T10:44:19,222 ############################ 2025-09-08T10:44:19,222 Python recognizes 'publiforge.Locale.fr.LC_MESSAGES' as an importable package[^1], 2025-09-08T10:44:19,222 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,222 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,223 package, please make sure that 'publiforge.Locale.fr.LC_MESSAGES' is explicitly added 2025-09-08T10:44:19,223 to the `packages` configuration field. 2025-09-08T10:44:19,223 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,223 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,223 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,223 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,223 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,223 If you don't want 'publiforge.Locale.fr.LC_MESSAGES' to be distributed and are 2025-09-08T10:44:19,224 already explicitly excluding 'publiforge.Locale.fr.LC_MESSAGES' via 2025-09-08T10:44:19,224 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,224 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,224 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,224 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,224 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,224 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,224 even if it does not contain any `.py` files. 2025-09-08T10:44:19,225 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,225 directory, all directories are treated like packages. 2025-09-08T10:44:19,225 ******************************************************************************** 2025-09-08T10:44:19,225 !! 2025-09-08T10:44:19,225 check.warn(importable) 2025-09-08T10:44:19,225 /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-08T10:44:19,225 !! 2025-09-08T10:44:19,225 ******************************************************************************** 2025-09-08T10:44:19,225 ############################ 2025-09-08T10:44:19,225 # Package would be ignored # 2025-09-08T10:44:19,225 ############################ 2025-09-08T10:44:19,226 Python recognizes 'publiforge.Openers.Image' as an importable package[^1], 2025-09-08T10:44:19,226 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,226 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,226 package, please make sure that 'publiforge.Openers.Image' is explicitly added 2025-09-08T10:44:19,226 to the `packages` configuration field. 2025-09-08T10:44:19,226 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,226 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,226 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,226 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,227 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,227 If you don't want 'publiforge.Openers.Image' to be distributed and are 2025-09-08T10:44:19,227 already explicitly excluding 'publiforge.Openers.Image' via 2025-09-08T10:44:19,227 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,227 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,227 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,227 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,227 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,228 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,228 even if it does not contain any `.py` files. 2025-09-08T10:44:19,228 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,228 directory, all directories are treated like packages. 2025-09-08T10:44:19,228 ******************************************************************************** 2025-09-08T10:44:19,228 !! 2025-09-08T10:44:19,228 check.warn(importable) 2025-09-08T10:44:19,228 /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-08T10:44:19,228 !! 2025-09-08T10:44:19,229 ******************************************************************************** 2025-09-08T10:44:19,229 ############################ 2025-09-08T10:44:19,229 # Package would be ignored # 2025-09-08T10:44:19,229 ############################ 2025-09-08T10:44:19,229 Python recognizes 'publiforge.Openers.ImageEdit' as an importable package[^1], 2025-09-08T10:44:19,229 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,229 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,229 package, please make sure that 'publiforge.Openers.ImageEdit' is explicitly added 2025-09-08T10:44:19,229 to the `packages` configuration field. 2025-09-08T10:44:19,229 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,230 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,230 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,230 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,230 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,230 If you don't want 'publiforge.Openers.ImageEdit' to be distributed and are 2025-09-08T10:44:19,230 already explicitly excluding 'publiforge.Openers.ImageEdit' via 2025-09-08T10:44:19,230 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,230 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,230 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,231 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,231 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,231 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,231 even if it does not contain any `.py` files. 2025-09-08T10:44:19,231 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,231 directory, all directories are treated like packages. 2025-09-08T10:44:19,231 ******************************************************************************** 2025-09-08T10:44:19,232 !! 2025-09-08T10:44:19,232 check.warn(importable) 2025-09-08T10:44:19,232 /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-08T10:44:19,232 !! 2025-09-08T10:44:19,232 ******************************************************************************** 2025-09-08T10:44:19,232 ############################ 2025-09-08T10:44:19,232 # Package would be ignored # 2025-09-08T10:44:19,232 ############################ 2025-09-08T10:44:19,232 Python recognizes 'publiforge.Openers.Ini' as an importable package[^1], 2025-09-08T10:44:19,232 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,233 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,233 package, please make sure that 'publiforge.Openers.Ini' is explicitly added 2025-09-08T10:44:19,233 to the `packages` configuration field. 2025-09-08T10:44:19,233 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,233 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,233 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,233 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,233 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,234 If you don't want 'publiforge.Openers.Ini' to be distributed and are 2025-09-08T10:44:19,234 already explicitly excluding 'publiforge.Openers.Ini' via 2025-09-08T10:44:19,234 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,234 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,234 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,234 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,234 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,235 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,235 even if it does not contain any `.py` files. 2025-09-08T10:44:19,235 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,235 directory, all directories are treated like packages. 2025-09-08T10:44:19,235 ******************************************************************************** 2025-09-08T10:44:19,235 !! 2025-09-08T10:44:19,235 check.warn(importable) 2025-09-08T10:44:19,235 /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-08T10:44:19,235 !! 2025-09-08T10:44:19,235 ******************************************************************************** 2025-09-08T10:44:19,236 ############################ 2025-09-08T10:44:19,236 # Package would be ignored # 2025-09-08T10:44:19,236 ############################ 2025-09-08T10:44:19,236 Python recognizes 'publiforge.Openers.NoMore' as an importable package[^1], 2025-09-08T10:44:19,236 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,236 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,236 package, please make sure that 'publiforge.Openers.NoMore' is explicitly added 2025-09-08T10:44:19,236 to the `packages` configuration field. 2025-09-08T10:44:19,236 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,237 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,237 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,237 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,237 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,237 If you don't want 'publiforge.Openers.NoMore' to be distributed and are 2025-09-08T10:44:19,237 already explicitly excluding 'publiforge.Openers.NoMore' via 2025-09-08T10:44:19,237 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,237 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,237 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,238 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,238 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,238 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,238 even if it does not contain any `.py` files. 2025-09-08T10:44:19,238 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,238 directory, all directories are treated like packages. 2025-09-08T10:44:19,238 ******************************************************************************** 2025-09-08T10:44:19,239 !! 2025-09-08T10:44:19,239 check.warn(importable) 2025-09-08T10:44:19,239 /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-08T10:44:19,239 !! 2025-09-08T10:44:19,239 ******************************************************************************** 2025-09-08T10:44:19,239 ############################ 2025-09-08T10:44:19,239 # Package would be ignored # 2025-09-08T10:44:19,239 ############################ 2025-09-08T10:44:19,239 Python recognizes 'publiforge.Openers.Plain' as an importable package[^1], 2025-09-08T10:44:19,239 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,240 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,240 package, please make sure that 'publiforge.Openers.Plain' is explicitly added 2025-09-08T10:44:19,240 to the `packages` configuration field. 2025-09-08T10:44:19,240 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,240 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,240 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,240 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,240 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,241 If you don't want 'publiforge.Openers.Plain' to be distributed and are 2025-09-08T10:44:19,241 already explicitly excluding 'publiforge.Openers.Plain' via 2025-09-08T10:44:19,241 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,241 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,241 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,241 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,241 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,242 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,242 even if it does not contain any `.py` files. 2025-09-08T10:44:19,242 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,242 directory, all directories are treated like packages. 2025-09-08T10:44:19,242 ******************************************************************************** 2025-09-08T10:44:19,242 !! 2025-09-08T10:44:19,242 check.warn(importable) 2025-09-08T10:44:19,242 /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-08T10:44:19,242 !! 2025-09-08T10:44:19,243 ******************************************************************************** 2025-09-08T10:44:19,243 ############################ 2025-09-08T10:44:19,243 # Package would be ignored # 2025-09-08T10:44:19,243 ############################ 2025-09-08T10:44:19,243 Python recognizes 'publiforge.Openers.Publidoc' as an importable package[^1], 2025-09-08T10:44:19,243 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,243 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,243 package, please make sure that 'publiforge.Openers.Publidoc' is explicitly added 2025-09-08T10:44:19,243 to the `packages` configuration field. 2025-09-08T10:44:19,244 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,244 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,244 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,244 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,244 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,244 If you don't want 'publiforge.Openers.Publidoc' to be distributed and are 2025-09-08T10:44:19,244 already explicitly excluding 'publiforge.Openers.Publidoc' via 2025-09-08T10:44:19,245 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,245 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,245 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,245 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,245 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,245 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,245 even if it does not contain any `.py` files. 2025-09-08T10:44:19,246 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,246 directory, all directories are treated like packages. 2025-09-08T10:44:19,246 ******************************************************************************** 2025-09-08T10:44:19,246 !! 2025-09-08T10:44:19,246 check.warn(importable) 2025-09-08T10:44:19,246 /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-08T10:44:19,246 !! 2025-09-08T10:44:19,246 ******************************************************************************** 2025-09-08T10:44:19,246 ############################ 2025-09-08T10:44:19,247 # Package would be ignored # 2025-09-08T10:44:19,247 ############################ 2025-09-08T10:44:19,247 Python recognizes 'publiforge.Openers.Publidoc.Maestro' as an importable package[^1], 2025-09-08T10:44:19,247 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,247 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,247 package, please make sure that 'publiforge.Openers.Publidoc.Maestro' is explicitly added 2025-09-08T10:44:19,247 to the `packages` configuration field. 2025-09-08T10:44:19,247 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,247 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,248 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,248 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,248 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,248 If you don't want 'publiforge.Openers.Publidoc.Maestro' to be distributed and are 2025-09-08T10:44:19,248 already explicitly excluding 'publiforge.Openers.Publidoc.Maestro' via 2025-09-08T10:44:19,248 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,248 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,248 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,249 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,249 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,249 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,249 even if it does not contain any `.py` files. 2025-09-08T10:44:19,249 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,249 directory, all directories are treated like packages. 2025-09-08T10:44:19,249 ******************************************************************************** 2025-09-08T10:44:19,250 !! 2025-09-08T10:44:19,250 check.warn(importable) 2025-09-08T10:44:19,250 /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-08T10:44:19,250 !! 2025-09-08T10:44:19,250 ******************************************************************************** 2025-09-08T10:44:19,250 ############################ 2025-09-08T10:44:19,250 # Package would be ignored # 2025-09-08T10:44:19,250 ############################ 2025-09-08T10:44:19,250 Python recognizes 'publiforge.Openers.Publidoc.Regex' as an importable package[^1], 2025-09-08T10:44:19,250 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,251 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,251 package, please make sure that 'publiforge.Openers.Publidoc.Regex' is explicitly added 2025-09-08T10:44:19,251 to the `packages` configuration field. 2025-09-08T10:44:19,251 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,251 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,251 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,251 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,251 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,252 If you don't want 'publiforge.Openers.Publidoc.Regex' to be distributed and are 2025-09-08T10:44:19,252 already explicitly excluding 'publiforge.Openers.Publidoc.Regex' via 2025-09-08T10:44:19,252 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,252 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,252 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,252 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,252 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,253 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,253 even if it does not contain any `.py` files. 2025-09-08T10:44:19,253 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,253 directory, all directories are treated like packages. 2025-09-08T10:44:19,253 ******************************************************************************** 2025-09-08T10:44:19,253 !! 2025-09-08T10:44:19,253 check.warn(importable) 2025-09-08T10:44:19,253 /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-08T10:44:19,253 !! 2025-09-08T10:44:19,254 ******************************************************************************** 2025-09-08T10:44:19,254 ############################ 2025-09-08T10:44:19,254 # Package would be ignored # 2025-09-08T10:44:19,254 ############################ 2025-09-08T10:44:19,254 Python recognizes 'publiforge.Openers.Publidoc.Seeds' as an importable package[^1], 2025-09-08T10:44:19,254 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,254 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,254 package, please make sure that 'publiforge.Openers.Publidoc.Seeds' is explicitly added 2025-09-08T10:44:19,254 to the `packages` configuration field. 2025-09-08T10:44:19,254 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,255 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,255 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,255 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,255 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,255 If you don't want 'publiforge.Openers.Publidoc.Seeds' to be distributed and are 2025-09-08T10:44:19,255 already explicitly excluding 'publiforge.Openers.Publidoc.Seeds' via 2025-09-08T10:44:19,255 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,255 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,256 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,256 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,256 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,256 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,256 even if it does not contain any `.py` files. 2025-09-08T10:44:19,256 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,256 directory, all directories are treated like packages. 2025-09-08T10:44:19,256 ******************************************************************************** 2025-09-08T10:44:19,257 !! 2025-09-08T10:44:19,257 check.warn(importable) 2025-09-08T10:44:19,257 /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-08T10:44:19,257 !! 2025-09-08T10:44:19,257 ******************************************************************************** 2025-09-08T10:44:19,257 ############################ 2025-09-08T10:44:19,257 # Package would be ignored # 2025-09-08T10:44:19,257 ############################ 2025-09-08T10:44:19,257 Python recognizes 'publiforge.Openers.Publidoc.Static.Css' as an importable package[^1], 2025-09-08T10:44:19,258 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,258 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,258 package, please make sure that 'publiforge.Openers.Publidoc.Static.Css' is explicitly added 2025-09-08T10:44:19,258 to the `packages` configuration field. 2025-09-08T10:44:19,258 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,258 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,258 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,258 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,259 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,259 If you don't want 'publiforge.Openers.Publidoc.Static.Css' to be distributed and are 2025-09-08T10:44:19,259 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Css' via 2025-09-08T10:44:19,259 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,259 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,259 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,259 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,259 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,260 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,260 even if it does not contain any `.py` files. 2025-09-08T10:44:19,260 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,260 directory, all directories are treated like packages. 2025-09-08T10:44:19,260 ******************************************************************************** 2025-09-08T10:44:19,260 !! 2025-09-08T10:44:19,260 check.warn(importable) 2025-09-08T10:44:19,260 /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-08T10:44:19,261 !! 2025-09-08T10:44:19,261 ******************************************************************************** 2025-09-08T10:44:19,261 ############################ 2025-09-08T10:44:19,261 # Package would be ignored # 2025-09-08T10:44:19,261 ############################ 2025-09-08T10:44:19,261 Python recognizes 'publiforge.Openers.Publidoc.Static.Js' as an importable package[^1], 2025-09-08T10:44:19,261 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,261 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,261 package, please make sure that 'publiforge.Openers.Publidoc.Static.Js' is explicitly added 2025-09-08T10:44:19,262 to the `packages` configuration field. 2025-09-08T10:44:19,262 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,262 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,262 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,262 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,262 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,262 If you don't want 'publiforge.Openers.Publidoc.Static.Js' to be distributed and are 2025-09-08T10:44:19,262 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Js' via 2025-09-08T10:44:19,263 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,263 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,263 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,263 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,263 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,263 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,263 even if it does not contain any `.py` files. 2025-09-08T10:44:19,263 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,263 directory, all directories are treated like packages. 2025-09-08T10:44:19,264 ******************************************************************************** 2025-09-08T10:44:19,264 !! 2025-09-08T10:44:19,264 check.warn(importable) 2025-09-08T10:44:19,264 /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-08T10:44:19,264 !! 2025-09-08T10:44:19,264 ******************************************************************************** 2025-09-08T10:44:19,264 ############################ 2025-09-08T10:44:19,264 # Package would be ignored # 2025-09-08T10:44:19,264 ############################ 2025-09-08T10:44:19,264 Python recognizes 'publiforge.Openers.Publidoc.Variables' as an importable package[^1], 2025-09-08T10:44:19,265 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,265 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,265 package, please make sure that 'publiforge.Openers.Publidoc.Variables' is explicitly added 2025-09-08T10:44:19,265 to the `packages` configuration field. 2025-09-08T10:44:19,265 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,265 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,265 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,265 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,265 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,266 If you don't want 'publiforge.Openers.Publidoc.Variables' to be distributed and are 2025-09-08T10:44:19,266 already explicitly excluding 'publiforge.Openers.Publidoc.Variables' via 2025-09-08T10:44:19,266 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,266 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,266 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,266 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,266 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,267 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,267 even if it does not contain any `.py` files. 2025-09-08T10:44:19,267 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,267 directory, all directories are treated like packages. 2025-09-08T10:44:19,267 ******************************************************************************** 2025-09-08T10:44:19,267 !! 2025-09-08T10:44:19,267 check.warn(importable) 2025-09-08T10:44:19,267 /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-08T10:44:19,267 !! 2025-09-08T10:44:19,267 ******************************************************************************** 2025-09-08T10:44:19,267 ############################ 2025-09-08T10:44:19,268 # Package would be ignored # 2025-09-08T10:44:19,268 ############################ 2025-09-08T10:44:19,268 Python recognizes 'publiforge.Openers.Publidoc.Xsl' as an importable package[^1], 2025-09-08T10:44:19,268 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,268 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,268 package, please make sure that 'publiforge.Openers.Publidoc.Xsl' is explicitly added 2025-09-08T10:44:19,268 to the `packages` configuration field. 2025-09-08T10:44:19,268 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,268 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,268 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,269 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,269 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,269 If you don't want 'publiforge.Openers.Publidoc.Xsl' to be distributed and are 2025-09-08T10:44:19,269 already explicitly excluding 'publiforge.Openers.Publidoc.Xsl' via 2025-09-08T10:44:19,269 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,269 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,269 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,269 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,270 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,270 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,270 even if it does not contain any `.py` files. 2025-09-08T10:44:19,270 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,270 directory, all directories are treated like packages. 2025-09-08T10:44:19,270 ******************************************************************************** 2025-09-08T10:44:19,270 !! 2025-09-08T10:44:19,270 check.warn(importable) 2025-09-08T10:44:19,270 /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-08T10:44:19,271 !! 2025-09-08T10:44:19,271 ******************************************************************************** 2025-09-08T10:44:19,271 ############################ 2025-09-08T10:44:19,271 # Package would be ignored # 2025-09-08T10:44:19,271 ############################ 2025-09-08T10:44:19,271 Python recognizes 'publiforge.Openers.Publiquiz' as an importable package[^1], 2025-09-08T10:44:19,271 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,271 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,271 package, please make sure that 'publiforge.Openers.Publiquiz' is explicitly added 2025-09-08T10:44:19,271 to the `packages` configuration field. 2025-09-08T10:44:19,272 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,272 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,272 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,272 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,272 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,272 If you don't want 'publiforge.Openers.Publiquiz' to be distributed and are 2025-09-08T10:44:19,272 already explicitly excluding 'publiforge.Openers.Publiquiz' via 2025-09-08T10:44:19,273 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,273 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,273 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,273 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,273 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,273 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,273 even if it does not contain any `.py` files. 2025-09-08T10:44:19,273 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,274 directory, all directories are treated like packages. 2025-09-08T10:44:19,274 ******************************************************************************** 2025-09-08T10:44:19,274 !! 2025-09-08T10:44:19,274 check.warn(importable) 2025-09-08T10:44:19,274 /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-08T10:44:19,274 !! 2025-09-08T10:44:19,274 ******************************************************************************** 2025-09-08T10:44:19,274 ############################ 2025-09-08T10:44:19,274 # Package would be ignored # 2025-09-08T10:44:19,274 ############################ 2025-09-08T10:44:19,275 Python recognizes 'publiforge.Openers.Publiquiz.Regex' as an importable package[^1], 2025-09-08T10:44:19,275 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,275 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,275 package, please make sure that 'publiforge.Openers.Publiquiz.Regex' is explicitly added 2025-09-08T10:44:19,275 to the `packages` configuration field. 2025-09-08T10:44:19,275 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,275 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,275 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,275 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,276 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,276 If you don't want 'publiforge.Openers.Publiquiz.Regex' to be distributed and are 2025-09-08T10:44:19,276 already explicitly excluding 'publiforge.Openers.Publiquiz.Regex' via 2025-09-08T10:44:19,276 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,276 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,276 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,276 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,276 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,277 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,277 even if it does not contain any `.py` files. 2025-09-08T10:44:19,277 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,277 directory, all directories are treated like packages. 2025-09-08T10:44:19,277 ******************************************************************************** 2025-09-08T10:44:19,277 !! 2025-09-08T10:44:19,277 check.warn(importable) 2025-09-08T10:44:19,277 /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-08T10:44:19,277 !! 2025-09-08T10:44:19,278 ******************************************************************************** 2025-09-08T10:44:19,278 ############################ 2025-09-08T10:44:19,278 # Package would be ignored # 2025-09-08T10:44:19,278 ############################ 2025-09-08T10:44:19,278 Python recognizes 'publiforge.Openers.Publiquiz.Seeds' as an importable package[^1], 2025-09-08T10:44:19,278 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,278 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,278 package, please make sure that 'publiforge.Openers.Publiquiz.Seeds' is explicitly added 2025-09-08T10:44:19,278 to the `packages` configuration field. 2025-09-08T10:44:19,278 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,279 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,279 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,279 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,279 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,279 If you don't want 'publiforge.Openers.Publiquiz.Seeds' to be distributed and are 2025-09-08T10:44:19,279 already explicitly excluding 'publiforge.Openers.Publiquiz.Seeds' via 2025-09-08T10:44:19,279 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,279 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,279 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,280 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,280 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,280 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,280 even if it does not contain any `.py` files. 2025-09-08T10:44:19,280 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,280 directory, all directories are treated like packages. 2025-09-08T10:44:19,280 ******************************************************************************** 2025-09-08T10:44:19,280 !! 2025-09-08T10:44:19,281 check.warn(importable) 2025-09-08T10:44:19,281 /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-08T10:44:19,281 !! 2025-09-08T10:44:19,281 ******************************************************************************** 2025-09-08T10:44:19,281 ############################ 2025-09-08T10:44:19,281 # Package would be ignored # 2025-09-08T10:44:19,281 ############################ 2025-09-08T10:44:19,281 Python recognizes 'publiforge.Openers.Publiquiz.Static.Css' as an importable package[^1], 2025-09-08T10:44:19,281 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,281 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,282 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Css' is explicitly added 2025-09-08T10:44:19,282 to the `packages` configuration field. 2025-09-08T10:44:19,282 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,282 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,282 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,282 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,282 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,282 If you don't want 'publiforge.Openers.Publiquiz.Static.Css' to be distributed and are 2025-09-08T10:44:19,283 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Css' via 2025-09-08T10:44:19,283 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,283 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,283 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,283 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,283 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,283 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,283 even if it does not contain any `.py` files. 2025-09-08T10:44:19,283 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,284 directory, all directories are treated like packages. 2025-09-08T10:44:19,284 ******************************************************************************** 2025-09-08T10:44:19,284 !! 2025-09-08T10:44:19,284 check.warn(importable) 2025-09-08T10:44:19,284 /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-08T10:44:19,284 !! 2025-09-08T10:44:19,284 ******************************************************************************** 2025-09-08T10:44:19,284 ############################ 2025-09-08T10:44:19,284 # Package would be ignored # 2025-09-08T10:44:19,284 ############################ 2025-09-08T10:44:19,285 Python recognizes 'publiforge.Openers.Publiquiz.Static.Fonts' as an importable package[^1], 2025-09-08T10:44:19,285 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,285 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,285 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Fonts' is explicitly added 2025-09-08T10:44:19,285 to the `packages` configuration field. 2025-09-08T10:44:19,285 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,285 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,285 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,286 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,286 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,286 If you don't want 'publiforge.Openers.Publiquiz.Static.Fonts' to be distributed and are 2025-09-08T10:44:19,286 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Fonts' via 2025-09-08T10:44:19,286 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,286 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,286 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,286 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,287 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,287 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,287 even if it does not contain any `.py` files. 2025-09-08T10:44:19,287 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,287 directory, all directories are treated like packages. 2025-09-08T10:44:19,287 ******************************************************************************** 2025-09-08T10:44:19,287 !! 2025-09-08T10:44:19,287 check.warn(importable) 2025-09-08T10:44:19,287 /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-08T10:44:19,288 !! 2025-09-08T10:44:19,288 ******************************************************************************** 2025-09-08T10:44:19,288 ############################ 2025-09-08T10:44:19,288 # Package would be ignored # 2025-09-08T10:44:19,288 ############################ 2025-09-08T10:44:19,288 Python recognizes 'publiforge.Openers.Publiquiz.Static.Js' as an importable package[^1], 2025-09-08T10:44:19,288 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,288 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,288 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Js' is explicitly added 2025-09-08T10:44:19,288 to the `packages` configuration field. 2025-09-08T10:44:19,289 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,289 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,289 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,289 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,289 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,289 If you don't want 'publiforge.Openers.Publiquiz.Static.Js' to be distributed and are 2025-09-08T10:44:19,289 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Js' via 2025-09-08T10:44:19,289 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,289 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,290 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,290 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,290 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,290 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,290 even if it does not contain any `.py` files. 2025-09-08T10:44:19,290 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,290 directory, all directories are treated like packages. 2025-09-08T10:44:19,290 ******************************************************************************** 2025-09-08T10:44:19,291 !! 2025-09-08T10:44:19,291 check.warn(importable) 2025-09-08T10:44:19,291 /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-08T10:44:19,291 !! 2025-09-08T10:44:19,291 ******************************************************************************** 2025-09-08T10:44:19,291 ############################ 2025-09-08T10:44:19,291 # Package would be ignored # 2025-09-08T10:44:19,291 ############################ 2025-09-08T10:44:19,291 Python recognizes 'publiforge.Openers.Publiquiz.Variables' as an importable package[^1], 2025-09-08T10:44:19,291 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,292 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,292 package, please make sure that 'publiforge.Openers.Publiquiz.Variables' is explicitly added 2025-09-08T10:44:19,292 to the `packages` configuration field. 2025-09-08T10:44:19,292 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,292 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,292 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,292 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,292 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,293 If you don't want 'publiforge.Openers.Publiquiz.Variables' to be distributed and are 2025-09-08T10:44:19,293 already explicitly excluding 'publiforge.Openers.Publiquiz.Variables' via 2025-09-08T10:44:19,293 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,293 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,293 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,293 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,293 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,293 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,294 even if it does not contain any `.py` files. 2025-09-08T10:44:19,294 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,294 directory, all directories are treated like packages. 2025-09-08T10:44:19,294 ******************************************************************************** 2025-09-08T10:44:19,294 !! 2025-09-08T10:44:19,294 check.warn(importable) 2025-09-08T10:44:19,294 /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-08T10:44:19,294 !! 2025-09-08T10:44:19,294 ******************************************************************************** 2025-09-08T10:44:19,294 ############################ 2025-09-08T10:44:19,295 # Package would be ignored # 2025-09-08T10:44:19,295 ############################ 2025-09-08T10:44:19,295 Python recognizes 'publiforge.Openers.Publiquiz.Xsl' as an importable package[^1], 2025-09-08T10:44:19,295 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,295 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,295 package, please make sure that 'publiforge.Openers.Publiquiz.Xsl' is explicitly added 2025-09-08T10:44:19,295 to the `packages` configuration field. 2025-09-08T10:44:19,295 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,295 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,295 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,296 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,296 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,296 If you don't want 'publiforge.Openers.Publiquiz.Xsl' to be distributed and are 2025-09-08T10:44:19,296 already explicitly excluding 'publiforge.Openers.Publiquiz.Xsl' via 2025-09-08T10:44:19,296 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,296 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,296 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,296 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,297 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,297 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,297 even if it does not contain any `.py` files. 2025-09-08T10:44:19,297 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,297 directory, all directories are treated like packages. 2025-09-08T10:44:19,297 ******************************************************************************** 2025-09-08T10:44:19,297 !! 2025-09-08T10:44:19,297 check.warn(importable) 2025-09-08T10:44:19,297 /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-08T10:44:19,298 !! 2025-09-08T10:44:19,298 ******************************************************************************** 2025-09-08T10:44:19,298 ############################ 2025-09-08T10:44:19,298 # Package would be ignored # 2025-09-08T10:44:19,298 ############################ 2025-09-08T10:44:19,298 Python recognizes 'publiforge.Openers.Publiset' as an importable package[^1], 2025-09-08T10:44:19,298 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,298 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,298 package, please make sure that 'publiforge.Openers.Publiset' is explicitly added 2025-09-08T10:44:19,299 to the `packages` configuration field. 2025-09-08T10:44:19,299 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,299 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,299 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,299 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,299 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,299 If you don't want 'publiforge.Openers.Publiset' to be distributed and are 2025-09-08T10:44:19,299 already explicitly excluding 'publiforge.Openers.Publiset' via 2025-09-08T10:44:19,300 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,300 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,300 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,300 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,300 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,300 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,300 even if it does not contain any `.py` files. 2025-09-08T10:44:19,300 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,300 directory, all directories are treated like packages. 2025-09-08T10:44:19,301 ******************************************************************************** 2025-09-08T10:44:19,301 !! 2025-09-08T10:44:19,301 check.warn(importable) 2025-09-08T10:44:19,301 /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-08T10:44:19,301 !! 2025-09-08T10:44:19,301 ******************************************************************************** 2025-09-08T10:44:19,301 ############################ 2025-09-08T10:44:19,301 # Package would be ignored # 2025-09-08T10:44:19,301 ############################ 2025-09-08T10:44:19,301 Python recognizes 'publiforge.Openers.Publiset.Regex' as an importable package[^1], 2025-09-08T10:44:19,302 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,302 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,302 package, please make sure that 'publiforge.Openers.Publiset.Regex' is explicitly added 2025-09-08T10:44:19,302 to the `packages` configuration field. 2025-09-08T10:44:19,302 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,302 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,302 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,302 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,303 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,303 If you don't want 'publiforge.Openers.Publiset.Regex' to be distributed and are 2025-09-08T10:44:19,303 already explicitly excluding 'publiforge.Openers.Publiset.Regex' via 2025-09-08T10:44:19,303 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,303 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,303 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,303 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,303 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,304 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,304 even if it does not contain any `.py` files. 2025-09-08T10:44:19,304 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,304 directory, all directories are treated like packages. 2025-09-08T10:44:19,304 ******************************************************************************** 2025-09-08T10:44:19,304 !! 2025-09-08T10:44:19,304 check.warn(importable) 2025-09-08T10:44:19,304 /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-08T10:44:19,304 !! 2025-09-08T10:44:19,304 ******************************************************************************** 2025-09-08T10:44:19,305 ############################ 2025-09-08T10:44:19,305 # Package would be ignored # 2025-09-08T10:44:19,305 ############################ 2025-09-08T10:44:19,305 Python recognizes 'publiforge.Openers.Publiset.Seeds' as an importable package[^1], 2025-09-08T10:44:19,305 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,305 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,305 package, please make sure that 'publiforge.Openers.Publiset.Seeds' is explicitly added 2025-09-08T10:44:19,305 to the `packages` configuration field. 2025-09-08T10:44:19,305 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,305 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,305 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,306 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,306 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,306 If you don't want 'publiforge.Openers.Publiset.Seeds' to be distributed and are 2025-09-08T10:44:19,306 already explicitly excluding 'publiforge.Openers.Publiset.Seeds' via 2025-09-08T10:44:19,306 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,306 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,306 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,306 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,307 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,307 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,307 even if it does not contain any `.py` files. 2025-09-08T10:44:19,307 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,307 directory, all directories are treated like packages. 2025-09-08T10:44:19,307 ******************************************************************************** 2025-09-08T10:44:19,307 !! 2025-09-08T10:44:19,307 check.warn(importable) 2025-09-08T10:44:19,307 /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-08T10:44:19,308 !! 2025-09-08T10:44:19,308 ******************************************************************************** 2025-09-08T10:44:19,308 ############################ 2025-09-08T10:44:19,308 # Package would be ignored # 2025-09-08T10:44:19,308 ############################ 2025-09-08T10:44:19,308 Python recognizes 'publiforge.Openers.Publiset.Static.Css' as an importable package[^1], 2025-09-08T10:44:19,308 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,308 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,308 package, please make sure that 'publiforge.Openers.Publiset.Static.Css' is explicitly added 2025-09-08T10:44:19,308 to the `packages` configuration field. 2025-09-08T10:44:19,309 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,309 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,309 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,309 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,309 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,309 If you don't want 'publiforge.Openers.Publiset.Static.Css' to be distributed and are 2025-09-08T10:44:19,309 already explicitly excluding 'publiforge.Openers.Publiset.Static.Css' via 2025-09-08T10:44:19,309 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,310 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,310 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,310 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,310 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,310 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,310 even if it does not contain any `.py` files. 2025-09-08T10:44:19,310 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,310 directory, all directories are treated like packages. 2025-09-08T10:44:19,310 ******************************************************************************** 2025-09-08T10:44:19,311 !! 2025-09-08T10:44:19,311 check.warn(importable) 2025-09-08T10:44:19,311 /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-08T10:44:19,311 !! 2025-09-08T10:44:19,311 ******************************************************************************** 2025-09-08T10:44:19,311 ############################ 2025-09-08T10:44:19,311 # Package would be ignored # 2025-09-08T10:44:19,311 ############################ 2025-09-08T10:44:19,311 Python recognizes 'publiforge.Openers.Publiset.Static.Images' as an importable package[^1], 2025-09-08T10:44:19,312 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,312 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,312 package, please make sure that 'publiforge.Openers.Publiset.Static.Images' is explicitly added 2025-09-08T10:44:19,312 to the `packages` configuration field. 2025-09-08T10:44:19,312 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,312 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,312 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,312 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,313 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,313 If you don't want 'publiforge.Openers.Publiset.Static.Images' to be distributed and are 2025-09-08T10:44:19,313 already explicitly excluding 'publiforge.Openers.Publiset.Static.Images' via 2025-09-08T10:44:19,313 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,313 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,313 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,313 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,313 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,314 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,314 even if it does not contain any `.py` files. 2025-09-08T10:44:19,314 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,314 directory, all directories are treated like packages. 2025-09-08T10:44:19,314 ******************************************************************************** 2025-09-08T10:44:19,314 !! 2025-09-08T10:44:19,314 check.warn(importable) 2025-09-08T10:44:19,314 /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-08T10:44:19,314 !! 2025-09-08T10:44:19,314 ******************************************************************************** 2025-09-08T10:44:19,315 ############################ 2025-09-08T10:44:19,315 # Package would be ignored # 2025-09-08T10:44:19,315 ############################ 2025-09-08T10:44:19,315 Python recognizes 'publiforge.Openers.Publiset.Static.Js' as an importable package[^1], 2025-09-08T10:44:19,315 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,315 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,315 package, please make sure that 'publiforge.Openers.Publiset.Static.Js' is explicitly added 2025-09-08T10:44:19,315 to the `packages` configuration field. 2025-09-08T10:44:19,315 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,315 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,316 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,316 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,316 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,316 If you don't want 'publiforge.Openers.Publiset.Static.Js' to be distributed and are 2025-09-08T10:44:19,316 already explicitly excluding 'publiforge.Openers.Publiset.Static.Js' via 2025-09-08T10:44:19,316 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,316 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,316 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,316 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,317 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,317 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,317 even if it does not contain any `.py` files. 2025-09-08T10:44:19,317 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,317 directory, all directories are treated like packages. 2025-09-08T10:44:19,317 ******************************************************************************** 2025-09-08T10:44:19,317 !! 2025-09-08T10:44:19,317 check.warn(importable) 2025-09-08T10:44:19,318 /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-08T10:44:19,318 !! 2025-09-08T10:44:19,318 ******************************************************************************** 2025-09-08T10:44:19,318 ############################ 2025-09-08T10:44:19,318 # Package would be ignored # 2025-09-08T10:44:19,318 ############################ 2025-09-08T10:44:19,318 Python recognizes 'publiforge.Openers.Publiset.Variables' as an importable package[^1], 2025-09-08T10:44:19,318 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,318 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,318 package, please make sure that 'publiforge.Openers.Publiset.Variables' is explicitly added 2025-09-08T10:44:19,318 to the `packages` configuration field. 2025-09-08T10:44:19,319 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,319 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,319 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,319 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,319 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,319 If you don't want 'publiforge.Openers.Publiset.Variables' to be distributed and are 2025-09-08T10:44:19,319 already explicitly excluding 'publiforge.Openers.Publiset.Variables' via 2025-09-08T10:44:19,319 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,320 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,320 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,320 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,320 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,320 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,320 even if it does not contain any `.py` files. 2025-09-08T10:44:19,320 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,320 directory, all directories are treated like packages. 2025-09-08T10:44:19,320 ******************************************************************************** 2025-09-08T10:44:19,321 !! 2025-09-08T10:44:19,321 check.warn(importable) 2025-09-08T10:44:19,321 /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-08T10:44:19,321 !! 2025-09-08T10:44:19,321 ******************************************************************************** 2025-09-08T10:44:19,321 ############################ 2025-09-08T10:44:19,321 # Package would be ignored # 2025-09-08T10:44:19,321 ############################ 2025-09-08T10:44:19,321 Python recognizes 'publiforge.Openers.Publiset.Xsl' as an importable package[^1], 2025-09-08T10:44:19,321 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,322 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,322 package, please make sure that 'publiforge.Openers.Publiset.Xsl' is explicitly added 2025-09-08T10:44:19,322 to the `packages` configuration field. 2025-09-08T10:44:19,322 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,322 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,322 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,322 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,322 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,323 If you don't want 'publiforge.Openers.Publiset.Xsl' to be distributed and are 2025-09-08T10:44:19,323 already explicitly excluding 'publiforge.Openers.Publiset.Xsl' via 2025-09-08T10:44:19,323 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,323 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,323 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,323 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,323 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,323 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,324 even if it does not contain any `.py` files. 2025-09-08T10:44:19,324 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,324 directory, all directories are treated like packages. 2025-09-08T10:44:19,324 ******************************************************************************** 2025-09-08T10:44:19,324 !! 2025-09-08T10:44:19,324 check.warn(importable) 2025-09-08T10:44:19,324 /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-08T10:44:19,324 !! 2025-09-08T10:44:19,324 ******************************************************************************** 2025-09-08T10:44:19,325 ############################ 2025-09-08T10:44:19,325 # Package would be ignored # 2025-09-08T10:44:19,325 ############################ 2025-09-08T10:44:19,325 Python recognizes 'publiforge.Openers.Xml' as an importable package[^1], 2025-09-08T10:44:19,325 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,325 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,325 package, please make sure that 'publiforge.Openers.Xml' is explicitly added 2025-09-08T10:44:19,325 to the `packages` configuration field. 2025-09-08T10:44:19,325 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,325 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,326 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,326 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,326 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,326 If you don't want 'publiforge.Openers.Xml' to be distributed and are 2025-09-08T10:44:19,326 already explicitly excluding 'publiforge.Openers.Xml' via 2025-09-08T10:44:19,326 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,326 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,326 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,326 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,327 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,327 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,327 even if it does not contain any `.py` files. 2025-09-08T10:44:19,327 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,327 directory, all directories are treated like packages. 2025-09-08T10:44:19,327 ******************************************************************************** 2025-09-08T10:44:19,327 !! 2025-09-08T10:44:19,327 check.warn(importable) 2025-09-08T10:44:19,328 /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-08T10:44:19,328 !! 2025-09-08T10:44:19,328 ******************************************************************************** 2025-09-08T10:44:19,328 ############################ 2025-09-08T10:44:19,328 # Package would be ignored # 2025-09-08T10:44:19,328 ############################ 2025-09-08T10:44:19,328 Python recognizes 'publiforge.Openers.Xml.Static.Css' as an importable package[^1], 2025-09-08T10:44:19,328 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,328 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,328 package, please make sure that 'publiforge.Openers.Xml.Static.Css' is explicitly added 2025-09-08T10:44:19,328 to the `packages` configuration field. 2025-09-08T10:44:19,329 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,329 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,329 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,329 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,329 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,329 If you don't want 'publiforge.Openers.Xml.Static.Css' to be distributed and are 2025-09-08T10:44:19,329 already explicitly excluding 'publiforge.Openers.Xml.Static.Css' via 2025-09-08T10:44:19,329 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,330 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,330 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,330 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,330 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,330 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,330 even if it does not contain any `.py` files. 2025-09-08T10:44:19,330 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,330 directory, all directories are treated like packages. 2025-09-08T10:44:19,330 ******************************************************************************** 2025-09-08T10:44:19,331 !! 2025-09-08T10:44:19,331 check.warn(importable) 2025-09-08T10:44:19,331 /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-08T10:44:19,331 !! 2025-09-08T10:44:19,331 ******************************************************************************** 2025-09-08T10:44:19,331 ############################ 2025-09-08T10:44:19,331 # Package would be ignored # 2025-09-08T10:44:19,331 ############################ 2025-09-08T10:44:19,331 Python recognizes 'publiforge.Openers.Xml.Static.Images' as an importable package[^1], 2025-09-08T10:44:19,331 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,332 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,332 package, please make sure that 'publiforge.Openers.Xml.Static.Images' is explicitly added 2025-09-08T10:44:19,332 to the `packages` configuration field. 2025-09-08T10:44:19,332 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,332 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,332 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,332 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,332 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,333 If you don't want 'publiforge.Openers.Xml.Static.Images' to be distributed and are 2025-09-08T10:44:19,333 already explicitly excluding 'publiforge.Openers.Xml.Static.Images' via 2025-09-08T10:44:19,333 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,333 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,333 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,333 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,333 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,333 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,334 even if it does not contain any `.py` files. 2025-09-08T10:44:19,334 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,334 directory, all directories are treated like packages. 2025-09-08T10:44:19,334 ******************************************************************************** 2025-09-08T10:44:19,334 !! 2025-09-08T10:44:19,334 check.warn(importable) 2025-09-08T10:44:19,334 /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-08T10:44:19,334 !! 2025-09-08T10:44:19,334 ******************************************************************************** 2025-09-08T10:44:19,334 ############################ 2025-09-08T10:44:19,335 # Package would be ignored # 2025-09-08T10:44:19,335 ############################ 2025-09-08T10:44:19,335 Python recognizes 'publiforge.Openers.Xml.Static.Js' as an importable package[^1], 2025-09-08T10:44:19,335 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,335 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,335 package, please make sure that 'publiforge.Openers.Xml.Static.Js' is explicitly added 2025-09-08T10:44:19,335 to the `packages` configuration field. 2025-09-08T10:44:19,335 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,335 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,335 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,336 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,336 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,336 If you don't want 'publiforge.Openers.Xml.Static.Js' to be distributed and are 2025-09-08T10:44:19,336 already explicitly excluding 'publiforge.Openers.Xml.Static.Js' via 2025-09-08T10:44:19,336 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,336 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,336 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,336 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,337 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,337 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,337 even if it does not contain any `.py` files. 2025-09-08T10:44:19,337 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,337 directory, all directories are treated like packages. 2025-09-08T10:44:19,337 ******************************************************************************** 2025-09-08T10:44:19,337 !! 2025-09-08T10:44:19,337 check.warn(importable) 2025-09-08T10:44:19,338 /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-08T10:44:19,338 !! 2025-09-08T10:44:19,338 ******************************************************************************** 2025-09-08T10:44:19,338 ############################ 2025-09-08T10:44:19,338 # Package would be ignored # 2025-09-08T10:44:19,338 ############################ 2025-09-08T10:44:19,338 Python recognizes 'publiforge.Processors.CharCount' as an importable package[^1], 2025-09-08T10:44:19,338 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,338 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,339 package, please make sure that 'publiforge.Processors.CharCount' is explicitly added 2025-09-08T10:44:19,339 to the `packages` configuration field. 2025-09-08T10:44:19,339 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,339 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,339 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,339 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,339 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,339 If you don't want 'publiforge.Processors.CharCount' to be distributed and are 2025-09-08T10:44:19,339 already explicitly excluding 'publiforge.Processors.CharCount' via 2025-09-08T10:44:19,340 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,340 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,340 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,340 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,340 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,340 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,340 even if it does not contain any `.py` files. 2025-09-08T10:44:19,340 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,341 directory, all directories are treated like packages. 2025-09-08T10:44:19,341 ******************************************************************************** 2025-09-08T10:44:19,341 !! 2025-09-08T10:44:19,341 check.warn(importable) 2025-09-08T10:44:19,341 /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-08T10:44:19,341 !! 2025-09-08T10:44:19,341 ******************************************************************************** 2025-09-08T10:44:19,341 ############################ 2025-09-08T10:44:19,341 # Package would be ignored # 2025-09-08T10:44:19,341 ############################ 2025-09-08T10:44:19,342 Python recognizes 'publiforge.Processors.CharCount.Xsl' as an importable package[^1], 2025-09-08T10:44:19,342 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,342 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,342 package, please make sure that 'publiforge.Processors.CharCount.Xsl' is explicitly added 2025-09-08T10:44:19,342 to the `packages` configuration field. 2025-09-08T10:44:19,342 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,342 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,342 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,342 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,343 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,343 If you don't want 'publiforge.Processors.CharCount.Xsl' to be distributed and are 2025-09-08T10:44:19,343 already explicitly excluding 'publiforge.Processors.CharCount.Xsl' via 2025-09-08T10:44:19,343 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,343 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,343 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,343 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,343 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,344 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,344 even if it does not contain any `.py` files. 2025-09-08T10:44:19,344 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,344 directory, all directories are treated like packages. 2025-09-08T10:44:19,344 ******************************************************************************** 2025-09-08T10:44:19,344 !! 2025-09-08T10:44:19,344 check.warn(importable) 2025-09-08T10:44:19,344 /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-08T10:44:19,344 !! 2025-09-08T10:44:19,345 ******************************************************************************** 2025-09-08T10:44:19,345 ############################ 2025-09-08T10:44:19,345 # Package would be ignored # 2025-09-08T10:44:19,345 ############################ 2025-09-08T10:44:19,345 Python recognizes 'publiforge.Processors.CleanStorage' as an importable package[^1], 2025-09-08T10:44:19,345 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,345 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,345 package, please make sure that 'publiforge.Processors.CleanStorage' is explicitly added 2025-09-08T10:44:19,345 to the `packages` configuration field. 2025-09-08T10:44:19,345 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,346 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,346 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,346 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,346 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,346 If you don't want 'publiforge.Processors.CleanStorage' to be distributed and are 2025-09-08T10:44:19,346 already explicitly excluding 'publiforge.Processors.CleanStorage' via 2025-09-08T10:44:19,346 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,346 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,346 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,347 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,347 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,347 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,347 even if it does not contain any `.py` files. 2025-09-08T10:44:19,347 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,347 directory, all directories are treated like packages. 2025-09-08T10:44:19,347 ******************************************************************************** 2025-09-08T10:44:19,348 !! 2025-09-08T10:44:19,348 check.warn(importable) 2025-09-08T10:44:19,348 /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-08T10:44:19,348 !! 2025-09-08T10:44:19,348 ******************************************************************************** 2025-09-08T10:44:19,348 ############################ 2025-09-08T10:44:19,348 # Package would be ignored # 2025-09-08T10:44:19,348 ############################ 2025-09-08T10:44:19,348 Python recognizes 'publiforge.Processors.CleanStorage.lib' as an importable package[^1], 2025-09-08T10:44:19,348 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,349 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,349 package, please make sure that 'publiforge.Processors.CleanStorage.lib' is explicitly added 2025-09-08T10:44:19,349 to the `packages` configuration field. 2025-09-08T10:44:19,349 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,349 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,349 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,349 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,349 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,349 If you don't want 'publiforge.Processors.CleanStorage.lib' to be distributed and are 2025-09-08T10:44:19,350 already explicitly excluding 'publiforge.Processors.CleanStorage.lib' via 2025-09-08T10:44:19,350 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,350 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,350 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,350 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,350 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,350 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,351 even if it does not contain any `.py` files. 2025-09-08T10:44:19,351 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,351 directory, all directories are treated like packages. 2025-09-08T10:44:19,351 ******************************************************************************** 2025-09-08T10:44:19,351 !! 2025-09-08T10:44:19,351 check.warn(importable) 2025-09-08T10:44:19,351 /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-08T10:44:19,351 !! 2025-09-08T10:44:19,351 ******************************************************************************** 2025-09-08T10:44:19,352 ############################ 2025-09-08T10:44:19,352 # Package would be ignored # 2025-09-08T10:44:19,352 ############################ 2025-09-08T10:44:19,352 Python recognizes 'publiforge.Processors.DTBookValid' as an importable package[^1], 2025-09-08T10:44:19,352 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,352 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,352 package, please make sure that 'publiforge.Processors.DTBookValid' is explicitly added 2025-09-08T10:44:19,352 to the `packages` configuration field. 2025-09-08T10:44:19,352 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,352 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,353 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,353 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,353 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,353 If you don't want 'publiforge.Processors.DTBookValid' to be distributed and are 2025-09-08T10:44:19,353 already explicitly excluding 'publiforge.Processors.DTBookValid' via 2025-09-08T10:44:19,353 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,353 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,353 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,354 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,354 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,354 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,354 even if it does not contain any `.py` files. 2025-09-08T10:44:19,354 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,354 directory, all directories are treated like packages. 2025-09-08T10:44:19,354 ******************************************************************************** 2025-09-08T10:44:19,354 !! 2025-09-08T10:44:19,355 check.warn(importable) 2025-09-08T10:44:19,355 /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-08T10:44:19,355 !! 2025-09-08T10:44:19,355 ******************************************************************************** 2025-09-08T10:44:19,355 ############################ 2025-09-08T10:44:19,355 # Package would be ignored # 2025-09-08T10:44:19,355 ############################ 2025-09-08T10:44:19,355 Python recognizes 'publiforge.Processors.DTBookValid.RelaxNG' as an importable package[^1], 2025-09-08T10:44:19,355 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,355 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,355 package, please make sure that 'publiforge.Processors.DTBookValid.RelaxNG' is explicitly added 2025-09-08T10:44:19,356 to the `packages` configuration field. 2025-09-08T10:44:19,356 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,356 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,356 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,356 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,356 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,356 If you don't want 'publiforge.Processors.DTBookValid.RelaxNG' to be distributed and are 2025-09-08T10:44:19,356 already explicitly excluding 'publiforge.Processors.DTBookValid.RelaxNG' via 2025-09-08T10:44:19,357 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,357 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,357 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,357 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,357 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,357 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,357 even if it does not contain any `.py` files. 2025-09-08T10:44:19,357 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,358 directory, all directories are treated like packages. 2025-09-08T10:44:19,358 ******************************************************************************** 2025-09-08T10:44:19,358 !! 2025-09-08T10:44:19,358 check.warn(importable) 2025-09-08T10:44:19,358 /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-08T10:44:19,358 !! 2025-09-08T10:44:19,358 ******************************************************************************** 2025-09-08T10:44:19,358 ############################ 2025-09-08T10:44:19,358 # Package would be ignored # 2025-09-08T10:44:19,358 ############################ 2025-09-08T10:44:19,358 Python recognizes 'publiforge.Processors.PackFilling' as an importable package[^1], 2025-09-08T10:44:19,359 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,359 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,359 package, please make sure that 'publiforge.Processors.PackFilling' is explicitly added 2025-09-08T10:44:19,359 to the `packages` configuration field. 2025-09-08T10:44:19,359 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,359 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,359 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,359 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,360 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,360 If you don't want 'publiforge.Processors.PackFilling' to be distributed and are 2025-09-08T10:44:19,360 already explicitly excluding 'publiforge.Processors.PackFilling' via 2025-09-08T10:44:19,360 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,360 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,360 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,360 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,360 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,361 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,361 even if it does not contain any `.py` files. 2025-09-08T10:44:19,361 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,361 directory, all directories are treated like packages. 2025-09-08T10:44:19,361 ******************************************************************************** 2025-09-08T10:44:19,361 !! 2025-09-08T10:44:19,361 check.warn(importable) 2025-09-08T10:44:19,361 /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-08T10:44:19,361 !! 2025-09-08T10:44:19,361 ******************************************************************************** 2025-09-08T10:44:19,362 ############################ 2025-09-08T10:44:19,362 # Package would be ignored # 2025-09-08T10:44:19,362 ############################ 2025-09-08T10:44:19,362 Python recognizes 'publiforge.Processors.PackFilling.Variables' as an importable package[^1], 2025-09-08T10:44:19,362 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,362 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,362 package, please make sure that 'publiforge.Processors.PackFilling.Variables' is explicitly added 2025-09-08T10:44:19,362 to the `packages` configuration field. 2025-09-08T10:44:19,362 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,362 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,363 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,363 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,363 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,363 If you don't want 'publiforge.Processors.PackFilling.Variables' to be distributed and are 2025-09-08T10:44:19,363 already explicitly excluding 'publiforge.Processors.PackFilling.Variables' via 2025-09-08T10:44:19,363 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,363 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,363 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,364 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,364 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,364 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,364 even if it does not contain any `.py` files. 2025-09-08T10:44:19,364 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,364 directory, all directories are treated like packages. 2025-09-08T10:44:19,364 ******************************************************************************** 2025-09-08T10:44:19,365 !! 2025-09-08T10:44:19,365 check.warn(importable) 2025-09-08T10:44:19,365 /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-08T10:44:19,365 !! 2025-09-08T10:44:19,365 ******************************************************************************** 2025-09-08T10:44:19,365 ############################ 2025-09-08T10:44:19,365 # Package would be ignored # 2025-09-08T10:44:19,365 ############################ 2025-09-08T10:44:19,365 Python recognizes 'publiforge.Processors.PackFilling.lib' as an importable package[^1], 2025-09-08T10:44:19,365 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,366 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,366 package, please make sure that 'publiforge.Processors.PackFilling.lib' is explicitly added 2025-09-08T10:44:19,366 to the `packages` configuration field. 2025-09-08T10:44:19,366 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,366 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,366 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,366 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,366 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,367 If you don't want 'publiforge.Processors.PackFilling.lib' to be distributed and are 2025-09-08T10:44:19,367 already explicitly excluding 'publiforge.Processors.PackFilling.lib' via 2025-09-08T10:44:19,367 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,367 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,367 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,367 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,367 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,367 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,368 even if it does not contain any `.py` files. 2025-09-08T10:44:19,368 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,368 directory, all directories are treated like packages. 2025-09-08T10:44:19,368 ******************************************************************************** 2025-09-08T10:44:19,368 !! 2025-09-08T10:44:19,368 check.warn(importable) 2025-09-08T10:44:19,368 /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-08T10:44:19,368 !! 2025-09-08T10:44:19,368 ******************************************************************************** 2025-09-08T10:44:19,368 ############################ 2025-09-08T10:44:19,369 # Package would be ignored # 2025-09-08T10:44:19,369 ############################ 2025-09-08T10:44:19,369 Python recognizes 'publiforge.Processors.Parallel' as an importable package[^1], 2025-09-08T10:44:19,369 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,369 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,369 package, please make sure that 'publiforge.Processors.Parallel' is explicitly added 2025-09-08T10:44:19,369 to the `packages` configuration field. 2025-09-08T10:44:19,369 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,369 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,369 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,370 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,370 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,370 If you don't want 'publiforge.Processors.Parallel' to be distributed and are 2025-09-08T10:44:19,370 already explicitly excluding 'publiforge.Processors.Parallel' via 2025-09-08T10:44:19,370 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,370 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,370 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,370 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,371 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,371 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,371 even if it does not contain any `.py` files. 2025-09-08T10:44:19,371 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,371 directory, all directories are treated like packages. 2025-09-08T10:44:19,371 ******************************************************************************** 2025-09-08T10:44:19,371 !! 2025-09-08T10:44:19,371 check.warn(importable) 2025-09-08T10:44:19,371 /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-08T10:44:19,372 !! 2025-09-08T10:44:19,372 ******************************************************************************** 2025-09-08T10:44:19,372 ############################ 2025-09-08T10:44:19,372 # Package would be ignored # 2025-09-08T10:44:19,372 ############################ 2025-09-08T10:44:19,372 Python recognizes 'publiforge.Processors.Parallel.Variables' as an importable package[^1], 2025-09-08T10:44:19,372 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,372 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,372 package, please make sure that 'publiforge.Processors.Parallel.Variables' is explicitly added 2025-09-08T10:44:19,372 to the `packages` configuration field. 2025-09-08T10:44:19,373 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,373 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,373 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,373 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,373 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,373 If you don't want 'publiforge.Processors.Parallel.Variables' to be distributed and are 2025-09-08T10:44:19,373 already explicitly excluding 'publiforge.Processors.Parallel.Variables' via 2025-09-08T10:44:19,373 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,374 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,374 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,374 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,374 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,374 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,374 even if it does not contain any `.py` files. 2025-09-08T10:44:19,374 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,374 directory, all directories are treated like packages. 2025-09-08T10:44:19,374 ******************************************************************************** 2025-09-08T10:44:19,375 !! 2025-09-08T10:44:19,375 check.warn(importable) 2025-09-08T10:44:19,375 /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-08T10:44:19,375 !! 2025-09-08T10:44:19,375 ******************************************************************************** 2025-09-08T10:44:19,375 ############################ 2025-09-08T10:44:19,375 # Package would be ignored # 2025-09-08T10:44:19,375 ############################ 2025-09-08T10:44:19,375 Python recognizes 'publiforge.Processors.Publianim2Html5' as an importable package[^1], 2025-09-08T10:44:19,375 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,376 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,376 package, please make sure that 'publiforge.Processors.Publianim2Html5' is explicitly added 2025-09-08T10:44:19,376 to the `packages` configuration field. 2025-09-08T10:44:19,376 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,376 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,376 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,376 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,377 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,377 If you don't want 'publiforge.Processors.Publianim2Html5' to be distributed and are 2025-09-08T10:44:19,377 already explicitly excluding 'publiforge.Processors.Publianim2Html5' via 2025-09-08T10:44:19,377 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,377 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,377 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,377 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,377 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,378 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,378 even if it does not contain any `.py` files. 2025-09-08T10:44:19,378 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,378 directory, all directories are treated like packages. 2025-09-08T10:44:19,378 ******************************************************************************** 2025-09-08T10:44:19,378 !! 2025-09-08T10:44:19,378 check.warn(importable) 2025-09-08T10:44:19,378 /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-08T10:44:19,378 !! 2025-09-08T10:44:19,379 ******************************************************************************** 2025-09-08T10:44:19,379 ############################ 2025-09-08T10:44:19,379 # Package would be ignored # 2025-09-08T10:44:19,379 ############################ 2025-09-08T10:44:19,379 Python recognizes 'publiforge.Processors.Publianim2Html5.Variables' as an importable package[^1], 2025-09-08T10:44:19,379 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,379 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,379 package, please make sure that 'publiforge.Processors.Publianim2Html5.Variables' is explicitly added 2025-09-08T10:44:19,379 to the `packages` configuration field. 2025-09-08T10:44:19,379 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,380 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,380 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,380 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,380 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,380 If you don't want 'publiforge.Processors.Publianim2Html5.Variables' to be distributed and are 2025-09-08T10:44:19,380 already explicitly excluding 'publiforge.Processors.Publianim2Html5.Variables' via 2025-09-08T10:44:19,380 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,380 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,380 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,381 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,381 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,381 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,381 even if it does not contain any `.py` files. 2025-09-08T10:44:19,381 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,381 directory, all directories are treated like packages. 2025-09-08T10:44:19,381 ******************************************************************************** 2025-09-08T10:44:19,381 !! 2025-09-08T10:44:19,382 check.warn(importable) 2025-09-08T10:44:19,382 /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-08T10:44:19,382 !! 2025-09-08T10:44:19,382 ******************************************************************************** 2025-09-08T10:44:19,382 ############################ 2025-09-08T10:44:19,382 # Package would be ignored # 2025-09-08T10:44:19,382 ############################ 2025-09-08T10:44:19,382 Python recognizes 'publiforge.Processors.Publianim2Html5.Xsl' as an importable package[^1], 2025-09-08T10:44:19,382 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,382 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,383 package, please make sure that 'publiforge.Processors.Publianim2Html5.Xsl' is explicitly added 2025-09-08T10:44:19,383 to the `packages` configuration field. 2025-09-08T10:44:19,383 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,383 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,383 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,383 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,383 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,383 If you don't want 'publiforge.Processors.Publianim2Html5.Xsl' to be distributed and are 2025-09-08T10:44:19,383 already explicitly excluding 'publiforge.Processors.Publianim2Html5.Xsl' via 2025-09-08T10:44:19,384 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,384 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,384 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,384 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,384 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,384 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,384 even if it does not contain any `.py` files. 2025-09-08T10:44:19,384 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,385 directory, all directories are treated like packages. 2025-09-08T10:44:19,385 ******************************************************************************** 2025-09-08T10:44:19,385 !! 2025-09-08T10:44:19,385 check.warn(importable) 2025-09-08T10:44:19,385 /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-08T10:44:19,385 !! 2025-09-08T10:44:19,385 ******************************************************************************** 2025-09-08T10:44:19,385 ############################ 2025-09-08T10:44:19,385 # Package would be ignored # 2025-09-08T10:44:19,385 ############################ 2025-09-08T10:44:19,385 Python recognizes 'publiforge.Processors.Publidoc2DTBook' as an importable package[^1], 2025-09-08T10:44:19,386 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,386 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,386 package, please make sure that 'publiforge.Processors.Publidoc2DTBook' is explicitly added 2025-09-08T10:44:19,386 to the `packages` configuration field. 2025-09-08T10:44:19,386 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,386 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,386 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,386 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,387 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,387 If you don't want 'publiforge.Processors.Publidoc2DTBook' to be distributed and are 2025-09-08T10:44:19,387 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook' via 2025-09-08T10:44:19,387 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,387 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,387 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,387 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,387 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,388 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,388 even if it does not contain any `.py` files. 2025-09-08T10:44:19,388 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,388 directory, all directories are treated like packages. 2025-09-08T10:44:19,388 ******************************************************************************** 2025-09-08T10:44:19,388 !! 2025-09-08T10:44:19,388 check.warn(importable) 2025-09-08T10:44:19,388 /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-08T10:44:19,388 !! 2025-09-08T10:44:19,389 ******************************************************************************** 2025-09-08T10:44:19,389 ############################ 2025-09-08T10:44:19,389 # Package would be ignored # 2025-09-08T10:44:19,389 ############################ 2025-09-08T10:44:19,389 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Variables' as an importable package[^1], 2025-09-08T10:44:19,389 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,389 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,389 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Variables' is explicitly added 2025-09-08T10:44:19,389 to the `packages` configuration field. 2025-09-08T10:44:19,389 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,390 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,390 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,390 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,390 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,390 If you don't want 'publiforge.Processors.Publidoc2DTBook.Variables' to be distributed and are 2025-09-08T10:44:19,390 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Variables' via 2025-09-08T10:44:19,390 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,390 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,390 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,391 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,391 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,391 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,391 even if it does not contain any `.py` files. 2025-09-08T10:44:19,391 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,391 directory, all directories are treated like packages. 2025-09-08T10:44:19,391 ******************************************************************************** 2025-09-08T10:44:19,392 !! 2025-09-08T10:44:19,392 check.warn(importable) 2025-09-08T10:44:19,392 /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-08T10:44:19,392 !! 2025-09-08T10:44:19,392 ******************************************************************************** 2025-09-08T10:44:19,392 ############################ 2025-09-08T10:44:19,392 # Package would be ignored # 2025-09-08T10:44:19,392 ############################ 2025-09-08T10:44:19,392 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Xsl' as an importable package[^1], 2025-09-08T10:44:19,392 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,393 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,393 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Xsl' is explicitly added 2025-09-08T10:44:19,393 to the `packages` configuration field. 2025-09-08T10:44:19,393 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,393 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,393 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,393 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,393 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,394 If you don't want 'publiforge.Processors.Publidoc2DTBook.Xsl' to be distributed and are 2025-09-08T10:44:19,394 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Xsl' via 2025-09-08T10:44:19,394 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,394 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,394 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,394 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,394 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,394 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,395 even if it does not contain any `.py` files. 2025-09-08T10:44:19,395 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,395 directory, all directories are treated like packages. 2025-09-08T10:44:19,395 ******************************************************************************** 2025-09-08T10:44:19,395 !! 2025-09-08T10:44:19,395 check.warn(importable) 2025-09-08T10:44:19,395 /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-08T10:44:19,395 !! 2025-09-08T10:44:19,395 ******************************************************************************** 2025-09-08T10:44:19,395 ############################ 2025-09-08T10:44:19,396 # Package would be ignored # 2025-09-08T10:44:19,396 ############################ 2025-09-08T10:44:19,396 Python recognizes 'publiforge.Processors.Publidoc2EPub2' as an importable package[^1], 2025-09-08T10:44:19,396 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,396 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,396 package, please make sure that 'publiforge.Processors.Publidoc2EPub2' is explicitly added 2025-09-08T10:44:19,396 to the `packages` configuration field. 2025-09-08T10:44:19,396 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,396 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,396 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,397 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,397 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,397 If you don't want 'publiforge.Processors.Publidoc2EPub2' to be distributed and are 2025-09-08T10:44:19,397 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2' via 2025-09-08T10:44:19,397 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,397 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,397 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,397 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,398 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,398 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,398 even if it does not contain any `.py` files. 2025-09-08T10:44:19,398 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,398 directory, all directories are treated like packages. 2025-09-08T10:44:19,398 ******************************************************************************** 2025-09-08T10:44:19,398 !! 2025-09-08T10:44:19,398 check.warn(importable) 2025-09-08T10:44:19,398 /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-08T10:44:19,399 !! 2025-09-08T10:44:19,399 ******************************************************************************** 2025-09-08T10:44:19,399 ############################ 2025-09-08T10:44:19,399 # Package would be ignored # 2025-09-08T10:44:19,399 ############################ 2025-09-08T10:44:19,399 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates' as an importable package[^1], 2025-09-08T10:44:19,399 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,399 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,399 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates' is explicitly added 2025-09-08T10:44:19,399 to the `packages` configuration field. 2025-09-08T10:44:19,400 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,400 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,400 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,400 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,400 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,400 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates' to be distributed and are 2025-09-08T10:44:19,400 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates' via 2025-09-08T10:44:19,400 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,400 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,401 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,401 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,401 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,401 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,401 even if it does not contain any `.py` files. 2025-09-08T10:44:19,401 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,401 directory, all directories are treated like packages. 2025-09-08T10:44:19,402 ******************************************************************************** 2025-09-08T10:44:19,402 !! 2025-09-08T10:44:19,402 check.warn(importable) 2025-09-08T10:44:19,402 /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-08T10:44:19,402 !! 2025-09-08T10:44:19,402 ******************************************************************************** 2025-09-08T10:44:19,402 ############################ 2025-09-08T10:44:19,402 # Package would be ignored # 2025-09-08T10:44:19,402 ############################ 2025-09-08T10:44:19,403 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' as an importable package[^1], 2025-09-08T10:44:19,403 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,403 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,403 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' is explicitly added 2025-09-08T10:44:19,403 to the `packages` configuration field. 2025-09-08T10:44:19,403 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,403 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,403 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,403 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,404 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,404 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' to be distributed and are 2025-09-08T10:44:19,404 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' via 2025-09-08T10:44:19,404 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,404 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,404 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,404 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,404 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,405 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,405 even if it does not contain any `.py` files. 2025-09-08T10:44:19,405 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,405 directory, all directories are treated like packages. 2025-09-08T10:44:19,405 ******************************************************************************** 2025-09-08T10:44:19,405 !! 2025-09-08T10:44:19,405 check.warn(importable) 2025-09-08T10:44:19,405 /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-08T10:44:19,405 !! 2025-09-08T10:44:19,406 ******************************************************************************** 2025-09-08T10:44:19,406 ############################ 2025-09-08T10:44:19,406 # Package would be ignored # 2025-09-08T10:44:19,406 ############################ 2025-09-08T10:44:19,406 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Variables' as an importable package[^1], 2025-09-08T10:44:19,406 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,406 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,406 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Variables' is explicitly added 2025-09-08T10:44:19,406 to the `packages` configuration field. 2025-09-08T10:44:19,406 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,406 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,407 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,407 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,407 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,407 If you don't want 'publiforge.Processors.Publidoc2EPub2.Variables' to be distributed and are 2025-09-08T10:44:19,407 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Variables' via 2025-09-08T10:44:19,407 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,407 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,407 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,408 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,408 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,408 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,408 even if it does not contain any `.py` files. 2025-09-08T10:44:19,408 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,408 directory, all directories are treated like packages. 2025-09-08T10:44:19,408 ******************************************************************************** 2025-09-08T10:44:19,408 !! 2025-09-08T10:44:19,408 check.warn(importable) 2025-09-08T10:44:19,409 /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-08T10:44:19,409 !! 2025-09-08T10:44:19,409 ******************************************************************************** 2025-09-08T10:44:19,409 ############################ 2025-09-08T10:44:19,409 # Package would be ignored # 2025-09-08T10:44:19,409 ############################ 2025-09-08T10:44:19,409 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Xsl' as an importable package[^1], 2025-09-08T10:44:19,409 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,409 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,409 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Xsl' is explicitly added 2025-09-08T10:44:19,410 to the `packages` configuration field. 2025-09-08T10:44:19,410 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,410 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,410 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,410 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,410 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,410 If you don't want 'publiforge.Processors.Publidoc2EPub2.Xsl' to be distributed and are 2025-09-08T10:44:19,410 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Xsl' via 2025-09-08T10:44:19,411 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,411 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,411 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,411 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,411 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,411 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,411 even if it does not contain any `.py` files. 2025-09-08T10:44:19,411 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,411 directory, all directories are treated like packages. 2025-09-08T10:44:19,412 ******************************************************************************** 2025-09-08T10:44:19,412 !! 2025-09-08T10:44:19,412 check.warn(importable) 2025-09-08T10:44:19,412 /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-08T10:44:19,412 !! 2025-09-08T10:44:19,412 ******************************************************************************** 2025-09-08T10:44:19,412 ############################ 2025-09-08T10:44:19,412 # Package would be ignored # 2025-09-08T10:44:19,412 ############################ 2025-09-08T10:44:19,412 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars' as an importable package[^1], 2025-09-08T10:44:19,413 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,413 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,413 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars' is explicitly added 2025-09-08T10:44:19,413 to the `packages` configuration field. 2025-09-08T10:44:19,413 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,413 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,413 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,413 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,413 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,414 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars' to be distributed and are 2025-09-08T10:44:19,414 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars' via 2025-09-08T10:44:19,414 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,414 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,414 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,414 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,414 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,415 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,415 even if it does not contain any `.py` files. 2025-09-08T10:44:19,415 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,415 directory, all directories are treated like packages. 2025-09-08T10:44:19,415 ******************************************************************************** 2025-09-08T10:44:19,415 !! 2025-09-08T10:44:19,415 check.warn(importable) 2025-09-08T10:44:19,415 /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-08T10:44:19,415 !! 2025-09-08T10:44:19,416 ******************************************************************************** 2025-09-08T10:44:19,416 ############################ 2025-09-08T10:44:19,416 # Package would be ignored # 2025-09-08T10:44:19,416 ############################ 2025-09-08T10:44:19,416 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.lib' as an importable package[^1], 2025-09-08T10:44:19,416 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,416 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,416 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.lib' is explicitly added 2025-09-08T10:44:19,416 to the `packages` configuration field. 2025-09-08T10:44:19,417 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,417 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,417 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,417 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,417 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,417 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.lib' to be distributed and are 2025-09-08T10:44:19,417 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.lib' via 2025-09-08T10:44:19,417 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,417 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,417 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,418 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,418 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,418 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,418 even if it does not contain any `.py` files. 2025-09-08T10:44:19,418 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,418 directory, all directories are treated like packages. 2025-09-08T10:44:19,418 ******************************************************************************** 2025-09-08T10:44:19,419 !! 2025-09-08T10:44:19,419 check.warn(importable) 2025-09-08T10:44:19,419 /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-08T10:44:19,419 !! 2025-09-08T10:44:19,419 ******************************************************************************** 2025-09-08T10:44:19,419 ############################ 2025-09-08T10:44:19,419 # Package would be ignored # 2025-09-08T10:44:19,419 ############################ 2025-09-08T10:44:19,419 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.licenses' as an importable package[^1], 2025-09-08T10:44:19,419 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,420 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,420 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.licenses' is explicitly added 2025-09-08T10:44:19,420 to the `packages` configuration field. 2025-09-08T10:44:19,420 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,420 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,420 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,420 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,420 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,420 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.licenses' to be distributed and are 2025-09-08T10:44:19,421 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.licenses' via 2025-09-08T10:44:19,421 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,421 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,421 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,421 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,421 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,421 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,422 even if it does not contain any `.py` files. 2025-09-08T10:44:19,422 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,422 directory, all directories are treated like packages. 2025-09-08T10:44:19,422 ******************************************************************************** 2025-09-08T10:44:19,422 !! 2025-09-08T10:44:19,422 check.warn(importable) 2025-09-08T10:44:19,422 /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-08T10:44:19,422 !! 2025-09-08T10:44:19,422 ******************************************************************************** 2025-09-08T10:44:19,422 ############################ 2025-09-08T10:44:19,422 # Package would be ignored # 2025-09-08T10:44:19,423 ############################ 2025-09-08T10:44:19,423 Python recognizes 'publiforge.Processors.Publidoc2EPub3' as an importable package[^1], 2025-09-08T10:44:19,423 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,423 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,423 package, please make sure that 'publiforge.Processors.Publidoc2EPub3' is explicitly added 2025-09-08T10:44:19,423 to the `packages` configuration field. 2025-09-08T10:44:19,423 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,423 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,423 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,424 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,424 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,424 If you don't want 'publiforge.Processors.Publidoc2EPub3' to be distributed and are 2025-09-08T10:44:19,424 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3' via 2025-09-08T10:44:19,424 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,424 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,424 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,424 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,425 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,425 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,425 even if it does not contain any `.py` files. 2025-09-08T10:44:19,425 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,425 directory, all directories are treated like packages. 2025-09-08T10:44:19,425 ******************************************************************************** 2025-09-08T10:44:19,425 !! 2025-09-08T10:44:19,425 check.warn(importable) 2025-09-08T10:44:19,425 /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-08T10:44:19,425 !! 2025-09-08T10:44:19,426 ******************************************************************************** 2025-09-08T10:44:19,426 ############################ 2025-09-08T10:44:19,426 # Package would be ignored # 2025-09-08T10:44:19,426 ############################ 2025-09-08T10:44:19,426 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates' as an importable package[^1], 2025-09-08T10:44:19,426 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,426 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,426 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates' is explicitly added 2025-09-08T10:44:19,426 to the `packages` configuration field. 2025-09-08T10:44:19,427 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,427 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,427 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,427 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,427 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,427 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates' to be distributed and are 2025-09-08T10:44:19,427 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates' via 2025-09-08T10:44:19,427 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,428 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,428 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,428 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,428 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,428 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,428 even if it does not contain any `.py` files. 2025-09-08T10:44:19,428 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,428 directory, all directories are treated like packages. 2025-09-08T10:44:19,429 ******************************************************************************** 2025-09-08T10:44:19,429 !! 2025-09-08T10:44:19,429 check.warn(importable) 2025-09-08T10:44:19,429 /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-08T10:44:19,429 !! 2025-09-08T10:44:19,429 ******************************************************************************** 2025-09-08T10:44:19,429 ############################ 2025-09-08T10:44:19,429 # Package would be ignored # 2025-09-08T10:44:19,429 ############################ 2025-09-08T10:44:19,429 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' as an importable package[^1], 2025-09-08T10:44:19,430 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,430 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,430 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' is explicitly added 2025-09-08T10:44:19,430 to the `packages` configuration field. 2025-09-08T10:44:19,430 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,430 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,430 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,430 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,430 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,431 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' to be distributed and are 2025-09-08T10:44:19,431 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' via 2025-09-08T10:44:19,431 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,431 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,431 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,431 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,431 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,432 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,432 even if it does not contain any `.py` files. 2025-09-08T10:44:19,432 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,432 directory, all directories are treated like packages. 2025-09-08T10:44:19,432 ******************************************************************************** 2025-09-08T10:44:19,432 !! 2025-09-08T10:44:19,432 check.warn(importable) 2025-09-08T10:44:19,432 /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-08T10:44:19,432 !! 2025-09-08T10:44:19,432 ******************************************************************************** 2025-09-08T10:44:19,433 ############################ 2025-09-08T10:44:19,433 # Package would be ignored # 2025-09-08T10:44:19,433 ############################ 2025-09-08T10:44:19,433 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Variables' as an importable package[^1], 2025-09-08T10:44:19,433 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,433 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,433 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Variables' is explicitly added 2025-09-08T10:44:19,433 to the `packages` configuration field. 2025-09-08T10:44:19,433 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,433 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,434 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,434 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,434 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,434 If you don't want 'publiforge.Processors.Publidoc2EPub3.Variables' to be distributed and are 2025-09-08T10:44:19,434 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Variables' via 2025-09-08T10:44:19,434 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,434 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,434 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,434 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,435 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,435 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,435 even if it does not contain any `.py` files. 2025-09-08T10:44:19,435 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,435 directory, all directories are treated like packages. 2025-09-08T10:44:19,435 ******************************************************************************** 2025-09-08T10:44:19,435 !! 2025-09-08T10:44:19,435 check.warn(importable) 2025-09-08T10:44:19,436 /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-08T10:44:19,436 !! 2025-09-08T10:44:19,436 ******************************************************************************** 2025-09-08T10:44:19,436 ############################ 2025-09-08T10:44:19,436 # Package would be ignored # 2025-09-08T10:44:19,436 ############################ 2025-09-08T10:44:19,436 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Xsl' as an importable package[^1], 2025-09-08T10:44:19,436 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,436 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,436 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Xsl' is explicitly added 2025-09-08T10:44:19,437 to the `packages` configuration field. 2025-09-08T10:44:19,437 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,437 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,437 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,437 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,437 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,437 If you don't want 'publiforge.Processors.Publidoc2EPub3.Xsl' to be distributed and are 2025-09-08T10:44:19,437 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Xsl' via 2025-09-08T10:44:19,437 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,438 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,438 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,438 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,438 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,438 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,438 even if it does not contain any `.py` files. 2025-09-08T10:44:19,438 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,438 directory, all directories are treated like packages. 2025-09-08T10:44:19,439 ******************************************************************************** 2025-09-08T10:44:19,439 !! 2025-09-08T10:44:19,439 check.warn(importable) 2025-09-08T10:44:19,439 /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-08T10:44:19,439 !! 2025-09-08T10:44:19,439 ******************************************************************************** 2025-09-08T10:44:19,439 ############################ 2025-09-08T10:44:19,439 # Package would be ignored # 2025-09-08T10:44:19,439 ############################ 2025-09-08T10:44:19,440 Python recognizes 'publiforge.Processors.Publidoc2Html5' as an importable package[^1], 2025-09-08T10:44:19,440 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,440 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,440 package, please make sure that 'publiforge.Processors.Publidoc2Html5' is explicitly added 2025-09-08T10:44:19,440 to the `packages` configuration field. 2025-09-08T10:44:19,440 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,440 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,440 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,440 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,441 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,441 If you don't want 'publiforge.Processors.Publidoc2Html5' to be distributed and are 2025-09-08T10:44:19,441 already explicitly excluding 'publiforge.Processors.Publidoc2Html5' via 2025-09-08T10:44:19,441 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,441 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,441 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,441 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,441 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,442 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,442 even if it does not contain any `.py` files. 2025-09-08T10:44:19,442 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,442 directory, all directories are treated like packages. 2025-09-08T10:44:19,442 ******************************************************************************** 2025-09-08T10:44:19,442 !! 2025-09-08T10:44:19,442 check.warn(importable) 2025-09-08T10:44:19,442 /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-08T10:44:19,442 !! 2025-09-08T10:44:19,443 ******************************************************************************** 2025-09-08T10:44:19,443 ############################ 2025-09-08T10:44:19,443 # Package would be ignored # 2025-09-08T10:44:19,443 ############################ 2025-09-08T10:44:19,443 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Css' as an importable package[^1], 2025-09-08T10:44:19,443 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,443 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,443 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Css' is explicitly added 2025-09-08T10:44:19,443 to the `packages` configuration field. 2025-09-08T10:44:19,444 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,444 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,444 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,444 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,444 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,444 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Css' to be distributed and are 2025-09-08T10:44:19,444 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Css' via 2025-09-08T10:44:19,444 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,444 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,445 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,445 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,445 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,445 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,445 even if it does not contain any `.py` files. 2025-09-08T10:44:19,445 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,445 directory, all directories are treated like packages. 2025-09-08T10:44:19,445 ******************************************************************************** 2025-09-08T10:44:19,446 !! 2025-09-08T10:44:19,446 check.warn(importable) 2025-09-08T10:44:19,446 /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-08T10:44:19,446 !! 2025-09-08T10:44:19,446 ******************************************************************************** 2025-09-08T10:44:19,446 ############################ 2025-09-08T10:44:19,446 # Package would be ignored # 2025-09-08T10:44:19,446 ############################ 2025-09-08T10:44:19,446 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Images' as an importable package[^1], 2025-09-08T10:44:19,446 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,447 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,447 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Images' is explicitly added 2025-09-08T10:44:19,447 to the `packages` configuration field. 2025-09-08T10:44:19,447 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,447 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,447 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,447 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,447 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,448 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Images' to be distributed and are 2025-09-08T10:44:19,448 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Images' via 2025-09-08T10:44:19,448 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,448 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,448 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,448 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,448 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,448 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,449 even if it does not contain any `.py` files. 2025-09-08T10:44:19,449 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,449 directory, all directories are treated like packages. 2025-09-08T10:44:19,449 ******************************************************************************** 2025-09-08T10:44:19,449 !! 2025-09-08T10:44:19,449 check.warn(importable) 2025-09-08T10:44:19,449 /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-08T10:44:19,449 !! 2025-09-08T10:44:19,449 ******************************************************************************** 2025-09-08T10:44:19,449 ############################ 2025-09-08T10:44:19,450 # Package would be ignored # 2025-09-08T10:44:19,450 ############################ 2025-09-08T10:44:19,450 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Js' as an importable package[^1], 2025-09-08T10:44:19,450 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,450 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,450 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Js' is explicitly added 2025-09-08T10:44:19,450 to the `packages` configuration field. 2025-09-08T10:44:19,450 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,450 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,450 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,451 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,451 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,451 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Js' to be distributed and are 2025-09-08T10:44:19,451 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Js' via 2025-09-08T10:44:19,451 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,451 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,451 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,451 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,452 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,452 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,452 even if it does not contain any `.py` files. 2025-09-08T10:44:19,452 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,452 directory, all directories are treated like packages. 2025-09-08T10:44:19,452 ******************************************************************************** 2025-09-08T10:44:19,452 !! 2025-09-08T10:44:19,452 check.warn(importable) 2025-09-08T10:44:19,453 /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-08T10:44:19,453 !! 2025-09-08T10:44:19,453 ******************************************************************************** 2025-09-08T10:44:19,453 ############################ 2025-09-08T10:44:19,453 # Package would be ignored # 2025-09-08T10:44:19,453 ############################ 2025-09-08T10:44:19,453 Python recognizes 'publiforge.Processors.Publidoc2Html5.Variables' as an importable package[^1], 2025-09-08T10:44:19,453 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,453 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,453 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Variables' is explicitly added 2025-09-08T10:44:19,454 to the `packages` configuration field. 2025-09-08T10:44:19,454 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,454 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,454 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,454 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,454 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,454 If you don't want 'publiforge.Processors.Publidoc2Html5.Variables' to be distributed and are 2025-09-08T10:44:19,454 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Variables' via 2025-09-08T10:44:19,455 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,455 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,455 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,455 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,455 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,455 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,455 even if it does not contain any `.py` files. 2025-09-08T10:44:19,455 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,456 directory, all directories are treated like packages. 2025-09-08T10:44:19,456 ******************************************************************************** 2025-09-08T10:44:19,456 !! 2025-09-08T10:44:19,456 check.warn(importable) 2025-09-08T10:44:19,456 /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-08T10:44:19,456 !! 2025-09-08T10:44:19,456 ******************************************************************************** 2025-09-08T10:44:19,456 ############################ 2025-09-08T10:44:19,456 # Package would be ignored # 2025-09-08T10:44:19,456 ############################ 2025-09-08T10:44:19,457 Python recognizes 'publiforge.Processors.Publidoc2Html5.Xsl' as an importable package[^1], 2025-09-08T10:44:19,457 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,457 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,457 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Xsl' is explicitly added 2025-09-08T10:44:19,457 to the `packages` configuration field. 2025-09-08T10:44:19,457 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,457 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,457 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,457 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,458 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,458 If you don't want 'publiforge.Processors.Publidoc2Html5.Xsl' to be distributed and are 2025-09-08T10:44:19,458 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Xsl' via 2025-09-08T10:44:19,458 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,458 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,458 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,458 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,458 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,459 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,459 even if it does not contain any `.py` files. 2025-09-08T10:44:19,459 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,459 directory, all directories are treated like packages. 2025-09-08T10:44:19,459 ******************************************************************************** 2025-09-08T10:44:19,459 !! 2025-09-08T10:44:19,459 check.warn(importable) 2025-09-08T10:44:19,459 /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-08T10:44:19,459 !! 2025-09-08T10:44:19,459 ******************************************************************************** 2025-09-08T10:44:19,460 ############################ 2025-09-08T10:44:19,460 # Package would be ignored # 2025-09-08T10:44:19,460 ############################ 2025-09-08T10:44:19,460 Python recognizes 'publiforge.Processors.Publidoc2Pdf' as an importable package[^1], 2025-09-08T10:44:19,460 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,460 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,460 package, please make sure that 'publiforge.Processors.Publidoc2Pdf' is explicitly added 2025-09-08T10:44:19,460 to the `packages` configuration field. 2025-09-08T10:44:19,460 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,460 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,461 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,461 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,461 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,461 If you don't want 'publiforge.Processors.Publidoc2Pdf' to be distributed and are 2025-09-08T10:44:19,461 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf' via 2025-09-08T10:44:19,461 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,461 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,461 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,462 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,462 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,462 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,462 even if it does not contain any `.py` files. 2025-09-08T10:44:19,462 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,462 directory, all directories are treated like packages. 2025-09-08T10:44:19,462 ******************************************************************************** 2025-09-08T10:44:19,462 !! 2025-09-08T10:44:19,463 check.warn(importable) 2025-09-08T10:44:19,463 /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-08T10:44:19,463 !! 2025-09-08T10:44:19,463 ******************************************************************************** 2025-09-08T10:44:19,463 ############################ 2025-09-08T10:44:19,463 # Package would be ignored # 2025-09-08T10:44:19,463 ############################ 2025-09-08T10:44:19,463 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Fonts' as an importable package[^1], 2025-09-08T10:44:19,463 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,463 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,464 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Fonts' is explicitly added 2025-09-08T10:44:19,464 to the `packages` configuration field. 2025-09-08T10:44:19,464 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,464 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,464 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,464 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,464 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,464 If you don't want 'publiforge.Processors.Publidoc2Pdf.Fonts' to be distributed and are 2025-09-08T10:44:19,465 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Fonts' via 2025-09-08T10:44:19,465 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,465 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,465 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,465 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,465 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,465 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,466 even if it does not contain any `.py` files. 2025-09-08T10:44:19,466 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,466 directory, all directories are treated like packages. 2025-09-08T10:44:19,466 ******************************************************************************** 2025-09-08T10:44:19,466 !! 2025-09-08T10:44:19,466 check.warn(importable) 2025-09-08T10:44:19,466 /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-08T10:44:19,466 !! 2025-09-08T10:44:19,466 ******************************************************************************** 2025-09-08T10:44:19,466 ############################ 2025-09-08T10:44:19,467 # Package would be ignored # 2025-09-08T10:44:19,467 ############################ 2025-09-08T10:44:19,467 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Regex' as an importable package[^1], 2025-09-08T10:44:19,467 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,467 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,467 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Regex' is explicitly added 2025-09-08T10:44:19,467 to the `packages` configuration field. 2025-09-08T10:44:19,467 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,467 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,467 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,468 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,468 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,468 If you don't want 'publiforge.Processors.Publidoc2Pdf.Regex' to be distributed and are 2025-09-08T10:44:19,468 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Regex' via 2025-09-08T10:44:19,468 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,468 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,468 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,468 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,469 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,469 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,469 even if it does not contain any `.py` files. 2025-09-08T10:44:19,469 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,469 directory, all directories are treated like packages. 2025-09-08T10:44:19,469 ******************************************************************************** 2025-09-08T10:44:19,469 !! 2025-09-08T10:44:19,469 check.warn(importable) 2025-09-08T10:44:19,469 /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-08T10:44:19,470 !! 2025-09-08T10:44:19,470 ******************************************************************************** 2025-09-08T10:44:19,470 ############################ 2025-09-08T10:44:19,470 # Package would be ignored # 2025-09-08T10:44:19,470 ############################ 2025-09-08T10:44:19,470 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Variables' as an importable package[^1], 2025-09-08T10:44:19,470 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,470 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,470 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Variables' is explicitly added 2025-09-08T10:44:19,470 to the `packages` configuration field. 2025-09-08T10:44:19,471 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,471 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,471 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,471 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,471 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,471 If you don't want 'publiforge.Processors.Publidoc2Pdf.Variables' to be distributed and are 2025-09-08T10:44:19,471 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Variables' via 2025-09-08T10:44:19,471 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,471 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,472 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,472 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,472 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,472 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,472 even if it does not contain any `.py` files. 2025-09-08T10:44:19,472 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,472 directory, all directories are treated like packages. 2025-09-08T10:44:19,472 ******************************************************************************** 2025-09-08T10:44:19,473 !! 2025-09-08T10:44:19,473 check.warn(importable) 2025-09-08T10:44:19,473 /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-08T10:44:19,473 !! 2025-09-08T10:44:19,473 ******************************************************************************** 2025-09-08T10:44:19,473 ############################ 2025-09-08T10:44:19,473 # Package would be ignored # 2025-09-08T10:44:19,473 ############################ 2025-09-08T10:44:19,473 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Xsl' as an importable package[^1], 2025-09-08T10:44:19,473 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,474 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,474 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Xsl' is explicitly added 2025-09-08T10:44:19,474 to the `packages` configuration field. 2025-09-08T10:44:19,474 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,474 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,474 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,474 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,474 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,475 If you don't want 'publiforge.Processors.Publidoc2Pdf.Xsl' to be distributed and are 2025-09-08T10:44:19,475 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Xsl' via 2025-09-08T10:44:19,475 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,475 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,475 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,475 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,475 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,475 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,476 even if it does not contain any `.py` files. 2025-09-08T10:44:19,476 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,476 directory, all directories are treated like packages. 2025-09-08T10:44:19,476 ******************************************************************************** 2025-09-08T10:44:19,476 !! 2025-09-08T10:44:19,476 check.warn(importable) 2025-09-08T10:44:19,476 /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-08T10:44:19,476 !! 2025-09-08T10:44:19,476 ******************************************************************************** 2025-09-08T10:44:19,476 ############################ 2025-09-08T10:44:19,477 # Package would be ignored # 2025-09-08T10:44:19,477 ############################ 2025-09-08T10:44:19,477 Python recognizes 'publiforge.Processors.Publidoc2XHtml' as an importable package[^1], 2025-09-08T10:44:19,477 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,477 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,477 package, please make sure that 'publiforge.Processors.Publidoc2XHtml' is explicitly added 2025-09-08T10:44:19,477 to the `packages` configuration field. 2025-09-08T10:44:19,477 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,477 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,477 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,478 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,478 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,478 If you don't want 'publiforge.Processors.Publidoc2XHtml' to be distributed and are 2025-09-08T10:44:19,478 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml' via 2025-09-08T10:44:19,478 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,478 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,478 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,479 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,479 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,479 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,479 even if it does not contain any `.py` files. 2025-09-08T10:44:19,479 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,479 directory, all directories are treated like packages. 2025-09-08T10:44:19,479 ******************************************************************************** 2025-09-08T10:44:19,479 !! 2025-09-08T10:44:19,480 check.warn(importable) 2025-09-08T10:44:19,480 /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-08T10:44:19,480 !! 2025-09-08T10:44:19,480 ******************************************************************************** 2025-09-08T10:44:19,480 ############################ 2025-09-08T10:44:19,480 # Package would be ignored # 2025-09-08T10:44:19,480 ############################ 2025-09-08T10:44:19,480 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Regex' as an importable package[^1], 2025-09-08T10:44:19,480 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,480 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,481 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Regex' is explicitly added 2025-09-08T10:44:19,481 to the `packages` configuration field. 2025-09-08T10:44:19,481 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,481 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,481 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,481 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,481 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,481 If you don't want 'publiforge.Processors.Publidoc2XHtml.Regex' to be distributed and are 2025-09-08T10:44:19,482 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Regex' via 2025-09-08T10:44:19,482 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,482 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,482 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,482 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,482 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,482 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,482 even if it does not contain any `.py` files. 2025-09-08T10:44:19,483 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,483 directory, all directories are treated like packages. 2025-09-08T10:44:19,483 ******************************************************************************** 2025-09-08T10:44:19,483 !! 2025-09-08T10:44:19,483 check.warn(importable) 2025-09-08T10:44:19,483 /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-08T10:44:19,483 !! 2025-09-08T10:44:19,483 ******************************************************************************** 2025-09-08T10:44:19,483 ############################ 2025-09-08T10:44:19,483 # Package would be ignored # 2025-09-08T10:44:19,483 ############################ 2025-09-08T10:44:19,484 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Scss' as an importable package[^1], 2025-09-08T10:44:19,484 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,484 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,484 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Scss' is explicitly added 2025-09-08T10:44:19,484 to the `packages` configuration field. 2025-09-08T10:44:19,484 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,484 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,484 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,484 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,485 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,485 If you don't want 'publiforge.Processors.Publidoc2XHtml.Scss' to be distributed and are 2025-09-08T10:44:19,485 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Scss' via 2025-09-08T10:44:19,485 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,485 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,485 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,485 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,485 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,486 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,486 even if it does not contain any `.py` files. 2025-09-08T10:44:19,486 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,486 directory, all directories are treated like packages. 2025-09-08T10:44:19,486 ******************************************************************************** 2025-09-08T10:44:19,486 !! 2025-09-08T10:44:19,486 check.warn(importable) 2025-09-08T10:44:19,486 /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-08T10:44:19,486 !! 2025-09-08T10:44:19,487 ******************************************************************************** 2025-09-08T10:44:19,487 ############################ 2025-09-08T10:44:19,487 # Package would be ignored # 2025-09-08T10:44:19,487 ############################ 2025-09-08T10:44:19,487 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Css' as an importable package[^1], 2025-09-08T10:44:19,487 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,487 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,487 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Css' is explicitly added 2025-09-08T10:44:19,487 to the `packages` configuration field. 2025-09-08T10:44:19,487 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,487 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,488 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,488 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,488 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,488 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Css' to be distributed and are 2025-09-08T10:44:19,488 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Css' via 2025-09-08T10:44:19,488 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,488 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,488 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,489 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,489 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,489 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,489 even if it does not contain any `.py` files. 2025-09-08T10:44:19,489 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,489 directory, all directories are treated like packages. 2025-09-08T10:44:19,489 ******************************************************************************** 2025-09-08T10:44:19,489 !! 2025-09-08T10:44:19,489 check.warn(importable) 2025-09-08T10:44:19,490 /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-08T10:44:19,490 !! 2025-09-08T10:44:19,490 ******************************************************************************** 2025-09-08T10:44:19,490 ############################ 2025-09-08T10:44:19,490 # Package would be ignored # 2025-09-08T10:44:19,490 ############################ 2025-09-08T10:44:19,490 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Images' as an importable package[^1], 2025-09-08T10:44:19,490 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,490 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,491 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Images' is explicitly added 2025-09-08T10:44:19,491 to the `packages` configuration field. 2025-09-08T10:44:19,491 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,491 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,491 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,491 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,491 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,491 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Images' to be distributed and are 2025-09-08T10:44:19,492 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Images' via 2025-09-08T10:44:19,492 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,492 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,492 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,492 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,492 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,492 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,492 even if it does not contain any `.py` files. 2025-09-08T10:44:19,493 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,493 directory, all directories are treated like packages. 2025-09-08T10:44:19,493 ******************************************************************************** 2025-09-08T10:44:19,493 !! 2025-09-08T10:44:19,493 check.warn(importable) 2025-09-08T10:44:19,493 /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-08T10:44:19,493 !! 2025-09-08T10:44:19,493 ******************************************************************************** 2025-09-08T10:44:19,493 ############################ 2025-09-08T10:44:19,493 # Package would be ignored # 2025-09-08T10:44:19,494 ############################ 2025-09-08T10:44:19,494 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Js' as an importable package[^1], 2025-09-08T10:44:19,494 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,494 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,494 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Js' is explicitly added 2025-09-08T10:44:19,494 to the `packages` configuration field. 2025-09-08T10:44:19,494 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,494 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,494 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,495 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,495 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,495 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Js' to be distributed and are 2025-09-08T10:44:19,495 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Js' via 2025-09-08T10:44:19,495 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,495 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,495 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,495 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,496 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,496 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,496 even if it does not contain any `.py` files. 2025-09-08T10:44:19,496 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,496 directory, all directories are treated like packages. 2025-09-08T10:44:19,496 ******************************************************************************** 2025-09-08T10:44:19,496 !! 2025-09-08T10:44:19,496 check.warn(importable) 2025-09-08T10:44:19,496 /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-08T10:44:19,496 !! 2025-09-08T10:44:19,497 ******************************************************************************** 2025-09-08T10:44:19,497 ############################ 2025-09-08T10:44:19,497 # Package would be ignored # 2025-09-08T10:44:19,497 ############################ 2025-09-08T10:44:19,497 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Variables' as an importable package[^1], 2025-09-08T10:44:19,497 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,497 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,497 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Variables' is explicitly added 2025-09-08T10:44:19,497 to the `packages` configuration field. 2025-09-08T10:44:19,498 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,498 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,498 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,498 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,498 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,498 If you don't want 'publiforge.Processors.Publidoc2XHtml.Variables' to be distributed and are 2025-09-08T10:44:19,498 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Variables' via 2025-09-08T10:44:19,498 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,498 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,499 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,499 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,499 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,499 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,499 even if it does not contain any `.py` files. 2025-09-08T10:44:19,499 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,499 directory, all directories are treated like packages. 2025-09-08T10:44:19,499 ******************************************************************************** 2025-09-08T10:44:19,500 !! 2025-09-08T10:44:19,500 check.warn(importable) 2025-09-08T10:44:19,500 /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-08T10:44:19,500 !! 2025-09-08T10:44:19,500 ******************************************************************************** 2025-09-08T10:44:19,500 ############################ 2025-09-08T10:44:19,500 # Package would be ignored # 2025-09-08T10:44:19,500 ############################ 2025-09-08T10:44:19,500 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Xsl' as an importable package[^1], 2025-09-08T10:44:19,500 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,501 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,501 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Xsl' is explicitly added 2025-09-08T10:44:19,501 to the `packages` configuration field. 2025-09-08T10:44:19,501 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,501 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,501 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,501 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,501 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,501 If you don't want 'publiforge.Processors.Publidoc2XHtml.Xsl' to be distributed and are 2025-09-08T10:44:19,502 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Xsl' via 2025-09-08T10:44:19,502 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,502 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,502 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,502 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,502 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,502 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,502 even if it does not contain any `.py` files. 2025-09-08T10:44:19,503 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,503 directory, all directories are treated like packages. 2025-09-08T10:44:19,503 ******************************************************************************** 2025-09-08T10:44:19,503 !! 2025-09-08T10:44:19,503 check.warn(importable) 2025-09-08T10:44:19,503 /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-08T10:44:19,503 !! 2025-09-08T10:44:19,503 ******************************************************************************** 2025-09-08T10:44:19,504 ############################ 2025-09-08T10:44:19,504 # Package would be ignored # 2025-09-08T10:44:19,504 ############################ 2025-09-08T10:44:19,504 Python recognizes 'publiforge.Processors.PublidocClean' as an importable package[^1], 2025-09-08T10:44:19,504 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,504 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,504 package, please make sure that 'publiforge.Processors.PublidocClean' is explicitly added 2025-09-08T10:44:19,504 to the `packages` configuration field. 2025-09-08T10:44:19,504 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,504 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,505 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,505 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,505 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,505 If you don't want 'publiforge.Processors.PublidocClean' to be distributed and are 2025-09-08T10:44:19,505 already explicitly excluding 'publiforge.Processors.PublidocClean' via 2025-09-08T10:44:19,505 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,505 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,505 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,506 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,506 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,506 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,506 even if it does not contain any `.py` files. 2025-09-08T10:44:19,506 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,506 directory, all directories are treated like packages. 2025-09-08T10:44:19,506 ******************************************************************************** 2025-09-08T10:44:19,506 !! 2025-09-08T10:44:19,506 check.warn(importable) 2025-09-08T10:44:19,507 /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-08T10:44:19,507 !! 2025-09-08T10:44:19,507 ******************************************************************************** 2025-09-08T10:44:19,507 ############################ 2025-09-08T10:44:19,507 # Package would be ignored # 2025-09-08T10:44:19,507 ############################ 2025-09-08T10:44:19,507 Python recognizes 'publiforge.Processors.PublidocClean.Regex' as an importable package[^1], 2025-09-08T10:44:19,507 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,507 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,507 package, please make sure that 'publiforge.Processors.PublidocClean.Regex' is explicitly added 2025-09-08T10:44:19,508 to the `packages` configuration field. 2025-09-08T10:44:19,508 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,508 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,508 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,508 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,508 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,508 If you don't want 'publiforge.Processors.PublidocClean.Regex' to be distributed and are 2025-09-08T10:44:19,508 already explicitly excluding 'publiforge.Processors.PublidocClean.Regex' via 2025-09-08T10:44:19,509 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,509 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,509 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,509 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,509 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,509 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,509 even if it does not contain any `.py` files. 2025-09-08T10:44:19,509 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,509 directory, all directories are treated like packages. 2025-09-08T10:44:19,510 ******************************************************************************** 2025-09-08T10:44:19,510 !! 2025-09-08T10:44:19,510 check.warn(importable) 2025-09-08T10:44:19,510 /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-08T10:44:19,510 !! 2025-09-08T10:44:19,510 ******************************************************************************** 2025-09-08T10:44:19,510 ############################ 2025-09-08T10:44:19,510 # Package would be ignored # 2025-09-08T10:44:19,510 ############################ 2025-09-08T10:44:19,510 Python recognizes 'publiforge.Processors.PublidocClean.Variables' as an importable package[^1], 2025-09-08T10:44:19,511 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,511 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,511 package, please make sure that 'publiforge.Processors.PublidocClean.Variables' is explicitly added 2025-09-08T10:44:19,511 to the `packages` configuration field. 2025-09-08T10:44:19,511 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,511 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,511 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,511 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,512 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,512 If you don't want 'publiforge.Processors.PublidocClean.Variables' to be distributed and are 2025-09-08T10:44:19,512 already explicitly excluding 'publiforge.Processors.PublidocClean.Variables' via 2025-09-08T10:44:19,512 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,512 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,512 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,512 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,512 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,513 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,513 even if it does not contain any `.py` files. 2025-09-08T10:44:19,513 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,513 directory, all directories are treated like packages. 2025-09-08T10:44:19,513 ******************************************************************************** 2025-09-08T10:44:19,513 !! 2025-09-08T10:44:19,513 check.warn(importable) 2025-09-08T10:44:19,513 /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-08T10:44:19,513 !! 2025-09-08T10:44:19,513 ******************************************************************************** 2025-09-08T10:44:19,514 ############################ 2025-09-08T10:44:19,514 # Package would be ignored # 2025-09-08T10:44:19,514 ############################ 2025-09-08T10:44:19,514 Python recognizes 'publiforge.Processors.PublidocClean.Xsl' as an importable package[^1], 2025-09-08T10:44:19,514 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,514 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,514 package, please make sure that 'publiforge.Processors.PublidocClean.Xsl' is explicitly added 2025-09-08T10:44:19,514 to the `packages` configuration field. 2025-09-08T10:44:19,514 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,514 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,515 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,515 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,515 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,515 If you don't want 'publiforge.Processors.PublidocClean.Xsl' to be distributed and are 2025-09-08T10:44:19,515 already explicitly excluding 'publiforge.Processors.PublidocClean.Xsl' via 2025-09-08T10:44:19,515 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,515 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,515 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,516 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,516 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,516 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,516 even if it does not contain any `.py` files. 2025-09-08T10:44:19,516 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,516 directory, all directories are treated like packages. 2025-09-08T10:44:19,516 ******************************************************************************** 2025-09-08T10:44:19,517 !! 2025-09-08T10:44:19,517 check.warn(importable) 2025-09-08T10:44:19,517 /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-08T10:44:19,517 !! 2025-09-08T10:44:19,517 ******************************************************************************** 2025-09-08T10:44:19,517 ############################ 2025-09-08T10:44:19,517 # Package would be ignored # 2025-09-08T10:44:19,517 ############################ 2025-09-08T10:44:19,517 Python recognizes 'publiforge.Processors.PublidocValid' as an importable package[^1], 2025-09-08T10:44:19,517 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,518 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,518 package, please make sure that 'publiforge.Processors.PublidocValid' is explicitly added 2025-09-08T10:44:19,518 to the `packages` configuration field. 2025-09-08T10:44:19,518 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,518 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,518 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,518 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,518 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,518 If you don't want 'publiforge.Processors.PublidocValid' to be distributed and are 2025-09-08T10:44:19,519 already explicitly excluding 'publiforge.Processors.PublidocValid' via 2025-09-08T10:44:19,519 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,519 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,519 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,519 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,519 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,519 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,519 even if it does not contain any `.py` files. 2025-09-08T10:44:19,520 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,520 directory, all directories are treated like packages. 2025-09-08T10:44:19,520 ******************************************************************************** 2025-09-08T10:44:19,520 !! 2025-09-08T10:44:19,520 check.warn(importable) 2025-09-08T10:44:19,520 /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-08T10:44:19,520 !! 2025-09-08T10:44:19,520 ******************************************************************************** 2025-09-08T10:44:19,520 ############################ 2025-09-08T10:44:19,520 # Package would be ignored # 2025-09-08T10:44:19,521 ############################ 2025-09-08T10:44:19,521 Python recognizes 'publiforge.Processors.PublidocValid.RelaxNG' as an importable package[^1], 2025-09-08T10:44:19,521 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,521 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,521 package, please make sure that 'publiforge.Processors.PublidocValid.RelaxNG' is explicitly added 2025-09-08T10:44:19,521 to the `packages` configuration field. 2025-09-08T10:44:19,521 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,521 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,521 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,522 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,522 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,522 If you don't want 'publiforge.Processors.PublidocValid.RelaxNG' to be distributed and are 2025-09-08T10:44:19,522 already explicitly excluding 'publiforge.Processors.PublidocValid.RelaxNG' via 2025-09-08T10:44:19,522 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,522 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,522 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,522 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,523 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,523 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,523 even if it does not contain any `.py` files. 2025-09-08T10:44:19,523 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,523 directory, all directories are treated like packages. 2025-09-08T10:44:19,523 ******************************************************************************** 2025-09-08T10:44:19,523 !! 2025-09-08T10:44:19,523 check.warn(importable) 2025-09-08T10:44:19,523 /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-08T10:44:19,523 !! 2025-09-08T10:44:19,524 ******************************************************************************** 2025-09-08T10:44:19,524 ############################ 2025-09-08T10:44:19,524 # Package would be ignored # 2025-09-08T10:44:19,524 ############################ 2025-09-08T10:44:19,524 Python recognizes 'publiforge.Processors.Publiquiz2EPub3' as an importable package[^1], 2025-09-08T10:44:19,524 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,524 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,524 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3' is explicitly added 2025-09-08T10:44:19,524 to the `packages` configuration field. 2025-09-08T10:44:19,525 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,525 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,525 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,525 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,525 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,525 If you don't want 'publiforge.Processors.Publiquiz2EPub3' to be distributed and are 2025-09-08T10:44:19,525 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3' via 2025-09-08T10:44:19,525 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,525 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,526 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,526 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,526 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,526 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,526 even if it does not contain any `.py` files. 2025-09-08T10:44:19,526 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,526 directory, all directories are treated like packages. 2025-09-08T10:44:19,526 ******************************************************************************** 2025-09-08T10:44:19,527 !! 2025-09-08T10:44:19,527 check.warn(importable) 2025-09-08T10:44:19,527 /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-08T10:44:19,527 !! 2025-09-08T10:44:19,527 ******************************************************************************** 2025-09-08T10:44:19,527 ############################ 2025-09-08T10:44:19,527 # Package would be ignored # 2025-09-08T10:44:19,527 ############################ 2025-09-08T10:44:19,527 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Variables' as an importable package[^1], 2025-09-08T10:44:19,527 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,528 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,528 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Variables' is explicitly added 2025-09-08T10:44:19,528 to the `packages` configuration field. 2025-09-08T10:44:19,528 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,528 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,528 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,528 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,528 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,529 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Variables' to be distributed and are 2025-09-08T10:44:19,529 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Variables' via 2025-09-08T10:44:19,529 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,529 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,529 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,529 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,529 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,530 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,530 even if it does not contain any `.py` files. 2025-09-08T10:44:19,530 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,530 directory, all directories are treated like packages. 2025-09-08T10:44:19,530 ******************************************************************************** 2025-09-08T10:44:19,530 !! 2025-09-08T10:44:19,530 check.warn(importable) 2025-09-08T10:44:19,530 /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-08T10:44:19,530 !! 2025-09-08T10:44:19,531 ******************************************************************************** 2025-09-08T10:44:19,531 ############################ 2025-09-08T10:44:19,531 # Package would be ignored # 2025-09-08T10:44:19,531 ############################ 2025-09-08T10:44:19,531 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Xsl' as an importable package[^1], 2025-09-08T10:44:19,531 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,531 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,531 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Xsl' is explicitly added 2025-09-08T10:44:19,531 to the `packages` configuration field. 2025-09-08T10:44:19,531 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,532 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,532 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,532 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,532 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,532 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Xsl' to be distributed and are 2025-09-08T10:44:19,532 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Xsl' via 2025-09-08T10:44:19,532 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,532 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,532 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,533 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,533 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,533 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,533 even if it does not contain any `.py` files. 2025-09-08T10:44:19,533 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,533 directory, all directories are treated like packages. 2025-09-08T10:44:19,533 ******************************************************************************** 2025-09-08T10:44:19,533 !! 2025-09-08T10:44:19,534 check.warn(importable) 2025-09-08T10:44:19,534 /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-08T10:44:19,534 !! 2025-09-08T10:44:19,534 ******************************************************************************** 2025-09-08T10:44:19,534 ############################ 2025-09-08T10:44:19,534 # Package would be ignored # 2025-09-08T10:44:19,534 ############################ 2025-09-08T10:44:19,534 Python recognizes 'publiforge.Processors.Publiquiz2Html5' as an importable package[^1], 2025-09-08T10:44:19,534 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,534 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,535 package, please make sure that 'publiforge.Processors.Publiquiz2Html5' is explicitly added 2025-09-08T10:44:19,535 to the `packages` configuration field. 2025-09-08T10:44:19,535 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,535 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,535 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,535 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,535 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,535 If you don't want 'publiforge.Processors.Publiquiz2Html5' to be distributed and are 2025-09-08T10:44:19,536 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5' via 2025-09-08T10:44:19,536 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,536 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,536 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,536 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,536 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,536 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,536 even if it does not contain any `.py` files. 2025-09-08T10:44:19,536 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,537 directory, all directories are treated like packages. 2025-09-08T10:44:19,537 ******************************************************************************** 2025-09-08T10:44:19,537 !! 2025-09-08T10:44:19,537 check.warn(importable) 2025-09-08T10:44:19,537 /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-08T10:44:19,537 !! 2025-09-08T10:44:19,537 ******************************************************************************** 2025-09-08T10:44:19,537 ############################ 2025-09-08T10:44:19,537 # Package would be ignored # 2025-09-08T10:44:19,537 ############################ 2025-09-08T10:44:19,538 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Scss' as an importable package[^1], 2025-09-08T10:44:19,538 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,538 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,538 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Scss' is explicitly added 2025-09-08T10:44:19,538 to the `packages` configuration field. 2025-09-08T10:44:19,538 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,538 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,538 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,538 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,539 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,539 If you don't want 'publiforge.Processors.Publiquiz2Html5.Scss' to be distributed and are 2025-09-08T10:44:19,539 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Scss' via 2025-09-08T10:44:19,539 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,539 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,539 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,539 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,539 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,540 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,540 even if it does not contain any `.py` files. 2025-09-08T10:44:19,540 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,540 directory, all directories are treated like packages. 2025-09-08T10:44:19,540 ******************************************************************************** 2025-09-08T10:44:19,540 !! 2025-09-08T10:44:19,540 check.warn(importable) 2025-09-08T10:44:19,540 /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-08T10:44:19,540 !! 2025-09-08T10:44:19,540 ******************************************************************************** 2025-09-08T10:44:19,541 ############################ 2025-09-08T10:44:19,541 # Package would be ignored # 2025-09-08T10:44:19,541 ############################ 2025-09-08T10:44:19,541 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Css' as an importable package[^1], 2025-09-08T10:44:19,541 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,541 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,541 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Css' is explicitly added 2025-09-08T10:44:19,541 to the `packages` configuration field. 2025-09-08T10:44:19,541 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,542 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,542 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,542 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,542 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,542 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Css' to be distributed and are 2025-09-08T10:44:19,542 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Css' via 2025-09-08T10:44:19,542 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,542 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,542 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,543 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,543 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,543 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,543 even if it does not contain any `.py` files. 2025-09-08T10:44:19,543 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,543 directory, all directories are treated like packages. 2025-09-08T10:44:19,543 ******************************************************************************** 2025-09-08T10:44:19,544 !! 2025-09-08T10:44:19,544 check.warn(importable) 2025-09-08T10:44:19,544 /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-08T10:44:19,544 !! 2025-09-08T10:44:19,544 ******************************************************************************** 2025-09-08T10:44:19,544 ############################ 2025-09-08T10:44:19,544 # Package would be ignored # 2025-09-08T10:44:19,544 ############################ 2025-09-08T10:44:19,544 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' as an importable package[^1], 2025-09-08T10:44:19,544 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,545 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,545 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' is explicitly added 2025-09-08T10:44:19,545 to the `packages` configuration field. 2025-09-08T10:44:19,545 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,545 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,545 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,545 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,545 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,546 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' to be distributed and are 2025-09-08T10:44:19,546 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' via 2025-09-08T10:44:19,546 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,546 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,546 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,546 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,546 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,546 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,547 even if it does not contain any `.py` files. 2025-09-08T10:44:19,547 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,547 directory, all directories are treated like packages. 2025-09-08T10:44:19,547 ******************************************************************************** 2025-09-08T10:44:19,547 !! 2025-09-08T10:44:19,547 check.warn(importable) 2025-09-08T10:44:19,547 /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-08T10:44:19,547 !! 2025-09-08T10:44:19,547 ******************************************************************************** 2025-09-08T10:44:19,547 ############################ 2025-09-08T10:44:19,548 # Package would be ignored # 2025-09-08T10:44:19,548 ############################ 2025-09-08T10:44:19,548 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Images' as an importable package[^1], 2025-09-08T10:44:19,548 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,548 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,548 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Images' is explicitly added 2025-09-08T10:44:19,548 to the `packages` configuration field. 2025-09-08T10:44:19,548 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,548 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,548 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,549 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,549 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,549 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Images' to be distributed and are 2025-09-08T10:44:19,549 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Images' via 2025-09-08T10:44:19,549 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,549 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,549 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,549 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,550 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,550 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,550 even if it does not contain any `.py` files. 2025-09-08T10:44:19,550 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,550 directory, all directories are treated like packages. 2025-09-08T10:44:19,550 ******************************************************************************** 2025-09-08T10:44:19,550 !! 2025-09-08T10:44:19,550 check.warn(importable) 2025-09-08T10:44:19,550 /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-08T10:44:19,550 !! 2025-09-08T10:44:19,551 ******************************************************************************** 2025-09-08T10:44:19,551 ############################ 2025-09-08T10:44:19,551 # Package would be ignored # 2025-09-08T10:44:19,551 ############################ 2025-09-08T10:44:19,551 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Js' as an importable package[^1], 2025-09-08T10:44:19,551 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,551 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,551 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Js' is explicitly added 2025-09-08T10:44:19,551 to the `packages` configuration field. 2025-09-08T10:44:19,552 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,552 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,552 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,552 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,552 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,552 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Js' to be distributed and are 2025-09-08T10:44:19,552 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Js' via 2025-09-08T10:44:19,552 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,552 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,553 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,553 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,553 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,553 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,553 even if it does not contain any `.py` files. 2025-09-08T10:44:19,553 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,553 directory, all directories are treated like packages. 2025-09-08T10:44:19,553 ******************************************************************************** 2025-09-08T10:44:19,554 !! 2025-09-08T10:44:19,554 check.warn(importable) 2025-09-08T10:44:19,554 /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-08T10:44:19,554 !! 2025-09-08T10:44:19,554 ******************************************************************************** 2025-09-08T10:44:19,554 ############################ 2025-09-08T10:44:19,554 # Package would be ignored # 2025-09-08T10:44:19,554 ############################ 2025-09-08T10:44:19,554 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Variables' as an importable package[^1], 2025-09-08T10:44:19,555 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,555 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,555 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Variables' is explicitly added 2025-09-08T10:44:19,555 to the `packages` configuration field. 2025-09-08T10:44:19,555 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,555 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,555 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,555 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,556 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,556 If you don't want 'publiforge.Processors.Publiquiz2Html5.Variables' to be distributed and are 2025-09-08T10:44:19,556 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Variables' via 2025-09-08T10:44:19,556 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,556 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,556 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,556 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,556 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,557 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,557 even if it does not contain any `.py` files. 2025-09-08T10:44:19,557 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,557 directory, all directories are treated like packages. 2025-09-08T10:44:19,557 ******************************************************************************** 2025-09-08T10:44:19,557 !! 2025-09-08T10:44:19,557 check.warn(importable) 2025-09-08T10:44:19,557 /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-08T10:44:19,557 !! 2025-09-08T10:44:19,557 ******************************************************************************** 2025-09-08T10:44:19,558 ############################ 2025-09-08T10:44:19,558 # Package would be ignored # 2025-09-08T10:44:19,558 ############################ 2025-09-08T10:44:19,558 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Xsl' as an importable package[^1], 2025-09-08T10:44:19,558 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,558 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,558 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Xsl' is explicitly added 2025-09-08T10:44:19,558 to the `packages` configuration field. 2025-09-08T10:44:19,558 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,558 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,559 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,559 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,559 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,559 If you don't want 'publiforge.Processors.Publiquiz2Html5.Xsl' to be distributed and are 2025-09-08T10:44:19,559 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Xsl' via 2025-09-08T10:44:19,559 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,559 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,559 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,559 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,560 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,560 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,560 even if it does not contain any `.py` files. 2025-09-08T10:44:19,560 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,560 directory, all directories are treated like packages. 2025-09-08T10:44:19,560 ******************************************************************************** 2025-09-08T10:44:19,560 !! 2025-09-08T10:44:19,560 check.warn(importable) 2025-09-08T10:44:19,561 /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-08T10:44:19,561 !! 2025-09-08T10:44:19,561 ******************************************************************************** 2025-09-08T10:44:19,561 ############################ 2025-09-08T10:44:19,561 # Package would be ignored # 2025-09-08T10:44:19,561 ############################ 2025-09-08T10:44:19,561 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12' as an importable package[^1], 2025-09-08T10:44:19,561 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,561 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,561 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12' is explicitly added 2025-09-08T10:44:19,561 to the `packages` configuration field. 2025-09-08T10:44:19,562 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,562 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,562 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,562 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,562 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,562 If you don't want 'publiforge.Processors.Publiquiz2Scorm12' to be distributed and are 2025-09-08T10:44:19,562 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12' via 2025-09-08T10:44:19,562 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,563 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,563 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,563 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,563 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,563 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,563 even if it does not contain any `.py` files. 2025-09-08T10:44:19,563 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,563 directory, all directories are treated like packages. 2025-09-08T10:44:19,564 ******************************************************************************** 2025-09-08T10:44:19,564 !! 2025-09-08T10:44:19,564 check.warn(importable) 2025-09-08T10:44:19,564 /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-08T10:44:19,564 !! 2025-09-08T10:44:19,564 ******************************************************************************** 2025-09-08T10:44:19,564 ############################ 2025-09-08T10:44:19,564 # Package would be ignored # 2025-09-08T10:44:19,564 ############################ 2025-09-08T10:44:19,564 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates' as an importable package[^1], 2025-09-08T10:44:19,565 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,565 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,565 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates' is explicitly added 2025-09-08T10:44:19,565 to the `packages` configuration field. 2025-09-08T10:44:19,565 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,565 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,565 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,565 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,565 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,566 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates' to be distributed and are 2025-09-08T10:44:19,566 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates' via 2025-09-08T10:44:19,566 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,566 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,566 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,566 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,566 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,567 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,567 even if it does not contain any `.py` files. 2025-09-08T10:44:19,567 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,567 directory, all directories are treated like packages. 2025-09-08T10:44:19,567 ******************************************************************************** 2025-09-08T10:44:19,567 !! 2025-09-08T10:44:19,567 check.warn(importable) 2025-09-08T10:44:19,567 /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-08T10:44:19,567 !! 2025-09-08T10:44:19,568 ******************************************************************************** 2025-09-08T10:44:19,568 ############################ 2025-09-08T10:44:19,568 # Package would be ignored # 2025-09-08T10:44:19,568 ############################ 2025-09-08T10:44:19,568 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' as an importable package[^1], 2025-09-08T10:44:19,568 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,568 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,568 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' is explicitly added 2025-09-08T10:44:19,568 to the `packages` configuration field. 2025-09-08T10:44:19,568 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,569 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,569 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,569 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,569 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,569 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' to be distributed and are 2025-09-08T10:44:19,569 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' via 2025-09-08T10:44:19,569 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,569 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,569 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,570 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,570 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,570 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,570 even if it does not contain any `.py` files. 2025-09-08T10:44:19,570 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,570 directory, all directories are treated like packages. 2025-09-08T10:44:19,570 ******************************************************************************** 2025-09-08T10:44:19,570 !! 2025-09-08T10:44:19,571 check.warn(importable) 2025-09-08T10:44:19,571 /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-08T10:44:19,571 !! 2025-09-08T10:44:19,571 ******************************************************************************** 2025-09-08T10:44:19,571 ############################ 2025-09-08T10:44:19,571 # Package would be ignored # 2025-09-08T10:44:19,571 ############################ 2025-09-08T10:44:19,571 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' as an importable package[^1], 2025-09-08T10:44:19,571 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,571 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,572 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' is explicitly added 2025-09-08T10:44:19,572 to the `packages` configuration field. 2025-09-08T10:44:19,572 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,572 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,572 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,572 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,572 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,572 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' to be distributed and are 2025-09-08T10:44:19,573 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' via 2025-09-08T10:44:19,573 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,573 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,573 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,573 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,573 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,573 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,573 even if it does not contain any `.py` files. 2025-09-08T10:44:19,573 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,574 directory, all directories are treated like packages. 2025-09-08T10:44:19,574 ******************************************************************************** 2025-09-08T10:44:19,574 !! 2025-09-08T10:44:19,574 check.warn(importable) 2025-09-08T10:44:19,574 /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-08T10:44:19,574 !! 2025-09-08T10:44:19,574 ******************************************************************************** 2025-09-08T10:44:19,574 ############################ 2025-09-08T10:44:19,574 # Package would be ignored # 2025-09-08T10:44:19,574 ############################ 2025-09-08T10:44:19,575 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' as an importable package[^1], 2025-09-08T10:44:19,575 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,575 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,575 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' is explicitly added 2025-09-08T10:44:19,575 to the `packages` configuration field. 2025-09-08T10:44:19,575 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,575 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,575 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,575 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,576 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,576 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' to be distributed and are 2025-09-08T10:44:19,576 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' via 2025-09-08T10:44:19,576 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,576 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,576 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,576 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,576 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,577 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,577 even if it does not contain any `.py` files. 2025-09-08T10:44:19,577 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,577 directory, all directories are treated like packages. 2025-09-08T10:44:19,577 ******************************************************************************** 2025-09-08T10:44:19,577 !! 2025-09-08T10:44:19,577 check.warn(importable) 2025-09-08T10:44:19,577 /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-08T10:44:19,577 !! 2025-09-08T10:44:19,578 ******************************************************************************** 2025-09-08T10:44:19,578 ############################ 2025-09-08T10:44:19,578 # Package would be ignored # 2025-09-08T10:44:19,578 ############################ 2025-09-08T10:44:19,578 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Variables' as an importable package[^1], 2025-09-08T10:44:19,578 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,578 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,578 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Variables' is explicitly added 2025-09-08T10:44:19,578 to the `packages` configuration field. 2025-09-08T10:44:19,578 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,578 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,579 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,579 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,579 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,579 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Variables' to be distributed and are 2025-09-08T10:44:19,579 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Variables' via 2025-09-08T10:44:19,579 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,579 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,580 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,580 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,580 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,580 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,580 even if it does not contain any `.py` files. 2025-09-08T10:44:19,580 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,580 directory, all directories are treated like packages. 2025-09-08T10:44:19,580 ******************************************************************************** 2025-09-08T10:44:19,581 !! 2025-09-08T10:44:19,581 check.warn(importable) 2025-09-08T10:44:19,581 /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-08T10:44:19,581 !! 2025-09-08T10:44:19,581 ******************************************************************************** 2025-09-08T10:44:19,581 ############################ 2025-09-08T10:44:19,581 # Package would be ignored # 2025-09-08T10:44:19,581 ############################ 2025-09-08T10:44:19,581 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Xsl' as an importable package[^1], 2025-09-08T10:44:19,581 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,582 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,582 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Xsl' is explicitly added 2025-09-08T10:44:19,582 to the `packages` configuration field. 2025-09-08T10:44:19,582 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,582 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,582 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,582 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,582 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,583 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Xsl' to be distributed and are 2025-09-08T10:44:19,583 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Xsl' via 2025-09-08T10:44:19,583 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,583 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,583 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,583 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,583 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,583 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,584 even if it does not contain any `.py` files. 2025-09-08T10:44:19,584 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,584 directory, all directories are treated like packages. 2025-09-08T10:44:19,584 ******************************************************************************** 2025-09-08T10:44:19,584 !! 2025-09-08T10:44:19,584 check.warn(importable) 2025-09-08T10:44:19,584 /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-08T10:44:19,584 !! 2025-09-08T10:44:19,584 ******************************************************************************** 2025-09-08T10:44:19,584 ############################ 2025-09-08T10:44:19,584 # Package would be ignored # 2025-09-08T10:44:19,585 ############################ 2025-09-08T10:44:19,585 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004' as an importable package[^1], 2025-09-08T10:44:19,585 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,585 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,585 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004' is explicitly added 2025-09-08T10:44:19,585 to the `packages` configuration field. 2025-09-08T10:44:19,585 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,585 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,585 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,586 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,586 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,586 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004' to be distributed and are 2025-09-08T10:44:19,586 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004' via 2025-09-08T10:44:19,586 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,586 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,586 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,586 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,587 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,587 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,587 even if it does not contain any `.py` files. 2025-09-08T10:44:19,587 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,587 directory, all directories are treated like packages. 2025-09-08T10:44:19,587 ******************************************************************************** 2025-09-08T10:44:19,587 !! 2025-09-08T10:44:19,587 check.warn(importable) 2025-09-08T10:44:19,587 /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-08T10:44:19,587 !! 2025-09-08T10:44:19,588 ******************************************************************************** 2025-09-08T10:44:19,588 ############################ 2025-09-08T10:44:19,588 # Package would be ignored # 2025-09-08T10:44:19,588 ############################ 2025-09-08T10:44:19,588 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates' as an importable package[^1], 2025-09-08T10:44:19,588 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,588 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,588 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates' is explicitly added 2025-09-08T10:44:19,588 to the `packages` configuration field. 2025-09-08T10:44:19,589 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,589 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,589 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,589 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,589 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,589 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates' to be distributed and are 2025-09-08T10:44:19,589 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates' via 2025-09-08T10:44:19,589 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,589 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,590 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,590 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,590 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,590 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,590 even if it does not contain any `.py` files. 2025-09-08T10:44:19,590 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,590 directory, all directories are treated like packages. 2025-09-08T10:44:19,590 ******************************************************************************** 2025-09-08T10:44:19,591 !! 2025-09-08T10:44:19,591 check.warn(importable) 2025-09-08T10:44:19,591 /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-08T10:44:19,591 !! 2025-09-08T10:44:19,591 ******************************************************************************** 2025-09-08T10:44:19,591 ############################ 2025-09-08T10:44:19,591 # Package would be ignored # 2025-09-08T10:44:19,591 ############################ 2025-09-08T10:44:19,591 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' as an importable package[^1], 2025-09-08T10:44:19,591 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,592 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,592 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' is explicitly added 2025-09-08T10:44:19,592 to the `packages` configuration field. 2025-09-08T10:44:19,592 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,592 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,592 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,592 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,593 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,593 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' to be distributed and are 2025-09-08T10:44:19,593 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' via 2025-09-08T10:44:19,593 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,593 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,593 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,593 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,593 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,594 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,594 even if it does not contain any `.py` files. 2025-09-08T10:44:19,594 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,594 directory, all directories are treated like packages. 2025-09-08T10:44:19,594 ******************************************************************************** 2025-09-08T10:44:19,594 !! 2025-09-08T10:44:19,594 check.warn(importable) 2025-09-08T10:44:19,594 /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-08T10:44:19,594 !! 2025-09-08T10:44:19,595 ******************************************************************************** 2025-09-08T10:44:19,595 ############################ 2025-09-08T10:44:19,595 # Package would be ignored # 2025-09-08T10:44:19,595 ############################ 2025-09-08T10:44:19,595 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' as an importable package[^1], 2025-09-08T10:44:19,595 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,595 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,595 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' is explicitly added 2025-09-08T10:44:19,595 to the `packages` configuration field. 2025-09-08T10:44:19,596 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,596 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,596 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,596 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,596 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,596 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' to be distributed and are 2025-09-08T10:44:19,596 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' via 2025-09-08T10:44:19,596 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,596 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,597 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,597 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,597 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,597 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,597 even if it does not contain any `.py` files. 2025-09-08T10:44:19,597 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,597 directory, all directories are treated like packages. 2025-09-08T10:44:19,597 ******************************************************************************** 2025-09-08T10:44:19,598 !! 2025-09-08T10:44:19,598 check.warn(importable) 2025-09-08T10:44:19,598 /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-08T10:44:19,598 !! 2025-09-08T10:44:19,598 ******************************************************************************** 2025-09-08T10:44:19,598 ############################ 2025-09-08T10:44:19,598 # Package would be ignored # 2025-09-08T10:44:19,598 ############################ 2025-09-08T10:44:19,598 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' as an importable package[^1], 2025-09-08T10:44:19,598 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,599 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,599 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' is explicitly added 2025-09-08T10:44:19,599 to the `packages` configuration field. 2025-09-08T10:44:19,599 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,599 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,599 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,599 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,599 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,600 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' to be distributed and are 2025-09-08T10:44:19,600 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' via 2025-09-08T10:44:19,600 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,600 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,600 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,600 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,600 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,601 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,601 even if it does not contain any `.py` files. 2025-09-08T10:44:19,601 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,601 directory, all directories are treated like packages. 2025-09-08T10:44:19,601 ******************************************************************************** 2025-09-08T10:44:19,601 !! 2025-09-08T10:44:19,601 check.warn(importable) 2025-09-08T10:44:19,601 /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-08T10:44:19,601 !! 2025-09-08T10:44:19,601 ******************************************************************************** 2025-09-08T10:44:19,602 ############################ 2025-09-08T10:44:19,602 # Package would be ignored # 2025-09-08T10:44:19,602 ############################ 2025-09-08T10:44:19,602 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' as an importable package[^1], 2025-09-08T10:44:19,602 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,602 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,602 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' is explicitly added 2025-09-08T10:44:19,602 to the `packages` configuration field. 2025-09-08T10:44:19,602 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,602 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,603 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,603 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,603 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,603 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' to be distributed and are 2025-09-08T10:44:19,603 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' via 2025-09-08T10:44:19,603 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,603 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,603 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,604 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,604 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,604 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,604 even if it does not contain any `.py` files. 2025-09-08T10:44:19,604 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,604 directory, all directories are treated like packages. 2025-09-08T10:44:19,604 ******************************************************************************** 2025-09-08T10:44:19,605 !! 2025-09-08T10:44:19,605 check.warn(importable) 2025-09-08T10:44:19,605 /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-08T10:44:19,605 !! 2025-09-08T10:44:19,605 ******************************************************************************** 2025-09-08T10:44:19,605 ############################ 2025-09-08T10:44:19,605 # Package would be ignored # 2025-09-08T10:44:19,605 ############################ 2025-09-08T10:44:19,605 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' as an importable package[^1], 2025-09-08T10:44:19,605 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,606 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,606 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' is explicitly added 2025-09-08T10:44:19,606 to the `packages` configuration field. 2025-09-08T10:44:19,606 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,606 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,606 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,606 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,606 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,607 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' to be distributed and are 2025-09-08T10:44:19,607 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' via 2025-09-08T10:44:19,607 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,607 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,607 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,607 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,607 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,607 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,608 even if it does not contain any `.py` files. 2025-09-08T10:44:19,608 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,608 directory, all directories are treated like packages. 2025-09-08T10:44:19,608 ******************************************************************************** 2025-09-08T10:44:19,608 !! 2025-09-08T10:44:19,608 check.warn(importable) 2025-09-08T10:44:19,608 /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-08T10:44:19,608 !! 2025-09-08T10:44:19,608 ******************************************************************************** 2025-09-08T10:44:19,608 ############################ 2025-09-08T10:44:19,609 # Package would be ignored # 2025-09-08T10:44:19,609 ############################ 2025-09-08T10:44:19,609 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' as an importable package[^1], 2025-09-08T10:44:19,609 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,609 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,609 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' is explicitly added 2025-09-08T10:44:19,609 to the `packages` configuration field. 2025-09-08T10:44:19,609 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,609 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,609 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,610 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,610 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,610 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' to be distributed and are 2025-09-08T10:44:19,610 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' via 2025-09-08T10:44:19,610 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,610 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,610 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,610 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,611 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,611 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,611 even if it does not contain any `.py` files. 2025-09-08T10:44:19,611 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,611 directory, all directories are treated like packages. 2025-09-08T10:44:19,611 ******************************************************************************** 2025-09-08T10:44:19,611 !! 2025-09-08T10:44:19,611 check.warn(importable) 2025-09-08T10:44:19,612 /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-08T10:44:19,612 !! 2025-09-08T10:44:19,612 ******************************************************************************** 2025-09-08T10:44:19,612 ############################ 2025-09-08T10:44:19,612 # Package would be ignored # 2025-09-08T10:44:19,612 ############################ 2025-09-08T10:44:19,612 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Variables' as an importable package[^1], 2025-09-08T10:44:19,612 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,612 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,612 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Variables' is explicitly added 2025-09-08T10:44:19,613 to the `packages` configuration field. 2025-09-08T10:44:19,613 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,613 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,613 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,613 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,613 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,613 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Variables' to be distributed and are 2025-09-08T10:44:19,613 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Variables' via 2025-09-08T10:44:19,614 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,614 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,614 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,614 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,614 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,614 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,614 even if it does not contain any `.py` files. 2025-09-08T10:44:19,614 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,615 directory, all directories are treated like packages. 2025-09-08T10:44:19,615 ******************************************************************************** 2025-09-08T10:44:19,615 !! 2025-09-08T10:44:19,615 check.warn(importable) 2025-09-08T10:44:19,615 /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-08T10:44:19,615 !! 2025-09-08T10:44:19,615 ******************************************************************************** 2025-09-08T10:44:19,615 ############################ 2025-09-08T10:44:19,615 # Package would be ignored # 2025-09-08T10:44:19,615 ############################ 2025-09-08T10:44:19,616 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' as an importable package[^1], 2025-09-08T10:44:19,616 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,616 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,616 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' is explicitly added 2025-09-08T10:44:19,616 to the `packages` configuration field. 2025-09-08T10:44:19,616 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,616 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,616 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,616 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,617 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,617 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' to be distributed and are 2025-09-08T10:44:19,617 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' via 2025-09-08T10:44:19,617 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,617 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,617 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,617 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,618 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,618 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,618 even if it does not contain any `.py` files. 2025-09-08T10:44:19,618 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,618 directory, all directories are treated like packages. 2025-09-08T10:44:19,618 ******************************************************************************** 2025-09-08T10:44:19,618 !! 2025-09-08T10:44:19,618 check.warn(importable) 2025-09-08T10:44:19,618 /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-08T10:44:19,619 !! 2025-09-08T10:44:19,619 ******************************************************************************** 2025-09-08T10:44:19,619 ############################ 2025-09-08T10:44:19,619 # Package would be ignored # 2025-09-08T10:44:19,619 ############################ 2025-09-08T10:44:19,619 Python recognizes 'publiforge.Processors.Publiset2Publidoc' as an importable package[^1], 2025-09-08T10:44:19,619 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,619 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,619 package, please make sure that 'publiforge.Processors.Publiset2Publidoc' is explicitly added 2025-09-08T10:44:19,619 to the `packages` configuration field. 2025-09-08T10:44:19,620 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,620 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,620 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,620 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,620 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,620 If you don't want 'publiforge.Processors.Publiset2Publidoc' to be distributed and are 2025-09-08T10:44:19,620 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc' via 2025-09-08T10:44:19,620 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,621 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,621 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,621 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,621 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,621 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,621 even if it does not contain any `.py` files. 2025-09-08T10:44:19,621 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,622 directory, all directories are treated like packages. 2025-09-08T10:44:19,622 ******************************************************************************** 2025-09-08T10:44:19,622 !! 2025-09-08T10:44:19,622 check.warn(importable) 2025-09-08T10:44:19,622 /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-08T10:44:19,622 !! 2025-09-08T10:44:19,622 ******************************************************************************** 2025-09-08T10:44:19,622 ############################ 2025-09-08T10:44:19,622 # Package would be ignored # 2025-09-08T10:44:19,622 ############################ 2025-09-08T10:44:19,623 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Variables' as an importable package[^1], 2025-09-08T10:44:19,623 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,623 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,623 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Variables' is explicitly added 2025-09-08T10:44:19,623 to the `packages` configuration field. 2025-09-08T10:44:19,623 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,623 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,623 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,623 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,624 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,624 If you don't want 'publiforge.Processors.Publiset2Publidoc.Variables' to be distributed and are 2025-09-08T10:44:19,624 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Variables' via 2025-09-08T10:44:19,624 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,624 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,624 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,624 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,624 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,625 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,625 even if it does not contain any `.py` files. 2025-09-08T10:44:19,625 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,625 directory, all directories are treated like packages. 2025-09-08T10:44:19,625 ******************************************************************************** 2025-09-08T10:44:19,625 !! 2025-09-08T10:44:19,625 check.warn(importable) 2025-09-08T10:44:19,625 /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-08T10:44:19,625 !! 2025-09-08T10:44:19,626 ******************************************************************************** 2025-09-08T10:44:19,626 ############################ 2025-09-08T10:44:19,626 # Package would be ignored # 2025-09-08T10:44:19,626 ############################ 2025-09-08T10:44:19,626 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Xsl' as an importable package[^1], 2025-09-08T10:44:19,626 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,626 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,626 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Xsl' is explicitly added 2025-09-08T10:44:19,626 to the `packages` configuration field. 2025-09-08T10:44:19,627 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,627 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,627 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,627 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,627 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,627 If you don't want 'publiforge.Processors.Publiset2Publidoc.Xsl' to be distributed and are 2025-09-08T10:44:19,627 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Xsl' via 2025-09-08T10:44:19,627 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,627 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,628 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,628 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,628 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,628 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,628 even if it does not contain any `.py` files. 2025-09-08T10:44:19,628 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,628 directory, all directories are treated like packages. 2025-09-08T10:44:19,628 ******************************************************************************** 2025-09-08T10:44:19,629 !! 2025-09-08T10:44:19,629 check.warn(importable) 2025-09-08T10:44:19,629 /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-08T10:44:19,629 !! 2025-09-08T10:44:19,629 ******************************************************************************** 2025-09-08T10:44:19,629 ############################ 2025-09-08T10:44:19,629 # Package would be ignored # 2025-09-08T10:44:19,629 ############################ 2025-09-08T10:44:19,629 Python recognizes 'publiforge.Processors.Publiset4Publidoc' as an importable package[^1], 2025-09-08T10:44:19,629 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,630 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,630 package, please make sure that 'publiforge.Processors.Publiset4Publidoc' is explicitly added 2025-09-08T10:44:19,630 to the `packages` configuration field. 2025-09-08T10:44:19,630 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,630 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,630 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,630 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,631 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,631 If you don't want 'publiforge.Processors.Publiset4Publidoc' to be distributed and are 2025-09-08T10:44:19,631 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc' via 2025-09-08T10:44:19,631 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,631 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,631 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,631 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,631 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,632 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,632 even if it does not contain any `.py` files. 2025-09-08T10:44:19,632 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,632 directory, all directories are treated like packages. 2025-09-08T10:44:19,632 ******************************************************************************** 2025-09-08T10:44:19,632 !! 2025-09-08T10:44:19,632 check.warn(importable) 2025-09-08T10:44:19,632 /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-08T10:44:19,632 !! 2025-09-08T10:44:19,633 ******************************************************************************** 2025-09-08T10:44:19,633 ############################ 2025-09-08T10:44:19,633 # Package would be ignored # 2025-09-08T10:44:19,633 ############################ 2025-09-08T10:44:19,633 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Variables' as an importable package[^1], 2025-09-08T10:44:19,633 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,633 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,633 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Variables' is explicitly added 2025-09-08T10:44:19,633 to the `packages` configuration field. 2025-09-08T10:44:19,634 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,634 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,634 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,634 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,634 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,634 If you don't want 'publiforge.Processors.Publiset4Publidoc.Variables' to be distributed and are 2025-09-08T10:44:19,634 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Variables' via 2025-09-08T10:44:19,634 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,634 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,635 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,635 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,635 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,635 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,635 even if it does not contain any `.py` files. 2025-09-08T10:44:19,635 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,635 directory, all directories are treated like packages. 2025-09-08T10:44:19,635 ******************************************************************************** 2025-09-08T10:44:19,636 !! 2025-09-08T10:44:19,636 check.warn(importable) 2025-09-08T10:44:19,636 /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-08T10:44:19,636 !! 2025-09-08T10:44:19,636 ******************************************************************************** 2025-09-08T10:44:19,636 ############################ 2025-09-08T10:44:19,636 # Package would be ignored # 2025-09-08T10:44:19,636 ############################ 2025-09-08T10:44:19,636 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Xsl' as an importable package[^1], 2025-09-08T10:44:19,636 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,637 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,637 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Xsl' is explicitly added 2025-09-08T10:44:19,637 to the `packages` configuration field. 2025-09-08T10:44:19,637 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,637 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,637 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,637 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,637 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,637 If you don't want 'publiforge.Processors.Publiset4Publidoc.Xsl' to be distributed and are 2025-09-08T10:44:19,638 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Xsl' via 2025-09-08T10:44:19,638 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,638 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,638 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,638 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,638 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,638 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,638 even if it does not contain any `.py` files. 2025-09-08T10:44:19,639 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,639 directory, all directories are treated like packages. 2025-09-08T10:44:19,639 ******************************************************************************** 2025-09-08T10:44:19,639 !! 2025-09-08T10:44:19,639 check.warn(importable) 2025-09-08T10:44:19,639 /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-08T10:44:19,639 !! 2025-09-08T10:44:19,639 ******************************************************************************** 2025-09-08T10:44:19,639 ############################ 2025-09-08T10:44:19,639 # Package would be ignored # 2025-09-08T10:44:19,640 ############################ 2025-09-08T10:44:19,640 Python recognizes 'publiforge.Processors.Publiset4Publiquiz' as an importable package[^1], 2025-09-08T10:44:19,640 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,640 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,640 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz' is explicitly added 2025-09-08T10:44:19,640 to the `packages` configuration field. 2025-09-08T10:44:19,640 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,640 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,640 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,640 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,641 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,641 If you don't want 'publiforge.Processors.Publiset4Publiquiz' to be distributed and are 2025-09-08T10:44:19,641 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz' via 2025-09-08T10:44:19,641 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,641 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,641 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,641 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,641 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,642 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,642 even if it does not contain any `.py` files. 2025-09-08T10:44:19,642 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,642 directory, all directories are treated like packages. 2025-09-08T10:44:19,642 ******************************************************************************** 2025-09-08T10:44:19,642 !! 2025-09-08T10:44:19,642 check.warn(importable) 2025-09-08T10:44:19,642 /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-08T10:44:19,643 !! 2025-09-08T10:44:19,643 ******************************************************************************** 2025-09-08T10:44:19,643 ############################ 2025-09-08T10:44:19,643 # Package would be ignored # 2025-09-08T10:44:19,643 ############################ 2025-09-08T10:44:19,643 Python recognizes 'publiforge.Processors.Publiset4Publiquiz.Xsl' as an importable package[^1], 2025-09-08T10:44:19,643 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,643 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,643 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz.Xsl' is explicitly added 2025-09-08T10:44:19,643 to the `packages` configuration field. 2025-09-08T10:44:19,644 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,644 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,644 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,644 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,644 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,644 If you don't want 'publiforge.Processors.Publiset4Publiquiz.Xsl' to be distributed and are 2025-09-08T10:44:19,644 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz.Xsl' via 2025-09-08T10:44:19,645 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,645 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,645 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,645 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,645 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,645 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,645 even if it does not contain any `.py` files. 2025-09-08T10:44:19,645 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,646 directory, all directories are treated like packages. 2025-09-08T10:44:19,646 ******************************************************************************** 2025-09-08T10:44:19,646 !! 2025-09-08T10:44:19,646 check.warn(importable) 2025-09-08T10:44:19,646 /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-08T10:44:19,646 !! 2025-09-08T10:44:19,646 ******************************************************************************** 2025-09-08T10:44:19,646 ############################ 2025-09-08T10:44:19,646 # Package would be ignored # 2025-09-08T10:44:19,646 ############################ 2025-09-08T10:44:19,646 Python recognizes 'publiforge.RelaxNG' as an importable package[^1], 2025-09-08T10:44:19,647 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,647 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,647 package, please make sure that 'publiforge.RelaxNG' is explicitly added 2025-09-08T10:44:19,647 to the `packages` configuration field. 2025-09-08T10:44:19,647 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,647 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,647 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,647 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,648 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,648 If you don't want 'publiforge.RelaxNG' to be distributed and are 2025-09-08T10:44:19,648 already explicitly excluding 'publiforge.RelaxNG' via 2025-09-08T10:44:19,648 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,648 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,648 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,648 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,648 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,649 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,649 even if it does not contain any `.py` files. 2025-09-08T10:44:19,649 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,649 directory, all directories are treated like packages. 2025-09-08T10:44:19,649 ******************************************************************************** 2025-09-08T10:44:19,649 !! 2025-09-08T10:44:19,649 check.warn(importable) 2025-09-08T10:44:19,649 /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-08T10:44:19,649 !! 2025-09-08T10:44:19,649 ******************************************************************************** 2025-09-08T10:44:19,650 ############################ 2025-09-08T10:44:19,650 # Package would be ignored # 2025-09-08T10:44:19,650 ############################ 2025-09-08T10:44:19,650 Python recognizes 'publiforge.Static' as an importable package[^1], 2025-09-08T10:44:19,650 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,650 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,650 package, please make sure that 'publiforge.Static' is explicitly added 2025-09-08T10:44:19,650 to the `packages` configuration field. 2025-09-08T10:44:19,650 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,650 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,651 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,651 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,651 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,651 If you don't want 'publiforge.Static' to be distributed and are 2025-09-08T10:44:19,651 already explicitly excluding 'publiforge.Static' via 2025-09-08T10:44:19,651 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,651 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,651 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,652 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,652 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,652 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,652 even if it does not contain any `.py` files. 2025-09-08T10:44:19,652 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,652 directory, all directories are treated like packages. 2025-09-08T10:44:19,652 ******************************************************************************** 2025-09-08T10:44:19,652 !! 2025-09-08T10:44:19,653 check.warn(importable) 2025-09-08T10:44:19,653 /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-08T10:44:19,653 !! 2025-09-08T10:44:19,653 ******************************************************************************** 2025-09-08T10:44:19,653 ############################ 2025-09-08T10:44:19,653 # Package would be ignored # 2025-09-08T10:44:19,653 ############################ 2025-09-08T10:44:19,653 Python recognizes 'publiforge.Static.Css' as an importable package[^1], 2025-09-08T10:44:19,653 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,653 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,653 package, please make sure that 'publiforge.Static.Css' is explicitly added 2025-09-08T10:44:19,654 to the `packages` configuration field. 2025-09-08T10:44:19,654 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,654 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,654 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,654 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,654 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,654 If you don't want 'publiforge.Static.Css' to be distributed and are 2025-09-08T10:44:19,654 already explicitly excluding 'publiforge.Static.Css' via 2025-09-08T10:44:19,655 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,655 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,655 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,655 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,655 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,655 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,655 even if it does not contain any `.py` files. 2025-09-08T10:44:19,655 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,655 directory, all directories are treated like packages. 2025-09-08T10:44:19,656 ******************************************************************************** 2025-09-08T10:44:19,656 !! 2025-09-08T10:44:19,656 check.warn(importable) 2025-09-08T10:44:19,656 /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-08T10:44:19,656 !! 2025-09-08T10:44:19,656 ******************************************************************************** 2025-09-08T10:44:19,656 ############################ 2025-09-08T10:44:19,656 # Package would be ignored # 2025-09-08T10:44:19,656 ############################ 2025-09-08T10:44:19,657 Python recognizes 'publiforge.Static.Images' as an importable package[^1], 2025-09-08T10:44:19,657 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,657 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,657 package, please make sure that 'publiforge.Static.Images' is explicitly added 2025-09-08T10:44:19,657 to the `packages` configuration field. 2025-09-08T10:44:19,657 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,657 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,657 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,658 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,658 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,658 If you don't want 'publiforge.Static.Images' to be distributed and are 2025-09-08T10:44:19,658 already explicitly excluding 'publiforge.Static.Images' via 2025-09-08T10:44:19,658 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,658 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,658 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,658 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,659 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,659 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,659 even if it does not contain any `.py` files. 2025-09-08T10:44:19,659 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,659 directory, all directories are treated like packages. 2025-09-08T10:44:19,659 ******************************************************************************** 2025-09-08T10:44:19,659 !! 2025-09-08T10:44:19,659 check.warn(importable) 2025-09-08T10:44:19,659 /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-08T10:44:19,660 !! 2025-09-08T10:44:19,660 ******************************************************************************** 2025-09-08T10:44:19,660 ############################ 2025-09-08T10:44:19,660 # Package would be ignored # 2025-09-08T10:44:19,660 ############################ 2025-09-08T10:44:19,660 Python recognizes 'publiforge.Static.Images.MimeTypes' as an importable package[^1], 2025-09-08T10:44:19,660 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,660 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,660 package, please make sure that 'publiforge.Static.Images.MimeTypes' is explicitly added 2025-09-08T10:44:19,660 to the `packages` configuration field. 2025-09-08T10:44:19,661 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,661 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,661 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,661 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,661 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,661 If you don't want 'publiforge.Static.Images.MimeTypes' to be distributed and are 2025-09-08T10:44:19,661 already explicitly excluding 'publiforge.Static.Images.MimeTypes' via 2025-09-08T10:44:19,661 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,662 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,662 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,662 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,662 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,662 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,662 even if it does not contain any `.py` files. 2025-09-08T10:44:19,662 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,662 directory, all directories are treated like packages. 2025-09-08T10:44:19,663 ******************************************************************************** 2025-09-08T10:44:19,663 !! 2025-09-08T10:44:19,663 check.warn(importable) 2025-09-08T10:44:19,663 /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-08T10:44:19,663 !! 2025-09-08T10:44:19,663 ******************************************************************************** 2025-09-08T10:44:19,663 ############################ 2025-09-08T10:44:19,663 # Package would be ignored # 2025-09-08T10:44:19,663 ############################ 2025-09-08T10:44:19,663 Python recognizes 'publiforge.Static.Js' as an importable package[^1], 2025-09-08T10:44:19,664 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,664 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,664 package, please make sure that 'publiforge.Static.Js' is explicitly added 2025-09-08T10:44:19,664 to the `packages` configuration field. 2025-09-08T10:44:19,664 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,664 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,664 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,664 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,665 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,665 If you don't want 'publiforge.Static.Js' to be distributed and are 2025-09-08T10:44:19,665 already explicitly excluding 'publiforge.Static.Js' via 2025-09-08T10:44:19,665 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,665 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,665 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,665 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,665 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,666 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,666 even if it does not contain any `.py` files. 2025-09-08T10:44:19,666 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,666 directory, all directories are treated like packages. 2025-09-08T10:44:19,666 ******************************************************************************** 2025-09-08T10:44:19,666 !! 2025-09-08T10:44:19,666 check.warn(importable) 2025-09-08T10:44:19,666 /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-08T10:44:19,666 !! 2025-09-08T10:44:19,667 ******************************************************************************** 2025-09-08T10:44:19,667 ############################ 2025-09-08T10:44:19,667 # Package would be ignored # 2025-09-08T10:44:19,667 ############################ 2025-09-08T10:44:19,667 Python recognizes 'publiforge.Static.Js.Tests' as an importable package[^1], 2025-09-08T10:44:19,667 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,667 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,667 package, please make sure that 'publiforge.Static.Js.Tests' is explicitly added 2025-09-08T10:44:19,667 to the `packages` configuration field. 2025-09-08T10:44:19,667 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,668 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,668 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,668 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,668 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,668 If you don't want 'publiforge.Static.Js.Tests' to be distributed and are 2025-09-08T10:44:19,668 already explicitly excluding 'publiforge.Static.Js.Tests' via 2025-09-08T10:44:19,668 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,668 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,668 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,669 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,669 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,669 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,669 even if it does not contain any `.py` files. 2025-09-08T10:44:19,669 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,669 directory, all directories are treated like packages. 2025-09-08T10:44:19,669 ******************************************************************************** 2025-09-08T10:44:19,670 !! 2025-09-08T10:44:19,670 check.warn(importable) 2025-09-08T10:44:19,670 /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-08T10:44:19,670 !! 2025-09-08T10:44:19,670 ******************************************************************************** 2025-09-08T10:44:19,670 ############################ 2025-09-08T10:44:19,670 # Package would be ignored # 2025-09-08T10:44:19,670 ############################ 2025-09-08T10:44:19,670 Python recognizes 'publiforge.Templates' as an importable package[^1], 2025-09-08T10:44:19,670 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,671 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,671 package, please make sure that 'publiforge.Templates' is explicitly added 2025-09-08T10:44:19,671 to the `packages` configuration field. 2025-09-08T10:44:19,671 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,671 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,671 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,671 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,671 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,672 If you don't want 'publiforge.Templates' to be distributed and are 2025-09-08T10:44:19,672 already explicitly excluding 'publiforge.Templates' via 2025-09-08T10:44:19,672 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,672 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,672 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,672 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,672 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,673 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,673 even if it does not contain any `.py` files. 2025-09-08T10:44:19,673 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,673 directory, all directories are treated like packages. 2025-09-08T10:44:19,673 ******************************************************************************** 2025-09-08T10:44:19,673 !! 2025-09-08T10:44:19,673 check.warn(importable) 2025-09-08T10:44:19,673 /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-08T10:44:19,673 !! 2025-09-08T10:44:19,673 ******************************************************************************** 2025-09-08T10:44:19,674 ############################ 2025-09-08T10:44:19,674 # Package would be ignored # 2025-09-08T10:44:19,674 ############################ 2025-09-08T10:44:19,674 Python recognizes 'publiforge.scaffolds.Front.PubliForge' as an importable package[^1], 2025-09-08T10:44:19,674 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,674 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,674 package, please make sure that 'publiforge.scaffolds.Front.PubliForge' is explicitly added 2025-09-08T10:44:19,674 to the `packages` configuration field. 2025-09-08T10:44:19,674 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,674 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,675 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,675 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,675 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,675 If you don't want 'publiforge.scaffolds.Front.PubliForge' to be distributed and are 2025-09-08T10:44:19,675 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge' via 2025-09-08T10:44:19,675 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,675 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,675 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,675 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,676 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,676 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,676 even if it does not contain any `.py` files. 2025-09-08T10:44:19,676 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,676 directory, all directories are treated like packages. 2025-09-08T10:44:19,676 ******************************************************************************** 2025-09-08T10:44:19,676 !! 2025-09-08T10:44:19,676 check.warn(importable) 2025-09-08T10:44:19,677 /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-08T10:44:19,677 !! 2025-09-08T10:44:19,677 ******************************************************************************** 2025-09-08T10:44:19,677 ############################ 2025-09-08T10:44:19,677 # Package would be ignored # 2025-09-08T10:44:19,677 ############################ 2025-09-08T10:44:19,677 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' as an importable package[^1], 2025-09-08T10:44:19,677 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,677 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,677 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' is explicitly added 2025-09-08T10:44:19,678 to the `packages` configuration field. 2025-09-08T10:44:19,678 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,678 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,678 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,678 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,678 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,678 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' to be distributed and are 2025-09-08T10:44:19,678 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' via 2025-09-08T10:44:19,679 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,679 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,679 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,679 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,679 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,679 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,680 even if it does not contain any `.py` files. 2025-09-08T10:44:19,680 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,680 directory, all directories are treated like packages. 2025-09-08T10:44:19,680 ******************************************************************************** 2025-09-08T10:44:19,680 !! 2025-09-08T10:44:19,680 check.warn(importable) 2025-09-08T10:44:19,680 /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-08T10:44:19,680 !! 2025-09-08T10:44:19,680 ******************************************************************************** 2025-09-08T10:44:19,681 ############################ 2025-09-08T10:44:19,681 # Package would be ignored # 2025-09-08T10:44:19,681 ############################ 2025-09-08T10:44:19,681 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' as an importable package[^1], 2025-09-08T10:44:19,681 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,681 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,681 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' is explicitly added 2025-09-08T10:44:19,681 to the `packages` configuration field. 2025-09-08T10:44:19,681 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,681 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,682 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,682 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,682 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,682 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' to be distributed and are 2025-09-08T10:44:19,682 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' via 2025-09-08T10:44:19,682 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,682 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,683 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,683 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,683 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,683 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,683 even if it does not contain any `.py` files. 2025-09-08T10:44:19,683 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,683 directory, all directories are treated like packages. 2025-09-08T10:44:19,683 ******************************************************************************** 2025-09-08T10:44:19,684 !! 2025-09-08T10:44:19,684 check.warn(importable) 2025-09-08T10:44:19,684 /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-08T10:44:19,684 !! 2025-09-08T10:44:19,684 ******************************************************************************** 2025-09-08T10:44:19,684 ############################ 2025-09-08T10:44:19,684 # Package would be ignored # 2025-09-08T10:44:19,684 ############################ 2025-09-08T10:44:19,684 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' as an importable package[^1], 2025-09-08T10:44:19,684 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,685 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,685 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' is explicitly added 2025-09-08T10:44:19,685 to the `packages` configuration field. 2025-09-08T10:44:19,685 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,685 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,685 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,685 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,685 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,686 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' to be distributed and are 2025-09-08T10:44:19,686 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' via 2025-09-08T10:44:19,686 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,686 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,686 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,686 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,686 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,687 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,687 even if it does not contain any `.py` files. 2025-09-08T10:44:19,687 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,687 directory, all directories are treated like packages. 2025-09-08T10:44:19,687 ******************************************************************************** 2025-09-08T10:44:19,687 !! 2025-09-08T10:44:19,687 check.warn(importable) 2025-09-08T10:44:19,687 /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-08T10:44:19,687 !! 2025-09-08T10:44:19,688 ******************************************************************************** 2025-09-08T10:44:19,688 ############################ 2025-09-08T10:44:19,688 # Package would be ignored # 2025-09-08T10:44:19,688 ############################ 2025-09-08T10:44:19,688 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' as an importable package[^1], 2025-09-08T10:44:19,688 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,688 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,688 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' is explicitly added 2025-09-08T10:44:19,688 to the `packages` configuration field. 2025-09-08T10:44:19,688 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,689 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,689 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,689 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,689 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,689 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' to be distributed and are 2025-09-08T10:44:19,689 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' via 2025-09-08T10:44:19,689 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,689 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,689 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,690 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,690 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,690 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,690 even if it does not contain any `.py` files. 2025-09-08T10:44:19,690 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,690 directory, all directories are treated like packages. 2025-09-08T10:44:19,690 ******************************************************************************** 2025-09-08T10:44:19,691 !! 2025-09-08T10:44:19,691 check.warn(importable) 2025-09-08T10:44:19,691 /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-08T10:44:19,691 !! 2025-09-08T10:44:19,691 ******************************************************************************** 2025-09-08T10:44:19,691 ############################ 2025-09-08T10:44:19,691 # Package would be ignored # 2025-09-08T10:44:19,691 ############################ 2025-09-08T10:44:19,691 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' as an importable package[^1], 2025-09-08T10:44:19,692 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,692 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,692 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' is explicitly added 2025-09-08T10:44:19,692 to the `packages` configuration field. 2025-09-08T10:44:19,692 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,692 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,692 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,692 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,693 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,693 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' to be distributed and are 2025-09-08T10:44:19,693 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' via 2025-09-08T10:44:19,693 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,693 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,693 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,693 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,693 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,694 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,694 even if it does not contain any `.py` files. 2025-09-08T10:44:19,694 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,694 directory, all directories are treated like packages. 2025-09-08T10:44:19,694 ******************************************************************************** 2025-09-08T10:44:19,694 !! 2025-09-08T10:44:19,694 check.warn(importable) 2025-09-08T10:44:19,695 /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-08T10:44:19,695 !! 2025-09-08T10:44:19,695 ******************************************************************************** 2025-09-08T10:44:19,695 ############################ 2025-09-08T10:44:19,695 # Package would be ignored # 2025-09-08T10:44:19,695 ############################ 2025-09-08T10:44:19,695 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static' as an importable package[^1], 2025-09-08T10:44:19,695 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,695 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,696 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static' is explicitly added 2025-09-08T10:44:19,696 to the `packages` configuration field. 2025-09-08T10:44:19,696 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,696 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,696 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,696 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,696 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,697 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static' to be distributed and are 2025-09-08T10:44:19,697 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static' via 2025-09-08T10:44:19,697 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,697 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,697 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,697 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,697 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,698 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,698 even if it does not contain any `.py` files. 2025-09-08T10:44:19,698 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,698 directory, all directories are treated like packages. 2025-09-08T10:44:19,698 ******************************************************************************** 2025-09-08T10:44:19,698 !! 2025-09-08T10:44:19,698 check.warn(importable) 2025-09-08T10:44:19,698 /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-08T10:44:19,698 !! 2025-09-08T10:44:19,699 ******************************************************************************** 2025-09-08T10:44:19,699 ############################ 2025-09-08T10:44:19,699 # Package would be ignored # 2025-09-08T10:44:19,699 ############################ 2025-09-08T10:44:19,699 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static.Css' as an importable package[^1], 2025-09-08T10:44:19,699 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,699 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,699 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static.Css' is explicitly added 2025-09-08T10:44:19,699 to the `packages` configuration field. 2025-09-08T10:44:19,699 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,700 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,700 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,700 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,700 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,700 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static.Css' to be distributed and are 2025-09-08T10:44:19,700 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static.Css' via 2025-09-08T10:44:19,700 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,700 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,701 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,701 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,701 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,701 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,701 even if it does not contain any `.py` files. 2025-09-08T10:44:19,701 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,701 directory, all directories are treated like packages. 2025-09-08T10:44:19,702 ******************************************************************************** 2025-09-08T10:44:19,702 !! 2025-09-08T10:44:19,702 check.warn(importable) 2025-09-08T10:44:19,702 /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-08T10:44:19,702 !! 2025-09-08T10:44:19,702 ******************************************************************************** 2025-09-08T10:44:19,702 ############################ 2025-09-08T10:44:19,702 # Package would be ignored # 2025-09-08T10:44:19,702 ############################ 2025-09-08T10:44:19,703 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static.Images' as an importable package[^1], 2025-09-08T10:44:19,703 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,703 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,703 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static.Images' is explicitly added 2025-09-08T10:44:19,703 to the `packages` configuration field. 2025-09-08T10:44:19,703 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,703 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,703 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,703 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,704 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,704 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static.Images' to be distributed and are 2025-09-08T10:44:19,704 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static.Images' via 2025-09-08T10:44:19,704 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,704 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,704 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,704 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,705 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,705 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,705 even if it does not contain any `.py` files. 2025-09-08T10:44:19,705 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,705 directory, all directories are treated like packages. 2025-09-08T10:44:19,705 ******************************************************************************** 2025-09-08T10:44:19,705 !! 2025-09-08T10:44:19,705 check.warn(importable) 2025-09-08T10:44:19,706 /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-08T10:44:19,706 !! 2025-09-08T10:44:19,706 ******************************************************************************** 2025-09-08T10:44:19,706 ############################ 2025-09-08T10:44:19,706 # Package would be ignored # 2025-09-08T10:44:19,706 ############################ 2025-09-08T10:44:19,706 Python recognizes 'publiforge.scaffolds.LePrisme' as an importable package[^1], 2025-09-08T10:44:19,706 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,706 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,706 package, please make sure that 'publiforge.scaffolds.LePrisme' is explicitly added 2025-09-08T10:44:19,707 to the `packages` configuration field. 2025-09-08T10:44:19,707 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,707 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,707 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,707 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,707 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,707 If you don't want 'publiforge.scaffolds.LePrisme' to be distributed and are 2025-09-08T10:44:19,708 already explicitly excluding 'publiforge.scaffolds.LePrisme' via 2025-09-08T10:44:19,708 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,708 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,708 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,708 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,708 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,708 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,708 even if it does not contain any `.py` files. 2025-09-08T10:44:19,709 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,709 directory, all directories are treated like packages. 2025-09-08T10:44:19,709 ******************************************************************************** 2025-09-08T10:44:19,709 !! 2025-09-08T10:44:19,709 check.warn(importable) 2025-09-08T10:44:19,709 /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-08T10:44:19,709 !! 2025-09-08T10:44:19,709 ******************************************************************************** 2025-09-08T10:44:19,709 ############################ 2025-09-08T10:44:19,710 # Package would be ignored # 2025-09-08T10:44:19,710 ############################ 2025-09-08T10:44:19,710 Python recognizes 'publiforge.scaffolds.LePrisme.Templates' as an importable package[^1], 2025-09-08T10:44:19,710 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,710 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,710 package, please make sure that 'publiforge.scaffolds.LePrisme.Templates' is explicitly added 2025-09-08T10:44:19,710 to the `packages` configuration field. 2025-09-08T10:44:19,710 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,711 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,711 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,711 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,711 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,711 If you don't want 'publiforge.scaffolds.LePrisme.Templates' to be distributed and are 2025-09-08T10:44:19,711 already explicitly excluding 'publiforge.scaffolds.LePrisme.Templates' via 2025-09-08T10:44:19,711 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,711 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,712 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,712 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,712 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,712 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,712 even if it does not contain any `.py` files. 2025-09-08T10:44:19,712 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,712 directory, all directories are treated like packages. 2025-09-08T10:44:19,713 ******************************************************************************** 2025-09-08T10:44:19,713 !! 2025-09-08T10:44:19,713 check.warn(importable) 2025-09-08T10:44:19,713 /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-08T10:44:19,713 !! 2025-09-08T10:44:19,713 ******************************************************************************** 2025-09-08T10:44:19,713 ############################ 2025-09-08T10:44:19,713 # Package would be ignored # 2025-09-08T10:44:19,713 ############################ 2025-09-08T10:44:19,714 Python recognizes 'publiforge.scaffolds.LePrisme.Variables' as an importable package[^1], 2025-09-08T10:44:19,714 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,714 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,714 package, please make sure that 'publiforge.scaffolds.LePrisme.Variables' is explicitly added 2025-09-08T10:44:19,714 to the `packages` configuration field. 2025-09-08T10:44:19,714 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,714 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,714 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,714 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,715 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,715 If you don't want 'publiforge.scaffolds.LePrisme.Variables' to be distributed and are 2025-09-08T10:44:19,715 already explicitly excluding 'publiforge.scaffolds.LePrisme.Variables' via 2025-09-08T10:44:19,715 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,715 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,715 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,715 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,716 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,716 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,716 even if it does not contain any `.py` files. 2025-09-08T10:44:19,716 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,716 directory, all directories are treated like packages. 2025-09-08T10:44:19,716 ******************************************************************************** 2025-09-08T10:44:19,716 !! 2025-09-08T10:44:19,716 check.warn(importable) 2025-09-08T10:44:19,717 /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-08T10:44:19,717 !! 2025-09-08T10:44:19,717 ******************************************************************************** 2025-09-08T10:44:19,717 ############################ 2025-09-08T10:44:19,717 # Package would be ignored # 2025-09-08T10:44:19,717 ############################ 2025-09-08T10:44:19,717 Python recognizes 'publiforge.scaffolds.LePrisme.lib' as an importable package[^1], 2025-09-08T10:44:19,717 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,717 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,717 package, please make sure that 'publiforge.scaffolds.LePrisme.lib' is explicitly added 2025-09-08T10:44:19,718 to the `packages` configuration field. 2025-09-08T10:44:19,718 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,718 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,718 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,718 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,718 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,718 If you don't want 'publiforge.scaffolds.LePrisme.lib' to be distributed and are 2025-09-08T10:44:19,719 already explicitly excluding 'publiforge.scaffolds.LePrisme.lib' via 2025-09-08T10:44:19,719 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,719 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,719 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,719 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,719 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,719 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,719 even if it does not contain any `.py` files. 2025-09-08T10:44:19,720 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,720 directory, all directories are treated like packages. 2025-09-08T10:44:19,720 ******************************************************************************** 2025-09-08T10:44:19,720 !! 2025-09-08T10:44:19,720 check.warn(importable) 2025-09-08T10:44:19,720 /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-08T10:44:19,720 !! 2025-09-08T10:44:19,720 ******************************************************************************** 2025-09-08T10:44:19,720 ############################ 2025-09-08T10:44:19,721 # Package would be ignored # 2025-09-08T10:44:19,721 ############################ 2025-09-08T10:44:19,721 Python recognizes 'publiforge.tests.Data' as an importable package[^1], 2025-09-08T10:44:19,721 but it is absent from setuptools' `packages` configuration. 2025-09-08T10:44:19,721 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T10:44:19,721 package, please make sure that 'publiforge.tests.Data' is explicitly added 2025-09-08T10:44:19,721 to the `packages` configuration field. 2025-09-08T10:44:19,721 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T10:44:19,721 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T10:44:19,722 instead of `find_packages(...)`/`find:`). 2025-09-08T10:44:19,722 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T10:44:19,722 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T10:44:19,722 If you don't want 'publiforge.tests.Data' to be distributed and are 2025-09-08T10:44:19,722 already explicitly excluding 'publiforge.tests.Data' via 2025-09-08T10:44:19,722 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T10:44:19,722 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T10:44:19,722 combination with a more fine grained `package-data` configuration. 2025-09-08T10:44:19,723 You can read more about "package data files" on setuptools documentation page: 2025-09-08T10:44:19,723 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T10:44:19,723 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T10:44:19,723 even if it does not contain any `.py` files. 2025-09-08T10:44:19,723 On the other hand, currently there is no concept of package data 2025-09-08T10:44:19,723 directory, all directories are treated like packages. 2025-09-08T10:44:19,723 ******************************************************************************** 2025-09-08T10:44:19,724 !! 2025-09-08T10:44:19,724 check.warn(importable) 2025-09-08T10:44:19,724 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale 2025-09-08T10:44:19,724 copying publiforge/Locale/publiforge.pot -> build/lib.linux-armv7l-cpython-313/publiforge/Locale 2025-09-08T10:44:19,724 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T10:44:19,724 copying publiforge/Locale/es/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T10:44:19,724 copying publiforge/Locale/es/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T10:44:19,724 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T10:44:19,724 copying publiforge/Locale/fr/LC_MESSAGES/colander.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T10:44:19,724 copying publiforge/Locale/fr/LC_MESSAGES/colander.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T10:44:19,725 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T10:44:19,725 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T10:44:19,725 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T10:44:19,725 copying publiforge/Openers/Image/image.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T10:44:19,725 copying publiforge/Openers/Image/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T10:44:19,725 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/ImageEdit 2025-09-08T10:44:19,725 copying publiforge/Openers/ImageEdit/image.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/ImageEdit 2025-09-08T10:44:19,725 copying publiforge/Openers/ImageEdit/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/ImageEdit 2025-09-08T10:44:19,725 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T10:44:19,725 copying publiforge/Openers/Ini/ini.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T10:44:19,725 copying publiforge/Openers/Ini/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T10:44:19,725 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/NoMore 2025-09-08T10:44:19,726 copying publiforge/Openers/NoMore/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/NoMore 2025-09-08T10:44:19,726 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Plain 2025-09-08T10:44:19,726 copying publiforge/Openers/Plain/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Plain 2025-09-08T10:44:19,726 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T10:44:19,726 copying publiforge/Openers/Publidoc/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T10:44:19,726 copying publiforge/Openers/Publidoc/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T10:44:19,726 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T10:44:19,726 copying publiforge/Openers/Publidoc/Maestro/publidoc_render4maestro.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T10:44:19,726 copying publiforge/Openers/Publidoc/Maestro/publidoc_xml4maestro.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T10:44:19,726 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Regex 2025-09-08T10:44:19,726 copying publiforge/Openers/Publidoc/Regex/publidoc_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Regex 2025-09-08T10:44:19,727 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T10:44:19,727 copying publiforge/Openers/Publidoc/Seeds/publidoc_document.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T10:44:19,727 copying publiforge/Openers/Publidoc/Seeds/publidoc_glossary.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T10:44:19,727 copying publiforge/Openers/Publidoc/Seeds/publidoc_topic.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T10:44:19,727 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T10:44:19,727 copying publiforge/Openers/Publidoc/Static/Css/publidoc_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T10:44:19,727 copying publiforge/Openers/Publidoc/Static/Css/publidoc_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T10:44:19,727 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T10:44:19,727 copying publiforge/Openers/Publidoc/Static/Js/codemirror4publidoc_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T10:44:19,727 copying publiforge/Openers/Publidoc/Static/Js/publidoc_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T10:44:19,727 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Variables 2025-09-08T10:44:19,727 copying publiforge/Openers/Publidoc/Variables/publidoc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Variables 2025-09-08T10:44:19,728 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T10:44:19,728 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T10:44:19,728 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T10:44:19,728 copying publiforge/Openers/Publidoc/Xsl/publidoc_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T10:44:19,728 copying publiforge/Openers/Publidoc/Xsl/publidoc_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T10:44:19,728 copying publiforge/Openers/Publidoc/Xsl/publidoc_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T10:44:19,728 copying publiforge/Openers/Publidoc/Xsl/publidoc_save_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T10:44:19,728 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T10:44:19,728 copying publiforge/Openers/Publiquiz/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T10:44:19,728 copying publiforge/Openers/Publiquiz/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T10:44:19,728 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Regex 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Regex/publiquiz_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Regex 2025-09-08T10:44:19,729 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-fill.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-media.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-select.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-check.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_composite.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_correct-line.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_blanks-fill.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,729 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_blanks-select.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_choices-check.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_choices-radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_matching.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing-categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_production.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_sort.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_wordsearch.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T10:44:19,730 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T10:44:19,730 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T10:44:19,731 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T10:44:19,731 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Fonts 2025-09-08T10:44:19,731 copying publiforge/Openers/Publiquiz/Static/Fonts/FontAwesome.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Fonts 2025-09-08T10:44:19,731 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T10:44:19,731 copying publiforge/Openers/Publiquiz/Static/Js/codemirror4publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T10:44:19,731 copying publiforge/Openers/Publiquiz/Static/Js/publiquiz_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T10:44:19,731 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Variables 2025-09-08T10:44:19,732 copying publiforge/Openers/Publiquiz/Variables/publiquiz.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Variables 2025-09-08T10:44:19,732 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T10:44:19,732 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T10:44:19,733 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T10:44:19,733 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T10:44:19,734 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T10:44:19,734 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T10:44:19,735 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T10:44:19,735 copying publiforge/Openers/Publiset/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T10:44:19,736 copying publiforge/Openers/Publiset/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T10:44:19,736 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Regex 2025-09-08T10:44:19,736 copying publiforge/Openers/Publiset/Regex/publiset_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Regex 2025-09-08T10:44:19,737 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T10:44:19,737 copying publiforge/Openers/Publiset/Seeds/publiset_composition.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T10:44:19,738 copying publiforge/Openers/Publiset/Seeds/publiset_selection.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T10:44:19,738 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T10:44:19,739 copying publiforge/Openers/Publiset/Static/Css/editor4publiset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T10:44:19,739 copying publiforge/Openers/Publiset/Static/Css/publiset_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T10:44:19,740 copying publiforge/Openers/Publiset/Static/Css/publiset_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T10:44:19,740 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T10:44:19,740 copying publiforge/Openers/Publiset/Static/Images/editor4publiset.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T10:44:19,741 copying publiforge/Openers/Publiset/Static/Images/editor4publiset.xcf -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Images 2025-09-08T10:44:19,741 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T10:44:19,742 copying publiforge/Openers/Publiset/Static/Js/codemirror4publiset_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T10:44:19,742 copying publiforge/Openers/Publiset/Static/Js/editor4publiset.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T10:44:19,743 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_en.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T10:44:19,743 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_fr.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T10:44:19,744 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T10:44:19,745 copying publiforge/Openers/Publiset/Static/Js/publiset_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T10:44:19,745 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Variables 2025-09-08T10:44:19,745 copying publiforge/Openers/Publiset/Variables/publiset.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Variables 2025-09-08T10:44:19,746 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T10:44:19,746 copying publiforge/Openers/Publiset/Xsl/publiset_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T10:44:19,747 copying publiforge/Openers/Publiset/Xsl/publiset_overview.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T10:44:19,747 copying publiforge/Openers/Publiset/Xsl/publiset_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T10:44:19,748 copying publiforge/Openers/Publiset/Xsl/publiset_render_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T10:44:19,748 copying publiforge/Openers/Publiset/Xsl/publiset_render_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T10:44:19,749 copying publiforge/Openers/Publiset/Xsl/publiset_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T10:44:19,749 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T10:44:19,750 copying publiforge/Openers/Xml/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T10:44:19,750 copying publiforge/Openers/Xml/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T10:44:19,751 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Css 2025-09-08T10:44:19,751 copying publiforge/Openers/Xml/Static/Css/editor4xml.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Css 2025-09-08T10:44:19,751 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T10:44:19,752 copying publiforge/Openers/Xml/Static/Images/e4x_folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T10:44:19,752 copying publiforge/Openers/Xml/Static/Images/editor4xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T10:44:19,753 copying publiforge/Openers/Xml/Static/Images/editor4xml.xcf -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Images 2025-09-08T10:44:19,754 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T10:44:19,754 copying publiforge/Openers/Xml/Static/Js/editor4xml.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T10:44:19,755 copying publiforge/Openers/Xml/Static/Js/editor4xml_en.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T10:44:19,755 copying publiforge/Openers/Xml/Static/Js/editor4xml_fr.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml/Static/Js 2025-09-08T10:44:19,756 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T10:44:19,756 copying publiforge/Processors/CharCount/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T10:44:19,757 copying publiforge/Processors/CharCount/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T10:44:19,757 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount/Xsl 2025-09-08T10:44:19,757 copying publiforge/Processors/CharCount/Xsl/charcount.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount/Xsl 2025-09-08T10:44:19,758 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T10:44:19,758 copying publiforge/Processors/CleanStorage/generator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T10:44:19,759 copying publiforge/Processors/CleanStorage/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage 2025-09-08T10:44:19,759 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T10:44:19,759 copying publiforge/Processors/CleanStorage/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T10:44:19,760 copying publiforge/Processors/CleanStorage/lib/clean_storage.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CleanStorage/lib 2025-09-08T10:44:19,760 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T10:44:19,761 copying publiforge/Processors/DTBookValid/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T10:44:19,761 copying publiforge/Processors/DTBookValid/validator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T10:44:19,762 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid/RelaxNG 2025-09-08T10:44:19,762 copying publiforge/Processors/DTBookValid/RelaxNG/dtbook-2005-3.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid/RelaxNG 2025-09-08T10:44:19,763 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T10:44:19,763 copying publiforge/Processors/PackFilling/generator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T10:44:19,764 copying publiforge/Processors/PackFilling/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling 2025-09-08T10:44:19,764 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/Variables 2025-09-08T10:44:19,765 copying publiforge/Processors/PackFilling/Variables/packfilling.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/Variables 2025-09-08T10:44:19,765 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T10:44:19,765 copying publiforge/Processors/PackFilling/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T10:44:19,766 copying publiforge/Processors/PackFilling/lib/packfilling.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PackFilling/lib 2025-09-08T10:44:19,766 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel 2025-09-08T10:44:19,767 copying publiforge/Processors/Parallel/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel 2025-09-08T10:44:19,767 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel/Variables 2025-09-08T10:44:19,767 copying publiforge/Processors/Parallel/Variables/parallel.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel/Variables 2025-09-08T10:44:19,768 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5 2025-09-08T10:44:19,768 copying publiforge/Processors/Publianim2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5 2025-09-08T10:44:19,769 copying publiforge/Processors/Publianim2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5 2025-09-08T10:44:19,769 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5/Variables 2025-09-08T10:44:19,769 copying publiforge/Processors/Publianim2Html5/Variables/publianim2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5/Variables 2025-09-08T10:44:19,770 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5/Xsl 2025-09-08T10:44:19,770 copying publiforge/Processors/Publianim2Html5/Xsl/publianim2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publianim2Html5/Xsl 2025-09-08T10:44:19,770 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T10:44:19,771 copying publiforge/Processors/Publidoc2DTBook/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T10:44:19,771 copying publiforge/Processors/Publidoc2DTBook/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T10:44:19,772 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T10:44:19,772 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T10:44:19,773 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T10:44:19,773 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T10:44:19,773 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T10:44:19,774 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T10:44:19,774 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T10:44:19,775 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T10:44:19,775 copying publiforge/Processors/Publidoc2EPub2/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T10:44:19,776 copying publiforge/Processors/Publidoc2EPub2/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T10:44:19,776 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates 2025-09-08T10:44:19,776 copying publiforge/Processors/Publidoc2EPub2/Templates/mimetype -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates 2025-09-08T10:44:19,777 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2025-09-08T10:44:19,777 copying publiforge/Processors/Publidoc2EPub2/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2025-09-08T10:44:19,778 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2025-09-08T10:44:19,778 copying publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2025-09-08T10:44:19,779 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T10:44:19,779 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T10:44:19,779 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T10:44:19,780 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T10:44:19,780 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T10:44:19,781 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T10:44:19,781 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T10:44:19,782 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T10:44:19,782 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ncx.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T10:44:19,783 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T10:44:19,783 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T10:44:19,784 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T10:44:19,784 copying publiforge/Processors/Publidoc2EPub2/jars/COPYING.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T10:44:19,785 copying publiforge/Processors/Publidoc2EPub2/jars/README.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T10:44:19,785 copying publiforge/Processors/Publidoc2EPub2/jars/THIRD-PARTY.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T10:44:19,786 copying publiforge/Processors/Publidoc2EPub2/jars/epubcheck.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T10:44:19,790 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T10:44:19,790 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-08T10:44:19,827 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-08T10:44:19,828 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-08T10:44:19,829 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-08T10:44:19,830 copying publiforge/Processors/Publidoc2EPub2/jars/lib/commons-compress-1.5.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T10:44:19,831 copying publiforge/Processors/Publidoc2EPub2/jars/lib/guava-14.0.1.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T10:44:19,839 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-08T10:44:19,840 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-08T10:44:19,841 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-08T10:44:19,842 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-08T10:44:19,844 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-08T10:44:19,847 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jing-20120724.0.0.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T10:44:19,850 copying publiforge/Processors/Publidoc2EPub2/jars/lib/sac-1.3.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T10:44:19,851 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T10:44:19,851 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/Apache-2.0.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T10:44:19,852 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/BSD-3-Clause.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T10:44:19,852 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/MPL-1.0.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T10:44:19,853 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/W3C.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T10:44:19,853 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T10:44:19,853 copying publiforge/Processors/Publidoc2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T10:44:19,854 copying publiforge/Processors/Publidoc2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T10:44:19,854 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates 2025-09-08T10:44:19,855 copying publiforge/Processors/Publidoc2EPub3/Templates/mimetype -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates 2025-09-08T10:44:19,855 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2025-09-08T10:44:19,855 copying publiforge/Processors/Publidoc2EPub3/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2025-09-08T10:44:19,856 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2025-09-08T10:44:19,856 copying publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2025-09-08T10:44:19,857 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Variables 2025-09-08T10:44:19,857 copying publiforge/Processors/Publidoc2EPub3/Variables/publidoc2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Variables 2025-09-08T10:44:19,858 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T10:44:19,858 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T10:44:19,858 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_nav.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T10:44:19,859 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T10:44:19,860 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_smil.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T10:44:19,860 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T10:44:19,861 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T10:44:19,861 copying publiforge/Processors/Publidoc2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T10:44:19,861 copying publiforge/Processors/Publidoc2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T10:44:19,862 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Css 2025-09-08T10:44:19,862 copying publiforge/Processors/Publidoc2Html5/Templates/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Css 2025-09-08T10:44:19,863 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T10:44:19,863 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_en.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T10:44:19,864 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_fr.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T10:44:19,864 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T10:44:19,865 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_play.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Images 2025-09-08T10:44:19,865 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Js 2025-09-08T10:44:19,865 copying publiforge/Processors/Publidoc2Html5/Templates/Js/audio_player.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Templates/Js 2025-09-08T10:44:19,866 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T10:44:19,866 copying publiforge/Processors/Publidoc2Html5/Variables/publidoc2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T10:44:19,867 copying publiforge/Processors/Publidoc2Html5/Variables/publidoc2html5_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T10:44:19,867 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T10:44:19,867 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T10:44:19,868 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T10:44:19,869 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_media.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T10:44:19,869 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T10:44:19,870 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T10:44:19,870 copying publiforge/Processors/Publidoc2Pdf/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T10:44:19,870 copying publiforge/Processors/Publidoc2Pdf/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T10:44:19,871 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T10:44:19,871 copying publiforge/Processors/Publidoc2Pdf/Fonts/Script.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T10:44:19,874 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T10:44:19,874 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_post.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T10:44:19,875 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T10:44:19,875 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T10:44:19,876 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_dimension.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T10:44:19,876 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_font.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T10:44:19,877 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T10:44:19,877 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_layout.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T10:44:19,878 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T10:44:19,878 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T10:44:19,879 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T10:44:19,879 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T10:44:19,880 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T10:44:19,880 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T10:44:19,881 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T10:44:19,881 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T10:44:19,882 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T10:44:19,882 copying publiforge/Processors/Publidoc2XHtml/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T10:44:19,883 copying publiforge/Processors/Publidoc2XHtml/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T10:44:19,883 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,884 copying publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60/_publidoc_block.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,884 copying publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60/_publidoc_component.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,885 copying publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60/_publidoc_division.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,885 copying publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60/_publidoc_head.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,886 copying publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60/_publidoc_inline.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,887 copying publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60/_publidoc_section.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,887 copying publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60/_publidoc_top.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,888 copying publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60/publidoc.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/.sass-cache/79eac27e49646dfbc0b5d1433a5851998ee65b60 2025-09-08T10:44:19,888 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Regex 2025-09-08T10:44:19,889 copying publiforge/Processors/Publidoc2XHtml/Regex/publidoc2xhtml_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Regex 2025-09-08T10:44:19,889 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,889 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_block.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,890 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_component.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,890 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_division.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,891 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_head.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,891 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_inline.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,892 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_section.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,892 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_top.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,893 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_xxx.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,894 copying publiforge/Processors/Publidoc2XHtml/Scss/publidoc.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Scss 2025-09-08T10:44:19,894 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T10:44:19,894 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T10:44:19,895 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/publidoc.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T10:44:19,895 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/publidoc.css.map -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T10:44:19,896 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/reset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T10:44:19,896 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,897 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/annotation.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,897 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,898 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,898 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio_play.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,899 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,899 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_previous.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,900 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,900 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/pulse.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,901 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/video.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T10:44:19,902 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T10:44:19,902 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/jquery.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T10:44:19,903 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/publidoc.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T10:44:19,903 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T10:44:19,904 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T10:44:19,904 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_html.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T10:44:19,905 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T10:44:19,905 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T10:44:19,906 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T10:44:19,906 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T10:44:19,907 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T10:44:19,907 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T10:44:19,907 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T10:44:19,908 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T10:44:19,909 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T10:44:19,909 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_media.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T10:44:19,910 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T10:44:19,911 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T10:44:19,911 copying publiforge/Processors/PublidocClean/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T10:44:19,912 copying publiforge/Processors/PublidocClean/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T10:44:19,912 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Regex 2025-09-08T10:44:19,912 copying publiforge/Processors/PublidocClean/Regex/publidocclean_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Regex 2025-09-08T10:44:19,913 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Variables 2025-09-08T10:44:19,913 copying publiforge/Processors/PublidocClean/Variables/publidocclean.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Variables 2025-09-08T10:44:19,913 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Xsl 2025-09-08T10:44:19,914 copying publiforge/Processors/PublidocClean/Xsl/publidocclean.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Xsl 2025-09-08T10:44:19,914 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T10:44:19,915 copying publiforge/Processors/PublidocValid/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T10:44:19,915 copying publiforge/Processors/PublidocValid/validator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T10:44:19,915 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T10:44:19,916 copying publiforge/Processors/PublidocValid/RelaxNG/publianim.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T10:44:19,916 copying publiforge/Processors/PublidocValid/RelaxNG/publidoc.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T10:44:19,917 copying publiforge/Processors/PublidocValid/RelaxNG/publiquiz.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T10:44:19,918 copying publiforge/Processors/PublidocValid/RelaxNG/publiset.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T10:44:19,919 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T10:44:19,919 copying publiforge/Processors/Publiquiz2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T10:44:19,919 copying publiforge/Processors/Publiquiz2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T10:44:19,920 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Variables 2025-09-08T10:44:19,920 copying publiforge/Processors/Publiquiz2EPub3/Variables/publiquiz2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Variables 2025-09-08T10:44:19,921 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T10:44:19,921 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T10:44:19,922 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T10:44:19,922 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T10:44:19,923 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T10:44:19,923 copying publiforge/Processors/Publiquiz2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T10:44:19,923 copying publiforge/Processors/Publiquiz2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T10:44:19,924 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,924 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_block.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,925 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_buttons.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,925 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_categories.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,926 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_category.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,927 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_choice.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,927 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_choices.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,928 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_flashcard.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,929 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_matching.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,929 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_point.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,930 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_pointing.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,930 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_production.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,931 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_engine_wordsearch.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,932 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_inline.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,932 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_quiz_category.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,933 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_quiz_choice.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,934 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_quiz_matching.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,934 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_section.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,935 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/_publiquiz_top.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,936 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961/publiquiz.scssc -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/.sass-cache/dbc939d8af3fcc50765c68a5d893c6bca0dd3961 2025-09-08T10:44:19,936 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,936 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_block.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,937 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_buttons.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,937 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_categories.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,938 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_choices.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,938 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_flashcard.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,939 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_matching.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,939 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_pointing.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,940 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_production.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,940 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_wordsearch.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,941 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_inline.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,942 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_section.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,942 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_top.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,943 copying publiforge/Processors/Publiquiz2Html5/Scss/publiquiz.scss -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Scss 2025-09-08T10:44:19,943 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T10:44:19,944 copying publiforge/Processors/Publiquiz2Html5/Templates/Css/publiquiz.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T10:44:19,944 copying publiforge/Processors/Publiquiz2Html5/Templates/Css/publiquiz.css.map -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T10:44:19,945 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2025-09-08T10:44:19,945 copying publiforge/Processors/Publiquiz2Html5/Templates/Fonts/FontAwesome.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2025-09-08T10:44:19,946 copying publiforge/Processors/Publiquiz2Html5/Templates/Fonts/FontAwesome.ttf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2025-09-08T10:44:19,947 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T10:44:19,947 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/close.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T10:44:19,948 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/eraser.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T10:44:19,949 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/highlighter.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T10:44:19,949 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/loading.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Images 2025-09-08T10:44:19,950 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,950 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/code.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,950 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,952 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_basics.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,953 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_correct_line.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,954 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_flashcard.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,954 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,955 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_matching_link.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,955 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_wordsearch.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T10:44:19,956 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T10:44:19,956 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T10:44:19,957 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5_quiz.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T10:44:19,957 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T10:44:19,958 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T10:44:19,958 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T10:44:19,959 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T10:44:19,960 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T10:44:19,960 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T10:44:19,961 copying publiforge/Processors/Publiquiz2Scorm12/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T10:44:19,961 copying publiforge/Processors/Publiquiz2Scorm12/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12 2025-09-08T10:44:19,962 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T10:44:19,962 copying publiforge/Processors/Publiquiz2Scorm12/Templates/adlcp_rootv1p2.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T10:44:19,962 copying publiforge/Processors/Publiquiz2Scorm12/Templates/ims_xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T10:44:19,963 copying publiforge/Processors/Publiquiz2Scorm12/Templates/imscp_rootv1p1p2.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T10:44:19,963 copying publiforge/Processors/Publiquiz2Scorm12/Templates/imsmd_rootv1p2p1.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates 2025-09-08T10:44:19,964 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css 2025-09-08T10:44:19,964 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css 2025-09-08T10:44:19,965 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T10:44:19,965 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T10:44:19,966 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images/audio_play.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2025-09-08T10:44:19,966 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T10:44:19,966 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T10:44:19,967 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js/scorm_apiwrapper.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2025-09-08T10:44:19,968 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T10:44:19,968 copying publiforge/Processors/Publiquiz2Scorm12/Variables/publiquiz2scorm12.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T10:44:19,968 copying publiforge/Processors/Publiquiz2Scorm12/Variables/publiquiz2scorm12_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Variables 2025-09-08T10:44:19,969 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T10:44:19,969 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T10:44:19,970 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T10:44:19,970 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_ims.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T10:44:19,971 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm12/Xsl 2025-09-08T10:44:19,972 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T10:44:19,972 copying publiforge/Processors/Publiquiz2Scorm2004/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T10:44:19,972 copying publiforge/Processors/Publiquiz2Scorm2004/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004 2025-09-08T10:44:19,973 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,973 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/XMLSchema.dtd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,974 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlcp_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,974 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlnav_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,975 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlseq_v1p3.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,975 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/datatypes.dtd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,976 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/ims_xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,976 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imscp_v1p1.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,977 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,977 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0auxresource.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,978 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0control.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,978 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0delivery.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,979 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0limit.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,979 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0objective.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,980 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0random.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,980 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0rollup.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,981 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0seqrule.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,982 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0util.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,982 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,983 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomCustom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,983 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomLoose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,984 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomStrict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,984 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/xml.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates 2025-09-08T10:44:19,985 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css 2025-09-08T10:44:19,985 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css 2025-09-08T10:44:19,985 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T10:44:19,986 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T10:44:19,986 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js/scorm_apiwrapper.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2025-09-08T10:44:19,987 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T10:44:19,987 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/anyElement.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T10:44:19,988 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/dataTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T10:44:19,988 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/elementNames.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T10:44:19,989 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/elementTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T10:44:19,989 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/rootElement.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T10:44:19,990 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/vocabTypes.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T10:44:19,990 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/vocabValues.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2025-09-08T10:44:19,991 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T10:44:19,991 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/extend/custom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T10:44:19,992 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/extend/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2025-09-08T10:44:19,992 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T10:44:19,993 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/unique/loose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T10:44:19,993 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/unique/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2025-09-08T10:44:19,994 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T10:44:19,994 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/custom.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T10:44:19,994 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/loose.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T10:44:19,995 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/strict.xsd -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2025-09-08T10:44:19,995 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T10:44:19,996 copying publiforge/Processors/Publiquiz2Scorm2004/Variables/publiquiz2scorm2004.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T10:44:19,996 copying publiforge/Processors/Publiquiz2Scorm2004/Variables/publiquiz2scorm2004_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Variables 2025-09-08T10:44:19,997 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T10:44:19,997 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T10:44:19,998 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T10:44:19,998 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_ims.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T10:44:19,999 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2025-09-08T10:44:19,999 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T10:44:19,999 copying publiforge/Processors/Publiset2Publidoc/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T10:44:20,000 copying publiforge/Processors/Publiset2Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T10:44:20,000 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T10:44:20,001 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T10:44:20,001 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T10:44:20,002 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T10:44:20,002 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T10:44:20,003 copying publiforge/Processors/Publiset2Publidoc/Xsl/composition.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T10:44:20,003 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T10:44:20,004 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T10:44:20,004 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T10:44:20,005 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T10:44:20,005 copying publiforge/Processors/Publiset4Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T10:44:20,006 copying publiforge/Processors/Publiset4Publidoc/publiseter.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T10:44:20,006 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T10:44:20,006 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_meta.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T10:44:20,007 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T10:44:20,007 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_schema.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T10:44:20,008 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Xsl 2025-09-08T10:44:20,008 copying publiforge/Processors/Publiset4Publidoc/Xsl/publiset4publidoc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Xsl 2025-09-08T10:44:20,009 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T10:44:20,009 copying publiforge/Processors/Publiset4Publiquiz/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T10:44:20,009 copying publiforge/Processors/Publiset4Publiquiz/publiseter.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T10:44:20,010 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz/Xsl 2025-09-08T10:44:20,010 copying publiforge/Processors/Publiset4Publiquiz/Xsl/publiset4publiquiz.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz/Xsl 2025-09-08T10:44:20,011 creating build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T10:44:20,011 copying publiforge/RelaxNG/publiforge.rnc -> build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T10:44:20,012 copying publiforge/RelaxNG/publiforge.rng -> build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T10:44:20,012 creating build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T10:44:20,013 copying publiforge/Static/favicon.ico -> build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T10:44:20,013 copying publiforge/Static/robots.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T10:44:20,014 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T10:44:20,014 copying publiforge/Static/Css/base.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T10:44:20,014 copying publiforge/Static/Css/codemirror.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T10:44:20,015 copying publiforge/Static/Css/login.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T10:44:20,016 copying publiforge/Static/Css/pygments.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T10:44:20,016 copying publiforge/Static/Css/reset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T10:44:20,016 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,017 copying publiforge/Static/Images/action_add.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,017 copying publiforge/Static/Images/action_add_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,018 copying publiforge/Static/Images/action_browse.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,018 copying publiforge/Static/Images/action_browse_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,019 copying publiforge/Static/Images/action_build.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,019 copying publiforge/Static/Images/action_build_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,020 copying publiforge/Static/Images/action_cancel.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,020 copying publiforge/Static/Images/action_create.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,021 copying publiforge/Static/Images/action_dashboard_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,021 copying publiforge/Static/Images/action_delete.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,022 copying publiforge/Static/Images/action_delete_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,022 copying publiforge/Static/Images/action_diff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,023 copying publiforge/Static/Images/action_diff_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,023 copying publiforge/Static/Images/action_display.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,024 copying publiforge/Static/Images/action_display_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,024 copying publiforge/Static/Images/action_down_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,025 copying publiforge/Static/Images/action_download.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,025 copying publiforge/Static/Images/action_download_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,026 copying publiforge/Static/Images/action_duplicate.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,026 copying publiforge/Static/Images/action_edit_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,027 copying publiforge/Static/Images/action_export.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,027 copying publiforge/Static/Images/action_export_csv.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,028 copying publiforge/Static/Images/action_export_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,028 copying publiforge/Static/Images/action_filter.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,029 copying publiforge/Static/Images/action_help_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,029 copying publiforge/Static/Images/action_history_empty.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,030 copying publiforge/Static/Images/action_import.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,030 copying publiforge/Static/Images/action_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,031 copying publiforge/Static/Images/action_info_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,031 copying publiforge/Static/Images/action_log.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,032 copying publiforge/Static/Images/action_log_empty.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,032 copying publiforge/Static/Images/action_log_empty_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,033 copying publiforge/Static/Images/action_mkdir.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,033 copying publiforge/Static/Images/action_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,034 copying publiforge/Static/Images/action_next_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,034 copying publiforge/Static/Images/action_note.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,035 copying publiforge/Static/Images/action_note_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,035 copying publiforge/Static/Images/action_overview_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,036 copying publiforge/Static/Images/action_overview_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,036 copying publiforge/Static/Images/action_pack.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,037 copying publiforge/Static/Images/action_pipe.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,037 copying publiforge/Static/Images/action_progress_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,038 copying publiforge/Static/Images/action_remove.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,038 copying publiforge/Static/Images/action_remove_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,039 copying publiforge/Static/Images/action_rename_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,039 copying publiforge/Static/Images/action_render.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,040 copying publiforge/Static/Images/action_render_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,040 copying publiforge/Static/Images/action_reset_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,041 copying publiforge/Static/Images/action_save.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,041 copying publiforge/Static/Images/action_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,042 copying publiforge/Static/Images/action_select.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,042 copying publiforge/Static/Images/action_select_get.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,043 copying publiforge/Static/Images/action_select_get_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,044 copying publiforge/Static/Images/action_select_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,044 copying publiforge/Static/Images/action_start.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,045 copying publiforge/Static/Images/action_start_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,045 copying publiforge/Static/Images/action_stop.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,046 copying publiforge/Static/Images/action_stop_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,046 copying publiforge/Static/Images/action_synchronize.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,047 copying publiforge/Static/Images/action_synchronize_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,047 copying publiforge/Static/Images/action_take.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,048 copying publiforge/Static/Images/action_take_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,048 copying publiforge/Static/Images/action_up_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,049 copying publiforge/Static/Images/action_upload.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,049 copying publiforge/Static/Images/action_upload_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,050 copying publiforge/Static/Images/action_view.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,050 copying publiforge/Static/Images/action_view_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,051 copying publiforge/Static/Images/admin.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,051 copying publiforge/Static/Images/back.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,052 copying publiforge/Static/Images/breadcrumbs_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,052 copying publiforge/Static/Images/build.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,053 copying publiforge/Static/Images/build22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,053 copying publiforge/Static/Images/build32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,054 copying publiforge/Static/Images/build72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,054 copying publiforge/Static/Images/build72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,055 copying publiforge/Static/Images/build96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,055 copying publiforge/Static/Images/check.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,056 copying publiforge/Static/Images/close_dark.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,056 copying publiforge/Static/Images/close_light.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,057 copying publiforge/Static/Images/collapse_closed.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,057 copying publiforge/Static/Images/collapse_current_closed.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,058 copying publiforge/Static/Images/collapse_current_open.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,058 copying publiforge/Static/Images/collapse_open.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,059 copying publiforge/Static/Images/edit32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,059 copying publiforge/Static/Images/equal.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,060 copying publiforge/Static/Images/extractor.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,060 copying publiforge/Static/Images/extractor22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,061 copying publiforge/Static/Images/extractor32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,061 copying publiforge/Static/Images/flash_alert.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,062 copying publiforge/Static/Images/flash_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,063 copying publiforge/Static/Images/folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,063 copying publiforge/Static/Images/folder22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,064 copying publiforge/Static/Images/folder32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,064 copying publiforge/Static/Images/footer_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,065 copying publiforge/Static/Images/go_first.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,065 copying publiforge/Static/Images/go_first_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,065 copying publiforge/Static/Images/go_last.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,066 copying publiforge/Static/Images/go_last_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,066 copying publiforge/Static/Images/go_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,067 copying publiforge/Static/Images/go_next_file.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,067 copying publiforge/Static/Images/go_next_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,068 copying publiforge/Static/Images/go_next_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,068 copying publiforge/Static/Images/go_previous.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,069 copying publiforge/Static/Images/go_previous_file.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,069 copying publiforge/Static/Images/go_previous_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,070 copying publiforge/Static/Images/go_previous_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,070 copying publiforge/Static/Images/go_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,071 copying publiforge/Static/Images/go_top22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,072 copying publiforge/Static/Images/group.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,072 copying publiforge/Static/Images/group22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,073 copying publiforge/Static/Images/group32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,073 copying publiforge/Static/Images/history.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,074 copying publiforge/Static/Images/history22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,074 copying publiforge/Static/Images/history32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,075 copying publiforge/Static/Images/in_menu_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,075 copying publiforge/Static/Images/in_menu_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,076 copying publiforge/Static/Images/indexer.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,076 copying publiforge/Static/Images/indexer22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,077 copying publiforge/Static/Images/indexer32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,077 copying publiforge/Static/Images/info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,078 copying publiforge/Static/Images/info22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,078 copying publiforge/Static/Images/info32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,078 copying publiforge/Static/Images/job.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,079 copying publiforge/Static/Images/job22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,079 copying publiforge/Static/Images/job32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,080 copying publiforge/Static/Images/left_title.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,080 copying publiforge/Static/Images/light_green.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,081 copying publiforge/Static/Images/light_grey.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,082 copying publiforge/Static/Images/light_red.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,082 copying publiforge/Static/Images/light_yellow.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,083 copying publiforge/Static/Images/link.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,083 copying publiforge/Static/Images/link22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,084 copying publiforge/Static/Images/link32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,084 copying publiforge/Static/Images/list_header.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,085 copying publiforge/Static/Images/log_download.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,085 copying publiforge/Static/Images/log_error.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,086 copying publiforge/Static/Images/log_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,086 copying publiforge/Static/Images/log_warning.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,087 copying publiforge/Static/Images/logout.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,087 copying publiforge/Static/Images/notfound.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,088 copying publiforge/Static/Images/open_false.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,088 copying publiforge/Static/Images/open_true.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,089 copying publiforge/Static/Images/opener22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,089 copying publiforge/Static/Images/opener32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,090 copying publiforge/Static/Images/overview_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,090 copying publiforge/Static/Images/overview_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,091 copying publiforge/Static/Images/pack.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,091 copying publiforge/Static/Images/pack22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,092 copying publiforge/Static/Images/pack32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,092 copying publiforge/Static/Images/pack72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,093 copying publiforge/Static/Images/pack72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,093 copying publiforge/Static/Images/pack96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,094 copying publiforge/Static/Images/processing.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,095 copying publiforge/Static/Images/processing22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,095 copying publiforge/Static/Images/processing32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,096 copying publiforge/Static/Images/progress.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,096 copying publiforge/Static/Images/project.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,097 copying publiforge/Static/Images/project22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,097 copying publiforge/Static/Images/project32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,098 copying publiforge/Static/Images/publiforge.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,098 copying publiforge/Static/Images/pyramid.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,099 copying publiforge/Static/Images/role.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,099 copying publiforge/Static/Images/role22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,100 copying publiforge/Static/Images/role32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,100 copying publiforge/Static/Images/search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,101 copying publiforge/Static/Images/search22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,101 copying publiforge/Static/Images/search32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,102 copying publiforge/Static/Images/selection.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,102 copying publiforge/Static/Images/selection_remove_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,103 copying publiforge/Static/Images/selection_remove_sure.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,103 copying publiforge/Static/Images/sort_asc.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,104 copying publiforge/Static/Images/sort_desc.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,104 copying publiforge/Static/Images/sort_down.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,105 copying publiforge/Static/Images/sort_down_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,105 copying publiforge/Static/Images/sort_up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,106 copying publiforge/Static/Images/sort_up_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,106 copying publiforge/Static/Images/storage.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,107 copying publiforge/Static/Images/storage22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,107 copying publiforge/Static/Images/storage32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,108 copying publiforge/Static/Images/tab.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,108 copying publiforge/Static/Images/task.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,109 copying publiforge/Static/Images/task22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,109 copying publiforge/Static/Images/task32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,110 copying publiforge/Static/Images/task72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,110 copying publiforge/Static/Images/task72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,111 copying publiforge/Static/Images/task96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,111 copying publiforge/Static/Images/up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,112 copying publiforge/Static/Images/user.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,112 copying publiforge/Static/Images/user22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,113 copying publiforge/Static/Images/user32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,113 copying publiforge/Static/Images/user_pre.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,114 copying publiforge/Static/Images/valid-xhtml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,114 copying publiforge/Static/Images/value.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,115 copying publiforge/Static/Images/value22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,115 copying publiforge/Static/Images/value32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,116 copying publiforge/Static/Images/vcss.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,116 copying publiforge/Static/Images/wait_build.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,117 copying publiforge/Static/Images/wait_slow.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,117 copying publiforge/Static/Images/wait_synchro.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,118 copying publiforge/Static/Images/wcag1aa.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T10:44:20,118 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,118 copying publiforge/Static/Images/MimeTypes/css.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,119 copying publiforge/Static/Images/MimeTypes/csv.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,119 copying publiforge/Static/Images/MimeTypes/epub+zip.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,120 copying publiforge/Static/Images/MimeTypes/folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,120 copying publiforge/Static/Images/MimeTypes/font-woff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,121 copying publiforge/Static/Images/MimeTypes/gif.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,122 copying publiforge/Static/Images/MimeTypes/html.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,122 copying publiforge/Static/Images/MimeTypes/indesign-idml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,123 copying publiforge/Static/Images/MimeTypes/indesign-indd.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,123 copying publiforge/Static/Images/MimeTypes/javascript.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,124 copying publiforge/Static/Images/MimeTypes/jpeg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,124 copying publiforge/Static/Images/MimeTypes/mp4.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,125 copying publiforge/Static/Images/MimeTypes/mpeg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,125 copying publiforge/Static/Images/MimeTypes/msword.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,126 copying publiforge/Static/Images/MimeTypes/octet-stream.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,126 copying publiforge/Static/Images/MimeTypes/ogg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,127 copying publiforge/Static/Images/MimeTypes/pdf.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,127 copying publiforge/Static/Images/MimeTypes/plain.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,128 copying publiforge/Static/Images/MimeTypes/png.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,128 copying publiforge/Static/Images/MimeTypes/postscript.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,129 copying publiforge/Static/Images/MimeTypes/relaxng.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,129 copying publiforge/Static/Images/MimeTypes/svg+xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,130 copying publiforge/Static/Images/MimeTypes/tiff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,130 copying publiforge/Static/Images/MimeTypes/unknown.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,131 copying publiforge/Static/Images/MimeTypes/vnd.ms-excel.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,131 copying publiforge/Static/Images/MimeTypes/vnd.ms-opentype.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,132 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.spreadsheet.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,132 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.text.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,133 copying publiforge/Static/Images/MimeTypes/x-msdos-program.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,133 copying publiforge/Static/Images/MimeTypes/x-msvideo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,134 copying publiforge/Static/Images/MimeTypes/x-python.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,134 copying publiforge/Static/Images/MimeTypes/x-shockwave-flash.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,135 copying publiforge/Static/Images/MimeTypes/x-tar.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,135 copying publiforge/Static/Images/MimeTypes/x-wav.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,136 copying publiforge/Static/Images/MimeTypes/xml-dtd.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,136 copying publiforge/Static/Images/MimeTypes/xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,137 copying publiforge/Static/Images/MimeTypes/zip.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T10:44:20,137 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,138 copying publiforge/Static/Js/base.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,138 copying publiforge/Static/Js/bld_progress.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,139 copying publiforge/Static/Js/bld_results.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,139 copying publiforge/Static/Js/bld_view.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,140 copying publiforge/Static/Js/codemirror.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,141 copying publiforge/Static/Js/codemirror4ini.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,142 copying publiforge/Static/Js/codemirror4xml.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,142 copying publiforge/Static/Js/codemirror_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,143 copying publiforge/Static/Js/jquery.cookie.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,143 copying publiforge/Static/Js/jquery.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,144 copying publiforge/Static/Js/prc_edit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,145 copying publiforge/Static/Js/stg_browse.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,145 copying publiforge/Static/Js/stg_edit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,146 copying publiforge/Static/Js/stg_index.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,146 copying publiforge/Static/Js/tsk_index.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T10:44:20,147 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T10:44:20,147 copying publiforge/Static/Js/Tests/index.html -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T10:44:20,147 copying publiforge/Static/Js/Tests/qunit.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T10:44:20,148 copying publiforge/Static/Js/Tests/qunit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T10:44:20,149 copying publiforge/Static/Js/Tests/tests.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T10:44:20,150 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Css 2025-09-08T10:44:20,150 copying publiforge/Storages~/DataHg/Css/prismallia.css -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Css 2025-09-08T10:44:20,150 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,151 copying publiforge/Storages~/DataHg/Images/butterfly.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,151 copying publiforge/Storages~/DataHg/Images/lanturlu.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,152 copying publiforge/Storages~/DataHg/Images/parrot.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,153 copying publiforge/Storages~/DataHg/Images/prismallia.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,154 copying publiforge/Storages~/DataHg/Images/pulse.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,154 copying publiforge/Storages~/DataHg/Images/pulse_devel.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,155 copying publiforge/Storages~/DataHg/Images/vitruvian_man.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,155 copying publiforge/Storages~/DataHg/Images/vitruvian_man.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Images 2025-09-08T10:44:20,160 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Ini 2025-09-08T10:44:20,160 copying publiforge/Storages~/DataHg/Ini/leprisme4xhtml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Ini 2025-09-08T10:44:20,160 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature 2025-09-08T10:44:20,161 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/balade_nature.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature 2025-09-08T10:44:20,162 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/balade_nature.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature 2025-09-08T10:44:20,162 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/balade_nature_rich.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature 2025-09-08T10:44:20,163 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Audios 2025-09-08T10:44:20,163 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Audios/balade_nature_003_voice.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Audios 2025-09-08T10:44:20,164 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Audios/balade_nature_004_voice.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Audios 2025-09-08T10:44:20,164 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Css 2025-09-08T10:44:20,164 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Css/balade_nature.css -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Css 2025-09-08T10:44:20,165 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Css/balade_nature_fonts.css -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Css 2025-09-08T10:44:20,165 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,166 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/anim_chardon.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,166 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/anim_grenouille1.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,167 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/anim_grenouille2.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,168 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/anim_grenouille3.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,168 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/anim_trefle.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,169 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_002.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,170 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_003.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,172 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_003.svg.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,175 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_003_rich.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,177 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_004.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,179 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_004.svg.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,182 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_004_rich.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,185 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_005.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,187 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_005.svg.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,189 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_006.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,192 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_006.svg.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,194 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_cover.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,197 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/balade_nature_rich_cover.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,201 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/grenouille.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,201 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/zoom_herisson.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,202 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Images/zoom_oiseau.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Images 2025-09-08T10:44:20,204 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Jpeg 2025-09-08T10:44:20,204 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Jpeg/balade_nature1.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Jpeg 2025-09-08T10:44:20,206 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Js 2025-09-08T10:44:20,206 copying publiforge/Storages~/DataHg/Pdf/BaladeNature/Js/balade_nature.js -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/BaladeNature/Js 2025-09-08T10:44:20,206 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/Lextenso 2025-09-08T10:44:20,207 copying publiforge/Storages~/DataHg/Pdf/Lextenso/9782297026642_extract.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/Lextenso 2025-09-08T10:44:20,207 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/Lextenso/Images 2025-09-08T10:44:20,207 copying publiforge/Storages~/DataHg/Pdf/Lextenso/Images/9782297026642_cover.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Pdf/Lextenso/Images 2025-09-08T10:44:20,209 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts 2025-09-08T10:44:20,209 copying publiforge/Storages~/DataHg/Texts/constante neper.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts 2025-09-08T10:44:20,210 copying publiforge/Storages~/DataHg/Texts/pi.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts 2025-09-08T10:44:20,210 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/LaFontaine 2025-09-08T10:44:20,210 copying publiforge/Storages~/DataHg/Texts/LaFontaine/le_chêne_et_le_roseau.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/LaFontaine 2025-09-08T10:44:20,211 copying publiforge/Storages~/DataHg/Texts/LaFontaine/le_coche_et_la_mouche.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/LaFontaine 2025-09-08T10:44:20,212 copying publiforge/Storages~/DataHg/Texts/LaFontaine/le_loup_et_le_chien.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/LaFontaine 2025-09-08T10:44:20,212 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/Écrits/XIXe 2025-09-08T10:44:20,212 copying publiforge/Storages~/DataHg/Texts/Écrits/XIXe/hugo.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/Écrits/XIXe 2025-09-08T10:44:20,213 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/Écrits/XXe 2025-09-08T10:44:20,213 copying publiforge/Storages~/DataHg/Texts/Écrits/XXe/de saint-exupéry.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/Écrits/XXe 2025-09-08T10:44:20,214 copying publiforge/Storages~/DataHg/Texts/Écrits/XXe/ormesson.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Texts/Écrits/XXe 2025-09-08T10:44:20,214 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/DTBook 2025-09-08T10:44:20,215 copying publiforge/Storages~/DataHg/Xml/DTBook/areyoureadyv3.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/DTBook 2025-09-08T10:44:20,216 copying publiforge/Storages~/DataHg/Xml/DTBook/cspla.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/DTBook 2025-09-08T10:44:20,219 copying publiforge/Storages~/DataHg/Xml/DTBook/greatpainters.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/DTBook 2025-09-08T10:44:20,220 copying publiforge/Storages~/DataHg/Xml/DTBook/le_canard_enchaine_20140416.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/DTBook 2025-09-08T10:44:20,220 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/DocBook5 2025-09-08T10:44:20,221 copying publiforge/Storages~/DataHg/Xml/DocBook5/docbook5-section.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/DocBook5 2025-09-08T10:44:20,221 copying publiforge/Storages~/DataHg/Xml/DocBook5/schemas.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/DocBook5 2025-09-08T10:44:20,222 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/LG 2025-09-08T10:44:20,222 copying publiforge/Storages~/DataHg/Xml/LG/a_capella.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/LG 2025-09-08T10:44:20,225 copying publiforge/Storages~/DataHg/Xml/LG/schemas.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/LG 2025-09-08T10:44:20,226 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/Onix 2025-09-08T10:44:20,226 copying publiforge/Storages~/DataHg/Xml/Onix/les_miserables.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/Onix 2025-09-08T10:44:20,227 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/Other 2025-09-08T10:44:20,227 copying publiforge/Storages~/DataHg/Xml/Other/mega_monster_v1.5_1.2.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/Other 2025-09-08T10:44:20,228 copying publiforge/Storages~/DataHg/Xml/Other/meta.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/DataHg/Xml/Other 2025-09-08T10:44:20,228 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents 2025-09-08T10:44:20,229 copying publiforge/Storages~/Publidoc/Data/Documents/les_miserables.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents 2025-09-08T10:44:20,229 copying publiforge/Storages~/Publidoc/Data/Documents/torture_test.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents 2025-09-08T10:44:20,230 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,230 copying publiforge/Storages~/Publidoc/Data/Documents/Images/big_bug_bunny_trailer.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,232 copying publiforge/Storages~/Publidoc/Data/Documents/Images/chicken_chair.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,233 copying publiforge/Storages~/Publidoc/Data/Documents/Images/cosette.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,234 copying publiforge/Storages~/Publidoc/Data/Documents/Images/culdelampe.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,235 copying publiforge/Storages~/Publidoc/Data/Documents/Images/f-gcru.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,237 copying publiforge/Storages~/Publidoc/Data/Documents/Images/footer.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,238 copying publiforge/Storages~/Publidoc/Data/Documents/Images/header.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,238 copying publiforge/Storages~/Publidoc/Data/Documents/Images/les_miserables_cover.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,240 copying publiforge/Storages~/Publidoc/Data/Documents/Images/plane.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,241 copying publiforge/Storages~/Publidoc/Data/Documents/Images/prismallia_logo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,241 copying publiforge/Storages~/Publidoc/Data/Documents/Images/publiforge_logo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,242 copying publiforge/Storages~/Publidoc/Data/Documents/Images/torture_test_cover.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,243 copying publiforge/Storages~/Publidoc/Data/Documents/Images/zoom_oil.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Documents/Images 2025-09-08T10:44:20,243 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Glossary 2025-09-08T10:44:20,244 copying publiforge/Storages~/Publidoc/Data/Glossary/english.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Glossary 2025-09-08T10:44:20,244 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Metadata 2025-09-08T10:44:20,244 copying publiforge/Storages~/Publidoc/Data/Metadata/metadatas.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Metadata 2025-09-08T10:44:20,245 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,245 copying publiforge/Storages~/Publidoc/Data/Quiz/blanks-choices.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,246 copying publiforge/Storages~/Publidoc/Data/Quiz/blanks-fill.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,246 copying publiforge/Storages~/Publidoc/Data/Quiz/blanks-fill_strict.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,247 copying publiforge/Storages~/Publidoc/Data/Quiz/blanks-fill_variant.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,247 copying publiforge/Storages~/Publidoc/Data/Quiz/blanks-media.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,248 copying publiforge/Storages~/Publidoc/Data/Quiz/blanks-select.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,248 copying publiforge/Storages~/Publidoc/Data/Quiz/blanks-select_dropzone.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,249 copying publiforge/Storages~/Publidoc/Data/Quiz/blanks-select_multiple.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,249 copying publiforge/Storages~/Publidoc/Data/Quiz/categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,250 copying publiforge/Storages~/Publidoc/Data/Quiz/categories_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,250 copying publiforge/Storages~/Publidoc/Data/Quiz/categories_multiple.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,251 copying publiforge/Storages~/Publidoc/Data/Quiz/choices-check.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,251 copying publiforge/Storages~/Publidoc/Data/Quiz/choices-check_audio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,252 copying publiforge/Storages~/Publidoc/Data/Quiz/choices-radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,253 copying publiforge/Storages~/Publidoc/Data/Quiz/choices-radio_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,253 copying publiforge/Storages~/Publidoc/Data/Quiz/choices.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,254 copying publiforge/Storages~/Publidoc/Data/Quiz/composite.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,254 copying publiforge/Storages~/Publidoc/Data/Quiz/correct-line.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,255 copying publiforge/Storages~/Publidoc/Data/Quiz/matching.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,255 copying publiforge/Storages~/Publidoc/Data/Quiz/matching_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,256 copying publiforge/Storages~/Publidoc/Data/Quiz/matching_multiple.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,256 copying publiforge/Storages~/Publidoc/Data/Quiz/pointing-categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,257 copying publiforge/Storages~/Publidoc/Data/Quiz/pointing.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,257 copying publiforge/Storages~/Publidoc/Data/Quiz/pointing_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,258 copying publiforge/Storages~/Publidoc/Data/Quiz/pointing_radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,258 copying publiforge/Storages~/Publidoc/Data/Quiz/production.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,259 copying publiforge/Storages~/Publidoc/Data/Quiz/sort.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,260 copying publiforge/Storages~/Publidoc/Data/Quiz/sort_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,260 copying publiforge/Storages~/Publidoc/Data/Quiz/wordsearch.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz 2025-09-08T10:44:20,260 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,261 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/bingo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,262 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/bingo_green.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,263 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/bingo_red.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,264 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/blanks-select_dropzonei01.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,265 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/chat.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,266 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/chaton.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,268 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/choices-q01i01.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,269 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/choices-q02i01.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,271 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/choices-radio_imagei00.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,271 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/choices-radio_imagei01.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,272 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/choices-radio_imagei02.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,272 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/choices-radio_imagei03.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,273 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/couleuvre.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,274 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/drapeau1.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,275 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/drapeau2.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,275 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/drapeau3.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,276 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/elephant.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,279 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/elephanteau.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,281 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/hippocampe.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,283 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/instruments.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,286 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/lezard.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,288 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/lievre.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,290 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/lion.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,292 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/lionceau.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,295 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/loup.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,297 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/lynx.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,299 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/ours.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,302 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/ourson.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,304 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/rouge-gorge.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,307 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/tigre.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,309 copying publiforge/Storages~/Publidoc/Data/Quiz/Images/tigreau.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Quiz/Images 2025-09-08T10:44:20,311 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Sets 2025-09-08T10:44:20,311 copying publiforge/Storages~/Publidoc/Data/Sets/composition.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Sets 2025-09-08T10:44:20,312 copying publiforge/Storages~/Publidoc/Data/Sets/proba.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Sets 2025-09-08T10:44:20,312 copying publiforge/Storages~/Publidoc/Data/Sets/quiz.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Sets 2025-09-08T10:44:20,313 copying publiforge/Storages~/Publidoc/Data/Sets/selection1.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Sets 2025-09-08T10:44:20,313 copying publiforge/Storages~/Publidoc/Data/Sets/selection2.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Sets 2025-09-08T10:44:20,314 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Sets/Images 2025-09-08T10:44:20,314 copying publiforge/Storages~/Publidoc/Data/Sets/Images/composition.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Sets/Images 2025-09-08T10:44:20,315 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,315 copying publiforge/Storages~/Publidoc/Data/Topics/a380.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,316 copying publiforge/Storages~/Publidoc/Data/Topics/cals.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,316 copying publiforge/Storages~/Publidoc/Data/Topics/centre_pompidou.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,317 copying publiforge/Storages~/Publidoc/Data/Topics/chasseurs.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,317 copying publiforge/Storages~/Publidoc/Data/Topics/maths.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,318 copying publiforge/Storages~/Publidoc/Data/Topics/portugal_ue.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,318 copying publiforge/Storages~/Publidoc/Data/Topics/proba01.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,319 copying publiforge/Storages~/Publidoc/Data/Topics/états-unis_les faucons.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics 2025-09-08T10:44:20,319 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics/Alternatives 2025-09-08T10:44:20,320 copying publiforge/Storages~/Publidoc/Data/Topics/Alternatives/rolls_phantom.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics/Alternatives 2025-09-08T10:44:20,320 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics/Images 2025-09-08T10:44:20,320 copying publiforge/Storages~/Publidoc/Data/Topics/Images/a380.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics/Images 2025-09-08T10:44:20,322 copying publiforge/Storages~/Publidoc/Data/Topics/Images/a380.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics/Images 2025-09-08T10:44:20,324 copying publiforge/Storages~/Publidoc/Data/Topics/Images/centre_pompidou.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics/Images 2025-09-08T10:44:20,325 copying publiforge/Storages~/Publidoc/Data/Topics/Images/chasseurs.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Data/Topics/Images 2025-09-08T10:44:20,327 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Css 2025-09-08T10:44:20,327 copying publiforge/Storages~/Publidoc/Xxe/Css/publidoc.css -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Css 2025-09-08T10:44:20,327 copying publiforge/Storages~/Publidoc/Xxe/Css/publiquiz.css -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Css 2025-09-08T10:44:20,328 copying publiforge/Storages~/Publidoc/Xxe/Css/top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Css 2025-09-08T10:44:20,329 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,329 copying publiforge/Storages~/Publidoc/Xxe/Templates/publidoc_document.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,329 copying publiforge/Storages~/Publidoc/Xxe/Templates/publidoc_topic.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,330 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_blanks-fill.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,330 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_blanks-select.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,331 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,331 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_categories_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,332 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_choices-check.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,332 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_choices-check_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,333 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_choices-radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,333 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_choices-radio_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,334 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_composite.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,334 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_matching.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,335 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_matching_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,336 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_point.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,336 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_production.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,337 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_sort.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,337 copying publiforge/Storages~/Publidoc/Xxe/Templates/publiquiz_sort_image.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Publidoc/Xxe/Templates 2025-09-08T10:44:20,338 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/ResultHg 2025-09-08T10:44:20,338 copying publiforge/Storages~/ResultHg/parrot.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/ResultHg 2025-09-08T10:44:20,339 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/ResultHg/Xml 2025-09-08T10:44:20,339 copying publiforge/Storages~/ResultHg/Xml/prince_belge.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/ResultHg/Xml 2025-09-08T10:44:20,340 copying publiforge/Storages~/ResultHg/Xml/proba01.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/ResultHg/Xml 2025-09-08T10:44:20,340 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/ResultHg/Xml/Images 2025-09-08T10:44:20,340 copying publiforge/Storages~/ResultHg/Xml/Images/chasseurs.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/ResultHg/Xml/Images 2025-09-08T10:44:20,342 copying publiforge/Storages~/ResultHg/Xml/Images/prince_belge.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/ResultHg/Xml/Images 2025-09-08T10:44:20,343 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents 2025-09-08T10:44:20,343 copying publiforge/Storages~/Sandbox/Documents/les_miserables.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents 2025-09-08T10:44:20,344 copying publiforge/Storages~/Sandbox/Documents/torture_test.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents 2025-09-08T10:44:20,345 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,345 copying publiforge/Storages~/Sandbox/Documents/Images/big_bug_bunny_trailer.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,347 copying publiforge/Storages~/Sandbox/Documents/Images/chicken_chair.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,348 copying publiforge/Storages~/Sandbox/Documents/Images/cosette.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,349 copying publiforge/Storages~/Sandbox/Documents/Images/culdelampe.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,349 copying publiforge/Storages~/Sandbox/Documents/Images/f-gcru.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,351 copying publiforge/Storages~/Sandbox/Documents/Images/footer.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,352 copying publiforge/Storages~/Sandbox/Documents/Images/header.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,353 copying publiforge/Storages~/Sandbox/Documents/Images/les_miserables_cover.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,354 copying publiforge/Storages~/Sandbox/Documents/Images/plane.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,355 copying publiforge/Storages~/Sandbox/Documents/Images/prismallia_logo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,356 copying publiforge/Storages~/Sandbox/Documents/Images/publiforge_logo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,356 copying publiforge/Storages~/Sandbox/Documents/Images/torture_test_cover.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,357 copying publiforge/Storages~/Sandbox/Documents/Images/zoom_oil.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Documents/Images 2025-09-08T10:44:20,358 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Glossary 2025-09-08T10:44:20,358 copying publiforge/Storages~/Sandbox/Glossary/glossary.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Glossary 2025-09-08T10:44:20,358 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Images 2025-09-08T10:44:20,359 copying publiforge/Storages~/Sandbox/Images/butterfly.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Images 2025-09-08T10:44:20,359 copying publiforge/Storages~/Sandbox/Images/code-1768379.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Images 2025-09-08T10:44:20,361 copying publiforge/Storages~/Sandbox/Images/lanturlu.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Images 2025-09-08T10:44:20,362 copying publiforge/Storages~/Sandbox/Images/parrot.png -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Images 2025-09-08T10:44:20,366 copying publiforge/Storages~/Sandbox/Images/pulse_devel.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Images 2025-09-08T10:44:20,367 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Sets 2025-09-08T10:44:20,367 copying publiforge/Storages~/Sandbox/Sets/composition.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Sets 2025-09-08T10:44:20,368 copying publiforge/Storages~/Sandbox/Sets/proba.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Sets 2025-09-08T10:44:20,368 copying publiforge/Storages~/Sandbox/Sets/quiz.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Sets 2025-09-08T10:44:20,369 copying publiforge/Storages~/Sandbox/Sets/selection1.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Sets 2025-09-08T10:44:20,369 copying publiforge/Storages~/Sandbox/Sets/selection2.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Sets 2025-09-08T10:44:20,370 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Sets/Images 2025-09-08T10:44:20,370 copying publiforge/Storages~/Sandbox/Sets/Images/composition.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Sets/Images 2025-09-08T10:44:20,371 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics 2025-09-08T10:44:20,371 copying publiforge/Storages~/Sandbox/Topics/a380.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics 2025-09-08T10:44:20,372 copying publiforge/Storages~/Sandbox/Topics/chasseurs.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics 2025-09-08T10:44:20,372 copying publiforge/Storages~/Sandbox/Topics/maths.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics 2025-09-08T10:44:20,373 copying publiforge/Storages~/Sandbox/Topics/portugal_ue.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics 2025-09-08T10:44:20,373 copying publiforge/Storages~/Sandbox/Topics/proba01.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics 2025-09-08T10:44:20,374 copying publiforge/Storages~/Sandbox/Topics/états-unis_les faucons.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics 2025-09-08T10:44:20,374 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics/Alternatives 2025-09-08T10:44:20,375 copying publiforge/Storages~/Sandbox/Topics/Alternatives/rolls_phantom.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics/Alternatives 2025-09-08T10:44:20,375 creating build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics/Images 2025-09-08T10:44:20,375 copying publiforge/Storages~/Sandbox/Topics/Images/a380.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics/Images 2025-09-08T10:44:20,377 copying publiforge/Storages~/Sandbox/Topics/Images/a380.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics/Images 2025-09-08T10:44:20,378 copying publiforge/Storages~/Sandbox/Topics/Images/centre_pompidou.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics/Images 2025-09-08T10:44:20,380 copying publiforge/Storages~/Sandbox/Topics/Images/chasseurs.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Storages~/Sandbox/Topics/Images 2025-09-08T10:44:20,381 creating build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,381 copying publiforge/Templates/base.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,382 copying publiforge/Templates/bld_launch.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,383 copying publiforge/Templates/bld_output.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,383 copying publiforge/Templates/bld_pack.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,384 copying publiforge/Templates/bld_processing.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,384 copying publiforge/Templates/bld_progress.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,385 copying publiforge/Templates/bld_results.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,385 copying publiforge/Templates/bld_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,386 copying publiforge/Templates/error.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,386 copying publiforge/Templates/fil_display.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,387 copying publiforge/Templates/fil_info.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,387 copying publiforge/Templates/fil_modify.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,388 copying publiforge/Templates/fil_search.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,388 copying publiforge/Templates/fil_vcs_params.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,389 copying publiforge/Templates/files_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,389 copying publiforge/Templates/files_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,390 copying publiforge/Templates/flash.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,390 copying publiforge/Templates/grp_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,391 copying publiforge/Templates/grp_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,391 copying publiforge/Templates/grp_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,392 copying publiforge/Templates/home.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,392 copying publiforge/Templates/idx_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,393 copying publiforge/Templates/idx_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,393 copying publiforge/Templates/idx_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,394 copying publiforge/Templates/job_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,394 copying publiforge/Templates/job_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,395 copying publiforge/Templates/job_log.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,395 copying publiforge/Templates/job_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,396 copying publiforge/Templates/login.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,396 copying publiforge/Templates/maintenance.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,397 copying publiforge/Templates/mbr_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,397 copying publiforge/Templates/mbr_groups_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,398 copying publiforge/Templates/mbr_groups_paging.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,398 copying publiforge/Templates/mbr_groups_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,399 copying publiforge/Templates/mbr_paging.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,399 copying publiforge/Templates/mbr_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,400 copying publiforge/Templates/pck_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,400 copying publiforge/Templates/pck_events.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,401 copying publiforge/Templates/pck_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,402 copying publiforge/Templates/pck_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,402 copying publiforge/Templates/prc_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,403 copying publiforge/Templates/prc_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,403 copying publiforge/Templates/prj_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,404 copying publiforge/Templates/prj_dashboard.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,404 copying publiforge/Templates/prj_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,405 copying publiforge/Templates/prj_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,405 copying publiforge/Templates/prj_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,406 copying publiforge/Templates/rol_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,406 copying publiforge/Templates/rol_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,407 copying publiforge/Templates/sit_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,407 copying publiforge/Templates/stg_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,408 copying publiforge/Templates/stg_browse.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,408 copying publiforge/Templates/stg_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,409 copying publiforge/Templates/stg_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,409 copying publiforge/Templates/stg_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,410 copying publiforge/Templates/tsk_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,410 copying publiforge/Templates/tsk_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,411 copying publiforge/Templates/tsk_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,412 copying publiforge/Templates/usr_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,412 copying publiforge/Templates/usr_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,413 copying publiforge/Templates/usr_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T10:44:20,413 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge 2025-09-08T10:44:20,413 copying publiforge/scaffolds/Front/PubliForge/development.ini_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge 2025-09-08T10:44:20,414 copying publiforge/scaffolds/Front/PubliForge/pf+package+.ini_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge 2025-09-08T10:44:20,415 copying publiforge/scaffolds/Front/PubliForge/pf+package+.wsgi_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge 2025-09-08T10:44:20,415 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Apache 2025-09-08T10:44:20,415 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-08T10:44:20,416 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2025-09-08T10:44:20,416 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/hgwebdir.conf_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2025-09-08T10:44:20,417 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/hgwebdir.wsgi_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2025-09-08T10:44:20,417 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/users_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2025-09-08T10:44:20,418 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Projects 2025-09-08T10:44:20,418 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-08T10:44:20,418 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2025-09-08T10:44:20,419 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-08T10:44:20,419 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-08T10:44:20,420 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-08T10:44:20,420 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-08T10:44:20,421 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Configuration/Users 2025-09-08T10:44:20,421 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-08T10:44:20,422 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static 2025-09-08T10:44:20,422 copying publiforge/scaffolds/Front/PubliForge/Static/favicon.ico -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static 2025-09-08T10:44:20,422 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static/Css 2025-09-08T10:44:20,422 copying publiforge/scaffolds/Front/PubliForge/Static/Css/+package+.css_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static/Css 2025-09-08T10:44:20,423 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static/Images 2025-09-08T10:44:20,423 copying publiforge/scaffolds/Front/PubliForge/Static/Images/+package+.png -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/Front/PubliForge/Static/Images 2025-09-08T10:44:20,424 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme 2025-09-08T10:44:20,424 copying publiforge/scaffolds/LePrisme/+package+.pfprc.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme 2025-09-08T10:44:20,425 copying publiforge/scaffolds/LePrisme/leprisme.ini_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme 2025-09-08T10:44:20,425 copying publiforge/scaffolds/LePrisme/processor.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme 2025-09-08T10:44:20,426 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Templates 2025-09-08T10:44:20,426 copying publiforge/scaffolds/LePrisme/Templates/dummy1.txt -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Templates 2025-09-08T10:44:20,426 copying publiforge/scaffolds/LePrisme/Templates/dummy2.txt -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Templates 2025-09-08T10:44:20,427 copying publiforge/scaffolds/LePrisme/Templates/dummy3.txt -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Templates 2025-09-08T10:44:20,427 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Variables 2025-09-08T10:44:20,427 copying publiforge/scaffolds/LePrisme/Variables/+package+.pfvar.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Variables 2025-09-08T10:44:20,428 copying publiforge/scaffolds/LePrisme/Variables/+package+_available.pfvar.xml_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Variables 2025-09-08T10:44:20,429 copying publiforge/scaffolds/LePrisme/Variables/+package+_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/Variables 2025-09-08T10:44:20,429 creating build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/lib 2025-09-08T10:44:20,429 copying publiforge/scaffolds/LePrisme/lib/__init__.py_tmpl -> build/lib.linux-armv7l-cpython-313/publiforge/scaffolds/LePrisme/lib 2025-09-08T10:44:20,430 copying publiforge/tests/test.ini -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T10:44:20,430 creating build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T10:44:20,430 copying publiforge/tests/Data/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T10:44:20,431 copying publiforge/tests/Data/test.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T10:44:20,432 copying publiforge/lib/rsync/_librsync.c -> build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T10:44:20,438 running build_ext 2025-09-08T10:44:20,794 building 'publiforge.lib.rsync._librsync' extension 2025-09-08T10:44:20,795 creating build/temp.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T10:44:20,796 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-08T10:44:21,156 publiforge/lib/rsync/_librsync.c:26:10: fatal error: librsync.h: No such file or directory 2025-09-08T10:44:21,157 26 | #include 2025-09-08T10:44:21,157 | ^~~~~~~~~~~~ 2025-09-08T10:44:21,157 compilation terminated. 2025-09-08T10:44:21,160 error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1 2025-09-08T10:44:21,314 ERROR: python setup.py bdist_wheel exited with 1 2025-09-08T10:44:21,325 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2025-09-08T10:44:21,325 exec(compile('"'"''"'"''"'"' 2025-09-08T10:44:21,325 # This is -- a caller that pip uses to run setup.py 2025-09-08T10:44:21,325 # 2025-09-08T10:44:21,325 # - It imports setuptools before invoking setup.py, to enable projects that directly 2025-09-08T10:44:21,325 # import from `distutils.core` to work with newer packaging standards. 2025-09-08T10:44:21,325 # - It provides a clear error message when setuptools is not installed. 2025-09-08T10:44:21,325 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2025-09-08T10:44:21,325 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2025-09-08T10:44:21,325 # manifest_maker: standard file '"'"'-c'"'"' not found". 2025-09-08T10:44:21,325 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2025-09-08T10:44:21,325 import os, sys, tokenize, traceback 2025-09-08T10:44:21,325 2025-09-08T10:44:21,325 try: 2025-09-08T10:44:21,325 import setuptools 2025-09-08T10:44:21,325 except ImportError: 2025-09-08T10:44:21,325 print( 2025-09-08T10:44:21,325 "ERROR: Can not execute `setup.py` since setuptools failed to import in " 2025-09-08T10:44:21,325 "the build environment with exception:", 2025-09-08T10:44:21,325 file=sys.stderr, 2025-09-08T10:44:21,325 ) 2025-09-08T10:44:21,325 traceback.print_exc() 2025-09-08T10:44:21,325 sys.exit(1) 2025-09-08T10:44:21,325 2025-09-08T10:44:21,325 __file__ = %r 2025-09-08T10:44:21,325 sys.argv[0] = __file__ 2025-09-08T10:44:21,325 2025-09-08T10:44:21,325 if os.path.exists(__file__): 2025-09-08T10:44:21,325 filename = __file__ 2025-09-08T10:44:21,325 with tokenize.open(__file__) as f: 2025-09-08T10:44:21,325 setup_py_code = f.read() 2025-09-08T10:44:21,325 else: 2025-09-08T10:44:21,325 filename = "" 2025-09-08T10:44:21,325 setup_py_code = "from setuptools import setup; setup()" 2025-09-08T10:44:21,325 2025-09-08T10:44:21,325 exec(compile(setup_py_code, filename, "exec")) 2025-09-08T10:44:21,325 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-6497a9jw/publiforge_cea0ad06fe8c4cb7916f9d8b29a21eb4/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-s16mzo7w[/] 2025-09-08T10:44:21,325 [bold magenta]cwd[/]: /tmp/pip-wheel-6497a9jw/publiforge_cea0ad06fe8c4cb7916f9d8b29a21eb4/ 2025-09-08T10:44:21,326 Building wheel for publiforge (setup.py): finished with status 'error' 2025-09-08T10:44:21,326 ERROR: Failed building wheel for publiforge 2025-09-08T10:44:21,327 Running setup.py clean for publiforge 2025-09-08T10:44:21,328 Running command python setup.py clean 2025-09-08T10:44:22,028 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T10:44:22,028 warnings.warn(msg) 2025-09-08T10:44:22,028 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T10:44:22,028 warnings.warn(msg) 2025-09-08T10:44:22,526 running clean 2025-09-08T10:44:22,675 removing 'build/temp.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T10:44:22,676 removing 'build/lib.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T10:44:22,736 'build/bdist.linux-armv7l' does not exist -- can't clean it 2025-09-08T10:44:22,736 'build/scripts-3.13' does not exist -- can't clean it 2025-09-08T10:44:22,736 removing 'build' 2025-09-08T10:44:22,849 Failed to build publiforge 2025-09-08T10:44:22,850 ERROR: Failed to build one or more wheels 2025-09-08T10:44:22,851 Exception information: 2025-09-08T10:44:22,851 Traceback (most recent call last): 2025-09-08T10:44:22,851 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper 2025-09-08T10:44:22,851 status = _inner_run() 2025-09-08T10:44:22,851 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run 2025-09-08T10:44:22,851 return self.run(options, args) 2025-09-08T10:44:22,851 ~~~~~~~~^^^^^^^^^^^^^^^ 2025-09-08T10:44:22,851 File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 68, in wrapper 2025-09-08T10:44:22,851 return func(self, options, args) 2025-09-08T10:44:22,851 File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line 180, in run 2025-09-08T10:44:22,851 raise CommandError("Failed to build one or more wheels") 2025-09-08T10:44:22,851 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2025-09-08T10:44:22,856 Removed build tracker: '/tmp/pip-build-tracker-0z8u64i3'