2025-09-08T01:31:59,285 Created temporary directory: /tmp/pip-build-tracker-byfjrlk1 2025-09-08T01:31:59,286 Initialized build tracking at /tmp/pip-build-tracker-byfjrlk1 2025-09-08T01:31:59,286 Created build tracker: /tmp/pip-build-tracker-byfjrlk1 2025-09-08T01:31:59,286 Entered build tracker: /tmp/pip-build-tracker-byfjrlk1 2025-09-08T01:31:59,287 Created temporary directory: /tmp/pip-wheel-tx12itpb 2025-09-08T01:31:59,290 Created temporary directory: /tmp/pip-ephem-wheel-cache-be1nfucr 2025-09-08T01:31:59,348 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-09-08T01:31:59,350 2 location(s) to search for versions of publiforge: 2025-09-08T01:31:59,350 * https://pypi.org/simple/publiforge/ 2025-09-08T01:31:59,350 * https://www.piwheels.org/simple/publiforge/ 2025-09-08T01:31:59,350 Fetching project page and analyzing links: https://pypi.org/simple/publiforge/ 2025-09-08T01:31:59,351 Getting page https://pypi.org/simple/publiforge/ 2025-09-08T01:31:59,352 Found index url https://pypi.org/simple/ 2025-09-08T01:31:59,421 Fetched page https://pypi.org/simple/publiforge/ as application/vnd.pypi.simple.v1+json 2025-09-08T01:31:59,423 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-08T01:31:59,423 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-08T01:31:59,423 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-08T01:31:59,423 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-08T01:31:59,424 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-08T01:31:59,424 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-08T01:31:59,424 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-08T01:31:59,424 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-08T01:31:59,425 Fetching project page and analyzing links: https://www.piwheels.org/simple/publiforge/ 2025-09-08T01:31:59,425 Getting page https://www.piwheels.org/simple/publiforge/ 2025-09-08T01:31:59,426 Found index url https://www.piwheels.org/simple/ 2025-09-08T01:31:59,530 Fetched page https://www.piwheels.org/simple/publiforge/ as text/html 2025-09-08T01:31:59,531 Skipping link: not a file: https://www.piwheels.org/simple/publiforge/ 2025-09-08T01:31:59,531 Skipping link: not a file: https://pypi.org/simple/publiforge/ 2025-09-08T01:31:59,556 Given no hashes to check 1 links for project 'publiforge': discarding no candidates 2025-09-08T01:31:59,557 Collecting publiforge==1.2 2025-09-08T01:31:59,558 Created temporary directory: /tmp/pip-unpack-erdq6ite 2025-09-08T01:31:59,715 Downloading PubliForge-1.2.tar.gz (7.3 MB) 2025-09-08T01:32:01,956 Added publiforge==1.2 from https://files.pythonhosted.org/packages/60/6a/084b0d0d919bddf8045a0ed312d5b877c5d3bd9e4e20109687d69b19dd1e/PubliForge-1.2.tar.gz to build tracker '/tmp/pip-build-tracker-byfjrlk1' 2025-09-08T01:32:01,957 Running setup.py (path:/tmp/pip-wheel-tx12itpb/publiforge_d63a48c6826a4e20b1860bd01fdef0f7/setup.py) egg_info for package publiforge 2025-09-08T01:32:01,958 Created temporary directory: /tmp/pip-pip-egg-info-ss4hkncm 2025-09-08T01:32:01,958 Preparing metadata (setup.py): started 2025-09-08T01:32:01,959 Running command python setup.py egg_info 2025-09-08T01:32:02,699 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T01:32:02,699 warnings.warn(msg) 2025-09-08T01:32:02,699 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T01:32:02,699 warnings.warn(msg) 2025-09-08T01:32:03,179 running egg_info 2025-09-08T01:32:03,253 creating /tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info 2025-09-08T01:32:03,253 writing /tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info/PKG-INFO 2025-09-08T01:32:03,254 writing dependency_links to /tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info/dependency_links.txt 2025-09-08T01:32:03,255 writing entry points to /tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info/entry_points.txt 2025-09-08T01:32:03,256 writing requirements to /tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info/requires.txt 2025-09-08T01:32:03,256 writing top-level names to /tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info/top_level.txt 2025-09-08T01:32:03,257 writing manifest file '/tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info/SOURCES.txt' 2025-09-08T01:32:03,567 reading manifest file '/tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info/SOURCES.txt' 2025-09-08T01:32:03,567 reading manifest template 'MANIFEST.in' 2025-09-08T01:32:03,569 warning: no files found matching '*.rst' 2025-09-08T01:32:03,998 writing manifest file '/tmp/pip-pip-egg-info-ss4hkncm/PubliForge.egg-info/SOURCES.txt' 2025-09-08T01:32:04,112 Preparing metadata (setup.py): finished with status 'done' 2025-09-08T01:32:04,117 Source in /tmp/pip-wheel-tx12itpb/publiforge_d63a48c6826a4e20b1860bd01fdef0f7 has version 1.2, which satisfies requirement publiforge==1.2 from https://files.pythonhosted.org/packages/60/6a/084b0d0d919bddf8045a0ed312d5b877c5d3bd9e4e20109687d69b19dd1e/PubliForge-1.2.tar.gz 2025-09-08T01:32:04,117 Removed publiforge==1.2 from https://files.pythonhosted.org/packages/60/6a/084b0d0d919bddf8045a0ed312d5b877c5d3bd9e4e20109687d69b19dd1e/PubliForge-1.2.tar.gz from build tracker '/tmp/pip-build-tracker-byfjrlk1' 2025-09-08T01:32:04,127 Created temporary directory: /tmp/pip-unpack-8uekrne8 2025-09-08T01:32:04,128 Created temporary directory: /tmp/pip-unpack-twc00h_z 2025-09-08T01:32:04,128 Building wheels for collected packages: publiforge 2025-09-08T01:32:04,130 Created temporary directory: /tmp/pip-wheel-kufnxl7n 2025-09-08T01:32:04,130 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-08T01:32:04,131 Building wheel for publiforge (setup.py): started 2025-09-08T01:32:04,132 Destination directory: /tmp/pip-wheel-kufnxl7n 2025-09-08T01:32:04,133 Running command python setup.py bdist_wheel 2025-09-08T01:32:04,823 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T01:32:04,823 warnings.warn(msg) 2025-09-08T01:32:04,824 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T01:32:04,824 warnings.warn(msg) 2025-09-08T01:32:05,219 running bdist_wheel 2025-09-08T01:32:05,585 running build 2025-09-08T01:32:05,585 running build_py 2025-09-08T01:32:05,662 creating build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T01:32:05,662 copying publiforge/initialize.py -> build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T01:32:05,663 copying publiforge/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge 2025-09-08T01:32:05,664 creating build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,664 copying publiforge/tests/test_views_security.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,665 copying publiforge/tests/test_scripts_pfbuild.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,665 copying publiforge/tests/test_models_users.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,666 copying publiforge/tests/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,666 copying publiforge/tests/test_lib_xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,667 copying publiforge/tests/test_views_project.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,667 copying publiforge/tests/test_lib_utils.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,668 copying publiforge/tests/test_models_processors.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,668 copying publiforge/tests/test_lib_widget.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,669 copying publiforge/tests/test_lib_form.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,669 copying publiforge/tests/test_models_projects.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,670 copying publiforge/tests/test_models_storages.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,670 copying publiforge/tests/test_models_groups.py -> build/lib.linux-armv7l-cpython-313/publiforge/tests 2025-09-08T01:32:05,671 creating build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,672 copying publiforge/models/processings.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,672 copying publiforge/models/tasks.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,673 copying publiforge/models/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,673 copying publiforge/models/indexers.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,674 copying publiforge/models/roles.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,674 copying publiforge/models/groups.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,675 copying publiforge/models/projects.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,675 copying publiforge/models/processors.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,676 copying publiforge/models/storages.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,676 copying publiforge/models/packs.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,677 copying publiforge/models/users.py -> build/lib.linux-armv7l-cpython-313/publiforge/models 2025-09-08T01:32:05,678 creating build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,678 copying publiforge/lib/form.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,679 copying publiforge/lib/viewutils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,680 copying publiforge/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,680 copying publiforge/lib/widget.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,681 copying publiforge/lib/packutils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,681 copying publiforge/lib/handler.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,682 copying publiforge/lib/xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,682 copying publiforge/lib/utils.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,683 copying publiforge/lib/debug.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib 2025-09-08T01:32:05,684 creating build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,684 copying publiforge/views/storage.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,685 copying publiforge/views/site.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,686 copying publiforge/views/processing.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,686 copying publiforge/views/task.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,687 copying publiforge/views/maestro.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,687 copying publiforge/views/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,688 copying publiforge/views/xmlrpc.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,688 copying publiforge/views/home.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,689 copying publiforge/views/indexer.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,689 copying publiforge/views/group.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,690 copying publiforge/views/user.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,691 copying publiforge/views/role.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,691 copying publiforge/views/build.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,692 copying publiforge/views/pack.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,692 copying publiforge/views/security.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,693 copying publiforge/views/file.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,694 copying publiforge/views/project.py -> build/lib.linux-armv7l-cpython-313/publiforge/views 2025-09-08T01:32:05,695 creating build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T01:32:05,695 copying publiforge/scripts/pfminify.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T01:32:05,695 copying publiforge/scripts/pfimage2svg.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T01:32:05,696 copying publiforge/scripts/pfbackup.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T01:32:05,696 copying publiforge/scripts/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T01:32:05,697 copying publiforge/scripts/pfpopulate.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T01:32:05,697 copying publiforge/scripts/pftexmath.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T01:32:05,698 copying publiforge/scripts/pfbuild.py -> build/lib.linux-armv7l-cpython-313/publiforge/scripts 2025-09-08T01:32:05,699 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T01:32:05,699 copying publiforge/lib/vcs/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T01:32:05,700 copying publiforge/lib/vcs/svn.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T01:32:05,700 copying publiforge/lib/vcs/hgsvn.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T01:32:05,701 copying publiforge/lib/vcs/hg.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/vcs 2025-09-08T01:32:05,702 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T01:32:05,702 copying publiforge/lib/opener/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T01:32:05,702 copying publiforge/lib/opener/xml.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T01:32:05,703 copying publiforge/lib/opener/image.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T01:32:05,704 copying publiforge/lib/opener/ini.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/opener 2025-09-08T01:32:05,704 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T01:32:05,705 copying publiforge/lib/build/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T01:32:05,705 copying publiforge/lib/build/front.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T01:32:05,706 copying publiforge/lib/build/agent.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/build 2025-09-08T01:32:05,707 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T01:32:05,707 copying publiforge/lib/rsync/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T01:32:05,708 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor 2025-09-08T01:32:05,708 copying publiforge/lib/processor/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor 2025-09-08T01:32:05,709 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/publiseter 2025-09-08T01:32:05,709 copying publiforge/lib/processor/publiseter/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/publiseter 2025-09-08T01:32:05,710 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T01:32:05,710 copying publiforge/lib/processor/leprisme/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T01:32:05,711 copying publiforge/lib/processor/leprisme/publiset.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T01:32:05,711 copying publiforge/lib/processor/leprisme/containers.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T01:32:05,712 copying publiforge/lib/processor/leprisme/transform.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T01:32:05,712 copying publiforge/lib/processor/leprisme/iniscript.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/leprisme 2025-09-08T01:32:05,713 creating build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/validator 2025-09-08T01:32:05,713 copying publiforge/lib/processor/validator/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/lib/processor/validator 2025-09-08T01:32:05,714 running egg_info 2025-09-08T01:32:05,789 writing PubliForge.egg-info/PKG-INFO 2025-09-08T01:32:05,790 writing dependency_links to PubliForge.egg-info/dependency_links.txt 2025-09-08T01:32:05,791 writing entry points to PubliForge.egg-info/entry_points.txt 2025-09-08T01:32:05,792 writing requirements to PubliForge.egg-info/requires.txt 2025-09-08T01:32:05,792 writing top-level names to PubliForge.egg-info/top_level.txt 2025-09-08T01:32:05,874 reading manifest file 'PubliForge.egg-info/SOURCES.txt' 2025-09-08T01:32:05,908 reading manifest template 'MANIFEST.in' 2025-09-08T01:32:05,910 warning: no files found matching '*.rst' 2025-09-08T01:32:06,346 writing manifest file 'PubliForge.egg-info/SOURCES.txt' 2025-09-08T01:32:06,348 /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-08T01:32:06,348 !! 2025-09-08T01:32:06,348 ******************************************************************************** 2025-09-08T01:32:06,348 ############################ 2025-09-08T01:32:06,348 # Package would be ignored # 2025-09-08T01:32:06,348 ############################ 2025-09-08T01:32:06,349 Python recognizes 'publiforge.Locale' as an importable package[^1], 2025-09-08T01:32:06,349 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,349 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,349 package, please make sure that 'publiforge.Locale' is explicitly added 2025-09-08T01:32:06,349 to the `packages` configuration field. 2025-09-08T01:32:06,349 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,349 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,349 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,350 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,350 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,350 If you don't want 'publiforge.Locale' to be distributed and are 2025-09-08T01:32:06,350 already explicitly excluding 'publiforge.Locale' via 2025-09-08T01:32:06,350 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,350 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,350 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,350 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,351 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,351 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,351 even if it does not contain any `.py` files. 2025-09-08T01:32:06,351 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,351 directory, all directories are treated like packages. 2025-09-08T01:32:06,351 ******************************************************************************** 2025-09-08T01:32:06,351 !! 2025-09-08T01:32:06,352 check.warn(importable) 2025-09-08T01:32:06,352 /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-08T01:32:06,352 !! 2025-09-08T01:32:06,352 ******************************************************************************** 2025-09-08T01:32:06,352 ############################ 2025-09-08T01:32:06,352 # Package would be ignored # 2025-09-08T01:32:06,352 ############################ 2025-09-08T01:32:06,352 Python recognizes 'publiforge.Locale.es.LC_MESSAGES' as an importable package[^1], 2025-09-08T01:32:06,352 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,353 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,353 package, please make sure that 'publiforge.Locale.es.LC_MESSAGES' is explicitly added 2025-09-08T01:32:06,353 to the `packages` configuration field. 2025-09-08T01:32:06,353 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,353 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,353 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,353 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,354 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,354 If you don't want 'publiforge.Locale.es.LC_MESSAGES' to be distributed and are 2025-09-08T01:32:06,354 already explicitly excluding 'publiforge.Locale.es.LC_MESSAGES' via 2025-09-08T01:32:06,354 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,354 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,354 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,354 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,354 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,355 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,355 even if it does not contain any `.py` files. 2025-09-08T01:32:06,355 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,355 directory, all directories are treated like packages. 2025-09-08T01:32:06,355 ******************************************************************************** 2025-09-08T01:32:06,355 !! 2025-09-08T01:32:06,355 check.warn(importable) 2025-09-08T01:32:06,355 /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-08T01:32:06,355 !! 2025-09-08T01:32:06,356 ******************************************************************************** 2025-09-08T01:32:06,356 ############################ 2025-09-08T01:32:06,356 # Package would be ignored # 2025-09-08T01:32:06,356 ############################ 2025-09-08T01:32:06,356 Python recognizes 'publiforge.Locale.fr.LC_MESSAGES' as an importable package[^1], 2025-09-08T01:32:06,356 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,356 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,356 package, please make sure that 'publiforge.Locale.fr.LC_MESSAGES' is explicitly added 2025-09-08T01:32:06,356 to the `packages` configuration field. 2025-09-08T01:32:06,357 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,357 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,357 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,357 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,357 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,357 If you don't want 'publiforge.Locale.fr.LC_MESSAGES' to be distributed and are 2025-09-08T01:32:06,357 already explicitly excluding 'publiforge.Locale.fr.LC_MESSAGES' via 2025-09-08T01:32:06,357 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,358 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,358 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,358 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,358 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,358 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,358 even if it does not contain any `.py` files. 2025-09-08T01:32:06,358 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,358 directory, all directories are treated like packages. 2025-09-08T01:32:06,358 ******************************************************************************** 2025-09-08T01:32:06,359 !! 2025-09-08T01:32:06,359 check.warn(importable) 2025-09-08T01:32:06,359 /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-08T01:32:06,359 !! 2025-09-08T01:32:06,359 ******************************************************************************** 2025-09-08T01:32:06,359 ############################ 2025-09-08T01:32:06,359 # Package would be ignored # 2025-09-08T01:32:06,359 ############################ 2025-09-08T01:32:06,359 Python recognizes 'publiforge.Openers.Image' as an importable package[^1], 2025-09-08T01:32:06,359 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,360 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,360 package, please make sure that 'publiforge.Openers.Image' is explicitly added 2025-09-08T01:32:06,360 to the `packages` configuration field. 2025-09-08T01:32:06,360 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,360 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,360 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,360 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,360 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,361 If you don't want 'publiforge.Openers.Image' to be distributed and are 2025-09-08T01:32:06,361 already explicitly excluding 'publiforge.Openers.Image' via 2025-09-08T01:32:06,361 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,361 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,361 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,361 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,361 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,362 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,362 even if it does not contain any `.py` files. 2025-09-08T01:32:06,362 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,362 directory, all directories are treated like packages. 2025-09-08T01:32:06,362 ******************************************************************************** 2025-09-08T01:32:06,362 !! 2025-09-08T01:32:06,362 check.warn(importable) 2025-09-08T01:32:06,362 /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-08T01:32:06,362 !! 2025-09-08T01:32:06,362 ******************************************************************************** 2025-09-08T01:32:06,363 ############################ 2025-09-08T01:32:06,363 # Package would be ignored # 2025-09-08T01:32:06,363 ############################ 2025-09-08T01:32:06,363 Python recognizes 'publiforge.Openers.Ini' as an importable package[^1], 2025-09-08T01:32:06,363 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,363 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,363 package, please make sure that 'publiforge.Openers.Ini' is explicitly added 2025-09-08T01:32:06,363 to the `packages` configuration field. 2025-09-08T01:32:06,363 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,363 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,364 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,364 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,364 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,364 If you don't want 'publiforge.Openers.Ini' to be distributed and are 2025-09-08T01:32:06,364 already explicitly excluding 'publiforge.Openers.Ini' via 2025-09-08T01:32:06,364 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,364 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,364 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,365 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,365 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,365 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,365 even if it does not contain any `.py` files. 2025-09-08T01:32:06,365 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,365 directory, all directories are treated like packages. 2025-09-08T01:32:06,365 ******************************************************************************** 2025-09-08T01:32:06,366 !! 2025-09-08T01:32:06,366 check.warn(importable) 2025-09-08T01:32:06,366 /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-08T01:32:06,366 !! 2025-09-08T01:32:06,366 ******************************************************************************** 2025-09-08T01:32:06,366 ############################ 2025-09-08T01:32:06,366 # Package would be ignored # 2025-09-08T01:32:06,366 ############################ 2025-09-08T01:32:06,366 Python recognizes 'publiforge.Openers.NoMore' as an importable package[^1], 2025-09-08T01:32:06,366 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,367 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,367 package, please make sure that 'publiforge.Openers.NoMore' is explicitly added 2025-09-08T01:32:06,367 to the `packages` configuration field. 2025-09-08T01:32:06,367 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,367 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,367 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,367 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,367 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,368 If you don't want 'publiforge.Openers.NoMore' to be distributed and are 2025-09-08T01:32:06,368 already explicitly excluding 'publiforge.Openers.NoMore' via 2025-09-08T01:32:06,368 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,368 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,368 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,368 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,368 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,369 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,369 even if it does not contain any `.py` files. 2025-09-08T01:32:06,369 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,369 directory, all directories are treated like packages. 2025-09-08T01:32:06,369 ******************************************************************************** 2025-09-08T01:32:06,369 !! 2025-09-08T01:32:06,369 check.warn(importable) 2025-09-08T01:32:06,369 /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-08T01:32:06,369 !! 2025-09-08T01:32:06,369 ******************************************************************************** 2025-09-08T01:32:06,370 ############################ 2025-09-08T01:32:06,370 # Package would be ignored # 2025-09-08T01:32:06,370 ############################ 2025-09-08T01:32:06,370 Python recognizes 'publiforge.Openers.Plain' as an importable package[^1], 2025-09-08T01:32:06,370 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,370 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,370 package, please make sure that 'publiforge.Openers.Plain' is explicitly added 2025-09-08T01:32:06,370 to the `packages` configuration field. 2025-09-08T01:32:06,370 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,370 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,370 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,371 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,371 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,371 If you don't want 'publiforge.Openers.Plain' to be distributed and are 2025-09-08T01:32:06,371 already explicitly excluding 'publiforge.Openers.Plain' via 2025-09-08T01:32:06,371 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,371 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,371 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,371 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,372 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,372 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,372 even if it does not contain any `.py` files. 2025-09-08T01:32:06,372 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,372 directory, all directories are treated like packages. 2025-09-08T01:32:06,372 ******************************************************************************** 2025-09-08T01:32:06,372 !! 2025-09-08T01:32:06,372 check.warn(importable) 2025-09-08T01:32:06,373 /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-08T01:32:06,373 !! 2025-09-08T01:32:06,373 ******************************************************************************** 2025-09-08T01:32:06,373 ############################ 2025-09-08T01:32:06,373 # Package would be ignored # 2025-09-08T01:32:06,373 ############################ 2025-09-08T01:32:06,373 Python recognizes 'publiforge.Openers.Publidoc' as an importable package[^1], 2025-09-08T01:32:06,373 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,373 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,373 package, please make sure that 'publiforge.Openers.Publidoc' is explicitly added 2025-09-08T01:32:06,374 to the `packages` configuration field. 2025-09-08T01:32:06,374 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,374 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,374 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,374 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,374 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,374 If you don't want 'publiforge.Openers.Publidoc' to be distributed and are 2025-09-08T01:32:06,374 already explicitly excluding 'publiforge.Openers.Publidoc' via 2025-09-08T01:32:06,374 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,375 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,375 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,375 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,375 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,375 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,375 even if it does not contain any `.py` files. 2025-09-08T01:32:06,375 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,375 directory, all directories are treated like packages. 2025-09-08T01:32:06,376 ******************************************************************************** 2025-09-08T01:32:06,376 !! 2025-09-08T01:32:06,376 check.warn(importable) 2025-09-08T01:32:06,376 /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-08T01:32:06,376 !! 2025-09-08T01:32:06,376 ******************************************************************************** 2025-09-08T01:32:06,376 ############################ 2025-09-08T01:32:06,376 # Package would be ignored # 2025-09-08T01:32:06,376 ############################ 2025-09-08T01:32:06,376 Python recognizes 'publiforge.Openers.Publidoc.Maestro' as an importable package[^1], 2025-09-08T01:32:06,377 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,377 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,377 package, please make sure that 'publiforge.Openers.Publidoc.Maestro' is explicitly added 2025-09-08T01:32:06,377 to the `packages` configuration field. 2025-09-08T01:32:06,377 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,377 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,377 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,377 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,377 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,378 If you don't want 'publiforge.Openers.Publidoc.Maestro' to be distributed and are 2025-09-08T01:32:06,378 already explicitly excluding 'publiforge.Openers.Publidoc.Maestro' via 2025-09-08T01:32:06,378 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,378 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,378 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,378 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,378 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,379 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,379 even if it does not contain any `.py` files. 2025-09-08T01:32:06,379 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,379 directory, all directories are treated like packages. 2025-09-08T01:32:06,379 ******************************************************************************** 2025-09-08T01:32:06,379 !! 2025-09-08T01:32:06,379 check.warn(importable) 2025-09-08T01:32:06,379 /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-08T01:32:06,379 !! 2025-09-08T01:32:06,380 ******************************************************************************** 2025-09-08T01:32:06,380 ############################ 2025-09-08T01:32:06,380 # Package would be ignored # 2025-09-08T01:32:06,380 ############################ 2025-09-08T01:32:06,380 Python recognizes 'publiforge.Openers.Publidoc.Regex' as an importable package[^1], 2025-09-08T01:32:06,380 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,380 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,380 package, please make sure that 'publiforge.Openers.Publidoc.Regex' is explicitly added 2025-09-08T01:32:06,380 to the `packages` configuration field. 2025-09-08T01:32:06,381 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,381 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,381 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,381 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,381 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,381 If you don't want 'publiforge.Openers.Publidoc.Regex' to be distributed and are 2025-09-08T01:32:06,381 already explicitly excluding 'publiforge.Openers.Publidoc.Regex' via 2025-09-08T01:32:06,381 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,381 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,382 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,382 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,382 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,382 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,382 even if it does not contain any `.py` files. 2025-09-08T01:32:06,382 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,382 directory, all directories are treated like packages. 2025-09-08T01:32:06,382 ******************************************************************************** 2025-09-08T01:32:06,383 !! 2025-09-08T01:32:06,383 check.warn(importable) 2025-09-08T01:32:06,383 /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-08T01:32:06,383 !! 2025-09-08T01:32:06,383 ******************************************************************************** 2025-09-08T01:32:06,383 ############################ 2025-09-08T01:32:06,383 # Package would be ignored # 2025-09-08T01:32:06,383 ############################ 2025-09-08T01:32:06,383 Python recognizes 'publiforge.Openers.Publidoc.Seeds' as an importable package[^1], 2025-09-08T01:32:06,383 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,384 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,384 package, please make sure that 'publiforge.Openers.Publidoc.Seeds' is explicitly added 2025-09-08T01:32:06,384 to the `packages` configuration field. 2025-09-08T01:32:06,384 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,384 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,384 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,384 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,384 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,385 If you don't want 'publiforge.Openers.Publidoc.Seeds' to be distributed and are 2025-09-08T01:32:06,385 already explicitly excluding 'publiforge.Openers.Publidoc.Seeds' via 2025-09-08T01:32:06,385 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,385 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,385 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,385 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,385 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,386 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,386 even if it does not contain any `.py` files. 2025-09-08T01:32:06,386 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,386 directory, all directories are treated like packages. 2025-09-08T01:32:06,386 ******************************************************************************** 2025-09-08T01:32:06,386 !! 2025-09-08T01:32:06,386 check.warn(importable) 2025-09-08T01:32:06,386 /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-08T01:32:06,386 !! 2025-09-08T01:32:06,386 ******************************************************************************** 2025-09-08T01:32:06,386 ############################ 2025-09-08T01:32:06,387 # Package would be ignored # 2025-09-08T01:32:06,387 ############################ 2025-09-08T01:32:06,387 Python recognizes 'publiforge.Openers.Publidoc.Static.Css' as an importable package[^1], 2025-09-08T01:32:06,387 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,387 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,387 package, please make sure that 'publiforge.Openers.Publidoc.Static.Css' is explicitly added 2025-09-08T01:32:06,387 to the `packages` configuration field. 2025-09-08T01:32:06,387 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,387 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,387 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,388 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,388 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,388 If you don't want 'publiforge.Openers.Publidoc.Static.Css' to be distributed and are 2025-09-08T01:32:06,388 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Css' via 2025-09-08T01:32:06,388 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,388 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,388 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,388 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,389 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,389 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,389 even if it does not contain any `.py` files. 2025-09-08T01:32:06,389 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,389 directory, all directories are treated like packages. 2025-09-08T01:32:06,389 ******************************************************************************** 2025-09-08T01:32:06,389 !! 2025-09-08T01:32:06,389 check.warn(importable) 2025-09-08T01:32:06,390 /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-08T01:32:06,390 !! 2025-09-08T01:32:06,390 ******************************************************************************** 2025-09-08T01:32:06,390 ############################ 2025-09-08T01:32:06,390 # Package would be ignored # 2025-09-08T01:32:06,390 ############################ 2025-09-08T01:32:06,390 Python recognizes 'publiforge.Openers.Publidoc.Static.Js' as an importable package[^1], 2025-09-08T01:32:06,390 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,390 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,390 package, please make sure that 'publiforge.Openers.Publidoc.Static.Js' is explicitly added 2025-09-08T01:32:06,391 to the `packages` configuration field. 2025-09-08T01:32:06,391 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,391 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,391 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,391 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,391 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,391 If you don't want 'publiforge.Openers.Publidoc.Static.Js' to be distributed and are 2025-09-08T01:32:06,391 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Js' via 2025-09-08T01:32:06,391 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,392 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,392 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,392 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,392 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,392 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,392 even if it does not contain any `.py` files. 2025-09-08T01:32:06,393 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,393 directory, all directories are treated like packages. 2025-09-08T01:32:06,393 ******************************************************************************** 2025-09-08T01:32:06,393 !! 2025-09-08T01:32:06,393 check.warn(importable) 2025-09-08T01:32:06,393 /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-08T01:32:06,393 !! 2025-09-08T01:32:06,393 ******************************************************************************** 2025-09-08T01:32:06,393 ############################ 2025-09-08T01:32:06,394 # Package would be ignored # 2025-09-08T01:32:06,394 ############################ 2025-09-08T01:32:06,394 Python recognizes 'publiforge.Openers.Publidoc.Variables' as an importable package[^1], 2025-09-08T01:32:06,394 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,394 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,394 package, please make sure that 'publiforge.Openers.Publidoc.Variables' is explicitly added 2025-09-08T01:32:06,394 to the `packages` configuration field. 2025-09-08T01:32:06,394 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,394 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,394 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,395 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,395 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,395 If you don't want 'publiforge.Openers.Publidoc.Variables' to be distributed and are 2025-09-08T01:32:06,395 already explicitly excluding 'publiforge.Openers.Publidoc.Variables' via 2025-09-08T01:32:06,395 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,395 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,395 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,395 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,396 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,396 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,396 even if it does not contain any `.py` files. 2025-09-08T01:32:06,396 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,396 directory, all directories are treated like packages. 2025-09-08T01:32:06,396 ******************************************************************************** 2025-09-08T01:32:06,396 !! 2025-09-08T01:32:06,396 check.warn(importable) 2025-09-08T01:32:06,396 /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-08T01:32:06,397 !! 2025-09-08T01:32:06,397 ******************************************************************************** 2025-09-08T01:32:06,397 ############################ 2025-09-08T01:32:06,397 # Package would be ignored # 2025-09-08T01:32:06,397 ############################ 2025-09-08T01:32:06,397 Python recognizes 'publiforge.Openers.Publidoc.Xsl' as an importable package[^1], 2025-09-08T01:32:06,397 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,397 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,397 package, please make sure that 'publiforge.Openers.Publidoc.Xsl' is explicitly added 2025-09-08T01:32:06,397 to the `packages` configuration field. 2025-09-08T01:32:06,398 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,398 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,398 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,398 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,398 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,398 If you don't want 'publiforge.Openers.Publidoc.Xsl' to be distributed and are 2025-09-08T01:32:06,398 already explicitly excluding 'publiforge.Openers.Publidoc.Xsl' via 2025-09-08T01:32:06,398 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,398 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,399 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,399 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,399 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,399 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,399 even if it does not contain any `.py` files. 2025-09-08T01:32:06,399 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,399 directory, all directories are treated like packages. 2025-09-08T01:32:06,399 ******************************************************************************** 2025-09-08T01:32:06,400 !! 2025-09-08T01:32:06,400 check.warn(importable) 2025-09-08T01:32:06,400 /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-08T01:32:06,400 !! 2025-09-08T01:32:06,400 ******************************************************************************** 2025-09-08T01:32:06,400 ############################ 2025-09-08T01:32:06,400 # Package would be ignored # 2025-09-08T01:32:06,400 ############################ 2025-09-08T01:32:06,400 Python recognizes 'publiforge.Openers.Publiquiz' as an importable package[^1], 2025-09-08T01:32:06,400 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,401 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,401 package, please make sure that 'publiforge.Openers.Publiquiz' is explicitly added 2025-09-08T01:32:06,401 to the `packages` configuration field. 2025-09-08T01:32:06,401 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,401 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,401 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,401 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,401 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,402 If you don't want 'publiforge.Openers.Publiquiz' to be distributed and are 2025-09-08T01:32:06,402 already explicitly excluding 'publiforge.Openers.Publiquiz' via 2025-09-08T01:32:06,402 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,402 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,402 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,402 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,402 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,402 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,403 even if it does not contain any `.py` files. 2025-09-08T01:32:06,403 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,403 directory, all directories are treated like packages. 2025-09-08T01:32:06,403 ******************************************************************************** 2025-09-08T01:32:06,403 !! 2025-09-08T01:32:06,403 check.warn(importable) 2025-09-08T01:32:06,403 /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-08T01:32:06,403 !! 2025-09-08T01:32:06,403 ******************************************************************************** 2025-09-08T01:32:06,404 ############################ 2025-09-08T01:32:06,404 # Package would be ignored # 2025-09-08T01:32:06,404 ############################ 2025-09-08T01:32:06,404 Python recognizes 'publiforge.Openers.Publiquiz.Regex' as an importable package[^1], 2025-09-08T01:32:06,404 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,404 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,404 package, please make sure that 'publiforge.Openers.Publiquiz.Regex' is explicitly added 2025-09-08T01:32:06,404 to the `packages` configuration field. 2025-09-08T01:32:06,404 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,404 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,405 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,405 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,405 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,405 If you don't want 'publiforge.Openers.Publiquiz.Regex' to be distributed and are 2025-09-08T01:32:06,405 already explicitly excluding 'publiforge.Openers.Publiquiz.Regex' via 2025-09-08T01:32:06,405 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,405 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,405 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,406 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,406 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,406 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,406 even if it does not contain any `.py` files. 2025-09-08T01:32:06,406 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,406 directory, all directories are treated like packages. 2025-09-08T01:32:06,406 ******************************************************************************** 2025-09-08T01:32:06,407 !! 2025-09-08T01:32:06,407 check.warn(importable) 2025-09-08T01:32:06,407 /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-08T01:32:06,407 !! 2025-09-08T01:32:06,407 ******************************************************************************** 2025-09-08T01:32:06,407 ############################ 2025-09-08T01:32:06,407 # Package would be ignored # 2025-09-08T01:32:06,407 ############################ 2025-09-08T01:32:06,407 Python recognizes 'publiforge.Openers.Publiquiz.Seeds' as an importable package[^1], 2025-09-08T01:32:06,407 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,408 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,408 package, please make sure that 'publiforge.Openers.Publiquiz.Seeds' is explicitly added 2025-09-08T01:32:06,408 to the `packages` configuration field. 2025-09-08T01:32:06,408 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,408 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,408 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,408 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,408 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,409 If you don't want 'publiforge.Openers.Publiquiz.Seeds' to be distributed and are 2025-09-08T01:32:06,409 already explicitly excluding 'publiforge.Openers.Publiquiz.Seeds' via 2025-09-08T01:32:06,409 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,409 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,409 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,409 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,409 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,409 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,410 even if it does not contain any `.py` files. 2025-09-08T01:32:06,410 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,410 directory, all directories are treated like packages. 2025-09-08T01:32:06,410 ******************************************************************************** 2025-09-08T01:32:06,410 !! 2025-09-08T01:32:06,410 check.warn(importable) 2025-09-08T01:32:06,410 /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-08T01:32:06,410 !! 2025-09-08T01:32:06,410 ******************************************************************************** 2025-09-08T01:32:06,410 ############################ 2025-09-08T01:32:06,410 # Package would be ignored # 2025-09-08T01:32:06,411 ############################ 2025-09-08T01:32:06,411 Python recognizes 'publiforge.Openers.Publiquiz.Static.Css' as an importable package[^1], 2025-09-08T01:32:06,411 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,411 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,411 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Css' is explicitly added 2025-09-08T01:32:06,411 to the `packages` configuration field. 2025-09-08T01:32:06,411 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,411 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,411 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,412 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,412 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,412 If you don't want 'publiforge.Openers.Publiquiz.Static.Css' to be distributed and are 2025-09-08T01:32:06,412 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Css' via 2025-09-08T01:32:06,412 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,412 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,412 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,412 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,413 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,413 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,413 even if it does not contain any `.py` files. 2025-09-08T01:32:06,413 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,413 directory, all directories are treated like packages. 2025-09-08T01:32:06,413 ******************************************************************************** 2025-09-08T01:32:06,413 !! 2025-09-08T01:32:06,413 check.warn(importable) 2025-09-08T01:32:06,413 /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-08T01:32:06,414 !! 2025-09-08T01:32:06,414 ******************************************************************************** 2025-09-08T01:32:06,414 ############################ 2025-09-08T01:32:06,414 # Package would be ignored # 2025-09-08T01:32:06,414 ############################ 2025-09-08T01:32:06,414 Python recognizes 'publiforge.Openers.Publiquiz.Static.Js' as an importable package[^1], 2025-09-08T01:32:06,414 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,414 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,414 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Js' is explicitly added 2025-09-08T01:32:06,414 to the `packages` configuration field. 2025-09-08T01:32:06,415 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,415 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,415 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,415 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,415 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,415 If you don't want 'publiforge.Openers.Publiquiz.Static.Js' to be distributed and are 2025-09-08T01:32:06,415 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Js' via 2025-09-08T01:32:06,415 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,415 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,416 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,416 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,416 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,416 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,416 even if it does not contain any `.py` files. 2025-09-08T01:32:06,416 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,416 directory, all directories are treated like packages. 2025-09-08T01:32:06,416 ******************************************************************************** 2025-09-08T01:32:06,417 !! 2025-09-08T01:32:06,417 check.warn(importable) 2025-09-08T01:32:06,417 /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-08T01:32:06,417 !! 2025-09-08T01:32:06,417 ******************************************************************************** 2025-09-08T01:32:06,417 ############################ 2025-09-08T01:32:06,417 # Package would be ignored # 2025-09-08T01:32:06,417 ############################ 2025-09-08T01:32:06,417 Python recognizes 'publiforge.Openers.Publiquiz.Variables' as an importable package[^1], 2025-09-08T01:32:06,417 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,418 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,418 package, please make sure that 'publiforge.Openers.Publiquiz.Variables' is explicitly added 2025-09-08T01:32:06,418 to the `packages` configuration field. 2025-09-08T01:32:06,418 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,418 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,418 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,418 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,419 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,419 If you don't want 'publiforge.Openers.Publiquiz.Variables' to be distributed and are 2025-09-08T01:32:06,419 already explicitly excluding 'publiforge.Openers.Publiquiz.Variables' via 2025-09-08T01:32:06,419 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,419 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,419 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,419 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,419 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,420 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,420 even if it does not contain any `.py` files. 2025-09-08T01:32:06,420 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,420 directory, all directories are treated like packages. 2025-09-08T01:32:06,420 ******************************************************************************** 2025-09-08T01:32:06,420 !! 2025-09-08T01:32:06,420 check.warn(importable) 2025-09-08T01:32:06,420 /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-08T01:32:06,420 !! 2025-09-08T01:32:06,421 ******************************************************************************** 2025-09-08T01:32:06,421 ############################ 2025-09-08T01:32:06,421 # Package would be ignored # 2025-09-08T01:32:06,421 ############################ 2025-09-08T01:32:06,421 Python recognizes 'publiforge.Openers.Publiquiz.Xsl' as an importable package[^1], 2025-09-08T01:32:06,421 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,421 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,421 package, please make sure that 'publiforge.Openers.Publiquiz.Xsl' is explicitly added 2025-09-08T01:32:06,421 to the `packages` configuration field. 2025-09-08T01:32:06,422 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,422 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,422 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,422 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,422 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,422 If you don't want 'publiforge.Openers.Publiquiz.Xsl' to be distributed and are 2025-09-08T01:32:06,422 already explicitly excluding 'publiforge.Openers.Publiquiz.Xsl' via 2025-09-08T01:32:06,422 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,422 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,423 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,423 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,423 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,423 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,423 even if it does not contain any `.py` files. 2025-09-08T01:32:06,423 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,423 directory, all directories are treated like packages. 2025-09-08T01:32:06,423 ******************************************************************************** 2025-09-08T01:32:06,424 !! 2025-09-08T01:32:06,424 check.warn(importable) 2025-09-08T01:32:06,424 /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-08T01:32:06,424 !! 2025-09-08T01:32:06,424 ******************************************************************************** 2025-09-08T01:32:06,424 ############################ 2025-09-08T01:32:06,424 # Package would be ignored # 2025-09-08T01:32:06,424 ############################ 2025-09-08T01:32:06,424 Python recognizes 'publiforge.Openers.Publiset' as an importable package[^1], 2025-09-08T01:32:06,424 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,425 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,425 package, please make sure that 'publiforge.Openers.Publiset' is explicitly added 2025-09-08T01:32:06,425 to the `packages` configuration field. 2025-09-08T01:32:06,425 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,425 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,425 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,425 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,425 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,426 If you don't want 'publiforge.Openers.Publiset' to be distributed and are 2025-09-08T01:32:06,426 already explicitly excluding 'publiforge.Openers.Publiset' via 2025-09-08T01:32:06,426 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,426 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,426 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,426 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,426 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,427 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,427 even if it does not contain any `.py` files. 2025-09-08T01:32:06,427 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,427 directory, all directories are treated like packages. 2025-09-08T01:32:06,427 ******************************************************************************** 2025-09-08T01:32:06,427 !! 2025-09-08T01:32:06,427 check.warn(importable) 2025-09-08T01:32:06,427 /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-08T01:32:06,427 !! 2025-09-08T01:32:06,427 ******************************************************************************** 2025-09-08T01:32:06,428 ############################ 2025-09-08T01:32:06,428 # Package would be ignored # 2025-09-08T01:32:06,428 ############################ 2025-09-08T01:32:06,428 Python recognizes 'publiforge.Openers.Publiset.Regex' as an importable package[^1], 2025-09-08T01:32:06,428 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,428 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,428 package, please make sure that 'publiforge.Openers.Publiset.Regex' is explicitly added 2025-09-08T01:32:06,428 to the `packages` configuration field. 2025-09-08T01:32:06,428 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,428 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,429 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,429 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,429 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,429 If you don't want 'publiforge.Openers.Publiset.Regex' to be distributed and are 2025-09-08T01:32:06,429 already explicitly excluding 'publiforge.Openers.Publiset.Regex' via 2025-09-08T01:32:06,429 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,429 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,429 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,429 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,430 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,430 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,430 even if it does not contain any `.py` files. 2025-09-08T01:32:06,430 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,430 directory, all directories are treated like packages. 2025-09-08T01:32:06,430 ******************************************************************************** 2025-09-08T01:32:06,430 !! 2025-09-08T01:32:06,430 check.warn(importable) 2025-09-08T01:32:06,431 /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-08T01:32:06,431 !! 2025-09-08T01:32:06,431 ******************************************************************************** 2025-09-08T01:32:06,431 ############################ 2025-09-08T01:32:06,431 # Package would be ignored # 2025-09-08T01:32:06,431 ############################ 2025-09-08T01:32:06,431 Python recognizes 'publiforge.Openers.Publiset.Seeds' as an importable package[^1], 2025-09-08T01:32:06,431 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,431 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,432 package, please make sure that 'publiforge.Openers.Publiset.Seeds' is explicitly added 2025-09-08T01:32:06,432 to the `packages` configuration field. 2025-09-08T01:32:06,432 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,432 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,432 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,432 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,432 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,433 If you don't want 'publiforge.Openers.Publiset.Seeds' to be distributed and are 2025-09-08T01:32:06,433 already explicitly excluding 'publiforge.Openers.Publiset.Seeds' via 2025-09-08T01:32:06,433 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,433 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,433 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,433 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,433 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,433 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,434 even if it does not contain any `.py` files. 2025-09-08T01:32:06,434 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,434 directory, all directories are treated like packages. 2025-09-08T01:32:06,434 ******************************************************************************** 2025-09-08T01:32:06,434 !! 2025-09-08T01:32:06,434 check.warn(importable) 2025-09-08T01:32:06,434 /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-08T01:32:06,434 !! 2025-09-08T01:32:06,434 ******************************************************************************** 2025-09-08T01:32:06,434 ############################ 2025-09-08T01:32:06,435 # Package would be ignored # 2025-09-08T01:32:06,435 ############################ 2025-09-08T01:32:06,435 Python recognizes 'publiforge.Openers.Publiset.Static.Css' as an importable package[^1], 2025-09-08T01:32:06,435 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,435 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,435 package, please make sure that 'publiforge.Openers.Publiset.Static.Css' is explicitly added 2025-09-08T01:32:06,435 to the `packages` configuration field. 2025-09-08T01:32:06,435 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,435 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,435 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,436 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,436 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,436 If you don't want 'publiforge.Openers.Publiset.Static.Css' to be distributed and are 2025-09-08T01:32:06,436 already explicitly excluding 'publiforge.Openers.Publiset.Static.Css' via 2025-09-08T01:32:06,436 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,436 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,436 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,436 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,437 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,437 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,437 even if it does not contain any `.py` files. 2025-09-08T01:32:06,437 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,437 directory, all directories are treated like packages. 2025-09-08T01:32:06,437 ******************************************************************************** 2025-09-08T01:32:06,437 !! 2025-09-08T01:32:06,437 check.warn(importable) 2025-09-08T01:32:06,437 /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-08T01:32:06,438 !! 2025-09-08T01:32:06,438 ******************************************************************************** 2025-09-08T01:32:06,438 ############################ 2025-09-08T01:32:06,438 # Package would be ignored # 2025-09-08T01:32:06,438 ############################ 2025-09-08T01:32:06,438 Python recognizes 'publiforge.Openers.Publiset.Static.Js' as an importable package[^1], 2025-09-08T01:32:06,438 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,438 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,438 package, please make sure that 'publiforge.Openers.Publiset.Static.Js' is explicitly added 2025-09-08T01:32:06,438 to the `packages` configuration field. 2025-09-08T01:32:06,439 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,439 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,439 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,439 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,439 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,439 If you don't want 'publiforge.Openers.Publiset.Static.Js' to be distributed and are 2025-09-08T01:32:06,439 already explicitly excluding 'publiforge.Openers.Publiset.Static.Js' via 2025-09-08T01:32:06,439 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,439 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,440 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,440 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,440 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,440 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,440 even if it does not contain any `.py` files. 2025-09-08T01:32:06,440 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,440 directory, all directories are treated like packages. 2025-09-08T01:32:06,440 ******************************************************************************** 2025-09-08T01:32:06,441 !! 2025-09-08T01:32:06,441 check.warn(importable) 2025-09-08T01:32:06,441 /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-08T01:32:06,441 !! 2025-09-08T01:32:06,441 ******************************************************************************** 2025-09-08T01:32:06,441 ############################ 2025-09-08T01:32:06,441 # Package would be ignored # 2025-09-08T01:32:06,441 ############################ 2025-09-08T01:32:06,441 Python recognizes 'publiforge.Openers.Publiset.Variables' as an importable package[^1], 2025-09-08T01:32:06,441 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,442 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,442 package, please make sure that 'publiforge.Openers.Publiset.Variables' is explicitly added 2025-09-08T01:32:06,442 to the `packages` configuration field. 2025-09-08T01:32:06,442 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,442 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,442 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,442 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,442 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,443 If you don't want 'publiforge.Openers.Publiset.Variables' to be distributed and are 2025-09-08T01:32:06,443 already explicitly excluding 'publiforge.Openers.Publiset.Variables' via 2025-09-08T01:32:06,443 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,443 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,443 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,443 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,443 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,444 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,444 even if it does not contain any `.py` files. 2025-09-08T01:32:06,444 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,444 directory, all directories are treated like packages. 2025-09-08T01:32:06,444 ******************************************************************************** 2025-09-08T01:32:06,444 !! 2025-09-08T01:32:06,444 check.warn(importable) 2025-09-08T01:32:06,444 /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-08T01:32:06,444 !! 2025-09-08T01:32:06,445 ******************************************************************************** 2025-09-08T01:32:06,445 ############################ 2025-09-08T01:32:06,445 # Package would be ignored # 2025-09-08T01:32:06,445 ############################ 2025-09-08T01:32:06,445 Python recognizes 'publiforge.Openers.Publiset.Xsl' as an importable package[^1], 2025-09-08T01:32:06,445 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,445 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,445 package, please make sure that 'publiforge.Openers.Publiset.Xsl' is explicitly added 2025-09-08T01:32:06,445 to the `packages` configuration field. 2025-09-08T01:32:06,445 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,446 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,446 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,446 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,446 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,446 If you don't want 'publiforge.Openers.Publiset.Xsl' to be distributed and are 2025-09-08T01:32:06,446 already explicitly excluding 'publiforge.Openers.Publiset.Xsl' via 2025-09-08T01:32:06,446 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,446 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,446 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,447 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,447 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,447 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,447 even if it does not contain any `.py` files. 2025-09-08T01:32:06,447 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,447 directory, all directories are treated like packages. 2025-09-08T01:32:06,447 ******************************************************************************** 2025-09-08T01:32:06,448 !! 2025-09-08T01:32:06,448 check.warn(importable) 2025-09-08T01:32:06,448 /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-08T01:32:06,448 !! 2025-09-08T01:32:06,448 ******************************************************************************** 2025-09-08T01:32:06,448 ############################ 2025-09-08T01:32:06,448 # Package would be ignored # 2025-09-08T01:32:06,448 ############################ 2025-09-08T01:32:06,448 Python recognizes 'publiforge.Openers.Xml' as an importable package[^1], 2025-09-08T01:32:06,448 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,449 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,449 package, please make sure that 'publiforge.Openers.Xml' is explicitly added 2025-09-08T01:32:06,449 to the `packages` configuration field. 2025-09-08T01:32:06,449 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,449 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,449 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,449 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,449 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,449 If you don't want 'publiforge.Openers.Xml' to be distributed and are 2025-09-08T01:32:06,450 already explicitly excluding 'publiforge.Openers.Xml' via 2025-09-08T01:32:06,450 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,450 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,450 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,450 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,450 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,450 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,450 even if it does not contain any `.py` files. 2025-09-08T01:32:06,451 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,451 directory, all directories are treated like packages. 2025-09-08T01:32:06,451 ******************************************************************************** 2025-09-08T01:32:06,451 !! 2025-09-08T01:32:06,451 check.warn(importable) 2025-09-08T01:32:06,451 /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-08T01:32:06,451 !! 2025-09-08T01:32:06,451 ******************************************************************************** 2025-09-08T01:32:06,451 ############################ 2025-09-08T01:32:06,451 # Package would be ignored # 2025-09-08T01:32:06,452 ############################ 2025-09-08T01:32:06,452 Python recognizes 'publiforge.Processors.CharCount' as an importable package[^1], 2025-09-08T01:32:06,452 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,452 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,452 package, please make sure that 'publiforge.Processors.CharCount' is explicitly added 2025-09-08T01:32:06,452 to the `packages` configuration field. 2025-09-08T01:32:06,452 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,452 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,452 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,452 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,453 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,453 If you don't want 'publiforge.Processors.CharCount' to be distributed and are 2025-09-08T01:32:06,453 already explicitly excluding 'publiforge.Processors.CharCount' via 2025-09-08T01:32:06,453 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,453 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,453 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,453 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,453 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,454 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,454 even if it does not contain any `.py` files. 2025-09-08T01:32:06,454 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,454 directory, all directories are treated like packages. 2025-09-08T01:32:06,454 ******************************************************************************** 2025-09-08T01:32:06,454 !! 2025-09-08T01:32:06,454 check.warn(importable) 2025-09-08T01:32:06,454 /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-08T01:32:06,454 !! 2025-09-08T01:32:06,455 ******************************************************************************** 2025-09-08T01:32:06,455 ############################ 2025-09-08T01:32:06,455 # Package would be ignored # 2025-09-08T01:32:06,455 ############################ 2025-09-08T01:32:06,455 Python recognizes 'publiforge.Processors.CharCount.Xsl' as an importable package[^1], 2025-09-08T01:32:06,455 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,455 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,455 package, please make sure that 'publiforge.Processors.CharCount.Xsl' is explicitly added 2025-09-08T01:32:06,455 to the `packages` configuration field. 2025-09-08T01:32:06,456 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,456 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,456 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,456 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,456 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,456 If you don't want 'publiforge.Processors.CharCount.Xsl' to be distributed and are 2025-09-08T01:32:06,456 already explicitly excluding 'publiforge.Processors.CharCount.Xsl' via 2025-09-08T01:32:06,456 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,456 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,457 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,457 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,457 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,457 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,457 even if it does not contain any `.py` files. 2025-09-08T01:32:06,457 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,457 directory, all directories are treated like packages. 2025-09-08T01:32:06,458 ******************************************************************************** 2025-09-08T01:32:06,458 !! 2025-09-08T01:32:06,458 check.warn(importable) 2025-09-08T01:32:06,458 /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-08T01:32:06,458 !! 2025-09-08T01:32:06,458 ******************************************************************************** 2025-09-08T01:32:06,458 ############################ 2025-09-08T01:32:06,458 # Package would be ignored # 2025-09-08T01:32:06,458 ############################ 2025-09-08T01:32:06,458 Python recognizes 'publiforge.Processors.DTBookValid' as an importable package[^1], 2025-09-08T01:32:06,459 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,459 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,459 package, please make sure that 'publiforge.Processors.DTBookValid' is explicitly added 2025-09-08T01:32:06,459 to the `packages` configuration field. 2025-09-08T01:32:06,459 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,459 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,459 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,459 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,460 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,460 If you don't want 'publiforge.Processors.DTBookValid' to be distributed and are 2025-09-08T01:32:06,460 already explicitly excluding 'publiforge.Processors.DTBookValid' via 2025-09-08T01:32:06,460 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,460 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,460 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,460 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,460 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,461 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,461 even if it does not contain any `.py` files. 2025-09-08T01:32:06,461 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,461 directory, all directories are treated like packages. 2025-09-08T01:32:06,461 ******************************************************************************** 2025-09-08T01:32:06,461 !! 2025-09-08T01:32:06,461 check.warn(importable) 2025-09-08T01:32:06,461 /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-08T01:32:06,461 !! 2025-09-08T01:32:06,462 ******************************************************************************** 2025-09-08T01:32:06,462 ############################ 2025-09-08T01:32:06,462 # Package would be ignored # 2025-09-08T01:32:06,462 ############################ 2025-09-08T01:32:06,462 Python recognizes 'publiforge.Processors.DTBookValid.RelaxNG' as an importable package[^1], 2025-09-08T01:32:06,462 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,462 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,462 package, please make sure that 'publiforge.Processors.DTBookValid.RelaxNG' is explicitly added 2025-09-08T01:32:06,462 to the `packages` configuration field. 2025-09-08T01:32:06,462 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,463 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,463 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,463 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,463 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,463 If you don't want 'publiforge.Processors.DTBookValid.RelaxNG' to be distributed and are 2025-09-08T01:32:06,463 already explicitly excluding 'publiforge.Processors.DTBookValid.RelaxNG' via 2025-09-08T01:32:06,463 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,463 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,463 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,464 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,464 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,464 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,464 even if it does not contain any `.py` files. 2025-09-08T01:32:06,464 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,464 directory, all directories are treated like packages. 2025-09-08T01:32:06,464 ******************************************************************************** 2025-09-08T01:32:06,465 !! 2025-09-08T01:32:06,465 check.warn(importable) 2025-09-08T01:32:06,465 /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-08T01:32:06,465 !! 2025-09-08T01:32:06,465 ******************************************************************************** 2025-09-08T01:32:06,465 ############################ 2025-09-08T01:32:06,465 # Package would be ignored # 2025-09-08T01:32:06,465 ############################ 2025-09-08T01:32:06,465 Python recognizes 'publiforge.Processors.Parallel' as an importable package[^1], 2025-09-08T01:32:06,465 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,465 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,466 package, please make sure that 'publiforge.Processors.Parallel' is explicitly added 2025-09-08T01:32:06,466 to the `packages` configuration field. 2025-09-08T01:32:06,466 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,466 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,466 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,466 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,466 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,466 If you don't want 'publiforge.Processors.Parallel' to be distributed and are 2025-09-08T01:32:06,467 already explicitly excluding 'publiforge.Processors.Parallel' via 2025-09-08T01:32:06,467 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,467 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,467 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,467 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,467 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,467 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,467 even if it does not contain any `.py` files. 2025-09-08T01:32:06,468 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,468 directory, all directories are treated like packages. 2025-09-08T01:32:06,468 ******************************************************************************** 2025-09-08T01:32:06,468 !! 2025-09-08T01:32:06,468 check.warn(importable) 2025-09-08T01:32:06,468 /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-08T01:32:06,468 !! 2025-09-08T01:32:06,468 ******************************************************************************** 2025-09-08T01:32:06,468 ############################ 2025-09-08T01:32:06,468 # Package would be ignored # 2025-09-08T01:32:06,468 ############################ 2025-09-08T01:32:06,469 Python recognizes 'publiforge.Processors.Parallel.Variables' as an importable package[^1], 2025-09-08T01:32:06,469 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,469 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,469 package, please make sure that 'publiforge.Processors.Parallel.Variables' is explicitly added 2025-09-08T01:32:06,469 to the `packages` configuration field. 2025-09-08T01:32:06,469 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,469 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,469 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,469 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,470 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,470 If you don't want 'publiforge.Processors.Parallel.Variables' to be distributed and are 2025-09-08T01:32:06,470 already explicitly excluding 'publiforge.Processors.Parallel.Variables' via 2025-09-08T01:32:06,470 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,470 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,470 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,470 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,471 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,471 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,471 even if it does not contain any `.py` files. 2025-09-08T01:32:06,471 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,471 directory, all directories are treated like packages. 2025-09-08T01:32:06,471 ******************************************************************************** 2025-09-08T01:32:06,471 !! 2025-09-08T01:32:06,471 check.warn(importable) 2025-09-08T01:32:06,472 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv' is absent from the `packages` configuration. 2025-09-08T01:32:06,472 !! 2025-09-08T01:32:06,472 ******************************************************************************** 2025-09-08T01:32:06,472 ############################ 2025-09-08T01:32:06,472 # Package would be ignored # 2025-09-08T01:32:06,472 ############################ 2025-09-08T01:32:06,472 Python recognizes 'publiforge.Processors.Publidoc2Csv' as an importable package[^1], 2025-09-08T01:32:06,472 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,472 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,472 package, please make sure that 'publiforge.Processors.Publidoc2Csv' is explicitly added 2025-09-08T01:32:06,473 to the `packages` configuration field. 2025-09-08T01:32:06,473 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,473 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,473 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,473 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,473 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,473 If you don't want 'publiforge.Processors.Publidoc2Csv' to be distributed and are 2025-09-08T01:32:06,473 already explicitly excluding 'publiforge.Processors.Publidoc2Csv' via 2025-09-08T01:32:06,474 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,474 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,474 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,474 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,474 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,474 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,474 even if it does not contain any `.py` files. 2025-09-08T01:32:06,474 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,475 directory, all directories are treated like packages. 2025-09-08T01:32:06,475 ******************************************************************************** 2025-09-08T01:32:06,475 !! 2025-09-08T01:32:06,475 check.warn(importable) 2025-09-08T01:32:06,475 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.Regex' is absent from the `packages` configuration. 2025-09-08T01:32:06,475 !! 2025-09-08T01:32:06,475 ******************************************************************************** 2025-09-08T01:32:06,475 ############################ 2025-09-08T01:32:06,475 # Package would be ignored # 2025-09-08T01:32:06,475 ############################ 2025-09-08T01:32:06,476 Python recognizes 'publiforge.Processors.Publidoc2Csv.Regex' as an importable package[^1], 2025-09-08T01:32:06,476 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,476 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,476 package, please make sure that 'publiforge.Processors.Publidoc2Csv.Regex' is explicitly added 2025-09-08T01:32:06,476 to the `packages` configuration field. 2025-09-08T01:32:06,476 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,476 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,476 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,476 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,477 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,477 If you don't want 'publiforge.Processors.Publidoc2Csv.Regex' to be distributed and are 2025-09-08T01:32:06,477 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.Regex' via 2025-09-08T01:32:06,477 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,477 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,477 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,477 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,477 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,478 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,478 even if it does not contain any `.py` files. 2025-09-08T01:32:06,478 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,478 directory, all directories are treated like packages. 2025-09-08T01:32:06,478 ******************************************************************************** 2025-09-08T01:32:06,478 !! 2025-09-08T01:32:06,478 check.warn(importable) 2025-09-08T01:32:06,478 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.Templates' is absent from the `packages` configuration. 2025-09-08T01:32:06,478 !! 2025-09-08T01:32:06,479 ******************************************************************************** 2025-09-08T01:32:06,479 ############################ 2025-09-08T01:32:06,479 # Package would be ignored # 2025-09-08T01:32:06,479 ############################ 2025-09-08T01:32:06,479 Python recognizes 'publiforge.Processors.Publidoc2Csv.Templates' as an importable package[^1], 2025-09-08T01:32:06,479 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,479 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,479 package, please make sure that 'publiforge.Processors.Publidoc2Csv.Templates' is explicitly added 2025-09-08T01:32:06,479 to the `packages` configuration field. 2025-09-08T01:32:06,479 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,480 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,480 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,480 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,480 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,480 If you don't want 'publiforge.Processors.Publidoc2Csv.Templates' to be distributed and are 2025-09-08T01:32:06,480 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.Templates' via 2025-09-08T01:32:06,480 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,480 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,480 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,481 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,481 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,481 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,481 even if it does not contain any `.py` files. 2025-09-08T01:32:06,481 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,481 directory, all directories are treated like packages. 2025-09-08T01:32:06,481 ******************************************************************************** 2025-09-08T01:32:06,481 !! 2025-09-08T01:32:06,482 check.warn(importable) 2025-09-08T01:32:06,482 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.Variables' is absent from the `packages` configuration. 2025-09-08T01:32:06,482 !! 2025-09-08T01:32:06,482 ******************************************************************************** 2025-09-08T01:32:06,482 ############################ 2025-09-08T01:32:06,482 # Package would be ignored # 2025-09-08T01:32:06,482 ############################ 2025-09-08T01:32:06,482 Python recognizes 'publiforge.Processors.Publidoc2Csv.Variables' as an importable package[^1], 2025-09-08T01:32:06,482 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,482 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,483 package, please make sure that 'publiforge.Processors.Publidoc2Csv.Variables' is explicitly added 2025-09-08T01:32:06,483 to the `packages` configuration field. 2025-09-08T01:32:06,483 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,483 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,483 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,483 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,483 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,483 If you don't want 'publiforge.Processors.Publidoc2Csv.Variables' to be distributed and are 2025-09-08T01:32:06,484 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.Variables' via 2025-09-08T01:32:06,484 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,484 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,484 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,484 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,484 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,484 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,485 even if it does not contain any `.py` files. 2025-09-08T01:32:06,485 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,485 directory, all directories are treated like packages. 2025-09-08T01:32:06,485 ******************************************************************************** 2025-09-08T01:32:06,485 !! 2025-09-08T01:32:06,485 check.warn(importable) 2025-09-08T01:32:06,485 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.Xsl' is absent from the `packages` configuration. 2025-09-08T01:32:06,485 !! 2025-09-08T01:32:06,485 ******************************************************************************** 2025-09-08T01:32:06,486 ############################ 2025-09-08T01:32:06,486 # Package would be ignored # 2025-09-08T01:32:06,486 ############################ 2025-09-08T01:32:06,486 Python recognizes 'publiforge.Processors.Publidoc2Csv.Xsl' as an importable package[^1], 2025-09-08T01:32:06,486 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,486 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,486 package, please make sure that 'publiforge.Processors.Publidoc2Csv.Xsl' is explicitly added 2025-09-08T01:32:06,486 to the `packages` configuration field. 2025-09-08T01:32:06,486 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,486 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,487 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,487 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,487 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,487 If you don't want 'publiforge.Processors.Publidoc2Csv.Xsl' to be distributed and are 2025-09-08T01:32:06,487 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.Xsl' via 2025-09-08T01:32:06,487 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,487 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,487 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,487 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,488 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,488 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,488 even if it does not contain any `.py` files. 2025-09-08T01:32:06,488 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,488 directory, all directories are treated like packages. 2025-09-08T01:32:06,488 ******************************************************************************** 2025-09-08T01:32:06,488 !! 2025-09-08T01:32:06,488 check.warn(importable) 2025-09-08T01:32:06,489 /usr/local/lib/python3.13/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'publiforge.Processors.Publidoc2Csv.lib' is absent from the `packages` configuration. 2025-09-08T01:32:06,489 !! 2025-09-08T01:32:06,489 ******************************************************************************** 2025-09-08T01:32:06,489 ############################ 2025-09-08T01:32:06,489 # Package would be ignored # 2025-09-08T01:32:06,489 ############################ 2025-09-08T01:32:06,489 Python recognizes 'publiforge.Processors.Publidoc2Csv.lib' as an importable package[^1], 2025-09-08T01:32:06,489 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,489 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,489 package, please make sure that 'publiforge.Processors.Publidoc2Csv.lib' is explicitly added 2025-09-08T01:32:06,490 to the `packages` configuration field. 2025-09-08T01:32:06,490 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,490 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,490 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,490 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,490 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,490 If you don't want 'publiforge.Processors.Publidoc2Csv.lib' to be distributed and are 2025-09-08T01:32:06,490 already explicitly excluding 'publiforge.Processors.Publidoc2Csv.lib' via 2025-09-08T01:32:06,491 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,491 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,491 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,491 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,491 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,491 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,491 even if it does not contain any `.py` files. 2025-09-08T01:32:06,491 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,492 directory, all directories are treated like packages. 2025-09-08T01:32:06,492 ******************************************************************************** 2025-09-08T01:32:06,492 !! 2025-09-08T01:32:06,492 check.warn(importable) 2025-09-08T01:32:06,492 /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-08T01:32:06,492 !! 2025-09-08T01:32:06,492 ******************************************************************************** 2025-09-08T01:32:06,492 ############################ 2025-09-08T01:32:06,492 # Package would be ignored # 2025-09-08T01:32:06,492 ############################ 2025-09-08T01:32:06,492 Python recognizes 'publiforge.Processors.Publidoc2DTBook' as an importable package[^1], 2025-09-08T01:32:06,493 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,493 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,493 package, please make sure that 'publiforge.Processors.Publidoc2DTBook' is explicitly added 2025-09-08T01:32:06,493 to the `packages` configuration field. 2025-09-08T01:32:06,493 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,493 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,493 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,493 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,494 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,494 If you don't want 'publiforge.Processors.Publidoc2DTBook' to be distributed and are 2025-09-08T01:32:06,494 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook' via 2025-09-08T01:32:06,494 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,494 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,494 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,494 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,494 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,495 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,495 even if it does not contain any `.py` files. 2025-09-08T01:32:06,495 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,495 directory, all directories are treated like packages. 2025-09-08T01:32:06,495 ******************************************************************************** 2025-09-08T01:32:06,495 !! 2025-09-08T01:32:06,495 check.warn(importable) 2025-09-08T01:32:06,495 /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-08T01:32:06,495 !! 2025-09-08T01:32:06,496 ******************************************************************************** 2025-09-08T01:32:06,496 ############################ 2025-09-08T01:32:06,496 # Package would be ignored # 2025-09-08T01:32:06,496 ############################ 2025-09-08T01:32:06,496 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Variables' as an importable package[^1], 2025-09-08T01:32:06,496 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,496 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,496 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Variables' is explicitly added 2025-09-08T01:32:06,496 to the `packages` configuration field. 2025-09-08T01:32:06,497 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,497 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,497 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,497 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,497 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,497 If you don't want 'publiforge.Processors.Publidoc2DTBook.Variables' to be distributed and are 2025-09-08T01:32:06,497 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Variables' via 2025-09-08T01:32:06,497 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,497 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,498 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,498 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,498 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,498 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,498 even if it does not contain any `.py` files. 2025-09-08T01:32:06,498 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,498 directory, all directories are treated like packages. 2025-09-08T01:32:06,499 ******************************************************************************** 2025-09-08T01:32:06,499 !! 2025-09-08T01:32:06,499 check.warn(importable) 2025-09-08T01:32:06,499 /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-08T01:32:06,499 !! 2025-09-08T01:32:06,499 ******************************************************************************** 2025-09-08T01:32:06,499 ############################ 2025-09-08T01:32:06,499 # Package would be ignored # 2025-09-08T01:32:06,499 ############################ 2025-09-08T01:32:06,499 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Xsl' as an importable package[^1], 2025-09-08T01:32:06,500 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,500 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,500 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Xsl' is explicitly added 2025-09-08T01:32:06,500 to the `packages` configuration field. 2025-09-08T01:32:06,500 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,500 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,500 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,500 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,500 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,501 If you don't want 'publiforge.Processors.Publidoc2DTBook.Xsl' to be distributed and are 2025-09-08T01:32:06,501 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Xsl' via 2025-09-08T01:32:06,501 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,501 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,501 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,501 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,501 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,502 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,502 even if it does not contain any `.py` files. 2025-09-08T01:32:06,502 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,502 directory, all directories are treated like packages. 2025-09-08T01:32:06,502 ******************************************************************************** 2025-09-08T01:32:06,502 !! 2025-09-08T01:32:06,502 check.warn(importable) 2025-09-08T01:32:06,502 /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-08T01:32:06,502 !! 2025-09-08T01:32:06,502 ******************************************************************************** 2025-09-08T01:32:06,503 ############################ 2025-09-08T01:32:06,503 # Package would be ignored # 2025-09-08T01:32:06,503 ############################ 2025-09-08T01:32:06,503 Python recognizes 'publiforge.Processors.Publidoc2EPub2' as an importable package[^1], 2025-09-08T01:32:06,503 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,503 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,503 package, please make sure that 'publiforge.Processors.Publidoc2EPub2' is explicitly added 2025-09-08T01:32:06,503 to the `packages` configuration field. 2025-09-08T01:32:06,503 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,503 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,504 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,504 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,504 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,504 If you don't want 'publiforge.Processors.Publidoc2EPub2' to be distributed and are 2025-09-08T01:32:06,504 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2' via 2025-09-08T01:32:06,504 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,504 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,504 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,505 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,505 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,505 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,505 even if it does not contain any `.py` files. 2025-09-08T01:32:06,505 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,505 directory, all directories are treated like packages. 2025-09-08T01:32:06,505 ******************************************************************************** 2025-09-08T01:32:06,505 !! 2025-09-08T01:32:06,506 check.warn(importable) 2025-09-08T01:32:06,506 /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-08T01:32:06,506 !! 2025-09-08T01:32:06,506 ******************************************************************************** 2025-09-08T01:32:06,506 ############################ 2025-09-08T01:32:06,506 # Package would be ignored # 2025-09-08T01:32:06,506 ############################ 2025-09-08T01:32:06,506 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates' as an importable package[^1], 2025-09-08T01:32:06,506 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,506 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,506 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates' is explicitly added 2025-09-08T01:32:06,507 to the `packages` configuration field. 2025-09-08T01:32:06,507 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,507 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,507 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,507 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,507 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,507 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates' to be distributed and are 2025-09-08T01:32:06,507 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates' via 2025-09-08T01:32:06,508 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,508 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,508 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,508 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,508 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,508 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,508 even if it does not contain any `.py` files. 2025-09-08T01:32:06,508 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,509 directory, all directories are treated like packages. 2025-09-08T01:32:06,509 ******************************************************************************** 2025-09-08T01:32:06,509 !! 2025-09-08T01:32:06,509 check.warn(importable) 2025-09-08T01:32:06,509 /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-08T01:32:06,509 !! 2025-09-08T01:32:06,509 ******************************************************************************** 2025-09-08T01:32:06,509 ############################ 2025-09-08T01:32:06,509 # Package would be ignored # 2025-09-08T01:32:06,510 ############################ 2025-09-08T01:32:06,510 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' as an importable package[^1], 2025-09-08T01:32:06,510 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,510 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,510 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' is explicitly added 2025-09-08T01:32:06,510 to the `packages` configuration field. 2025-09-08T01:32:06,510 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,510 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,510 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,511 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,511 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,511 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' to be distributed and are 2025-09-08T01:32:06,511 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' via 2025-09-08T01:32:06,511 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,511 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,511 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,511 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,512 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,512 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,512 even if it does not contain any `.py` files. 2025-09-08T01:32:06,512 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,512 directory, all directories are treated like packages. 2025-09-08T01:32:06,512 ******************************************************************************** 2025-09-08T01:32:06,512 !! 2025-09-08T01:32:06,512 check.warn(importable) 2025-09-08T01:32:06,513 /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-08T01:32:06,513 !! 2025-09-08T01:32:06,513 ******************************************************************************** 2025-09-08T01:32:06,513 ############################ 2025-09-08T01:32:06,513 # Package would be ignored # 2025-09-08T01:32:06,513 ############################ 2025-09-08T01:32:06,513 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Variables' as an importable package[^1], 2025-09-08T01:32:06,513 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,513 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,513 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Variables' is explicitly added 2025-09-08T01:32:06,514 to the `packages` configuration field. 2025-09-08T01:32:06,514 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,514 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,514 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,514 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,514 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,514 If you don't want 'publiforge.Processors.Publidoc2EPub2.Variables' to be distributed and are 2025-09-08T01:32:06,514 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Variables' via 2025-09-08T01:32:06,515 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,515 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,515 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,515 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,515 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,515 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,515 even if it does not contain any `.py` files. 2025-09-08T01:32:06,515 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,515 directory, all directories are treated like packages. 2025-09-08T01:32:06,516 ******************************************************************************** 2025-09-08T01:32:06,516 !! 2025-09-08T01:32:06,516 check.warn(importable) 2025-09-08T01:32:06,516 /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-08T01:32:06,516 !! 2025-09-08T01:32:06,516 ******************************************************************************** 2025-09-08T01:32:06,516 ############################ 2025-09-08T01:32:06,516 # Package would be ignored # 2025-09-08T01:32:06,516 ############################ 2025-09-08T01:32:06,516 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Xsl' as an importable package[^1], 2025-09-08T01:32:06,517 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,517 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,517 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Xsl' is explicitly added 2025-09-08T01:32:06,517 to the `packages` configuration field. 2025-09-08T01:32:06,517 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,517 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,517 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,517 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,518 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,518 If you don't want 'publiforge.Processors.Publidoc2EPub2.Xsl' to be distributed and are 2025-09-08T01:32:06,518 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Xsl' via 2025-09-08T01:32:06,518 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,518 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,518 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,518 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,518 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,519 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,519 even if it does not contain any `.py` files. 2025-09-08T01:32:06,519 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,519 directory, all directories are treated like packages. 2025-09-08T01:32:06,519 ******************************************************************************** 2025-09-08T01:32:06,519 !! 2025-09-08T01:32:06,519 check.warn(importable) 2025-09-08T01:32:06,519 /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-08T01:32:06,519 !! 2025-09-08T01:32:06,519 ******************************************************************************** 2025-09-08T01:32:06,520 ############################ 2025-09-08T01:32:06,520 # Package would be ignored # 2025-09-08T01:32:06,520 ############################ 2025-09-08T01:32:06,520 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars' as an importable package[^1], 2025-09-08T01:32:06,520 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,520 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,520 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars' is explicitly added 2025-09-08T01:32:06,520 to the `packages` configuration field. 2025-09-08T01:32:06,520 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,520 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,521 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,521 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,521 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,521 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars' to be distributed and are 2025-09-08T01:32:06,521 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars' via 2025-09-08T01:32:06,521 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,521 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,521 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,522 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,522 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,522 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,522 even if it does not contain any `.py` files. 2025-09-08T01:32:06,522 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,522 directory, all directories are treated like packages. 2025-09-08T01:32:06,522 ******************************************************************************** 2025-09-08T01:32:06,523 !! 2025-09-08T01:32:06,523 check.warn(importable) 2025-09-08T01:32:06,523 /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-08T01:32:06,523 !! 2025-09-08T01:32:06,523 ******************************************************************************** 2025-09-08T01:32:06,523 ############################ 2025-09-08T01:32:06,523 # Package would be ignored # 2025-09-08T01:32:06,523 ############################ 2025-09-08T01:32:06,523 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.lib' as an importable package[^1], 2025-09-08T01:32:06,523 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,524 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,524 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.lib' is explicitly added 2025-09-08T01:32:06,524 to the `packages` configuration field. 2025-09-08T01:32:06,524 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,524 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,524 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,524 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,524 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,525 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.lib' to be distributed and are 2025-09-08T01:32:06,525 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.lib' via 2025-09-08T01:32:06,525 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,525 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,525 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,525 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,525 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,526 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,526 even if it does not contain any `.py` files. 2025-09-08T01:32:06,526 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,526 directory, all directories are treated like packages. 2025-09-08T01:32:06,526 ******************************************************************************** 2025-09-08T01:32:06,526 !! 2025-09-08T01:32:06,526 check.warn(importable) 2025-09-08T01:32:06,526 /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-08T01:32:06,526 !! 2025-09-08T01:32:06,526 ******************************************************************************** 2025-09-08T01:32:06,527 ############################ 2025-09-08T01:32:06,527 # Package would be ignored # 2025-09-08T01:32:06,527 ############################ 2025-09-08T01:32:06,527 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.licenses' as an importable package[^1], 2025-09-08T01:32:06,527 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,527 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,527 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.licenses' is explicitly added 2025-09-08T01:32:06,527 to the `packages` configuration field. 2025-09-08T01:32:06,527 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,527 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,527 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,528 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,528 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,528 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.licenses' to be distributed and are 2025-09-08T01:32:06,528 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.licenses' via 2025-09-08T01:32:06,528 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,528 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,528 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,528 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,529 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,529 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,529 even if it does not contain any `.py` files. 2025-09-08T01:32:06,529 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,529 directory, all directories are treated like packages. 2025-09-08T01:32:06,529 ******************************************************************************** 2025-09-08T01:32:06,529 !! 2025-09-08T01:32:06,529 check.warn(importable) 2025-09-08T01:32:06,530 /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-08T01:32:06,530 !! 2025-09-08T01:32:06,530 ******************************************************************************** 2025-09-08T01:32:06,530 ############################ 2025-09-08T01:32:06,530 # Package would be ignored # 2025-09-08T01:32:06,530 ############################ 2025-09-08T01:32:06,530 Python recognizes 'publiforge.Processors.Publidoc2EPub3' as an importable package[^1], 2025-09-08T01:32:06,530 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,530 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,530 package, please make sure that 'publiforge.Processors.Publidoc2EPub3' is explicitly added 2025-09-08T01:32:06,530 to the `packages` configuration field. 2025-09-08T01:32:06,531 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,531 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,531 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,531 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,531 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,531 If you don't want 'publiforge.Processors.Publidoc2EPub3' to be distributed and are 2025-09-08T01:32:06,531 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3' via 2025-09-08T01:32:06,531 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,532 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,532 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,532 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,532 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,532 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,532 even if it does not contain any `.py` files. 2025-09-08T01:32:06,532 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,532 directory, all directories are treated like packages. 2025-09-08T01:32:06,533 ******************************************************************************** 2025-09-08T01:32:06,533 !! 2025-09-08T01:32:06,533 check.warn(importable) 2025-09-08T01:32:06,533 /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-08T01:32:06,533 !! 2025-09-08T01:32:06,533 ******************************************************************************** 2025-09-08T01:32:06,533 ############################ 2025-09-08T01:32:06,533 # Package would be ignored # 2025-09-08T01:32:06,533 ############################ 2025-09-08T01:32:06,533 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates' as an importable package[^1], 2025-09-08T01:32:06,534 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,534 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,534 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates' is explicitly added 2025-09-08T01:32:06,534 to the `packages` configuration field. 2025-09-08T01:32:06,534 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,534 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,534 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,534 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,535 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,535 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates' to be distributed and are 2025-09-08T01:32:06,535 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates' via 2025-09-08T01:32:06,535 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,535 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,535 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,535 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,535 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,536 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,536 even if it does not contain any `.py` files. 2025-09-08T01:32:06,536 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,536 directory, all directories are treated like packages. 2025-09-08T01:32:06,536 ******************************************************************************** 2025-09-08T01:32:06,536 !! 2025-09-08T01:32:06,536 check.warn(importable) 2025-09-08T01:32:06,536 /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-08T01:32:06,536 !! 2025-09-08T01:32:06,537 ******************************************************************************** 2025-09-08T01:32:06,537 ############################ 2025-09-08T01:32:06,537 # Package would be ignored # 2025-09-08T01:32:06,537 ############################ 2025-09-08T01:32:06,537 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' as an importable package[^1], 2025-09-08T01:32:06,537 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,537 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,537 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' is explicitly added 2025-09-08T01:32:06,537 to the `packages` configuration field. 2025-09-08T01:32:06,538 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,538 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,538 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,538 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,538 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,538 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' to be distributed and are 2025-09-08T01:32:06,538 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' via 2025-09-08T01:32:06,538 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,538 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,539 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,539 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,539 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,539 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,539 even if it does not contain any `.py` files. 2025-09-08T01:32:06,539 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,539 directory, all directories are treated like packages. 2025-09-08T01:32:06,539 ******************************************************************************** 2025-09-08T01:32:06,540 !! 2025-09-08T01:32:06,540 check.warn(importable) 2025-09-08T01:32:06,540 /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-08T01:32:06,540 !! 2025-09-08T01:32:06,540 ******************************************************************************** 2025-09-08T01:32:06,540 ############################ 2025-09-08T01:32:06,540 # Package would be ignored # 2025-09-08T01:32:06,540 ############################ 2025-09-08T01:32:06,540 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Variables' as an importable package[^1], 2025-09-08T01:32:06,540 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,541 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,541 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Variables' is explicitly added 2025-09-08T01:32:06,541 to the `packages` configuration field. 2025-09-08T01:32:06,541 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,541 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,541 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,541 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,541 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,542 If you don't want 'publiforge.Processors.Publidoc2EPub3.Variables' to be distributed and are 2025-09-08T01:32:06,542 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Variables' via 2025-09-08T01:32:06,542 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,542 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,542 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,542 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,542 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,542 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,543 even if it does not contain any `.py` files. 2025-09-08T01:32:06,543 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,543 directory, all directories are treated like packages. 2025-09-08T01:32:06,543 ******************************************************************************** 2025-09-08T01:32:06,543 !! 2025-09-08T01:32:06,543 check.warn(importable) 2025-09-08T01:32:06,543 /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-08T01:32:06,543 !! 2025-09-08T01:32:06,543 ******************************************************************************** 2025-09-08T01:32:06,543 ############################ 2025-09-08T01:32:06,544 # Package would be ignored # 2025-09-08T01:32:06,544 ############################ 2025-09-08T01:32:06,544 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Xsl' as an importable package[^1], 2025-09-08T01:32:06,544 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,544 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,544 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Xsl' is explicitly added 2025-09-08T01:32:06,544 to the `packages` configuration field. 2025-09-08T01:32:06,544 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,544 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,544 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,545 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,545 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,545 If you don't want 'publiforge.Processors.Publidoc2EPub3.Xsl' to be distributed and are 2025-09-08T01:32:06,545 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Xsl' via 2025-09-08T01:32:06,545 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,545 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,545 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,545 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,546 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,546 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,546 even if it does not contain any `.py` files. 2025-09-08T01:32:06,546 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,546 directory, all directories are treated like packages. 2025-09-08T01:32:06,546 ******************************************************************************** 2025-09-08T01:32:06,546 !! 2025-09-08T01:32:06,546 check.warn(importable) 2025-09-08T01:32:06,546 /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-08T01:32:06,547 !! 2025-09-08T01:32:06,547 ******************************************************************************** 2025-09-08T01:32:06,547 ############################ 2025-09-08T01:32:06,547 # Package would be ignored # 2025-09-08T01:32:06,547 ############################ 2025-09-08T01:32:06,547 Python recognizes 'publiforge.Processors.Publidoc2Html5' as an importable package[^1], 2025-09-08T01:32:06,547 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,547 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,547 package, please make sure that 'publiforge.Processors.Publidoc2Html5' is explicitly added 2025-09-08T01:32:06,547 to the `packages` configuration field. 2025-09-08T01:32:06,548 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,548 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,548 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,548 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,548 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,548 If you don't want 'publiforge.Processors.Publidoc2Html5' to be distributed and are 2025-09-08T01:32:06,548 already explicitly excluding 'publiforge.Processors.Publidoc2Html5' via 2025-09-08T01:32:06,549 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,549 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,549 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,549 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,549 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,549 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,549 even if it does not contain any `.py` files. 2025-09-08T01:32:06,550 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,550 directory, all directories are treated like packages. 2025-09-08T01:32:06,550 ******************************************************************************** 2025-09-08T01:32:06,550 !! 2025-09-08T01:32:06,550 check.warn(importable) 2025-09-08T01:32:06,550 /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-08T01:32:06,550 !! 2025-09-08T01:32:06,550 ******************************************************************************** 2025-09-08T01:32:06,550 ############################ 2025-09-08T01:32:06,550 # Package would be ignored # 2025-09-08T01:32:06,551 ############################ 2025-09-08T01:32:06,551 Python recognizes 'publiforge.Processors.Publidoc2Html5.Variables' as an importable package[^1], 2025-09-08T01:32:06,551 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,551 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,551 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Variables' is explicitly added 2025-09-08T01:32:06,551 to the `packages` configuration field. 2025-09-08T01:32:06,551 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,551 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,551 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,551 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,552 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,552 If you don't want 'publiforge.Processors.Publidoc2Html5.Variables' to be distributed and are 2025-09-08T01:32:06,552 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Variables' via 2025-09-08T01:32:06,552 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,552 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,552 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,552 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,552 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,553 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,553 even if it does not contain any `.py` files. 2025-09-08T01:32:06,553 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,553 directory, all directories are treated like packages. 2025-09-08T01:32:06,553 ******************************************************************************** 2025-09-08T01:32:06,553 !! 2025-09-08T01:32:06,553 check.warn(importable) 2025-09-08T01:32:06,553 /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-08T01:32:06,553 !! 2025-09-08T01:32:06,554 ******************************************************************************** 2025-09-08T01:32:06,554 ############################ 2025-09-08T01:32:06,554 # Package would be ignored # 2025-09-08T01:32:06,554 ############################ 2025-09-08T01:32:06,554 Python recognizes 'publiforge.Processors.Publidoc2Html5.Xsl' as an importable package[^1], 2025-09-08T01:32:06,554 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,554 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,554 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Xsl' is explicitly added 2025-09-08T01:32:06,554 to the `packages` configuration field. 2025-09-08T01:32:06,554 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,555 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,555 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,555 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,555 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,555 If you don't want 'publiforge.Processors.Publidoc2Html5.Xsl' to be distributed and are 2025-09-08T01:32:06,555 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Xsl' via 2025-09-08T01:32:06,555 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,555 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,555 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,556 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,556 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,556 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,556 even if it does not contain any `.py` files. 2025-09-08T01:32:06,556 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,556 directory, all directories are treated like packages. 2025-09-08T01:32:06,556 ******************************************************************************** 2025-09-08T01:32:06,557 !! 2025-09-08T01:32:06,557 check.warn(importable) 2025-09-08T01:32:06,557 /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-08T01:32:06,557 !! 2025-09-08T01:32:06,557 ******************************************************************************** 2025-09-08T01:32:06,557 ############################ 2025-09-08T01:32:06,557 # Package would be ignored # 2025-09-08T01:32:06,557 ############################ 2025-09-08T01:32:06,557 Python recognizes 'publiforge.Processors.Publidoc2Pdf' as an importable package[^1], 2025-09-08T01:32:06,557 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,557 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,558 package, please make sure that 'publiforge.Processors.Publidoc2Pdf' is explicitly added 2025-09-08T01:32:06,558 to the `packages` configuration field. 2025-09-08T01:32:06,558 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,558 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,558 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,558 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,558 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,558 If you don't want 'publiforge.Processors.Publidoc2Pdf' to be distributed and are 2025-09-08T01:32:06,559 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf' via 2025-09-08T01:32:06,559 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,559 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,559 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,559 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,559 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,559 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,559 even if it does not contain any `.py` files. 2025-09-08T01:32:06,559 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,560 directory, all directories are treated like packages. 2025-09-08T01:32:06,560 ******************************************************************************** 2025-09-08T01:32:06,560 !! 2025-09-08T01:32:06,560 check.warn(importable) 2025-09-08T01:32:06,560 /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-08T01:32:06,560 !! 2025-09-08T01:32:06,560 ******************************************************************************** 2025-09-08T01:32:06,560 ############################ 2025-09-08T01:32:06,560 # Package would be ignored # 2025-09-08T01:32:06,560 ############################ 2025-09-08T01:32:06,561 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Fonts' as an importable package[^1], 2025-09-08T01:32:06,561 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,561 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,561 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Fonts' is explicitly added 2025-09-08T01:32:06,561 to the `packages` configuration field. 2025-09-08T01:32:06,561 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,561 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,561 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,562 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,562 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,562 If you don't want 'publiforge.Processors.Publidoc2Pdf.Fonts' to be distributed and are 2025-09-08T01:32:06,562 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Fonts' via 2025-09-08T01:32:06,562 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,562 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,562 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,562 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,563 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,563 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,563 even if it does not contain any `.py` files. 2025-09-08T01:32:06,563 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,563 directory, all directories are treated like packages. 2025-09-08T01:32:06,563 ******************************************************************************** 2025-09-08T01:32:06,563 !! 2025-09-08T01:32:06,563 check.warn(importable) 2025-09-08T01:32:06,564 /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-08T01:32:06,564 !! 2025-09-08T01:32:06,564 ******************************************************************************** 2025-09-08T01:32:06,564 ############################ 2025-09-08T01:32:06,564 # Package would be ignored # 2025-09-08T01:32:06,564 ############################ 2025-09-08T01:32:06,564 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Regex' as an importable package[^1], 2025-09-08T01:32:06,564 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,564 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,564 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Regex' is explicitly added 2025-09-08T01:32:06,565 to the `packages` configuration field. 2025-09-08T01:32:06,565 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,565 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,565 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,565 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,565 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,565 If you don't want 'publiforge.Processors.Publidoc2Pdf.Regex' to be distributed and are 2025-09-08T01:32:06,565 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Regex' via 2025-09-08T01:32:06,565 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,566 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,566 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,566 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,566 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,566 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,566 even if it does not contain any `.py` files. 2025-09-08T01:32:06,566 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,566 directory, all directories are treated like packages. 2025-09-08T01:32:06,567 ******************************************************************************** 2025-09-08T01:32:06,567 !! 2025-09-08T01:32:06,567 check.warn(importable) 2025-09-08T01:32:06,567 /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-08T01:32:06,567 !! 2025-09-08T01:32:06,567 ******************************************************************************** 2025-09-08T01:32:06,567 ############################ 2025-09-08T01:32:06,567 # Package would be ignored # 2025-09-08T01:32:06,567 ############################ 2025-09-08T01:32:06,567 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Variables' as an importable package[^1], 2025-09-08T01:32:06,568 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,568 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,568 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Variables' is explicitly added 2025-09-08T01:32:06,568 to the `packages` configuration field. 2025-09-08T01:32:06,568 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,568 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,568 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,568 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,569 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,569 If you don't want 'publiforge.Processors.Publidoc2Pdf.Variables' to be distributed and are 2025-09-08T01:32:06,569 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Variables' via 2025-09-08T01:32:06,569 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,569 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,569 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,569 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,569 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,570 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,570 even if it does not contain any `.py` files. 2025-09-08T01:32:06,570 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,570 directory, all directories are treated like packages. 2025-09-08T01:32:06,570 ******************************************************************************** 2025-09-08T01:32:06,570 !! 2025-09-08T01:32:06,570 check.warn(importable) 2025-09-08T01:32:06,570 /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-08T01:32:06,570 !! 2025-09-08T01:32:06,570 ******************************************************************************** 2025-09-08T01:32:06,571 ############################ 2025-09-08T01:32:06,571 # Package would be ignored # 2025-09-08T01:32:06,571 ############################ 2025-09-08T01:32:06,571 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Xsl' as an importable package[^1], 2025-09-08T01:32:06,571 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,571 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,571 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Xsl' is explicitly added 2025-09-08T01:32:06,571 to the `packages` configuration field. 2025-09-08T01:32:06,571 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,571 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,572 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,572 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,572 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,572 If you don't want 'publiforge.Processors.Publidoc2Pdf.Xsl' to be distributed and are 2025-09-08T01:32:06,572 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Xsl' via 2025-09-08T01:32:06,572 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,572 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,572 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,573 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,573 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,573 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,573 even if it does not contain any `.py` files. 2025-09-08T01:32:06,573 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,573 directory, all directories are treated like packages. 2025-09-08T01:32:06,573 ******************************************************************************** 2025-09-08T01:32:06,573 !! 2025-09-08T01:32:06,574 check.warn(importable) 2025-09-08T01:32:06,574 /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-08T01:32:06,574 !! 2025-09-08T01:32:06,574 ******************************************************************************** 2025-09-08T01:32:06,574 ############################ 2025-09-08T01:32:06,574 # Package would be ignored # 2025-09-08T01:32:06,574 ############################ 2025-09-08T01:32:06,574 Python recognizes 'publiforge.Processors.Publidoc2XHtml' as an importable package[^1], 2025-09-08T01:32:06,574 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,575 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,575 package, please make sure that 'publiforge.Processors.Publidoc2XHtml' is explicitly added 2025-09-08T01:32:06,575 to the `packages` configuration field. 2025-09-08T01:32:06,575 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,575 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,575 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,575 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,575 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,576 If you don't want 'publiforge.Processors.Publidoc2XHtml' to be distributed and are 2025-09-08T01:32:06,576 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml' via 2025-09-08T01:32:06,576 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,576 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,576 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,576 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,576 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,576 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,577 even if it does not contain any `.py` files. 2025-09-08T01:32:06,577 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,577 directory, all directories are treated like packages. 2025-09-08T01:32:06,577 ******************************************************************************** 2025-09-08T01:32:06,577 !! 2025-09-08T01:32:06,577 check.warn(importable) 2025-09-08T01:32:06,577 /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-08T01:32:06,577 !! 2025-09-08T01:32:06,577 ******************************************************************************** 2025-09-08T01:32:06,577 ############################ 2025-09-08T01:32:06,578 # Package would be ignored # 2025-09-08T01:32:06,578 ############################ 2025-09-08T01:32:06,578 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Regex' as an importable package[^1], 2025-09-08T01:32:06,578 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,578 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,578 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Regex' is explicitly added 2025-09-08T01:32:06,578 to the `packages` configuration field. 2025-09-08T01:32:06,578 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,578 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,578 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,579 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,579 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,579 If you don't want 'publiforge.Processors.Publidoc2XHtml.Regex' to be distributed and are 2025-09-08T01:32:06,579 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Regex' via 2025-09-08T01:32:06,579 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,579 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,579 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,579 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,580 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,580 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,580 even if it does not contain any `.py` files. 2025-09-08T01:32:06,580 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,580 directory, all directories are treated like packages. 2025-09-08T01:32:06,580 ******************************************************************************** 2025-09-08T01:32:06,580 !! 2025-09-08T01:32:06,580 check.warn(importable) 2025-09-08T01:32:06,580 /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-08T01:32:06,581 !! 2025-09-08T01:32:06,581 ******************************************************************************** 2025-09-08T01:32:06,581 ############################ 2025-09-08T01:32:06,581 # Package would be ignored # 2025-09-08T01:32:06,581 ############################ 2025-09-08T01:32:06,581 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Css' as an importable package[^1], 2025-09-08T01:32:06,581 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,581 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,581 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Css' is explicitly added 2025-09-08T01:32:06,581 to the `packages` configuration field. 2025-09-08T01:32:06,582 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,582 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,582 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,582 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,582 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,582 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Css' to be distributed and are 2025-09-08T01:32:06,582 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Css' via 2025-09-08T01:32:06,582 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,582 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,583 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,583 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,583 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,583 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,583 even if it does not contain any `.py` files. 2025-09-08T01:32:06,583 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,583 directory, all directories are treated like packages. 2025-09-08T01:32:06,583 ******************************************************************************** 2025-09-08T01:32:06,584 !! 2025-09-08T01:32:06,584 check.warn(importable) 2025-09-08T01:32:06,584 /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-08T01:32:06,584 !! 2025-09-08T01:32:06,584 ******************************************************************************** 2025-09-08T01:32:06,584 ############################ 2025-09-08T01:32:06,584 # Package would be ignored # 2025-09-08T01:32:06,584 ############################ 2025-09-08T01:32:06,584 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Images' as an importable package[^1], 2025-09-08T01:32:06,584 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,585 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,585 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Images' is explicitly added 2025-09-08T01:32:06,585 to the `packages` configuration field. 2025-09-08T01:32:06,585 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,585 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,585 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,585 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,585 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,586 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Images' to be distributed and are 2025-09-08T01:32:06,586 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Images' via 2025-09-08T01:32:06,586 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,586 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,586 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,586 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,586 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,587 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,587 even if it does not contain any `.py` files. 2025-09-08T01:32:06,587 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,587 directory, all directories are treated like packages. 2025-09-08T01:32:06,587 ******************************************************************************** 2025-09-08T01:32:06,587 !! 2025-09-08T01:32:06,587 check.warn(importable) 2025-09-08T01:32:06,587 /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-08T01:32:06,587 !! 2025-09-08T01:32:06,588 ******************************************************************************** 2025-09-08T01:32:06,588 ############################ 2025-09-08T01:32:06,588 # Package would be ignored # 2025-09-08T01:32:06,588 ############################ 2025-09-08T01:32:06,588 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Js' as an importable package[^1], 2025-09-08T01:32:06,588 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,588 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,588 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Js' is explicitly added 2025-09-08T01:32:06,588 to the `packages` configuration field. 2025-09-08T01:32:06,588 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,589 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,589 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,589 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,589 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,589 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Js' to be distributed and are 2025-09-08T01:32:06,589 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Js' via 2025-09-08T01:32:06,589 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,589 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,589 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,590 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,590 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,590 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,590 even if it does not contain any `.py` files. 2025-09-08T01:32:06,590 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,590 directory, all directories are treated like packages. 2025-09-08T01:32:06,590 ******************************************************************************** 2025-09-08T01:32:06,591 !! 2025-09-08T01:32:06,591 check.warn(importable) 2025-09-08T01:32:06,591 /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-08T01:32:06,591 !! 2025-09-08T01:32:06,591 ******************************************************************************** 2025-09-08T01:32:06,591 ############################ 2025-09-08T01:32:06,591 # Package would be ignored # 2025-09-08T01:32:06,591 ############################ 2025-09-08T01:32:06,591 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Variables' as an importable package[^1], 2025-09-08T01:32:06,591 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,592 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,592 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Variables' is explicitly added 2025-09-08T01:32:06,592 to the `packages` configuration field. 2025-09-08T01:32:06,592 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,592 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,592 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,592 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,592 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,593 If you don't want 'publiforge.Processors.Publidoc2XHtml.Variables' to be distributed and are 2025-09-08T01:32:06,593 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Variables' via 2025-09-08T01:32:06,593 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,593 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,593 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,593 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,593 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,593 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,594 even if it does not contain any `.py` files. 2025-09-08T01:32:06,594 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,594 directory, all directories are treated like packages. 2025-09-08T01:32:06,594 ******************************************************************************** 2025-09-08T01:32:06,594 !! 2025-09-08T01:32:06,594 check.warn(importable) 2025-09-08T01:32:06,594 /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-08T01:32:06,594 !! 2025-09-08T01:32:06,594 ******************************************************************************** 2025-09-08T01:32:06,594 ############################ 2025-09-08T01:32:06,595 # Package would be ignored # 2025-09-08T01:32:06,595 ############################ 2025-09-08T01:32:06,595 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Xsl' as an importable package[^1], 2025-09-08T01:32:06,595 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,595 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,595 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Xsl' is explicitly added 2025-09-08T01:32:06,595 to the `packages` configuration field. 2025-09-08T01:32:06,595 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,595 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,595 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,596 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,596 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,596 If you don't want 'publiforge.Processors.Publidoc2XHtml.Xsl' to be distributed and are 2025-09-08T01:32:06,596 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Xsl' via 2025-09-08T01:32:06,596 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,596 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,596 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,596 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,597 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,597 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,597 even if it does not contain any `.py` files. 2025-09-08T01:32:06,597 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,597 directory, all directories are treated like packages. 2025-09-08T01:32:06,597 ******************************************************************************** 2025-09-08T01:32:06,597 !! 2025-09-08T01:32:06,597 check.warn(importable) 2025-09-08T01:32:06,597 /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-08T01:32:06,598 !! 2025-09-08T01:32:06,598 ******************************************************************************** 2025-09-08T01:32:06,598 ############################ 2025-09-08T01:32:06,598 # Package would be ignored # 2025-09-08T01:32:06,598 ############################ 2025-09-08T01:32:06,598 Python recognizes 'publiforge.Processors.PublidocClean' as an importable package[^1], 2025-09-08T01:32:06,598 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,598 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,598 package, please make sure that 'publiforge.Processors.PublidocClean' is explicitly added 2025-09-08T01:32:06,598 to the `packages` configuration field. 2025-09-08T01:32:06,599 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,599 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,599 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,599 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,599 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,599 If you don't want 'publiforge.Processors.PublidocClean' to be distributed and are 2025-09-08T01:32:06,599 already explicitly excluding 'publiforge.Processors.PublidocClean' via 2025-09-08T01:32:06,600 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,600 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,600 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,600 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,600 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,600 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,600 even if it does not contain any `.py` files. 2025-09-08T01:32:06,600 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,601 directory, all directories are treated like packages. 2025-09-08T01:32:06,601 ******************************************************************************** 2025-09-08T01:32:06,601 !! 2025-09-08T01:32:06,601 check.warn(importable) 2025-09-08T01:32:06,601 /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-08T01:32:06,601 !! 2025-09-08T01:32:06,601 ******************************************************************************** 2025-09-08T01:32:06,601 ############################ 2025-09-08T01:32:06,601 # Package would be ignored # 2025-09-08T01:32:06,601 ############################ 2025-09-08T01:32:06,602 Python recognizes 'publiforge.Processors.PublidocClean.Regex' as an importable package[^1], 2025-09-08T01:32:06,602 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,602 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,602 package, please make sure that 'publiforge.Processors.PublidocClean.Regex' is explicitly added 2025-09-08T01:32:06,602 to the `packages` configuration field. 2025-09-08T01:32:06,602 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,602 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,602 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,602 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,603 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,603 If you don't want 'publiforge.Processors.PublidocClean.Regex' to be distributed and are 2025-09-08T01:32:06,603 already explicitly excluding 'publiforge.Processors.PublidocClean.Regex' via 2025-09-08T01:32:06,603 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,603 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,603 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,603 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,603 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,604 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,604 even if it does not contain any `.py` files. 2025-09-08T01:32:06,604 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,604 directory, all directories are treated like packages. 2025-09-08T01:32:06,604 ******************************************************************************** 2025-09-08T01:32:06,604 !! 2025-09-08T01:32:06,604 check.warn(importable) 2025-09-08T01:32:06,604 /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-08T01:32:06,604 !! 2025-09-08T01:32:06,605 ******************************************************************************** 2025-09-08T01:32:06,605 ############################ 2025-09-08T01:32:06,605 # Package would be ignored # 2025-09-08T01:32:06,605 ############################ 2025-09-08T01:32:06,605 Python recognizes 'publiforge.Processors.PublidocClean.Variables' as an importable package[^1], 2025-09-08T01:32:06,605 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,605 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,605 package, please make sure that 'publiforge.Processors.PublidocClean.Variables' is explicitly added 2025-09-08T01:32:06,605 to the `packages` configuration field. 2025-09-08T01:32:06,606 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,606 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,606 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,606 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,606 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,606 If you don't want 'publiforge.Processors.PublidocClean.Variables' to be distributed and are 2025-09-08T01:32:06,606 already explicitly excluding 'publiforge.Processors.PublidocClean.Variables' via 2025-09-08T01:32:06,606 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,606 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,606 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,607 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,607 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,607 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,607 even if it does not contain any `.py` files. 2025-09-08T01:32:06,607 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,607 directory, all directories are treated like packages. 2025-09-08T01:32:06,607 ******************************************************************************** 2025-09-08T01:32:06,608 !! 2025-09-08T01:32:06,608 check.warn(importable) 2025-09-08T01:32:06,608 /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-08T01:32:06,608 !! 2025-09-08T01:32:06,608 ******************************************************************************** 2025-09-08T01:32:06,608 ############################ 2025-09-08T01:32:06,608 # Package would be ignored # 2025-09-08T01:32:06,608 ############################ 2025-09-08T01:32:06,608 Python recognizes 'publiforge.Processors.PublidocClean.Xsl' as an importable package[^1], 2025-09-08T01:32:06,608 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,609 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,609 package, please make sure that 'publiforge.Processors.PublidocClean.Xsl' is explicitly added 2025-09-08T01:32:06,609 to the `packages` configuration field. 2025-09-08T01:32:06,609 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,609 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,609 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,609 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,609 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,610 If you don't want 'publiforge.Processors.PublidocClean.Xsl' to be distributed and are 2025-09-08T01:32:06,610 already explicitly excluding 'publiforge.Processors.PublidocClean.Xsl' via 2025-09-08T01:32:06,610 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,610 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,610 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,610 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,610 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,610 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,611 even if it does not contain any `.py` files. 2025-09-08T01:32:06,611 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,611 directory, all directories are treated like packages. 2025-09-08T01:32:06,611 ******************************************************************************** 2025-09-08T01:32:06,611 !! 2025-09-08T01:32:06,611 check.warn(importable) 2025-09-08T01:32:06,611 /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-08T01:32:06,611 !! 2025-09-08T01:32:06,611 ******************************************************************************** 2025-09-08T01:32:06,611 ############################ 2025-09-08T01:32:06,611 # Package would be ignored # 2025-09-08T01:32:06,612 ############################ 2025-09-08T01:32:06,612 Python recognizes 'publiforge.Processors.PublidocValid' as an importable package[^1], 2025-09-08T01:32:06,612 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,612 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,612 package, please make sure that 'publiforge.Processors.PublidocValid' is explicitly added 2025-09-08T01:32:06,612 to the `packages` configuration field. 2025-09-08T01:32:06,612 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,612 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,612 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,613 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,613 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,613 If you don't want 'publiforge.Processors.PublidocValid' to be distributed and are 2025-09-08T01:32:06,613 already explicitly excluding 'publiforge.Processors.PublidocValid' via 2025-09-08T01:32:06,613 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,613 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,613 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,614 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,614 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,614 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,614 even if it does not contain any `.py` files. 2025-09-08T01:32:06,614 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,614 directory, all directories are treated like packages. 2025-09-08T01:32:06,614 ******************************************************************************** 2025-09-08T01:32:06,615 !! 2025-09-08T01:32:06,615 check.warn(importable) 2025-09-08T01:32:06,615 /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-08T01:32:06,615 !! 2025-09-08T01:32:06,615 ******************************************************************************** 2025-09-08T01:32:06,615 ############################ 2025-09-08T01:32:06,615 # Package would be ignored # 2025-09-08T01:32:06,615 ############################ 2025-09-08T01:32:06,615 Python recognizes 'publiforge.Processors.PublidocValid.RelaxNG' as an importable package[^1], 2025-09-08T01:32:06,615 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,616 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,616 package, please make sure that 'publiforge.Processors.PublidocValid.RelaxNG' is explicitly added 2025-09-08T01:32:06,616 to the `packages` configuration field. 2025-09-08T01:32:06,616 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,616 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,616 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,616 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,616 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,616 If you don't want 'publiforge.Processors.PublidocValid.RelaxNG' to be distributed and are 2025-09-08T01:32:06,617 already explicitly excluding 'publiforge.Processors.PublidocValid.RelaxNG' via 2025-09-08T01:32:06,617 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,617 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,617 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,617 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,617 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,617 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,617 even if it does not contain any `.py` files. 2025-09-08T01:32:06,618 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,618 directory, all directories are treated like packages. 2025-09-08T01:32:06,618 ******************************************************************************** 2025-09-08T01:32:06,618 !! 2025-09-08T01:32:06,618 check.warn(importable) 2025-09-08T01:32:06,618 /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-08T01:32:06,618 !! 2025-09-08T01:32:06,618 ******************************************************************************** 2025-09-08T01:32:06,618 ############################ 2025-09-08T01:32:06,618 # Package would be ignored # 2025-09-08T01:32:06,619 ############################ 2025-09-08T01:32:06,619 Python recognizes 'publiforge.Processors.Publiquiz2EPub3' as an importable package[^1], 2025-09-08T01:32:06,619 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,619 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,619 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3' is explicitly added 2025-09-08T01:32:06,619 to the `packages` configuration field. 2025-09-08T01:32:06,619 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,619 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,619 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,620 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,620 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,620 If you don't want 'publiforge.Processors.Publiquiz2EPub3' to be distributed and are 2025-09-08T01:32:06,620 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3' via 2025-09-08T01:32:06,620 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,620 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,620 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,620 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,620 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,621 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,621 even if it does not contain any `.py` files. 2025-09-08T01:32:06,621 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,621 directory, all directories are treated like packages. 2025-09-08T01:32:06,621 ******************************************************************************** 2025-09-08T01:32:06,621 !! 2025-09-08T01:32:06,621 check.warn(importable) 2025-09-08T01:32:06,621 /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-08T01:32:06,621 !! 2025-09-08T01:32:06,622 ******************************************************************************** 2025-09-08T01:32:06,622 ############################ 2025-09-08T01:32:06,622 # Package would be ignored # 2025-09-08T01:32:06,622 ############################ 2025-09-08T01:32:06,622 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Variables' as an importable package[^1], 2025-09-08T01:32:06,622 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,622 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,622 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Variables' is explicitly added 2025-09-08T01:32:06,622 to the `packages` configuration field. 2025-09-08T01:32:06,623 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,623 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,623 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,623 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,623 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,623 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Variables' to be distributed and are 2025-09-08T01:32:06,623 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Variables' via 2025-09-08T01:32:06,623 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,623 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,624 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,624 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,624 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,624 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,624 even if it does not contain any `.py` files. 2025-09-08T01:32:06,624 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,624 directory, all directories are treated like packages. 2025-09-08T01:32:06,624 ******************************************************************************** 2025-09-08T01:32:06,625 !! 2025-09-08T01:32:06,625 check.warn(importable) 2025-09-08T01:32:06,625 /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-08T01:32:06,625 !! 2025-09-08T01:32:06,625 ******************************************************************************** 2025-09-08T01:32:06,625 ############################ 2025-09-08T01:32:06,625 # Package would be ignored # 2025-09-08T01:32:06,625 ############################ 2025-09-08T01:32:06,625 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Xsl' as an importable package[^1], 2025-09-08T01:32:06,625 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,626 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,626 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Xsl' is explicitly added 2025-09-08T01:32:06,626 to the `packages` configuration field. 2025-09-08T01:32:06,626 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,626 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,626 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,626 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,627 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,627 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Xsl' to be distributed and are 2025-09-08T01:32:06,627 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Xsl' via 2025-09-08T01:32:06,627 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,627 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,627 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,627 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,627 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,628 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,628 even if it does not contain any `.py` files. 2025-09-08T01:32:06,628 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,628 directory, all directories are treated like packages. 2025-09-08T01:32:06,628 ******************************************************************************** 2025-09-08T01:32:06,628 !! 2025-09-08T01:32:06,628 check.warn(importable) 2025-09-08T01:32:06,628 /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-08T01:32:06,628 !! 2025-09-08T01:32:06,629 ******************************************************************************** 2025-09-08T01:32:06,629 ############################ 2025-09-08T01:32:06,629 # Package would be ignored # 2025-09-08T01:32:06,629 ############################ 2025-09-08T01:32:06,629 Python recognizes 'publiforge.Processors.Publiquiz2Html5' as an importable package[^1], 2025-09-08T01:32:06,629 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,629 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,629 package, please make sure that 'publiforge.Processors.Publiquiz2Html5' is explicitly added 2025-09-08T01:32:06,629 to the `packages` configuration field. 2025-09-08T01:32:06,629 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,630 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,630 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,630 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,630 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,630 If you don't want 'publiforge.Processors.Publiquiz2Html5' to be distributed and are 2025-09-08T01:32:06,630 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5' via 2025-09-08T01:32:06,630 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,630 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,631 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,631 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,631 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,631 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,631 even if it does not contain any `.py` files. 2025-09-08T01:32:06,631 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,631 directory, all directories are treated like packages. 2025-09-08T01:32:06,631 ******************************************************************************** 2025-09-08T01:32:06,632 !! 2025-09-08T01:32:06,632 check.warn(importable) 2025-09-08T01:32:06,632 /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-08T01:32:06,632 !! 2025-09-08T01:32:06,632 ******************************************************************************** 2025-09-08T01:32:06,632 ############################ 2025-09-08T01:32:06,632 # Package would be ignored # 2025-09-08T01:32:06,632 ############################ 2025-09-08T01:32:06,632 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Css' as an importable package[^1], 2025-09-08T01:32:06,632 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,633 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,633 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Css' is explicitly added 2025-09-08T01:32:06,633 to the `packages` configuration field. 2025-09-08T01:32:06,633 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,633 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,633 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,633 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,634 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,634 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Css' to be distributed and are 2025-09-08T01:32:06,634 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Css' via 2025-09-08T01:32:06,634 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,634 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,634 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,634 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,634 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,635 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,635 even if it does not contain any `.py` files. 2025-09-08T01:32:06,635 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,635 directory, all directories are treated like packages. 2025-09-08T01:32:06,635 ******************************************************************************** 2025-09-08T01:32:06,635 !! 2025-09-08T01:32:06,635 check.warn(importable) 2025-09-08T01:32:06,635 /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-08T01:32:06,635 !! 2025-09-08T01:32:06,636 ******************************************************************************** 2025-09-08T01:32:06,636 ############################ 2025-09-08T01:32:06,636 # Package would be ignored # 2025-09-08T01:32:06,636 ############################ 2025-09-08T01:32:06,636 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Js' as an importable package[^1], 2025-09-08T01:32:06,636 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,636 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,636 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Js' is explicitly added 2025-09-08T01:32:06,636 to the `packages` configuration field. 2025-09-08T01:32:06,636 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,637 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,637 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,637 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,637 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,637 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Js' to be distributed and are 2025-09-08T01:32:06,637 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Js' via 2025-09-08T01:32:06,637 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,637 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,637 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,638 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,638 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,638 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,638 even if it does not contain any `.py` files. 2025-09-08T01:32:06,638 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,638 directory, all directories are treated like packages. 2025-09-08T01:32:06,638 ******************************************************************************** 2025-09-08T01:32:06,639 !! 2025-09-08T01:32:06,639 check.warn(importable) 2025-09-08T01:32:06,639 /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-08T01:32:06,639 !! 2025-09-08T01:32:06,639 ******************************************************************************** 2025-09-08T01:32:06,639 ############################ 2025-09-08T01:32:06,639 # Package would be ignored # 2025-09-08T01:32:06,639 ############################ 2025-09-08T01:32:06,639 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Variables' as an importable package[^1], 2025-09-08T01:32:06,640 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,640 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,640 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Variables' is explicitly added 2025-09-08T01:32:06,640 to the `packages` configuration field. 2025-09-08T01:32:06,640 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,640 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,640 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,640 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,641 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,641 If you don't want 'publiforge.Processors.Publiquiz2Html5.Variables' to be distributed and are 2025-09-08T01:32:06,641 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Variables' via 2025-09-08T01:32:06,641 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,641 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,641 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,641 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,641 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,642 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,642 even if it does not contain any `.py` files. 2025-09-08T01:32:06,642 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,642 directory, all directories are treated like packages. 2025-09-08T01:32:06,642 ******************************************************************************** 2025-09-08T01:32:06,642 !! 2025-09-08T01:32:06,642 check.warn(importable) 2025-09-08T01:32:06,642 /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-08T01:32:06,642 !! 2025-09-08T01:32:06,643 ******************************************************************************** 2025-09-08T01:32:06,643 ############################ 2025-09-08T01:32:06,643 # Package would be ignored # 2025-09-08T01:32:06,643 ############################ 2025-09-08T01:32:06,643 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Xsl' as an importable package[^1], 2025-09-08T01:32:06,643 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,643 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,643 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Xsl' is explicitly added 2025-09-08T01:32:06,643 to the `packages` configuration field. 2025-09-08T01:32:06,644 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,644 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,644 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,644 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,644 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,644 If you don't want 'publiforge.Processors.Publiquiz2Html5.Xsl' to be distributed and are 2025-09-08T01:32:06,644 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Xsl' via 2025-09-08T01:32:06,644 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,644 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,645 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,645 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,645 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,645 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,645 even if it does not contain any `.py` files. 2025-09-08T01:32:06,645 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,645 directory, all directories are treated like packages. 2025-09-08T01:32:06,645 ******************************************************************************** 2025-09-08T01:32:06,646 !! 2025-09-08T01:32:06,646 check.warn(importable) 2025-09-08T01:32:06,646 /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-08T01:32:06,646 !! 2025-09-08T01:32:06,646 ******************************************************************************** 2025-09-08T01:32:06,646 ############################ 2025-09-08T01:32:06,646 # Package would be ignored # 2025-09-08T01:32:06,646 ############################ 2025-09-08T01:32:06,646 Python recognizes 'publiforge.Processors.Publiset2Publidoc' as an importable package[^1], 2025-09-08T01:32:06,647 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,647 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,647 package, please make sure that 'publiforge.Processors.Publiset2Publidoc' is explicitly added 2025-09-08T01:32:06,647 to the `packages` configuration field. 2025-09-08T01:32:06,647 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,647 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,647 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,647 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,648 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,648 If you don't want 'publiforge.Processors.Publiset2Publidoc' to be distributed and are 2025-09-08T01:32:06,648 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc' via 2025-09-08T01:32:06,648 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,648 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,648 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,648 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,648 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,649 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,649 even if it does not contain any `.py` files. 2025-09-08T01:32:06,649 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,649 directory, all directories are treated like packages. 2025-09-08T01:32:06,649 ******************************************************************************** 2025-09-08T01:32:06,649 !! 2025-09-08T01:32:06,649 check.warn(importable) 2025-09-08T01:32:06,649 /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-08T01:32:06,649 !! 2025-09-08T01:32:06,650 ******************************************************************************** 2025-09-08T01:32:06,650 ############################ 2025-09-08T01:32:06,650 # Package would be ignored # 2025-09-08T01:32:06,650 ############################ 2025-09-08T01:32:06,650 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Variables' as an importable package[^1], 2025-09-08T01:32:06,650 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,650 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,650 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Variables' is explicitly added 2025-09-08T01:32:06,650 to the `packages` configuration field. 2025-09-08T01:32:06,650 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,651 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,651 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,651 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,651 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,651 If you don't want 'publiforge.Processors.Publiset2Publidoc.Variables' to be distributed and are 2025-09-08T01:32:06,651 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Variables' via 2025-09-08T01:32:06,651 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,651 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,652 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,652 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,652 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,652 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,652 even if it does not contain any `.py` files. 2025-09-08T01:32:06,652 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,652 directory, all directories are treated like packages. 2025-09-08T01:32:06,652 ******************************************************************************** 2025-09-08T01:32:06,653 !! 2025-09-08T01:32:06,653 check.warn(importable) 2025-09-08T01:32:06,653 /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-08T01:32:06,653 !! 2025-09-08T01:32:06,653 ******************************************************************************** 2025-09-08T01:32:06,653 ############################ 2025-09-08T01:32:06,653 # Package would be ignored # 2025-09-08T01:32:06,653 ############################ 2025-09-08T01:32:06,653 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Xsl' as an importable package[^1], 2025-09-08T01:32:06,654 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,654 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,654 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Xsl' is explicitly added 2025-09-08T01:32:06,654 to the `packages` configuration field. 2025-09-08T01:32:06,654 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,654 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,654 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,654 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,655 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,655 If you don't want 'publiforge.Processors.Publiset2Publidoc.Xsl' to be distributed and are 2025-09-08T01:32:06,655 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Xsl' via 2025-09-08T01:32:06,655 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,655 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,655 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,655 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,655 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,656 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,656 even if it does not contain any `.py` files. 2025-09-08T01:32:06,656 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,656 directory, all directories are treated like packages. 2025-09-08T01:32:06,656 ******************************************************************************** 2025-09-08T01:32:06,656 !! 2025-09-08T01:32:06,656 check.warn(importable) 2025-09-08T01:32:06,656 /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-08T01:32:06,656 !! 2025-09-08T01:32:06,657 ******************************************************************************** 2025-09-08T01:32:06,657 ############################ 2025-09-08T01:32:06,657 # Package would be ignored # 2025-09-08T01:32:06,657 ############################ 2025-09-08T01:32:06,657 Python recognizes 'publiforge.Processors.Publiset4Publidoc' as an importable package[^1], 2025-09-08T01:32:06,657 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,657 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,657 package, please make sure that 'publiforge.Processors.Publiset4Publidoc' is explicitly added 2025-09-08T01:32:06,657 to the `packages` configuration field. 2025-09-08T01:32:06,657 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,658 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,658 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,658 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,658 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,658 If you don't want 'publiforge.Processors.Publiset4Publidoc' to be distributed and are 2025-09-08T01:32:06,658 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc' via 2025-09-08T01:32:06,658 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,658 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,658 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,659 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,659 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,659 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,659 even if it does not contain any `.py` files. 2025-09-08T01:32:06,659 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,659 directory, all directories are treated like packages. 2025-09-08T01:32:06,659 ******************************************************************************** 2025-09-08T01:32:06,659 !! 2025-09-08T01:32:06,660 check.warn(importable) 2025-09-08T01:32:06,660 /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-08T01:32:06,660 !! 2025-09-08T01:32:06,660 ******************************************************************************** 2025-09-08T01:32:06,660 ############################ 2025-09-08T01:32:06,660 # Package would be ignored # 2025-09-08T01:32:06,660 ############################ 2025-09-08T01:32:06,660 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Variables' as an importable package[^1], 2025-09-08T01:32:06,660 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,661 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,661 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Variables' is explicitly added 2025-09-08T01:32:06,661 to the `packages` configuration field. 2025-09-08T01:32:06,661 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,661 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,661 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,661 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,661 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,662 If you don't want 'publiforge.Processors.Publiset4Publidoc.Variables' to be distributed and are 2025-09-08T01:32:06,662 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Variables' via 2025-09-08T01:32:06,662 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,662 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,662 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,662 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,662 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,662 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,663 even if it does not contain any `.py` files. 2025-09-08T01:32:06,663 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,663 directory, all directories are treated like packages. 2025-09-08T01:32:06,663 ******************************************************************************** 2025-09-08T01:32:06,663 !! 2025-09-08T01:32:06,663 check.warn(importable) 2025-09-08T01:32:06,663 /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-08T01:32:06,663 !! 2025-09-08T01:32:06,663 ******************************************************************************** 2025-09-08T01:32:06,664 ############################ 2025-09-08T01:32:06,664 # Package would be ignored # 2025-09-08T01:32:06,664 ############################ 2025-09-08T01:32:06,664 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Xsl' as an importable package[^1], 2025-09-08T01:32:06,664 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,664 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,664 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Xsl' is explicitly added 2025-09-08T01:32:06,664 to the `packages` configuration field. 2025-09-08T01:32:06,665 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,665 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,665 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,665 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,665 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,665 If you don't want 'publiforge.Processors.Publiset4Publidoc.Xsl' to be distributed and are 2025-09-08T01:32:06,665 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Xsl' via 2025-09-08T01:32:06,666 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,666 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,666 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,666 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,666 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,666 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,666 even if it does not contain any `.py` files. 2025-09-08T01:32:06,666 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,667 directory, all directories are treated like packages. 2025-09-08T01:32:06,667 ******************************************************************************** 2025-09-08T01:32:06,667 !! 2025-09-08T01:32:06,667 check.warn(importable) 2025-09-08T01:32:06,667 /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-08T01:32:06,667 !! 2025-09-08T01:32:06,667 ******************************************************************************** 2025-09-08T01:32:06,667 ############################ 2025-09-08T01:32:06,667 # Package would be ignored # 2025-09-08T01:32:06,668 ############################ 2025-09-08T01:32:06,668 Python recognizes 'publiforge.Processors.Publiset4Publiquiz' as an importable package[^1], 2025-09-08T01:32:06,668 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,668 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,668 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz' is explicitly added 2025-09-08T01:32:06,668 to the `packages` configuration field. 2025-09-08T01:32:06,668 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,668 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,668 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,669 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,669 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,669 If you don't want 'publiforge.Processors.Publiset4Publiquiz' to be distributed and are 2025-09-08T01:32:06,669 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz' via 2025-09-08T01:32:06,669 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,669 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,669 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,670 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,670 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,670 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,670 even if it does not contain any `.py` files. 2025-09-08T01:32:06,670 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,670 directory, all directories are treated like packages. 2025-09-08T01:32:06,670 ******************************************************************************** 2025-09-08T01:32:06,670 !! 2025-09-08T01:32:06,671 check.warn(importable) 2025-09-08T01:32:06,671 /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-08T01:32:06,671 !! 2025-09-08T01:32:06,671 ******************************************************************************** 2025-09-08T01:32:06,671 ############################ 2025-09-08T01:32:06,671 # Package would be ignored # 2025-09-08T01:32:06,671 ############################ 2025-09-08T01:32:06,671 Python recognizes 'publiforge.Processors.Publiset4Publiquiz.Xsl' as an importable package[^1], 2025-09-08T01:32:06,671 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,672 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,672 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz.Xsl' is explicitly added 2025-09-08T01:32:06,672 to the `packages` configuration field. 2025-09-08T01:32:06,672 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,672 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,672 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,672 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,672 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,673 If you don't want 'publiforge.Processors.Publiset4Publiquiz.Xsl' to be distributed and are 2025-09-08T01:32:06,673 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz.Xsl' via 2025-09-08T01:32:06,673 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,673 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,673 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,673 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,673 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,674 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,674 even if it does not contain any `.py` files. 2025-09-08T01:32:06,674 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,674 directory, all directories are treated like packages. 2025-09-08T01:32:06,674 ******************************************************************************** 2025-09-08T01:32:06,674 !! 2025-09-08T01:32:06,674 check.warn(importable) 2025-09-08T01:32:06,674 /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-08T01:32:06,675 !! 2025-09-08T01:32:06,675 ******************************************************************************** 2025-09-08T01:32:06,675 ############################ 2025-09-08T01:32:06,675 # Package would be ignored # 2025-09-08T01:32:06,675 ############################ 2025-09-08T01:32:06,675 Python recognizes 'publiforge.RelaxNG' as an importable package[^1], 2025-09-08T01:32:06,675 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,675 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,675 package, please make sure that 'publiforge.RelaxNG' is explicitly added 2025-09-08T01:32:06,676 to the `packages` configuration field. 2025-09-08T01:32:06,676 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,676 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,676 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,676 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,676 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,676 If you don't want 'publiforge.RelaxNG' to be distributed and are 2025-09-08T01:32:06,677 already explicitly excluding 'publiforge.RelaxNG' via 2025-09-08T01:32:06,677 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,677 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,677 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,677 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,677 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,678 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,678 even if it does not contain any `.py` files. 2025-09-08T01:32:06,678 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,678 directory, all directories are treated like packages. 2025-09-08T01:32:06,678 ******************************************************************************** 2025-09-08T01:32:06,678 !! 2025-09-08T01:32:06,678 check.warn(importable) 2025-09-08T01:32:06,678 /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-08T01:32:06,678 !! 2025-09-08T01:32:06,678 ******************************************************************************** 2025-09-08T01:32:06,679 ############################ 2025-09-08T01:32:06,679 # Package would be ignored # 2025-09-08T01:32:06,679 ############################ 2025-09-08T01:32:06,679 Python recognizes 'publiforge.Static' as an importable package[^1], 2025-09-08T01:32:06,679 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,679 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,679 package, please make sure that 'publiforge.Static' is explicitly added 2025-09-08T01:32:06,679 to the `packages` configuration field. 2025-09-08T01:32:06,680 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,680 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,680 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,680 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,680 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,680 If you don't want 'publiforge.Static' to be distributed and are 2025-09-08T01:32:06,680 already explicitly excluding 'publiforge.Static' via 2025-09-08T01:32:06,680 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,681 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,681 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,681 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,681 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,681 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,681 even if it does not contain any `.py` files. 2025-09-08T01:32:06,681 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,682 directory, all directories are treated like packages. 2025-09-08T01:32:06,682 ******************************************************************************** 2025-09-08T01:32:06,682 !! 2025-09-08T01:32:06,682 check.warn(importable) 2025-09-08T01:32:06,682 /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-08T01:32:06,682 !! 2025-09-08T01:32:06,682 ******************************************************************************** 2025-09-08T01:32:06,682 ############################ 2025-09-08T01:32:06,682 # Package would be ignored # 2025-09-08T01:32:06,683 ############################ 2025-09-08T01:32:06,683 Python recognizes 'publiforge.Static.Css' as an importable package[^1], 2025-09-08T01:32:06,683 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,683 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,683 package, please make sure that 'publiforge.Static.Css' is explicitly added 2025-09-08T01:32:06,683 to the `packages` configuration field. 2025-09-08T01:32:06,683 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,683 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,683 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,684 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,684 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,684 If you don't want 'publiforge.Static.Css' to be distributed and are 2025-09-08T01:32:06,684 already explicitly excluding 'publiforge.Static.Css' via 2025-09-08T01:32:06,684 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,684 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,684 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,685 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,685 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,685 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,685 even if it does not contain any `.py` files. 2025-09-08T01:32:06,685 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,685 directory, all directories are treated like packages. 2025-09-08T01:32:06,685 ******************************************************************************** 2025-09-08T01:32:06,686 !! 2025-09-08T01:32:06,686 check.warn(importable) 2025-09-08T01:32:06,686 /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-08T01:32:06,686 !! 2025-09-08T01:32:06,686 ******************************************************************************** 2025-09-08T01:32:06,686 ############################ 2025-09-08T01:32:06,686 # Package would be ignored # 2025-09-08T01:32:06,686 ############################ 2025-09-08T01:32:06,686 Python recognizes 'publiforge.Static.Images' as an importable package[^1], 2025-09-08T01:32:06,686 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,687 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,687 package, please make sure that 'publiforge.Static.Images' is explicitly added 2025-09-08T01:32:06,687 to the `packages` configuration field. 2025-09-08T01:32:06,687 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,687 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,687 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,687 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,688 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,688 If you don't want 'publiforge.Static.Images' to be distributed and are 2025-09-08T01:32:06,688 already explicitly excluding 'publiforge.Static.Images' via 2025-09-08T01:32:06,688 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,688 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,688 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,688 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,688 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,689 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,689 even if it does not contain any `.py` files. 2025-09-08T01:32:06,689 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,689 directory, all directories are treated like packages. 2025-09-08T01:32:06,689 ******************************************************************************** 2025-09-08T01:32:06,689 !! 2025-09-08T01:32:06,689 check.warn(importable) 2025-09-08T01:32:06,689 /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-08T01:32:06,689 !! 2025-09-08T01:32:06,690 ******************************************************************************** 2025-09-08T01:32:06,690 ############################ 2025-09-08T01:32:06,690 # Package would be ignored # 2025-09-08T01:32:06,690 ############################ 2025-09-08T01:32:06,690 Python recognizes 'publiforge.Static.Images.MimeTypes' as an importable package[^1], 2025-09-08T01:32:06,690 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,690 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,690 package, please make sure that 'publiforge.Static.Images.MimeTypes' is explicitly added 2025-09-08T01:32:06,690 to the `packages` configuration field. 2025-09-08T01:32:06,691 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,691 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,691 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,691 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,691 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,691 If you don't want 'publiforge.Static.Images.MimeTypes' to be distributed and are 2025-09-08T01:32:06,691 already explicitly excluding 'publiforge.Static.Images.MimeTypes' via 2025-09-08T01:32:06,692 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,692 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,692 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,692 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,692 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,692 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,692 even if it does not contain any `.py` files. 2025-09-08T01:32:06,693 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,693 directory, all directories are treated like packages. 2025-09-08T01:32:06,693 ******************************************************************************** 2025-09-08T01:32:06,693 !! 2025-09-08T01:32:06,693 check.warn(importable) 2025-09-08T01:32:06,693 /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-08T01:32:06,693 !! 2025-09-08T01:32:06,693 ******************************************************************************** 2025-09-08T01:32:06,694 ############################ 2025-09-08T01:32:06,694 # Package would be ignored # 2025-09-08T01:32:06,694 ############################ 2025-09-08T01:32:06,694 Python recognizes 'publiforge.Static.Js' as an importable package[^1], 2025-09-08T01:32:06,694 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,694 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,694 package, please make sure that 'publiforge.Static.Js' is explicitly added 2025-09-08T01:32:06,694 to the `packages` configuration field. 2025-09-08T01:32:06,695 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,695 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,695 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,695 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,695 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,695 If you don't want 'publiforge.Static.Js' to be distributed and are 2025-09-08T01:32:06,695 already explicitly excluding 'publiforge.Static.Js' via 2025-09-08T01:32:06,695 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,696 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,696 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,696 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,696 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,696 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,696 even if it does not contain any `.py` files. 2025-09-08T01:32:06,696 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,697 directory, all directories are treated like packages. 2025-09-08T01:32:06,697 ******************************************************************************** 2025-09-08T01:32:06,697 !! 2025-09-08T01:32:06,697 check.warn(importable) 2025-09-08T01:32:06,697 /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-08T01:32:06,697 !! 2025-09-08T01:32:06,697 ******************************************************************************** 2025-09-08T01:32:06,697 ############################ 2025-09-08T01:32:06,697 # Package would be ignored # 2025-09-08T01:32:06,697 ############################ 2025-09-08T01:32:06,698 Python recognizes 'publiforge.Static.Js.Tests' as an importable package[^1], 2025-09-08T01:32:06,698 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,698 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,698 package, please make sure that 'publiforge.Static.Js.Tests' is explicitly added 2025-09-08T01:32:06,698 to the `packages` configuration field. 2025-09-08T01:32:06,698 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,698 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,698 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,699 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,699 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,699 If you don't want 'publiforge.Static.Js.Tests' to be distributed and are 2025-09-08T01:32:06,699 already explicitly excluding 'publiforge.Static.Js.Tests' via 2025-09-08T01:32:06,699 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,699 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,699 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,700 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,700 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,700 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,700 even if it does not contain any `.py` files. 2025-09-08T01:32:06,700 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,700 directory, all directories are treated like packages. 2025-09-08T01:32:06,700 ******************************************************************************** 2025-09-08T01:32:06,700 !! 2025-09-08T01:32:06,701 check.warn(importable) 2025-09-08T01:32:06,701 /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-08T01:32:06,701 !! 2025-09-08T01:32:06,701 ******************************************************************************** 2025-09-08T01:32:06,701 ############################ 2025-09-08T01:32:06,701 # Package would be ignored # 2025-09-08T01:32:06,701 ############################ 2025-09-08T01:32:06,701 Python recognizes 'publiforge.Templates' as an importable package[^1], 2025-09-08T01:32:06,701 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,702 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,702 package, please make sure that 'publiforge.Templates' is explicitly added 2025-09-08T01:32:06,702 to the `packages` configuration field. 2025-09-08T01:32:06,702 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,702 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,702 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,702 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,702 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,703 If you don't want 'publiforge.Templates' to be distributed and are 2025-09-08T01:32:06,703 already explicitly excluding 'publiforge.Templates' via 2025-09-08T01:32:06,703 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,703 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,703 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,703 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,703 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,704 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,704 even if it does not contain any `.py` files. 2025-09-08T01:32:06,704 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,704 directory, all directories are treated like packages. 2025-09-08T01:32:06,704 ******************************************************************************** 2025-09-08T01:32:06,704 !! 2025-09-08T01:32:06,704 check.warn(importable) 2025-09-08T01:32:06,704 /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-08T01:32:06,705 !! 2025-09-08T01:32:06,705 ******************************************************************************** 2025-09-08T01:32:06,705 ############################ 2025-09-08T01:32:06,705 # Package would be ignored # 2025-09-08T01:32:06,705 ############################ 2025-09-08T01:32:06,705 Python recognizes 'publiforge.tests.Data' as an importable package[^1], 2025-09-08T01:32:06,705 but it is absent from setuptools' `packages` configuration. 2025-09-08T01:32:06,705 This leads to an ambiguous overall configuration. If you want to distribute this 2025-09-08T01:32:06,705 package, please make sure that 'publiforge.tests.Data' is explicitly added 2025-09-08T01:32:06,706 to the `packages` configuration field. 2025-09-08T01:32:06,706 Alternatively, you can also rely on setuptools' discovery methods 2025-09-08T01:32:06,706 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-09-08T01:32:06,706 instead of `find_packages(...)`/`find:`). 2025-09-08T01:32:06,706 You can read more about "package discovery" on setuptools documentation page: 2025-09-08T01:32:06,706 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-09-08T01:32:06,706 If you don't want 'publiforge.tests.Data' to be distributed and are 2025-09-08T01:32:06,706 already explicitly excluding 'publiforge.tests.Data' via 2025-09-08T01:32:06,707 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-09-08T01:32:06,707 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-09-08T01:32:06,707 combination with a more fine grained `package-data` configuration. 2025-09-08T01:32:06,707 You can read more about "package data files" on setuptools documentation page: 2025-09-08T01:32:06,707 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-09-08T01:32:06,707 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-09-08T01:32:06,707 even if it does not contain any `.py` files. 2025-09-08T01:32:06,708 On the other hand, currently there is no concept of package data 2025-09-08T01:32:06,708 directory, all directories are treated like packages. 2025-09-08T01:32:06,708 ******************************************************************************** 2025-09-08T01:32:06,708 !! 2025-09-08T01:32:06,708 check.warn(importable) 2025-09-08T01:32:06,708 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale 2025-09-08T01:32:06,708 copying publiforge/Locale/publiforge.pot -> build/lib.linux-armv7l-cpython-313/publiforge/Locale 2025-09-08T01:32:06,708 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T01:32:06,708 copying publiforge/Locale/es/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T01:32:06,709 copying publiforge/Locale/es/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/es/LC_MESSAGES 2025-09-08T01:32:06,709 creating build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T01:32:06,709 copying publiforge/Locale/fr/LC_MESSAGES/colander.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T01:32:06,709 copying publiforge/Locale/fr/LC_MESSAGES/colander.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T01:32:06,709 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T01:32:06,709 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-313/publiforge/Locale/fr/LC_MESSAGES 2025-09-08T01:32:06,709 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T01:32:06,709 copying publiforge/Openers/Image/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Image 2025-09-08T01:32:06,709 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T01:32:06,709 copying publiforge/Openers/Ini/ini.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T01:32:06,709 copying publiforge/Openers/Ini/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Ini 2025-09-08T01:32:06,710 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/NoMore 2025-09-08T01:32:06,710 copying publiforge/Openers/NoMore/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/NoMore 2025-09-08T01:32:06,710 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Plain 2025-09-08T01:32:06,710 copying publiforge/Openers/Plain/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Plain 2025-09-08T01:32:06,710 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T01:32:06,710 copying publiforge/Openers/Publidoc/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T01:32:06,710 copying publiforge/Openers/Publidoc/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc 2025-09-08T01:32:06,710 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T01:32:06,710 copying publiforge/Openers/Publidoc/Maestro/publidoc_render4maestro.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T01:32:06,710 copying publiforge/Openers/Publidoc/Maestro/publidoc_xml4maestro.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Maestro 2025-09-08T01:32:06,710 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Regex 2025-09-08T01:32:06,711 copying publiforge/Openers/Publidoc/Regex/publidoc_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Regex 2025-09-08T01:32:06,711 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T01:32:06,711 copying publiforge/Openers/Publidoc/Seeds/publidoc_document.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T01:32:06,711 copying publiforge/Openers/Publidoc/Seeds/publidoc_topic.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Seeds 2025-09-08T01:32:06,711 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T01:32:06,711 copying publiforge/Openers/Publidoc/Static/Css/publidoc_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T01:32:06,711 copying publiforge/Openers/Publidoc/Static/Css/publidoc_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Css 2025-09-08T01:32:06,711 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T01:32:06,711 copying publiforge/Openers/Publidoc/Static/Js/codemirror4publidoc_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T01:32:06,711 copying publiforge/Openers/Publidoc/Static/Js/publidoc_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Static/Js 2025-09-08T01:32:06,711 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Variables 2025-09-08T01:32:06,712 copying publiforge/Openers/Publidoc/Variables/publidoc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Variables 2025-09-08T01:32:06,712 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T01:32:06,712 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T01:32:06,712 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T01:32:06,712 copying publiforge/Openers/Publidoc/Xsl/publidoc_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T01:32:06,712 copying publiforge/Openers/Publidoc/Xsl/publidoc_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T01:32:06,712 copying publiforge/Openers/Publidoc/Xsl/publidoc_save_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publidoc/Xsl 2025-09-08T01:32:06,712 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T01:32:06,712 copying publiforge/Openers/Publiquiz/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T01:32:06,712 copying publiforge/Openers/Publiquiz/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz 2025-09-08T01:32:06,712 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Regex 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Regex/publiquiz_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Regex 2025-09-08T01:32:06,713 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-fill.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-select.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-check.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-radio.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_composite.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_matching.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,713 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing-categories.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,714 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,714 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_production.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,714 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_sort.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Seeds 2025-09-08T01:32:06,714 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T01:32:06,714 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T01:32:06,714 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_schema.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Css 2025-09-08T01:32:06,714 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T01:32:06,714 copying publiforge/Openers/Publiquiz/Static/Js/codemirror4publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T01:32:06,714 copying publiforge/Openers/Publiquiz/Static/Js/publiquiz_schema.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Static/Js 2025-09-08T01:32:06,714 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Variables 2025-09-08T01:32:06,714 copying publiforge/Openers/Publiquiz/Variables/publiquiz.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Variables 2025-09-08T01:32:06,715 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T01:32:06,715 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T01:32:06,715 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T01:32:06,715 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T01:32:06,715 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiquiz/Xsl 2025-09-08T01:32:06,715 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T01:32:06,715 copying publiforge/Openers/Publiset/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T01:32:06,715 copying publiforge/Openers/Publiset/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset 2025-09-08T01:32:06,715 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Regex 2025-09-08T01:32:06,715 copying publiforge/Openers/Publiset/Regex/publiset_save.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Regex 2025-09-08T01:32:06,716 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T01:32:06,716 copying publiforge/Openers/Publiset/Seeds/publiset_composition.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T01:32:06,716 copying publiforge/Openers/Publiset/Seeds/publiset_selection.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Seeds 2025-09-08T01:32:06,716 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T01:32:06,716 copying publiforge/Openers/Publiset/Static/Css/publiset_opener.css -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Css 2025-09-08T01:32:06,716 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T01:32:06,716 copying publiforge/Openers/Publiset/Static/Js/codemirror4publiset_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Static/Js 2025-09-08T01:32:06,716 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Variables 2025-09-08T01:32:06,716 copying publiforge/Openers/Publiset/Variables/publiset.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Variables 2025-09-08T01:32:06,716 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T01:32:06,716 copying publiforge/Openers/Publiset/Xsl/publiset_edit.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T01:32:06,717 copying publiforge/Openers/Publiset/Xsl/publiset_render.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T01:32:06,717 copying publiforge/Openers/Publiset/Xsl/publiset_save.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Publiset/Xsl 2025-09-08T01:32:06,717 creating build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T01:32:06,717 copying publiforge/Openers/Xml/opener.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T01:32:06,717 copying publiforge/Openers/Xml/xml.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Openers/Xml 2025-09-08T01:32:06,717 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T01:32:06,717 copying publiforge/Processors/CharCount/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T01:32:06,717 copying publiforge/Processors/CharCount/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount 2025-09-08T01:32:06,717 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount/Xsl 2025-09-08T01:32:06,717 copying publiforge/Processors/CharCount/Xsl/charcount.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/CharCount/Xsl 2025-09-08T01:32:06,717 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T01:32:06,718 copying publiforge/Processors/DTBookValid/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T01:32:06,718 copying publiforge/Processors/DTBookValid/validator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid 2025-09-08T01:32:06,718 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid/RelaxNG 2025-09-08T01:32:06,718 copying publiforge/Processors/DTBookValid/RelaxNG/dtbook-2005-3.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/DTBookValid/RelaxNG 2025-09-08T01:32:06,718 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel 2025-09-08T01:32:06,718 copying publiforge/Processors/Parallel/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel 2025-09-08T01:32:06,718 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel/Variables 2025-09-08T01:32:06,718 copying publiforge/Processors/Parallel/Variables/parallel.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Parallel/Variables 2025-09-08T01:32:06,718 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv 2025-09-08T01:32:06,718 copying publiforge/Processors/Publidoc2Csv/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv 2025-09-08T01:32:06,719 copying publiforge/Processors/Publidoc2Csv/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv 2025-09-08T01:32:06,719 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T01:32:06,719 copying publiforge/Processors/Publidoc2Csv/Regex/publidoc2csv1_post.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T01:32:06,719 copying publiforge/Processors/Publidoc2Csv/Regex/publidoc2csv1a_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T01:32:06,719 copying publiforge/Processors/Publidoc2Csv/Regex/publidoc2csv1b_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T01:32:06,719 copying publiforge/Processors/Publidoc2Csv/Regex/publidoc2csv2_post.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Regex 2025-09-08T01:32:06,720 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Templates 2025-09-08T01:32:06,720 copying publiforge/Processors/Publidoc2Csv/Templates/dummy1.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Templates 2025-09-08T01:32:06,721 copying publiforge/Processors/Publidoc2Csv/Templates/dummy2.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Templates 2025-09-08T01:32:06,721 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Variables 2025-09-08T01:32:06,721 copying publiforge/Processors/Publidoc2Csv/Variables/publidoc2csv.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Variables 2025-09-08T01:32:06,722 copying publiforge/Processors/Publidoc2Csv/Variables/publidoc2csv_unused.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Variables 2025-09-08T01:32:06,722 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Xsl 2025-09-08T01:32:06,723 copying publiforge/Processors/Publidoc2Csv/Xsl/composition.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Xsl 2025-09-08T01:32:06,723 copying publiforge/Processors/Publidoc2Csv/Xsl/publidoc2csv1.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/Xsl 2025-09-08T01:32:06,724 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T01:32:06,724 copying publiforge/Processors/Publidoc2Csv/lib/__init__.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T01:32:06,724 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv1_post.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T01:32:06,725 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv1_pre.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T01:32:06,725 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv2_post.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T01:32:06,726 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv_final.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T01:32:06,727 copying publiforge/Processors/Publidoc2Csv/lib/publidoc2csv_init.py -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Csv/lib 2025-09-08T01:32:06,727 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T01:32:06,727 copying publiforge/Processors/Publidoc2DTBook/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T01:32:06,728 copying publiforge/Processors/Publidoc2DTBook/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook 2025-09-08T01:32:06,728 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T01:32:06,728 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T01:32:06,729 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Variables 2025-09-08T01:32:06,730 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T01:32:06,730 copying publiforge/Processors/Publidoc2DTBook/Xsl/composition.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T01:32:06,730 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T01:32:06,731 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T01:32:06,731 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2DTBook/Xsl 2025-09-08T01:32:06,732 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T01:32:06,732 copying publiforge/Processors/Publidoc2EPub2/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T01:32:06,733 copying publiforge/Processors/Publidoc2EPub2/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2 2025-09-08T01:32:06,733 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates 2025-09-08T01:32:06,734 copying publiforge/Processors/Publidoc2EPub2/Templates/mimetype -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates 2025-09-08T01:32:06,734 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2025-09-08T01:32:06,734 copying publiforge/Processors/Publidoc2EPub2/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2025-09-08T01:32:06,735 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2025-09-08T01:32:06,735 copying publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2025-09-08T01:32:06,736 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T01:32:06,736 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T01:32:06,736 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Variables 2025-09-08T01:32:06,737 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T01:32:06,737 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T01:32:06,738 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T01:32:06,738 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T01:32:06,739 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T01:32:06,739 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ncx.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T01:32:06,740 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T01:32:06,741 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/Xsl 2025-09-08T01:32:06,741 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T01:32:06,741 copying publiforge/Processors/Publidoc2EPub2/jars/COPYING.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T01:32:06,742 copying publiforge/Processors/Publidoc2EPub2/jars/THIRD-PARTY.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T01:32:06,742 copying publiforge/Processors/Publidoc2EPub2/jars/epubcheck-3.0.1.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars 2025-09-08T01:32:06,745 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T01:32:06,746 copying publiforge/Processors/Publidoc2EPub2/jars/lib/Saxon-HE-9.4.0.6.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T01:32:06,781 copying publiforge/Processors/Publidoc2EPub2/jars/lib/commons-compress-1.4.1.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T01:32:06,782 copying publiforge/Processors/Publidoc2EPub2/jars/lib/guava-13.0.1.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T01:32:06,790 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jing-20120724.0.0.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T01:32:06,793 copying publiforge/Processors/Publidoc2EPub2/jars/lib/sac-1.3.jar -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/lib 2025-09-08T01:32:06,793 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T01:32:06,794 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/Apache-2.0.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T01:32:06,794 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/BSD-3-Clause.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T01:32:06,795 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/MPL-1.0.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T01:32:06,795 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/W3C.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub2/jars/licenses 2025-09-08T01:32:06,796 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T01:32:06,796 copying publiforge/Processors/Publidoc2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T01:32:06,797 copying publiforge/Processors/Publidoc2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3 2025-09-08T01:32:06,797 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates 2025-09-08T01:32:06,797 copying publiforge/Processors/Publidoc2EPub3/Templates/mimetype -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates 2025-09-08T01:32:06,798 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2025-09-08T01:32:06,798 copying publiforge/Processors/Publidoc2EPub3/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2025-09-08T01:32:06,799 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2025-09-08T01:32:06,799 copying publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2025-09-08T01:32:06,799 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Variables 2025-09-08T01:32:06,800 copying publiforge/Processors/Publidoc2EPub3/Variables/publidoc2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Variables 2025-09-08T01:32:06,800 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T01:32:06,800 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T01:32:06,801 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_nav.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T01:32:06,802 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T01:32:06,802 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_smil.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T01:32:06,803 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2EPub3/Xsl 2025-09-08T01:32:06,803 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T01:32:06,804 copying publiforge/Processors/Publidoc2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T01:32:06,804 copying publiforge/Processors/Publidoc2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5 2025-09-08T01:32:06,805 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T01:32:06,805 copying publiforge/Processors/Publidoc2Html5/Variables/publidoc2html5_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Variables 2025-09-08T01:32:06,805 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T01:32:06,806 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T01:32:06,806 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T01:32:06,807 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Html5/Xsl 2025-09-08T01:32:06,807 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T01:32:06,808 copying publiforge/Processors/Publidoc2Pdf/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T01:32:06,808 copying publiforge/Processors/Publidoc2Pdf/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf 2025-09-08T01:32:06,809 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T01:32:06,809 copying publiforge/Processors/Publidoc2Pdf/Fonts/Mono-Bold.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T01:32:06,810 copying publiforge/Processors/Publidoc2Pdf/Fonts/Mono-BoldItalic.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T01:32:06,811 copying publiforge/Processors/Publidoc2Pdf/Fonts/Mono-Italic.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T01:32:06,813 copying publiforge/Processors/Publidoc2Pdf/Fonts/Mono-Regular.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T01:32:06,814 copying publiforge/Processors/Publidoc2Pdf/Fonts/Script.otf -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Fonts 2025-09-08T01:32:06,817 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T01:32:06,817 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_post.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T01:32:06,817 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Regex 2025-09-08T01:32:06,818 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T01:32:06,818 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_dimension.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T01:32:06,819 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_font.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T01:32:06,819 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T01:32:06,820 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_layout.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T01:32:06,820 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T01:32:06,821 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Variables 2025-09-08T01:32:06,821 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T01:32:06,822 copying publiforge/Processors/Publidoc2Pdf/Xsl/composition.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T01:32:06,822 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T01:32:06,823 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T01:32:06,824 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T01:32:06,824 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T01:32:06,825 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2Pdf/Xsl 2025-09-08T01:32:06,825 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T01:32:06,825 copying publiforge/Processors/Publidoc2XHtml/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T01:32:06,826 copying publiforge/Processors/Publidoc2XHtml/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml 2025-09-08T01:32:06,826 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Regex 2025-09-08T01:32:06,827 copying publiforge/Processors/Publidoc2XHtml/Regex/publidoc2xhtml_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Regex 2025-09-08T01:32:06,827 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T01:32:06,828 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/custom.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T01:32:06,828 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/publidoc.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T01:32:06,829 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/reset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Css 2025-09-08T01:32:06,829 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T01:32:06,829 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T01:32:06,830 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T01:32:06,830 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_previous.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T01:32:06,831 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T01:32:06,831 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/pulse.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T01:32:06,832 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/video.png -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Images 2025-09-08T01:32:06,833 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T01:32:06,833 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/jquery.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T01:32:06,834 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/publidoc.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Templates/Js 2025-09-08T01:32:06,834 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T01:32:06,835 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T01:32:06,835 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T01:32:06,836 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T01:32:06,836 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T01:32:06,837 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Variables 2025-09-08T01:32:06,837 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T01:32:06,837 copying publiforge/Processors/Publidoc2XHtml/Xsl/composition.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T01:32:06,838 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T01:32:06,839 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T01:32:06,839 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T01:32:06,840 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_ini.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T01:32:06,840 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_media.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T01:32:06,841 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publidoc2XHtml/Xsl 2025-09-08T01:32:06,842 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T01:32:06,842 copying publiforge/Processors/PublidocClean/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T01:32:06,842 copying publiforge/Processors/PublidocClean/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean 2025-09-08T01:32:06,843 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Regex 2025-09-08T01:32:06,843 copying publiforge/Processors/PublidocClean/Regex/publidocclean_pre.regex -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Regex 2025-09-08T01:32:06,844 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Variables 2025-09-08T01:32:06,844 copying publiforge/Processors/PublidocClean/Variables/publidocclean.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Variables 2025-09-08T01:32:06,845 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Xsl 2025-09-08T01:32:06,845 copying publiforge/Processors/PublidocClean/Xsl/publidocclean.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocClean/Xsl 2025-09-08T01:32:06,845 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T01:32:06,846 copying publiforge/Processors/PublidocValid/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T01:32:06,846 copying publiforge/Processors/PublidocValid/validator.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid 2025-09-08T01:32:06,847 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T01:32:06,847 copying publiforge/Processors/PublidocValid/RelaxNG/publidoc.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T01:32:06,848 copying publiforge/Processors/PublidocValid/RelaxNG/publiquiz.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T01:32:06,848 copying publiforge/Processors/PublidocValid/RelaxNG/publiset.rng -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/PublidocValid/RelaxNG 2025-09-08T01:32:06,849 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T01:32:06,849 copying publiforge/Processors/Publiquiz2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T01:32:06,850 copying publiforge/Processors/Publiquiz2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3 2025-09-08T01:32:06,850 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Variables 2025-09-08T01:32:06,850 copying publiforge/Processors/Publiquiz2EPub3/Variables/publiquiz2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Variables 2025-09-08T01:32:06,851 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T01:32:06,851 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T01:32:06,852 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T01:32:06,852 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2EPub3/Xsl 2025-09-08T01:32:06,853 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T01:32:06,853 copying publiforge/Processors/Publiquiz2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T01:32:06,854 copying publiforge/Processors/Publiquiz2Html5/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5 2025-09-08T01:32:06,854 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T01:32:06,854 copying publiforge/Processors/Publiquiz2Html5/Templates/Css/publiquiz.css -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Css 2025-09-08T01:32:06,855 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T01:32:06,855 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T01:32:06,856 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_basics.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T01:32:06,857 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T01:32:06,858 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_matching_link.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T01:32:06,858 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_pip.js -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Templates/Js 2025-09-08T01:32:06,859 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T01:32:06,859 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T01:32:06,860 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5_quiz.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Variables 2025-09-08T01:32:06,860 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T01:32:06,860 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T01:32:06,861 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_base.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T01:32:06,862 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T01:32:06,862 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiquiz2Html5/Xsl 2025-09-08T01:32:06,863 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T01:32:06,863 copying publiforge/Processors/Publiset2Publidoc/leprisme.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T01:32:06,864 copying publiforge/Processors/Publiset2Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc 2025-09-08T01:32:06,864 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T01:32:06,864 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_image.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T01:32:06,865 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T01:32:06,865 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Variables 2025-09-08T01:32:06,866 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T01:32:06,866 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset2Publidoc/Xsl 2025-09-08T01:32:06,867 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T01:32:06,867 copying publiforge/Processors/Publiset4Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T01:32:06,868 copying publiforge/Processors/Publiset4Publidoc/publiseter.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc 2025-09-08T01:32:06,868 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T01:32:06,868 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_meta.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T01:32:06,869 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T01:32:06,869 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_schema.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Variables 2025-09-08T01:32:06,870 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Xsl 2025-09-08T01:32:06,870 copying publiforge/Processors/Publiset4Publidoc/Xsl/publiset4publidoc.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publidoc/Xsl 2025-09-08T01:32:06,871 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T01:32:06,871 copying publiforge/Processors/Publiset4Publiquiz/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T01:32:06,871 copying publiforge/Processors/Publiset4Publiquiz/publiseter.ini -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz 2025-09-08T01:32:06,872 creating build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz/Xsl 2025-09-08T01:32:06,872 copying publiforge/Processors/Publiset4Publiquiz/Xsl/publiset4publiquiz.xsl -> build/lib.linux-armv7l-cpython-313/publiforge/Processors/Publiset4Publiquiz/Xsl 2025-09-08T01:32:06,873 creating build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T01:32:06,873 copying publiforge/RelaxNG/publiforge.rnc -> build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T01:32:06,874 copying publiforge/RelaxNG/publiforge.rng -> build/lib.linux-armv7l-cpython-313/publiforge/RelaxNG 2025-09-08T01:32:06,874 creating build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T01:32:06,875 copying publiforge/Static/favicon.ico -> build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T01:32:06,875 copying publiforge/Static/robots.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Static 2025-09-08T01:32:06,876 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T01:32:06,876 copying publiforge/Static/Css/base.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T01:32:06,877 copying publiforge/Static/Css/codemirror.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T01:32:06,877 copying publiforge/Static/Css/colors.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T01:32:06,878 copying publiforge/Static/Css/login.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T01:32:06,878 copying publiforge/Static/Css/pygments.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T01:32:06,879 copying publiforge/Static/Css/reset.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T01:32:06,879 copying publiforge/Static/Css/reset.txt -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Css 2025-09-08T01:32:06,880 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,880 copying publiforge/Static/Images/action_add.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,881 copying publiforge/Static/Images/action_add_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,881 copying publiforge/Static/Images/action_browse.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,882 copying publiforge/Static/Images/action_browse_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,882 copying publiforge/Static/Images/action_build.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,883 copying publiforge/Static/Images/action_build_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,883 copying publiforge/Static/Images/action_cancel.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,884 copying publiforge/Static/Images/action_create.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,884 copying publiforge/Static/Images/action_dashboard_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,885 copying publiforge/Static/Images/action_delete.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,885 copying publiforge/Static/Images/action_delete_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,886 copying publiforge/Static/Images/action_diff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,886 copying publiforge/Static/Images/action_diff_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,887 copying publiforge/Static/Images/action_display.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,887 copying publiforge/Static/Images/action_display_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,888 copying publiforge/Static/Images/action_down_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,888 copying publiforge/Static/Images/action_download.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,889 copying publiforge/Static/Images/action_download_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,889 copying publiforge/Static/Images/action_duplicate.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,890 copying publiforge/Static/Images/action_edit_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,890 copying publiforge/Static/Images/action_export.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,891 copying publiforge/Static/Images/action_export_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,891 copying publiforge/Static/Images/action_filter.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,892 copying publiforge/Static/Images/action_help_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,892 copying publiforge/Static/Images/action_import.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,893 copying publiforge/Static/Images/action_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,893 copying publiforge/Static/Images/action_info_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,894 copying publiforge/Static/Images/action_mkdir.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,895 copying publiforge/Static/Images/action_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,895 copying publiforge/Static/Images/action_next_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,896 copying publiforge/Static/Images/action_note.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,896 copying publiforge/Static/Images/action_note_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,897 copying publiforge/Static/Images/action_pack.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,897 copying publiforge/Static/Images/action_pipe.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,898 copying publiforge/Static/Images/action_progress_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,898 copying publiforge/Static/Images/action_remove.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,899 copying publiforge/Static/Images/action_remove_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,899 copying publiforge/Static/Images/action_rename_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,900 copying publiforge/Static/Images/action_render.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,900 copying publiforge/Static/Images/action_render_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,901 copying publiforge/Static/Images/action_reset_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,901 copying publiforge/Static/Images/action_save.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,902 copying publiforge/Static/Images/action_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,902 copying publiforge/Static/Images/action_stop.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,903 copying publiforge/Static/Images/action_stop_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,903 copying publiforge/Static/Images/action_synchronize.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,904 copying publiforge/Static/Images/action_synchronize_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,904 copying publiforge/Static/Images/action_take.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,905 copying publiforge/Static/Images/action_take_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,905 copying publiforge/Static/Images/action_up_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,906 copying publiforge/Static/Images/action_upload.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,906 copying publiforge/Static/Images/action_upload_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,907 copying publiforge/Static/Images/action_view.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,907 copying publiforge/Static/Images/action_view_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,908 copying publiforge/Static/Images/back.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,908 copying publiforge/Static/Images/basket.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,909 copying publiforge/Static/Images/basket_one.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,909 copying publiforge/Static/Images/breadcrumbs_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,910 copying publiforge/Static/Images/build.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,910 copying publiforge/Static/Images/build22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,911 copying publiforge/Static/Images/build32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,911 copying publiforge/Static/Images/build72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,912 copying publiforge/Static/Images/build72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,913 copying publiforge/Static/Images/build96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,913 copying publiforge/Static/Images/check.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,914 copying publiforge/Static/Images/close_dark.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,914 copying publiforge/Static/Images/close_light.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,915 copying publiforge/Static/Images/collapse_closed.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,915 copying publiforge/Static/Images/collapse_current_closed.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,916 copying publiforge/Static/Images/collapse_current_open.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,916 copying publiforge/Static/Images/collapse_open.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,917 copying publiforge/Static/Images/container_add.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,917 copying publiforge/Static/Images/container_back.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,918 copying publiforge/Static/Images/container_select.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,918 copying publiforge/Static/Images/edit32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,919 copying publiforge/Static/Images/equal.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,919 copying publiforge/Static/Images/extractor.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,920 copying publiforge/Static/Images/extractor22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,920 copying publiforge/Static/Images/extractor32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,921 copying publiforge/Static/Images/flash_alert.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,921 copying publiforge/Static/Images/flash_info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,922 copying publiforge/Static/Images/folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,922 copying publiforge/Static/Images/folder22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,923 copying publiforge/Static/Images/folder32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,924 copying publiforge/Static/Images/footer_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,924 copying publiforge/Static/Images/go_first.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,925 copying publiforge/Static/Images/go_last.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,925 copying publiforge/Static/Images/go_next.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,926 copying publiforge/Static/Images/go_next_file.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,926 copying publiforge/Static/Images/go_next_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,927 copying publiforge/Static/Images/go_previous.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,927 copying publiforge/Static/Images/go_previous_file.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,928 copying publiforge/Static/Images/go_previous_search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,928 copying publiforge/Static/Images/go_top.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,929 copying publiforge/Static/Images/go_top22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,929 copying publiforge/Static/Images/group.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,930 copying publiforge/Static/Images/group22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,930 copying publiforge/Static/Images/group32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,931 copying publiforge/Static/Images/history.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,931 copying publiforge/Static/Images/history22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,932 copying publiforge/Static/Images/history32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,932 copying publiforge/Static/Images/in_menu_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,933 copying publiforge/Static/Images/in_menu_on.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,933 copying publiforge/Static/Images/indexer.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,934 copying publiforge/Static/Images/indexer22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,934 copying publiforge/Static/Images/indexer32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,935 copying publiforge/Static/Images/info.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,935 copying publiforge/Static/Images/info22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,936 copying publiforge/Static/Images/info32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,936 copying publiforge/Static/Images/left_background.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,937 copying publiforge/Static/Images/left_title.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,937 copying publiforge/Static/Images/link.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,938 copying publiforge/Static/Images/link22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,938 copying publiforge/Static/Images/link32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,939 copying publiforge/Static/Images/list_header.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,939 copying publiforge/Static/Images/log_download.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,940 copying publiforge/Static/Images/login_bottom_center.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,940 copying publiforge/Static/Images/login_bottom_left.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,941 copying publiforge/Static/Images/login_bottom_right.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,941 copying publiforge/Static/Images/login_middle_left.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,942 copying publiforge/Static/Images/login_middle_right.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,942 copying publiforge/Static/Images/login_top_center.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,943 copying publiforge/Static/Images/login_top_left.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,944 copying publiforge/Static/Images/login_top_right.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,944 copying publiforge/Static/Images/logout.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,945 copying publiforge/Static/Images/notfound.jpg -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,945 copying publiforge/Static/Images/open_false.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,946 copying publiforge/Static/Images/open_true.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,946 copying publiforge/Static/Images/opener22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,947 copying publiforge/Static/Images/opener32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,947 copying publiforge/Static/Images/pack.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,948 copying publiforge/Static/Images/pack22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,948 copying publiforge/Static/Images/pack32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,949 copying publiforge/Static/Images/pack72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,949 copying publiforge/Static/Images/pack72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,950 copying publiforge/Static/Images/pack96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,950 copying publiforge/Static/Images/processing.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,951 copying publiforge/Static/Images/processing22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,951 copying publiforge/Static/Images/processing32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,952 copying publiforge/Static/Images/progress.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,952 copying publiforge/Static/Images/project.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,953 copying publiforge/Static/Images/project22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,953 copying publiforge/Static/Images/project32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,954 copying publiforge/Static/Images/publiforge.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,954 copying publiforge/Static/Images/pyramid.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,955 copying publiforge/Static/Images/role.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,956 copying publiforge/Static/Images/role22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,956 copying publiforge/Static/Images/role32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,957 copying publiforge/Static/Images/search.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,957 copying publiforge/Static/Images/search22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,958 copying publiforge/Static/Images/search32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,958 copying publiforge/Static/Images/sort_down.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,959 copying publiforge/Static/Images/sort_down_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,959 copying publiforge/Static/Images/sort_up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,960 copying publiforge/Static/Images/sort_up_off.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,960 copying publiforge/Static/Images/storage.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,961 copying publiforge/Static/Images/storage22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,961 copying publiforge/Static/Images/storage32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,962 copying publiforge/Static/Images/tab.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,962 copying publiforge/Static/Images/task.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,963 copying publiforge/Static/Images/task22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,963 copying publiforge/Static/Images/task32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,964 copying publiforge/Static/Images/task72.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,964 copying publiforge/Static/Images/task72_over.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,965 copying publiforge/Static/Images/task96.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,965 copying publiforge/Static/Images/up.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,966 copying publiforge/Static/Images/user.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,966 copying publiforge/Static/Images/user22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,967 copying publiforge/Static/Images/user32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,967 copying publiforge/Static/Images/user_pre.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,968 copying publiforge/Static/Images/valid-xhtml11.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,968 copying publiforge/Static/Images/value.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,969 copying publiforge/Static/Images/value22.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,969 copying publiforge/Static/Images/value32.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,970 copying publiforge/Static/Images/vcss.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,970 copying publiforge/Static/Images/wait_build.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,971 copying publiforge/Static/Images/wait_slow.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,971 copying publiforge/Static/Images/wait_synchro.gif -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,972 copying publiforge/Static/Images/wcag1aa.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images 2025-09-08T01:32:06,972 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,973 copying publiforge/Static/Images/MimeTypes/css.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,973 copying publiforge/Static/Images/MimeTypes/csv.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,974 copying publiforge/Static/Images/MimeTypes/epub+zip.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,974 copying publiforge/Static/Images/MimeTypes/folder.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,975 copying publiforge/Static/Images/MimeTypes/font-woff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,975 copying publiforge/Static/Images/MimeTypes/gif.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,976 copying publiforge/Static/Images/MimeTypes/html.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,976 copying publiforge/Static/Images/MimeTypes/indesign-idml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,977 copying publiforge/Static/Images/MimeTypes/indesign-indd.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,977 copying publiforge/Static/Images/MimeTypes/javascript.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,978 copying publiforge/Static/Images/MimeTypes/jpeg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,978 copying publiforge/Static/Images/MimeTypes/mime.types -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,979 copying publiforge/Static/Images/MimeTypes/mp4.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,979 copying publiforge/Static/Images/MimeTypes/mpeg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,980 copying publiforge/Static/Images/MimeTypes/msword.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,980 copying publiforge/Static/Images/MimeTypes/octet-stream.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,981 copying publiforge/Static/Images/MimeTypes/ogg.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,981 copying publiforge/Static/Images/MimeTypes/pdf.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,982 copying publiforge/Static/Images/MimeTypes/plain.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,982 copying publiforge/Static/Images/MimeTypes/png.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,983 copying publiforge/Static/Images/MimeTypes/postscript.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,984 copying publiforge/Static/Images/MimeTypes/relaxng.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,984 copying publiforge/Static/Images/MimeTypes/svg+xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,985 copying publiforge/Static/Images/MimeTypes/tiff.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,985 copying publiforge/Static/Images/MimeTypes/unknown.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,986 copying publiforge/Static/Images/MimeTypes/vnd.ms-excel.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,986 copying publiforge/Static/Images/MimeTypes/vnd.ms-opentype.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,987 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.spreadsheet.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,987 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.text.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,988 copying publiforge/Static/Images/MimeTypes/x-msdos-program.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,988 copying publiforge/Static/Images/MimeTypes/x-msvideo.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,989 copying publiforge/Static/Images/MimeTypes/x-python.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,989 copying publiforge/Static/Images/MimeTypes/x-shockwave-flash.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,990 copying publiforge/Static/Images/MimeTypes/x-tar.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,990 copying publiforge/Static/Images/MimeTypes/x-wav.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,991 copying publiforge/Static/Images/MimeTypes/xml-dtd.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,991 copying publiforge/Static/Images/MimeTypes/xml.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,992 copying publiforge/Static/Images/MimeTypes/zip.png -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Images/MimeTypes 2025-09-08T01:32:06,992 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,992 copying publiforge/Static/Js/base.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,993 copying publiforge/Static/Js/bld_progress.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,994 copying publiforge/Static/Js/bld_results.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,994 copying publiforge/Static/Js/bld_view.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,995 copying publiforge/Static/Js/codemirror.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,996 copying publiforge/Static/Js/codemirror4ini.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,996 copying publiforge/Static/Js/codemirror4xml.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,997 copying publiforge/Static/Js/codemirror_loader.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,998 copying publiforge/Static/Js/jquery.cookie.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,998 copying publiforge/Static/Js/jquery.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:06,999 copying publiforge/Static/Js/stg_browse.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:07,000 copying publiforge/Static/Js/stg_edit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:07,000 copying publiforge/Static/Js/stg_index.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:07,001 copying publiforge/Static/Js/tsk_index.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js 2025-09-08T01:32:07,001 creating build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T01:32:07,001 copying publiforge/Static/Js/Tests/index.html -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T01:32:07,002 copying publiforge/Static/Js/Tests/qunit.css -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T01:32:07,002 copying publiforge/Static/Js/Tests/qunit.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T01:32:07,003 copying publiforge/Static/Js/Tests/tests.js -> build/lib.linux-armv7l-cpython-313/publiforge/Static/Js/Tests 2025-09-08T01:32:07,004 creating build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,004 copying publiforge/Templates/base.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,005 copying publiforge/Templates/bld_launch.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,005 copying publiforge/Templates/bld_output.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,006 copying publiforge/Templates/bld_pack.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,006 copying publiforge/Templates/bld_processing.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,007 copying publiforge/Templates/bld_progress.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,007 copying publiforge/Templates/bld_results.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,008 copying publiforge/Templates/bld_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,008 copying publiforge/Templates/container.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,009 copying publiforge/Templates/container_one.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,009 copying publiforge/Templates/error.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,010 copying publiforge/Templates/fil_display.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,010 copying publiforge/Templates/fil_info.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,011 copying publiforge/Templates/fil_modify.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,011 copying publiforge/Templates/fil_search.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,012 copying publiforge/Templates/fil_vcs_params.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,012 copying publiforge/Templates/files_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,013 copying publiforge/Templates/files_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,013 copying publiforge/Templates/flash.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,014 copying publiforge/Templates/grp_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,014 copying publiforge/Templates/grp_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,015 copying publiforge/Templates/grp_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,015 copying publiforge/Templates/home.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,016 copying publiforge/Templates/idx_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,016 copying publiforge/Templates/idx_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,017 copying publiforge/Templates/idx_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,017 copying publiforge/Templates/login.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,018 copying publiforge/Templates/mbr_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,018 copying publiforge/Templates/mbr_groups_edit.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,019 copying publiforge/Templates/mbr_groups_paging.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,019 copying publiforge/Templates/mbr_groups_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,020 copying publiforge/Templates/mbr_paging.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,020 copying publiforge/Templates/mbr_view.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,021 copying publiforge/Templates/pck_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,021 copying publiforge/Templates/pck_events.macro.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,022 copying publiforge/Templates/pck_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,022 copying publiforge/Templates/pck_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,023 copying publiforge/Templates/prc_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,024 copying publiforge/Templates/prc_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,024 copying publiforge/Templates/prj_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,025 copying publiforge/Templates/prj_dashboard.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,025 copying publiforge/Templates/prj_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,026 copying publiforge/Templates/prj_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,026 copying publiforge/Templates/prj_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,027 copying publiforge/Templates/rol_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,027 copying publiforge/Templates/rol_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,028 copying publiforge/Templates/sit_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,028 copying publiforge/Templates/stg_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,029 copying publiforge/Templates/stg_browse.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,029 copying publiforge/Templates/stg_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,030 copying publiforge/Templates/stg_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,031 copying publiforge/Templates/stg_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,031 copying publiforge/Templates/tsk_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,032 copying publiforge/Templates/tsk_index.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,032 copying publiforge/Templates/tsk_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,033 copying publiforge/Templates/usr_admin.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,033 copying publiforge/Templates/usr_edit.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,034 copying publiforge/Templates/usr_view.pt -> build/lib.linux-armv7l-cpython-313/publiforge/Templates 2025-09-08T01:32:07,034 creating build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T01:32:07,034 copying publiforge/tests/Data/processor.xml -> build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T01:32:07,035 copying publiforge/tests/Data/test.pfvar.xml -> build/lib.linux-armv7l-cpython-313/publiforge/tests/Data 2025-09-08T01:32:07,035 copying publiforge/lib/rsync/_librsync.c -> build/lib.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T01:32:07,040 running build_ext 2025-09-08T01:32:07,368 building 'publiforge.lib.rsync._librsync' extension 2025-09-08T01:32:07,369 creating build/temp.linux-armv7l-cpython-313/publiforge/lib/rsync 2025-09-08T01:32:07,370 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-08T01:32:07,728 publiforge/lib/rsync/_librsync.c:27:10: fatal error: librsync.h: No such file or directory 2025-09-08T01:32:07,729 27 | #include 2025-09-08T01:32:07,729 | ^~~~~~~~~~~~ 2025-09-08T01:32:07,729 compilation terminated. 2025-09-08T01:32:07,732 error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1 2025-09-08T01:32:07,884 ERROR: python setup.py bdist_wheel exited with 1 2025-09-08T01:32:07,895 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2025-09-08T01:32:07,895 exec(compile('"'"''"'"''"'"' 2025-09-08T01:32:07,895 # This is -- a caller that pip uses to run setup.py 2025-09-08T01:32:07,895 # 2025-09-08T01:32:07,895 # - It imports setuptools before invoking setup.py, to enable projects that directly 2025-09-08T01:32:07,895 # import from `distutils.core` to work with newer packaging standards. 2025-09-08T01:32:07,895 # - It provides a clear error message when setuptools is not installed. 2025-09-08T01:32:07,895 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2025-09-08T01:32:07,895 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2025-09-08T01:32:07,895 # manifest_maker: standard file '"'"'-c'"'"' not found". 2025-09-08T01:32:07,895 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2025-09-08T01:32:07,895 import os, sys, tokenize, traceback 2025-09-08T01:32:07,895 2025-09-08T01:32:07,895 try: 2025-09-08T01:32:07,895 import setuptools 2025-09-08T01:32:07,895 except ImportError: 2025-09-08T01:32:07,895 print( 2025-09-08T01:32:07,895 "ERROR: Can not execute `setup.py` since setuptools failed to import in " 2025-09-08T01:32:07,895 "the build environment with exception:", 2025-09-08T01:32:07,895 file=sys.stderr, 2025-09-08T01:32:07,895 ) 2025-09-08T01:32:07,895 traceback.print_exc() 2025-09-08T01:32:07,895 sys.exit(1) 2025-09-08T01:32:07,895 2025-09-08T01:32:07,895 __file__ = %r 2025-09-08T01:32:07,895 sys.argv[0] = __file__ 2025-09-08T01:32:07,895 2025-09-08T01:32:07,895 if os.path.exists(__file__): 2025-09-08T01:32:07,895 filename = __file__ 2025-09-08T01:32:07,895 with tokenize.open(__file__) as f: 2025-09-08T01:32:07,895 setup_py_code = f.read() 2025-09-08T01:32:07,895 else: 2025-09-08T01:32:07,895 filename = "" 2025-09-08T01:32:07,895 setup_py_code = "from setuptools import setup; setup()" 2025-09-08T01:32:07,895 2025-09-08T01:32:07,895 exec(compile(setup_py_code, filename, "exec")) 2025-09-08T01:32:07,895 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-tx12itpb/publiforge_d63a48c6826a4e20b1860bd01fdef0f7/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-kufnxl7n[/] 2025-09-08T01:32:07,896 [bold magenta]cwd[/]: /tmp/pip-wheel-tx12itpb/publiforge_d63a48c6826a4e20b1860bd01fdef0f7/ 2025-09-08T01:32:07,896 Building wheel for publiforge (setup.py): finished with status 'error' 2025-09-08T01:32:07,896 ERROR: Failed building wheel for publiforge 2025-09-08T01:32:07,897 Running setup.py clean for publiforge 2025-09-08T01:32:07,898 Running command python setup.py clean 2025-09-08T01:32:08,587 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' 2025-09-08T01:32:08,587 warnings.warn(msg) 2025-09-08T01:32:08,587 /usr/local/lib/python3.13/dist-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'message_extractors' 2025-09-08T01:32:08,587 warnings.warn(msg) 2025-09-08T01:32:09,057 running clean 2025-09-08T01:32:09,203 removing 'build/temp.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T01:32:09,203 removing 'build/lib.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T01:32:09,233 'build/bdist.linux-armv7l' does not exist -- can't clean it 2025-09-08T01:32:09,234 'build/scripts-3.13' does not exist -- can't clean it 2025-09-08T01:32:09,234 removing 'build' 2025-09-08T01:32:09,348 Failed to build publiforge 2025-09-08T01:32:09,349 ERROR: Failed to build one or more wheels 2025-09-08T01:32:09,349 Exception information: 2025-09-08T01:32:09,349 Traceback (most recent call last): 2025-09-08T01:32:09,349 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper 2025-09-08T01:32:09,349 status = _inner_run() 2025-09-08T01:32:09,349 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run 2025-09-08T01:32:09,349 return self.run(options, args) 2025-09-08T01:32:09,349 ~~~~~~~~^^^^^^^^^^^^^^^ 2025-09-08T01:32:09,349 File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 68, in wrapper 2025-09-08T01:32:09,349 return func(self, options, args) 2025-09-08T01:32:09,349 File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line 180, in run 2025-09-08T01:32:09,349 raise CommandError("Failed to build one or more wheels") 2025-09-08T01:32:09,349 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2025-09-08T01:32:09,354 Removed build tracker: '/tmp/pip-build-tracker-byfjrlk1'