2023-09-10T10:26:50,656 Created temporary directory: /tmp/pip-build-tracker-6aunmirc 2023-09-10T10:26:50,657 Initialized build tracking at /tmp/pip-build-tracker-6aunmirc 2023-09-10T10:26:50,657 Created build tracker: /tmp/pip-build-tracker-6aunmirc 2023-09-10T10:26:50,658 Entered build tracker: /tmp/pip-build-tracker-6aunmirc 2023-09-10T10:26:50,659 Created temporary directory: /tmp/pip-wheel-znht63uh 2023-09-10T10:26:50,661 Created temporary directory: /tmp/pip-ephem-wheel-cache-2jqp92l8 2023-09-10T10:26:50,683 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2023-09-10T10:26:50,688 2 location(s) to search for versions of publiforge: 2023-09-10T10:26:50,688 * https://pypi.org/simple/publiforge/ 2023-09-10T10:26:50,688 * https://www.piwheels.org/simple/publiforge/ 2023-09-10T10:26:50,689 Fetching project page and analyzing links: https://pypi.org/simple/publiforge/ 2023-09-10T10:26:50,690 Getting page https://pypi.org/simple/publiforge/ 2023-09-10T10:26:50,692 Found index url https://pypi.org/simple/ 2023-09-10T10:26:50,952 Fetched page https://pypi.org/simple/publiforge/ as application/vnd.pypi.simple.v1+json 2023-09-10T10:26:50,955 Found link https://files.pythonhosted.org/packages/eb/e9/c48710181b0fabcdb65e51ba05ce1b39809ff351ac566be9467443e3be68/PubliForge-0.5.tar.gz (from https://pypi.org/simple/publiforge/), version: 0.5 2023-09-10T10:26:50,956 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 2023-09-10T10:26:50,956 Found link https://files.pythonhosted.org/packages/33/8c/1057344a688eac7f4750f3a60b7cdd57a38033f834211e366c058d91fda6/PubliForge-0.6.tar.gz (from https://pypi.org/simple/publiforge/), version: 0.6 2023-09-10T10:26:50,957 Found link https://files.pythonhosted.org/packages/bc/d5/7a12945ea459ec20b888c87beb6712d5d8fafe2bcb59d97bbf26b9071998/PubliForge-0.7.tar.gz (from https://pypi.org/simple/publiforge/), version: 0.7 2023-09-10T10:26:50,957 Found link https://files.pythonhosted.org/packages/60/6a/084b0d0d919bddf8045a0ed312d5b877c5d3bd9e4e20109687d69b19dd1e/PubliForge-1.2.tar.gz (from https://pypi.org/simple/publiforge/), version: 1.2 2023-09-10T10:26:50,958 Found link https://files.pythonhosted.org/packages/eb/14/1674e1d4ba9518eaa2e5f6a0a6872e2d069b22819ac554b3a75eaca34b22/PubliForge-2.0.tar.gz (from https://pypi.org/simple/publiforge/), version: 2.0 2023-09-10T10:26:50,959 Found link https://files.pythonhosted.org/packages/ce/99/e78d990cae82141d5f57421395959774c03e3a34d2927996a60732875354/PubliForge-2.1.tar.gz (from https://pypi.org/simple/publiforge/), version: 2.1 2023-09-10T10:26:50,959 Found link https://files.pythonhosted.org/packages/bd/9c/0d22a6f3cc43369284069985bacff0a2eaf355421b58bc6721ac572b2764/PubliForge-2.2.tar.gz (from https://pypi.org/simple/publiforge/), version: 2.2 2023-09-10T10:26:50,960 Fetching project page and analyzing links: https://www.piwheels.org/simple/publiforge/ 2023-09-10T10:26:50,961 Getting page https://www.piwheels.org/simple/publiforge/ 2023-09-10T10:26:50,962 Found index url https://www.piwheels.org/simple/ 2023-09-10T10:26:58,198 Fetched page https://www.piwheels.org/simple/publiforge/ as text/html 2023-09-10T10:26:58,200 Skipping link: not a file: https://www.piwheels.org/simple/publiforge/ 2023-09-10T10:26:58,201 Skipping link: not a file: https://pypi.org/simple/publiforge/ 2023-09-10T10:26:58,246 Given no hashes to check 1 links for project 'publiforge': discarding no candidates 2023-09-10T10:26:58,280 Collecting publiforge==2.2 2023-09-10T10:26:58,283 Created temporary directory: /tmp/pip-unpack-8bkjovwu 2023-09-10T10:26:58,512 Downloading PubliForge-2.2.tar.gz (10.3 MB) 2023-09-10T10:27:02,026 Added publiforge==2.2 from https://files.pythonhosted.org/packages/bd/9c/0d22a6f3cc43369284069985bacff0a2eaf355421b58bc6721ac572b2764/PubliForge-2.2.tar.gz to build tracker '/tmp/pip-build-tracker-6aunmirc' 2023-09-10T10:27:02,029 Running setup.py (path:/tmp/pip-wheel-znht63uh/publiforge_2a7b16393a8d4da68d908348b59ff7c1/setup.py) egg_info for package publiforge 2023-09-10T10:27:02,030 Created temporary directory: /tmp/pip-pip-egg-info-bp1miorq 2023-09-10T10:27:02,031 Preparing metadata (setup.py): started 2023-09-10T10:27:02,032 Running command python setup.py egg_info 2023-09-10T10:27:02,583 /usr/local/lib/python3.11/dist-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'message_extractors' 2023-09-10T10:27:02,583 warnings.warn(msg) 2023-09-10T10:27:03,159 running egg_info 2023-09-10T10:27:03,161 creating /tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info 2023-09-10T10:27:03,186 writing /tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info/PKG-INFO 2023-09-10T10:27:03,193 writing dependency_links to /tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info/dependency_links.txt 2023-09-10T10:27:03,195 writing entry points to /tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info/entry_points.txt 2023-09-10T10:27:03,198 writing requirements to /tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info/requires.txt 2023-09-10T10:27:03,199 writing top-level names to /tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info/top_level.txt 2023-09-10T10:27:03,201 writing manifest file '/tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info/SOURCES.txt' 2023-09-10T10:27:03,310 reading manifest file '/tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info/SOURCES.txt' 2023-09-10T10:27:03,312 reading manifest template 'MANIFEST.in' 2023-09-10T10:27:03,315 warning: no files found matching '*.rst' 2023-09-10T10:27:05,270 warning: no files found matching '*.jinja2' under directory 'publiforge' 2023-09-10T10:27:06,234 warning: no files found matching '*.mak' under directory 'publiforge' 2023-09-10T10:27:06,546 warning: no files found matching '*.mako' under directory 'publiforge' 2023-09-10T10:27:08,160 warning: no files found matching '*.conf' under directory 'publiforge' 2023-09-10T10:27:08,744 writing manifest file '/tmp/pip-pip-egg-info-bp1miorq/PubliForge.egg-info/SOURCES.txt' 2023-09-10T10:27:08,856 Preparing metadata (setup.py): finished with status 'done' 2023-09-10T10:27:08,860 Source in /tmp/pip-wheel-znht63uh/publiforge_2a7b16393a8d4da68d908348b59ff7c1 has version 2.2, which satisfies requirement publiforge==2.2 from https://files.pythonhosted.org/packages/bd/9c/0d22a6f3cc43369284069985bacff0a2eaf355421b58bc6721ac572b2764/PubliForge-2.2.tar.gz 2023-09-10T10:27:08,861 Removed publiforge==2.2 from https://files.pythonhosted.org/packages/bd/9c/0d22a6f3cc43369284069985bacff0a2eaf355421b58bc6721ac572b2764/PubliForge-2.2.tar.gz from build tracker '/tmp/pip-build-tracker-6aunmirc' 2023-09-10T10:27:08,866 Created temporary directory: /tmp/pip-unpack-e1fxdzkn 2023-09-10T10:27:08,867 Created temporary directory: /tmp/pip-unpack-3f3zmpok 2023-09-10T10:27:08,925 Building wheels for collected packages: publiforge 2023-09-10T10:27:08,929 Created temporary directory: /tmp/pip-wheel-c5rvjd6q 2023-09-10T10:27:08,930 Building wheel for publiforge (setup.py): started 2023-09-10T10:27:08,931 Destination directory: /tmp/pip-wheel-c5rvjd6q 2023-09-10T10:27:08,932 Running command python setup.py bdist_wheel 2023-09-10T10:27:09,449 /usr/local/lib/python3.11/dist-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'message_extractors' 2023-09-10T10:27:09,450 warnings.warn(msg) 2023-09-10T10:27:10,031 running bdist_wheel 2023-09-10T10:27:10,128 running build 2023-09-10T10:27:10,129 running build_py 2023-09-10T10:27:10,157 creating build 2023-09-10T10:27:10,157 creating build/lib.linux-armv7l-cpython-311 2023-09-10T10:27:10,158 creating build/lib.linux-armv7l-cpython-311/publiforge 2023-09-10T10:27:10,160 copying publiforge/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge 2023-09-10T10:27:10,162 copying publiforge/initialize.py -> build/lib.linux-armv7l-cpython-311/publiforge 2023-09-10T10:27:10,165 creating build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,166 copying publiforge/views/pack.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,169 copying publiforge/views/site.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,171 copying publiforge/views/project.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,174 copying publiforge/views/xmlrpc.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,176 copying publiforge/views/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,178 copying publiforge/views/maintenance.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,180 copying publiforge/views/task.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,183 copying publiforge/views/home.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,184 copying publiforge/views/user.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,187 copying publiforge/views/job.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,189 copying publiforge/views/file.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,192 copying publiforge/views/build.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,195 copying publiforge/views/processing.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,197 copying publiforge/views/security.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,199 copying publiforge/views/group.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,202 copying publiforge/views/indexer.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,205 copying publiforge/views/storage.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,208 copying publiforge/views/role.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,210 copying publiforge/views/maestro.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,213 copying publiforge/views/selection.py -> build/lib.linux-armv7l-cpython-311/publiforge/views 2023-09-10T10:27:10,216 creating build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,217 copying publiforge/models/projects.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,219 copying publiforge/models/users.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,222 copying publiforge/models/roles.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,224 copying publiforge/models/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,225 copying publiforge/models/packs.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,228 copying publiforge/models/groups.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,231 copying publiforge/models/storages.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,233 copying publiforge/models/jobs.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,235 copying publiforge/models/tasks.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,237 copying publiforge/models/processings.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,240 copying publiforge/models/indexers.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,242 copying publiforge/models/processors.py -> build/lib.linux-armv7l-cpython-311/publiforge/models 2023-09-10T10:27:10,245 creating build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,246 copying publiforge/tests/test_models_processors.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,249 copying publiforge/tests/test_lib_menu.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,251 copying publiforge/tests/test_views_security.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,253 copying publiforge/tests/test_models_users.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,255 copying publiforge/tests/test_lib_config.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,257 copying publiforge/tests/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,260 copying publiforge/tests/test_lib_form.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,262 copying publiforge/tests/test_models_projects.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,264 copying publiforge/tests/test_models_storages.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,266 copying publiforge/tests/test_lib_xml.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,269 copying publiforge/tests/test_lib_utils.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,271 copying publiforge/tests/test_scripts_pfbuild.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,273 copying publiforge/tests/test_views_project.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,275 copying publiforge/tests/test_lib_i18n.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,277 copying publiforge/tests/test_models_groups.py -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:10,280 creating build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,280 copying publiforge/lib/tabset.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,282 copying publiforge/lib/paging.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,285 copying publiforge/lib/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,287 copying publiforge/lib/handler.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,290 copying publiforge/lib/menu.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,292 copying publiforge/lib/packutils.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,295 copying publiforge/lib/log.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,296 copying publiforge/lib/debug.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,298 copying publiforge/lib/i18n.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,300 copying publiforge/lib/form.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,303 copying publiforge/lib/breadcrumbs.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,305 copying publiforge/lib/xml.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,307 copying publiforge/lib/utils.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,310 copying publiforge/lib/config.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,312 copying publiforge/lib/viewutils.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,315 copying publiforge/lib/filter.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:10,318 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds 2023-09-10T10:27:10,319 copying publiforge/scaffolds/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds 2023-09-10T10:27:10,322 creating build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,323 copying publiforge/scripts/pfminify.py -> build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,325 copying publiforge/scripts/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,327 copying publiforge/scripts/pfbackup.py -> build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,329 copying publiforge/scripts/pfscheduler.py -> build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,332 copying publiforge/scripts/pfimage2svg.py -> build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,334 copying publiforge/scripts/pfpopulate.py -> build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,336 copying publiforge/scripts/pftexmath.py -> build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,338 copying publiforge/scripts/pfbuild.py -> build/lib.linux-armv7l-cpython-311/publiforge/scripts 2023-09-10T10:27:10,341 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/processor 2023-09-10T10:27:10,342 copying publiforge/lib/processor/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor 2023-09-10T10:27:10,344 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/rsync 2023-09-10T10:27:10,345 copying publiforge/lib/rsync/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/rsync 2023-09-10T10:27:10,348 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/opener 2023-09-10T10:27:10,349 copying publiforge/lib/opener/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/opener 2023-09-10T10:27:10,352 copying publiforge/lib/opener/image.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/opener 2023-09-10T10:27:10,354 copying publiforge/lib/opener/ini.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/opener 2023-09-10T10:27:10,356 copying publiforge/lib/opener/xml.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/opener 2023-09-10T10:27:10,359 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/vcs 2023-09-10T10:27:10,360 copying publiforge/lib/vcs/svn.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/vcs 2023-09-10T10:27:10,363 copying publiforge/lib/vcs/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/vcs 2023-09-10T10:27:10,365 copying publiforge/lib/vcs/hgsvn.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/vcs 2023-09-10T10:27:10,367 copying publiforge/lib/vcs/hg.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/vcs 2023-09-10T10:27:10,370 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/build 2023-09-10T10:27:10,371 copying publiforge/lib/build/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/build 2023-09-10T10:27:10,373 copying publiforge/lib/build/front.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/build 2023-09-10T10:27:10,376 copying publiforge/lib/build/agent.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/build 2023-09-10T10:27:10,379 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/publiseter 2023-09-10T10:27:10,381 copying publiforge/lib/processor/publiseter/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/publiseter 2023-09-10T10:27:10,384 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/validator 2023-09-10T10:27:10,385 copying publiforge/lib/processor/validator/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/validator 2023-09-10T10:27:10,388 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/generator 2023-09-10T10:27:10,389 copying publiforge/lib/processor/generator/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/generator 2023-09-10T10:27:10,392 creating build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/leprisme 2023-09-10T10:27:10,393 copying publiforge/lib/processor/leprisme/transform.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/leprisme 2023-09-10T10:27:10,396 copying publiforge/lib/processor/leprisme/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/leprisme 2023-09-10T10:27:10,399 copying publiforge/lib/processor/leprisme/publiset.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/leprisme 2023-09-10T10:27:10,401 copying publiforge/lib/processor/leprisme/containers.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/leprisme 2023-09-10T10:27:10,403 copying publiforge/lib/processor/leprisme/iniscript.py -> build/lib.linux-armv7l-cpython-311/publiforge/lib/processor/leprisme 2023-09-10T10:27:10,406 running egg_info 2023-09-10T10:27:10,463 writing PubliForge.egg-info/PKG-INFO 2023-09-10T10:27:10,471 writing dependency_links to PubliForge.egg-info/dependency_links.txt 2023-09-10T10:27:10,473 writing entry points to PubliForge.egg-info/entry_points.txt 2023-09-10T10:27:10,477 writing requirements to PubliForge.egg-info/requires.txt 2023-09-10T10:27:10,478 writing top-level names to PubliForge.egg-info/top_level.txt 2023-09-10T10:27:10,514 reading manifest file 'PubliForge.egg-info/SOURCES.txt' 2023-09-10T10:27:10,534 reading manifest template 'MANIFEST.in' 2023-09-10T10:27:10,537 warning: no files found matching '*.rst' 2023-09-10T10:27:13,145 warning: no files found matching '*.jinja2' under directory 'publiforge' 2023-09-10T10:27:14,664 warning: no files found matching '*.mak' under directory 'publiforge' 2023-09-10T10:27:14,988 warning: no files found matching '*.mako' under directory 'publiforge' 2023-09-10T10:27:16,620 warning: no files found matching '*.conf' under directory 'publiforge' 2023-09-10T10:27:17,193 writing manifest file 'PubliForge.egg-info/SOURCES.txt' 2023-09-10T10:27:17,196 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Locale' is absent from the `packages` configuration. 2023-09-10T10:27:17,197 !! 2023-09-10T10:27:17,198 ******************************************************************************** 2023-09-10T10:27:17,199 ############################ 2023-09-10T10:27:17,199 # Package would be ignored # 2023-09-10T10:27:17,200 ############################ 2023-09-10T10:27:17,200 Python recognizes 'publiforge.Locale' as an importable package[^1], 2023-09-10T10:27:17,201 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,202 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,202 package, please make sure that 'publiforge.Locale' is explicitly added 2023-09-10T10:27:17,203 to the `packages` configuration field. 2023-09-10T10:27:17,204 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,204 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,205 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,206 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,207 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,208 If you don't want 'publiforge.Locale' to be distributed and are 2023-09-10T10:27:17,208 already explicitly excluding 'publiforge.Locale' via 2023-09-10T10:27:17,209 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,209 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,210 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,211 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,212 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,213 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,214 even if it does not contain any `.py` files. 2023-09-10T10:27:17,214 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,214 directory, all directories are treated like packages. 2023-09-10T10:27:17,215 ******************************************************************************** 2023-09-10T10:27:17,216 !! 2023-09-10T10:27:17,217 check.warn(importable) 2023-09-10T10:27:17,217 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Locale.es.LC_MESSAGES' is absent from the `packages` configuration. 2023-09-10T10:27:17,217 !! 2023-09-10T10:27:17,218 ******************************************************************************** 2023-09-10T10:27:17,219 ############################ 2023-09-10T10:27:17,219 # Package would be ignored # 2023-09-10T10:27:17,220 ############################ 2023-09-10T10:27:17,220 Python recognizes 'publiforge.Locale.es.LC_MESSAGES' as an importable package[^1], 2023-09-10T10:27:17,220 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,221 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,222 package, please make sure that 'publiforge.Locale.es.LC_MESSAGES' is explicitly added 2023-09-10T10:27:17,222 to the `packages` configuration field. 2023-09-10T10:27:17,223 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,223 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,224 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,224 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,225 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,226 If you don't want 'publiforge.Locale.es.LC_MESSAGES' to be distributed and are 2023-09-10T10:27:17,227 already explicitly excluding 'publiforge.Locale.es.LC_MESSAGES' via 2023-09-10T10:27:17,227 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,227 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,228 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,229 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,230 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,231 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,232 even if it does not contain any `.py` files. 2023-09-10T10:27:17,232 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,233 directory, all directories are treated like packages. 2023-09-10T10:27:17,234 ******************************************************************************** 2023-09-10T10:27:17,234 !! 2023-09-10T10:27:17,235 check.warn(importable) 2023-09-10T10:27:17,235 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Locale.fr.LC_MESSAGES' is absent from the `packages` configuration. 2023-09-10T10:27:17,236 !! 2023-09-10T10:27:17,237 ******************************************************************************** 2023-09-10T10:27:17,237 ############################ 2023-09-10T10:27:17,237 # Package would be ignored # 2023-09-10T10:27:17,238 ############################ 2023-09-10T10:27:17,238 Python recognizes 'publiforge.Locale.fr.LC_MESSAGES' as an importable package[^1], 2023-09-10T10:27:17,239 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,240 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,241 package, please make sure that 'publiforge.Locale.fr.LC_MESSAGES' is explicitly added 2023-09-10T10:27:17,241 to the `packages` configuration field. 2023-09-10T10:27:17,242 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,242 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,243 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,244 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,244 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,245 If you don't want 'publiforge.Locale.fr.LC_MESSAGES' to be distributed and are 2023-09-10T10:27:17,245 already explicitly excluding 'publiforge.Locale.fr.LC_MESSAGES' via 2023-09-10T10:27:17,246 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,246 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,246 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,247 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,248 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,249 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,250 even if it does not contain any `.py` files. 2023-09-10T10:27:17,250 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,250 directory, all directories are treated like packages. 2023-09-10T10:27:17,251 ******************************************************************************** 2023-09-10T10:27:17,251 !! 2023-09-10T10:27:17,252 check.warn(importable) 2023-09-10T10:27:17,252 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Image' is absent from the `packages` configuration. 2023-09-10T10:27:17,253 !! 2023-09-10T10:27:17,253 ******************************************************************************** 2023-09-10T10:27:17,254 ############################ 2023-09-10T10:27:17,254 # Package would be ignored # 2023-09-10T10:27:17,255 ############################ 2023-09-10T10:27:17,255 Python recognizes 'publiforge.Openers.Image' as an importable package[^1], 2023-09-10T10:27:17,256 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,257 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,257 package, please make sure that 'publiforge.Openers.Image' is explicitly added 2023-09-10T10:27:17,258 to the `packages` configuration field. 2023-09-10T10:27:17,259 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,259 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,259 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,260 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,261 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,262 If you don't want 'publiforge.Openers.Image' to be distributed and are 2023-09-10T10:27:17,263 already explicitly excluding 'publiforge.Openers.Image' via 2023-09-10T10:27:17,263 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,264 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,264 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,265 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,266 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,267 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,268 even if it does not contain any `.py` files. 2023-09-10T10:27:17,268 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,268 directory, all directories are treated like packages. 2023-09-10T10:27:17,269 ******************************************************************************** 2023-09-10T10:27:17,269 !! 2023-09-10T10:27:17,270 check.warn(importable) 2023-09-10T10:27:17,270 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.ImageEdit' is absent from the `packages` configuration. 2023-09-10T10:27:17,270 !! 2023-09-10T10:27:17,271 ******************************************************************************** 2023-09-10T10:27:17,272 ############################ 2023-09-10T10:27:17,272 # Package would be ignored # 2023-09-10T10:27:17,272 ############################ 2023-09-10T10:27:17,273 Python recognizes 'publiforge.Openers.ImageEdit' as an importable package[^1], 2023-09-10T10:27:17,273 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,274 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,274 package, please make sure that 'publiforge.Openers.ImageEdit' is explicitly added 2023-09-10T10:27:17,274 to the `packages` configuration field. 2023-09-10T10:27:17,275 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,276 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,276 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,277 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,278 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,279 If you don't want 'publiforge.Openers.ImageEdit' to be distributed and are 2023-09-10T10:27:17,280 already explicitly excluding 'publiforge.Openers.ImageEdit' via 2023-09-10T10:27:17,280 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,280 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,281 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,282 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,283 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,284 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,284 even if it does not contain any `.py` files. 2023-09-10T10:27:17,285 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,286 directory, all directories are treated like packages. 2023-09-10T10:27:17,286 ******************************************************************************** 2023-09-10T10:27:17,287 !! 2023-09-10T10:27:17,288 check.warn(importable) 2023-09-10T10:27:17,288 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Ini' is absent from the `packages` configuration. 2023-09-10T10:27:17,289 !! 2023-09-10T10:27:17,290 ******************************************************************************** 2023-09-10T10:27:17,290 ############################ 2023-09-10T10:27:17,290 # Package would be ignored # 2023-09-10T10:27:17,291 ############################ 2023-09-10T10:27:17,291 Python recognizes 'publiforge.Openers.Ini' as an importable package[^1], 2023-09-10T10:27:17,292 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,293 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,293 package, please make sure that 'publiforge.Openers.Ini' is explicitly added 2023-09-10T10:27:17,293 to the `packages` configuration field. 2023-09-10T10:27:17,294 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,294 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,295 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,296 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,296 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,297 If you don't want 'publiforge.Openers.Ini' to be distributed and are 2023-09-10T10:27:17,297 already explicitly excluding 'publiforge.Openers.Ini' via 2023-09-10T10:27:17,298 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,298 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,298 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,299 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,300 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,301 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,302 even if it does not contain any `.py` files. 2023-09-10T10:27:17,302 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,302 directory, all directories are treated like packages. 2023-09-10T10:27:17,303 ******************************************************************************** 2023-09-10T10:27:17,304 !! 2023-09-10T10:27:17,304 check.warn(importable) 2023-09-10T10:27:17,304 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.NoMore' is absent from the `packages` configuration. 2023-09-10T10:27:17,305 !! 2023-09-10T10:27:17,306 ******************************************************************************** 2023-09-10T10:27:17,306 ############################ 2023-09-10T10:27:17,306 # Package would be ignored # 2023-09-10T10:27:17,307 ############################ 2023-09-10T10:27:17,307 Python recognizes 'publiforge.Openers.NoMore' as an importable package[^1], 2023-09-10T10:27:17,308 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,309 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,309 package, please make sure that 'publiforge.Openers.NoMore' is explicitly added 2023-09-10T10:27:17,309 to the `packages` configuration field. 2023-09-10T10:27:17,310 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,311 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,311 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,312 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,313 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,314 If you don't want 'publiforge.Openers.NoMore' to be distributed and are 2023-09-10T10:27:17,315 already explicitly excluding 'publiforge.Openers.NoMore' via 2023-09-10T10:27:17,315 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,316 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,316 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,317 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,318 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,319 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,319 even if it does not contain any `.py` files. 2023-09-10T10:27:17,319 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,320 directory, all directories are treated like packages. 2023-09-10T10:27:17,320 ******************************************************************************** 2023-09-10T10:27:17,321 !! 2023-09-10T10:27:17,321 check.warn(importable) 2023-09-10T10:27:17,322 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Plain' is absent from the `packages` configuration. 2023-09-10T10:27:17,322 !! 2023-09-10T10:27:17,323 ******************************************************************************** 2023-09-10T10:27:17,323 ############################ 2023-09-10T10:27:17,324 # Package would be ignored # 2023-09-10T10:27:17,324 ############################ 2023-09-10T10:27:17,324 Python recognizes 'publiforge.Openers.Plain' as an importable package[^1], 2023-09-10T10:27:17,325 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,326 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,326 package, please make sure that 'publiforge.Openers.Plain' is explicitly added 2023-09-10T10:27:17,326 to the `packages` configuration field. 2023-09-10T10:27:17,327 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,328 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,328 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,329 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,330 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,331 If you don't want 'publiforge.Openers.Plain' to be distributed and are 2023-09-10T10:27:17,331 already explicitly excluding 'publiforge.Openers.Plain' via 2023-09-10T10:27:17,332 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,332 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,332 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,333 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,334 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,335 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,336 even if it does not contain any `.py` files. 2023-09-10T10:27:17,336 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,337 directory, all directories are treated like packages. 2023-09-10T10:27:17,337 ******************************************************************************** 2023-09-10T10:27:17,338 !! 2023-09-10T10:27:17,339 check.warn(importable) 2023-09-10T10:27:17,339 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publidoc' is absent from the `packages` configuration. 2023-09-10T10:27:17,339 !! 2023-09-10T10:27:17,340 ******************************************************************************** 2023-09-10T10:27:17,341 ############################ 2023-09-10T10:27:17,341 # Package would be ignored # 2023-09-10T10:27:17,341 ############################ 2023-09-10T10:27:17,342 Python recognizes 'publiforge.Openers.Publidoc' as an importable package[^1], 2023-09-10T10:27:17,342 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,343 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,343 package, please make sure that 'publiforge.Openers.Publidoc' is explicitly added 2023-09-10T10:27:17,343 to the `packages` configuration field. 2023-09-10T10:27:17,344 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,344 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,345 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,345 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,346 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,347 If you don't want 'publiforge.Openers.Publidoc' to be distributed and are 2023-09-10T10:27:17,347 already explicitly excluding 'publiforge.Openers.Publidoc' via 2023-09-10T10:27:17,348 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,348 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,349 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,350 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,350 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,352 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,353 even if it does not contain any `.py` files. 2023-09-10T10:27:17,354 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,354 directory, all directories are treated like packages. 2023-09-10T10:27:17,355 ******************************************************************************** 2023-09-10T10:27:17,356 !! 2023-09-10T10:27:17,357 check.warn(importable) 2023-09-10T10:27:17,357 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publidoc.Maestro' is absent from the `packages` configuration. 2023-09-10T10:27:17,358 !! 2023-09-10T10:27:17,359 ******************************************************************************** 2023-09-10T10:27:17,359 ############################ 2023-09-10T10:27:17,360 # Package would be ignored # 2023-09-10T10:27:17,360 ############################ 2023-09-10T10:27:17,361 Python recognizes 'publiforge.Openers.Publidoc.Maestro' as an importable package[^1], 2023-09-10T10:27:17,361 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,362 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,362 package, please make sure that 'publiforge.Openers.Publidoc.Maestro' is explicitly added 2023-09-10T10:27:17,363 to the `packages` configuration field. 2023-09-10T10:27:17,364 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,364 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,365 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,366 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,367 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,367 If you don't want 'publiforge.Openers.Publidoc.Maestro' to be distributed and are 2023-09-10T10:27:17,368 already explicitly excluding 'publiforge.Openers.Publidoc.Maestro' via 2023-09-10T10:27:17,368 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,368 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,369 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,370 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,370 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,371 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,372 even if it does not contain any `.py` files. 2023-09-10T10:27:17,372 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,372 directory, all directories are treated like packages. 2023-09-10T10:27:17,373 ******************************************************************************** 2023-09-10T10:27:17,374 !! 2023-09-10T10:27:17,374 check.warn(importable) 2023-09-10T10:27:17,374 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publidoc.Regex' is absent from the `packages` configuration. 2023-09-10T10:27:17,375 !! 2023-09-10T10:27:17,375 ******************************************************************************** 2023-09-10T10:27:17,376 ############################ 2023-09-10T10:27:17,376 # Package would be ignored # 2023-09-10T10:27:17,377 ############################ 2023-09-10T10:27:17,377 Python recognizes 'publiforge.Openers.Publidoc.Regex' as an importable package[^1], 2023-09-10T10:27:17,377 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,378 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,379 package, please make sure that 'publiforge.Openers.Publidoc.Regex' is explicitly added 2023-09-10T10:27:17,379 to the `packages` configuration field. 2023-09-10T10:27:17,380 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,380 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,381 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,382 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,383 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,383 If you don't want 'publiforge.Openers.Publidoc.Regex' to be distributed and are 2023-09-10T10:27:17,384 already explicitly excluding 'publiforge.Openers.Publidoc.Regex' via 2023-09-10T10:27:17,384 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,385 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,385 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,386 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,387 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,388 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,389 even if it does not contain any `.py` files. 2023-09-10T10:27:17,389 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,389 directory, all directories are treated like packages. 2023-09-10T10:27:17,390 ******************************************************************************** 2023-09-10T10:27:17,391 !! 2023-09-10T10:27:17,391 check.warn(importable) 2023-09-10T10:27:17,391 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publidoc.Seeds' is absent from the `packages` configuration. 2023-09-10T10:27:17,392 !! 2023-09-10T10:27:17,392 ******************************************************************************** 2023-09-10T10:27:17,393 ############################ 2023-09-10T10:27:17,393 # Package would be ignored # 2023-09-10T10:27:17,394 ############################ 2023-09-10T10:27:17,394 Python recognizes 'publiforge.Openers.Publidoc.Seeds' as an importable package[^1], 2023-09-10T10:27:17,394 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,395 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,395 package, please make sure that 'publiforge.Openers.Publidoc.Seeds' is explicitly added 2023-09-10T10:27:17,396 to the `packages` configuration field. 2023-09-10T10:27:17,397 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,397 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,397 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,398 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,399 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,400 If you don't want 'publiforge.Openers.Publidoc.Seeds' to be distributed and are 2023-09-10T10:27:17,400 already explicitly excluding 'publiforge.Openers.Publidoc.Seeds' via 2023-09-10T10:27:17,400 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,401 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,401 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,402 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,403 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,405 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,405 even if it does not contain any `.py` files. 2023-09-10T10:27:17,406 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,406 directory, all directories are treated like packages. 2023-09-10T10:27:17,406 ******************************************************************************** 2023-09-10T10:27:17,407 !! 2023-09-10T10:27:17,408 check.warn(importable) 2023-09-10T10:27:17,408 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publidoc.Static.Css' is absent from the `packages` configuration. 2023-09-10T10:27:17,409 !! 2023-09-10T10:27:17,410 ******************************************************************************** 2023-09-10T10:27:17,410 ############################ 2023-09-10T10:27:17,411 # Package would be ignored # 2023-09-10T10:27:17,411 ############################ 2023-09-10T10:27:17,412 Python recognizes 'publiforge.Openers.Publidoc.Static.Css' as an importable package[^1], 2023-09-10T10:27:17,412 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,413 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,414 package, please make sure that 'publiforge.Openers.Publidoc.Static.Css' is explicitly added 2023-09-10T10:27:17,414 to the `packages` configuration field. 2023-09-10T10:27:17,415 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,415 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,416 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,416 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,417 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,418 If you don't want 'publiforge.Openers.Publidoc.Static.Css' to be distributed and are 2023-09-10T10:27:17,418 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Css' via 2023-09-10T10:27:17,418 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,419 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,419 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,420 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,421 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,422 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,423 even if it does not contain any `.py` files. 2023-09-10T10:27:17,423 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,424 directory, all directories are treated like packages. 2023-09-10T10:27:17,424 ******************************************************************************** 2023-09-10T10:27:17,425 !! 2023-09-10T10:27:17,425 check.warn(importable) 2023-09-10T10:27:17,426 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publidoc.Static.Js' is absent from the `packages` configuration. 2023-09-10T10:27:17,426 !! 2023-09-10T10:27:17,427 ******************************************************************************** 2023-09-10T10:27:17,428 ############################ 2023-09-10T10:27:17,428 # Package would be ignored # 2023-09-10T10:27:17,429 ############################ 2023-09-10T10:27:17,429 Python recognizes 'publiforge.Openers.Publidoc.Static.Js' as an importable package[^1], 2023-09-10T10:27:17,430 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,431 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,431 package, please make sure that 'publiforge.Openers.Publidoc.Static.Js' is explicitly added 2023-09-10T10:27:17,432 to the `packages` configuration field. 2023-09-10T10:27:17,432 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,433 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,433 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,434 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,435 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,436 If you don't want 'publiforge.Openers.Publidoc.Static.Js' to be distributed and are 2023-09-10T10:27:17,437 already explicitly excluding 'publiforge.Openers.Publidoc.Static.Js' via 2023-09-10T10:27:17,437 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,438 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,438 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,439 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,440 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,441 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,441 even if it does not contain any `.py` files. 2023-09-10T10:27:17,442 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,442 directory, all directories are treated like packages. 2023-09-10T10:27:17,442 ******************************************************************************** 2023-09-10T10:27:17,443 !! 2023-09-10T10:27:17,444 check.warn(importable) 2023-09-10T10:27:17,444 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publidoc.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:17,444 !! 2023-09-10T10:27:17,445 ******************************************************************************** 2023-09-10T10:27:17,445 ############################ 2023-09-10T10:27:17,446 # Package would be ignored # 2023-09-10T10:27:17,446 ############################ 2023-09-10T10:27:17,446 Python recognizes 'publiforge.Openers.Publidoc.Variables' as an importable package[^1], 2023-09-10T10:27:17,447 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,448 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,448 package, please make sure that 'publiforge.Openers.Publidoc.Variables' is explicitly added 2023-09-10T10:27:17,448 to the `packages` configuration field. 2023-09-10T10:27:17,449 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,450 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,450 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,451 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,452 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,453 If you don't want 'publiforge.Openers.Publidoc.Variables' to be distributed and are 2023-09-10T10:27:17,453 already explicitly excluding 'publiforge.Openers.Publidoc.Variables' via 2023-09-10T10:27:17,453 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,454 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,454 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,455 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,456 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,457 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,458 even if it does not contain any `.py` files. 2023-09-10T10:27:17,458 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,459 directory, all directories are treated like packages. 2023-09-10T10:27:17,459 ******************************************************************************** 2023-09-10T10:27:17,460 !! 2023-09-10T10:27:17,461 check.warn(importable) 2023-09-10T10:27:17,462 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publidoc.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:17,462 !! 2023-09-10T10:27:17,463 ******************************************************************************** 2023-09-10T10:27:17,464 ############################ 2023-09-10T10:27:17,464 # Package would be ignored # 2023-09-10T10:27:17,465 ############################ 2023-09-10T10:27:17,465 Python recognizes 'publiforge.Openers.Publidoc.Xsl' as an importable package[^1], 2023-09-10T10:27:17,466 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,466 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,467 package, please make sure that 'publiforge.Openers.Publidoc.Xsl' is explicitly added 2023-09-10T10:27:17,467 to the `packages` configuration field. 2023-09-10T10:27:17,468 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,468 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,469 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,469 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,470 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,471 If you don't want 'publiforge.Openers.Publidoc.Xsl' to be distributed and are 2023-09-10T10:27:17,472 already explicitly excluding 'publiforge.Openers.Publidoc.Xsl' via 2023-09-10T10:27:17,472 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,472 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,473 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,474 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,475 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,476 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,476 even if it does not contain any `.py` files. 2023-09-10T10:27:17,477 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,477 directory, all directories are treated like packages. 2023-09-10T10:27:17,478 ******************************************************************************** 2023-09-10T10:27:17,479 !! 2023-09-10T10:27:17,480 check.warn(importable) 2023-09-10T10:27:17,480 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiquiz' is absent from the `packages` configuration. 2023-09-10T10:27:17,481 !! 2023-09-10T10:27:17,482 ******************************************************************************** 2023-09-10T10:27:17,482 ############################ 2023-09-10T10:27:17,483 # Package would be ignored # 2023-09-10T10:27:17,483 ############################ 2023-09-10T10:27:17,484 Python recognizes 'publiforge.Openers.Publiquiz' as an importable package[^1], 2023-09-10T10:27:17,485 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,486 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,486 package, please make sure that 'publiforge.Openers.Publiquiz' is explicitly added 2023-09-10T10:27:17,487 to the `packages` configuration field. 2023-09-10T10:27:17,488 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,489 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,489 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,490 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,491 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,493 If you don't want 'publiforge.Openers.Publiquiz' to be distributed and are 2023-09-10T10:27:17,493 already explicitly excluding 'publiforge.Openers.Publiquiz' via 2023-09-10T10:27:17,494 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,494 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,495 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,495 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,496 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,497 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,497 even if it does not contain any `.py` files. 2023-09-10T10:27:17,498 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,498 directory, all directories are treated like packages. 2023-09-10T10:27:17,499 ******************************************************************************** 2023-09-10T10:27:17,500 !! 2023-09-10T10:27:17,500 check.warn(importable) 2023-09-10T10:27:17,500 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiquiz.Regex' is absent from the `packages` configuration. 2023-09-10T10:27:17,501 !! 2023-09-10T10:27:17,502 ******************************************************************************** 2023-09-10T10:27:17,502 ############################ 2023-09-10T10:27:17,502 # Package would be ignored # 2023-09-10T10:27:17,503 ############################ 2023-09-10T10:27:17,503 Python recognizes 'publiforge.Openers.Publiquiz.Regex' as an importable package[^1], 2023-09-10T10:27:17,504 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,505 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,505 package, please make sure that 'publiforge.Openers.Publiquiz.Regex' is explicitly added 2023-09-10T10:27:17,506 to the `packages` configuration field. 2023-09-10T10:27:17,507 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,507 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,508 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,509 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,510 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,511 If you don't want 'publiforge.Openers.Publiquiz.Regex' to be distributed and are 2023-09-10T10:27:17,512 already explicitly excluding 'publiforge.Openers.Publiquiz.Regex' via 2023-09-10T10:27:17,512 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,513 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,513 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,514 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,515 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,517 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,517 even if it does not contain any `.py` files. 2023-09-10T10:27:17,518 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,518 directory, all directories are treated like packages. 2023-09-10T10:27:17,519 ******************************************************************************** 2023-09-10T10:27:17,520 !! 2023-09-10T10:27:17,521 check.warn(importable) 2023-09-10T10:27:17,521 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiquiz.Seeds' is absent from the `packages` configuration. 2023-09-10T10:27:17,521 !! 2023-09-10T10:27:17,522 ******************************************************************************** 2023-09-10T10:27:17,522 ############################ 2023-09-10T10:27:17,523 # Package would be ignored # 2023-09-10T10:27:17,523 ############################ 2023-09-10T10:27:17,524 Python recognizes 'publiforge.Openers.Publiquiz.Seeds' as an importable package[^1], 2023-09-10T10:27:17,524 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,525 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,525 package, please make sure that 'publiforge.Openers.Publiquiz.Seeds' is explicitly added 2023-09-10T10:27:17,525 to the `packages` configuration field. 2023-09-10T10:27:17,526 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,527 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,527 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,528 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,529 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,530 If you don't want 'publiforge.Openers.Publiquiz.Seeds' to be distributed and are 2023-09-10T10:27:17,530 already explicitly excluding 'publiforge.Openers.Publiquiz.Seeds' via 2023-09-10T10:27:17,531 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,531 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,532 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,533 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,534 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,535 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,536 even if it does not contain any `.py` files. 2023-09-10T10:27:17,536 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,537 directory, all directories are treated like packages. 2023-09-10T10:27:17,537 ******************************************************************************** 2023-09-10T10:27:17,538 !! 2023-09-10T10:27:17,539 check.warn(importable) 2023-09-10T10:27:17,539 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiquiz.Static.Css' is absent from the `packages` configuration. 2023-09-10T10:27:17,540 !! 2023-09-10T10:27:17,541 ******************************************************************************** 2023-09-10T10:27:17,541 ############################ 2023-09-10T10:27:17,542 # Package would be ignored # 2023-09-10T10:27:17,542 ############################ 2023-09-10T10:27:17,543 Python recognizes 'publiforge.Openers.Publiquiz.Static.Css' as an importable package[^1], 2023-09-10T10:27:17,543 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,544 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,545 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Css' is explicitly added 2023-09-10T10:27:17,545 to the `packages` configuration field. 2023-09-10T10:27:17,547 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,547 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,547 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,548 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,549 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,550 If you don't want 'publiforge.Openers.Publiquiz.Static.Css' to be distributed and are 2023-09-10T10:27:17,550 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Css' via 2023-09-10T10:27:17,550 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,551 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,551 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,552 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,553 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,554 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,554 even if it does not contain any `.py` files. 2023-09-10T10:27:17,555 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,555 directory, all directories are treated like packages. 2023-09-10T10:27:17,556 ******************************************************************************** 2023-09-10T10:27:17,556 !! 2023-09-10T10:27:17,557 check.warn(importable) 2023-09-10T10:27:17,557 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiquiz.Static.Fonts' is absent from the `packages` configuration. 2023-09-10T10:27:17,558 !! 2023-09-10T10:27:17,559 ******************************************************************************** 2023-09-10T10:27:17,560 ############################ 2023-09-10T10:27:17,560 # Package would be ignored # 2023-09-10T10:27:17,561 ############################ 2023-09-10T10:27:17,561 Python recognizes 'publiforge.Openers.Publiquiz.Static.Fonts' as an importable package[^1], 2023-09-10T10:27:17,562 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,563 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,564 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Fonts' is explicitly added 2023-09-10T10:27:17,565 to the `packages` configuration field. 2023-09-10T10:27:17,566 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,567 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,567 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,569 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,570 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,572 If you don't want 'publiforge.Openers.Publiquiz.Static.Fonts' to be distributed and are 2023-09-10T10:27:17,572 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Fonts' via 2023-09-10T10:27:17,573 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,574 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,574 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,576 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,577 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,579 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,580 even if it does not contain any `.py` files. 2023-09-10T10:27:17,580 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,581 directory, all directories are treated like packages. 2023-09-10T10:27:17,581 ******************************************************************************** 2023-09-10T10:27:17,582 !! 2023-09-10T10:27:17,583 check.warn(importable) 2023-09-10T10:27:17,583 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiquiz.Static.Js' is absent from the `packages` configuration. 2023-09-10T10:27:17,584 !! 2023-09-10T10:27:17,585 ******************************************************************************** 2023-09-10T10:27:17,585 ############################ 2023-09-10T10:27:17,586 # Package would be ignored # 2023-09-10T10:27:17,586 ############################ 2023-09-10T10:27:17,587 Python recognizes 'publiforge.Openers.Publiquiz.Static.Js' as an importable package[^1], 2023-09-10T10:27:17,588 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,589 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,590 package, please make sure that 'publiforge.Openers.Publiquiz.Static.Js' is explicitly added 2023-09-10T10:27:17,590 to the `packages` configuration field. 2023-09-10T10:27:17,591 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,592 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,592 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,594 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,595 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,596 If you don't want 'publiforge.Openers.Publiquiz.Static.Js' to be distributed and are 2023-09-10T10:27:17,597 already explicitly excluding 'publiforge.Openers.Publiquiz.Static.Js' via 2023-09-10T10:27:17,598 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,598 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,599 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,600 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,601 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,603 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,604 even if it does not contain any `.py` files. 2023-09-10T10:27:17,604 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,605 directory, all directories are treated like packages. 2023-09-10T10:27:17,606 ******************************************************************************** 2023-09-10T10:27:17,607 !! 2023-09-10T10:27:17,607 check.warn(importable) 2023-09-10T10:27:17,608 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiquiz.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:17,609 !! 2023-09-10T10:27:17,610 ******************************************************************************** 2023-09-10T10:27:17,611 ############################ 2023-09-10T10:27:17,612 # Package would be ignored # 2023-09-10T10:27:17,613 ############################ 2023-09-10T10:27:17,613 Python recognizes 'publiforge.Openers.Publiquiz.Variables' as an importable package[^1], 2023-09-10T10:27:17,614 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,615 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,615 package, please make sure that 'publiforge.Openers.Publiquiz.Variables' is explicitly added 2023-09-10T10:27:17,616 to the `packages` configuration field. 2023-09-10T10:27:17,617 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,617 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,618 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,619 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,620 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,621 If you don't want 'publiforge.Openers.Publiquiz.Variables' to be distributed and are 2023-09-10T10:27:17,621 already explicitly excluding 'publiforge.Openers.Publiquiz.Variables' via 2023-09-10T10:27:17,622 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,622 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,623 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,624 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,625 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,627 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,628 even if it does not contain any `.py` files. 2023-09-10T10:27:17,628 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,629 directory, all directories are treated like packages. 2023-09-10T10:27:17,629 ******************************************************************************** 2023-09-10T10:27:17,631 !! 2023-09-10T10:27:17,631 check.warn(importable) 2023-09-10T10:27:17,632 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiquiz.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:17,633 !! 2023-09-10T10:27:17,634 ******************************************************************************** 2023-09-10T10:27:17,634 ############################ 2023-09-10T10:27:17,635 # Package would be ignored # 2023-09-10T10:27:17,636 ############################ 2023-09-10T10:27:17,636 Python recognizes 'publiforge.Openers.Publiquiz.Xsl' as an importable package[^1], 2023-09-10T10:27:17,637 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,638 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,639 package, please make sure that 'publiforge.Openers.Publiquiz.Xsl' is explicitly added 2023-09-10T10:27:17,639 to the `packages` configuration field. 2023-09-10T10:27:17,641 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,641 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,642 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,643 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,644 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,646 If you don't want 'publiforge.Openers.Publiquiz.Xsl' to be distributed and are 2023-09-10T10:27:17,646 already explicitly excluding 'publiforge.Openers.Publiquiz.Xsl' via 2023-09-10T10:27:17,647 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,647 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,648 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,649 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,650 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,651 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,652 even if it does not contain any `.py` files. 2023-09-10T10:27:17,652 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,653 directory, all directories are treated like packages. 2023-09-10T10:27:17,653 ******************************************************************************** 2023-09-10T10:27:17,654 !! 2023-09-10T10:27:17,655 check.warn(importable) 2023-09-10T10:27:17,655 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiset' is absent from the `packages` configuration. 2023-09-10T10:27:17,656 !! 2023-09-10T10:27:17,657 ******************************************************************************** 2023-09-10T10:27:17,658 ############################ 2023-09-10T10:27:17,658 # Package would be ignored # 2023-09-10T10:27:17,659 ############################ 2023-09-10T10:27:17,659 Python recognizes 'publiforge.Openers.Publiset' as an importable package[^1], 2023-09-10T10:27:17,660 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,662 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,662 package, please make sure that 'publiforge.Openers.Publiset' is explicitly added 2023-09-10T10:27:17,663 to the `packages` configuration field. 2023-09-10T10:27:17,664 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,664 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,664 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,665 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,666 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,667 If you don't want 'publiforge.Openers.Publiset' to be distributed and are 2023-09-10T10:27:17,668 already explicitly excluding 'publiforge.Openers.Publiset' via 2023-09-10T10:27:17,668 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,669 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,669 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,670 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,671 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,673 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,673 even if it does not contain any `.py` files. 2023-09-10T10:27:17,674 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,674 directory, all directories are treated like packages. 2023-09-10T10:27:17,675 ******************************************************************************** 2023-09-10T10:27:17,676 !! 2023-09-10T10:27:17,676 check.warn(importable) 2023-09-10T10:27:17,677 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiset.Regex' is absent from the `packages` configuration. 2023-09-10T10:27:17,677 !! 2023-09-10T10:27:17,678 ******************************************************************************** 2023-09-10T10:27:17,678 ############################ 2023-09-10T10:27:17,679 # Package would be ignored # 2023-09-10T10:27:17,679 ############################ 2023-09-10T10:27:17,679 Python recognizes 'publiforge.Openers.Publiset.Regex' as an importable package[^1], 2023-09-10T10:27:17,680 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,680 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,681 package, please make sure that 'publiforge.Openers.Publiset.Regex' is explicitly added 2023-09-10T10:27:17,681 to the `packages` configuration field. 2023-09-10T10:27:17,682 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,682 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,683 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,684 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,684 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,685 If you don't want 'publiforge.Openers.Publiset.Regex' to be distributed and are 2023-09-10T10:27:17,686 already explicitly excluding 'publiforge.Openers.Publiset.Regex' via 2023-09-10T10:27:17,686 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,687 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,687 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,688 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,689 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,690 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,691 even if it does not contain any `.py` files. 2023-09-10T10:27:17,691 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,692 directory, all directories are treated like packages. 2023-09-10T10:27:17,693 ******************************************************************************** 2023-09-10T10:27:17,693 !! 2023-09-10T10:27:17,694 check.warn(importable) 2023-09-10T10:27:17,694 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiset.Seeds' is absent from the `packages` configuration. 2023-09-10T10:27:17,695 !! 2023-09-10T10:27:17,696 ******************************************************************************** 2023-09-10T10:27:17,696 ############################ 2023-09-10T10:27:17,697 # Package would be ignored # 2023-09-10T10:27:17,697 ############################ 2023-09-10T10:27:17,698 Python recognizes 'publiforge.Openers.Publiset.Seeds' as an importable package[^1], 2023-09-10T10:27:17,698 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,699 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,700 package, please make sure that 'publiforge.Openers.Publiset.Seeds' is explicitly added 2023-09-10T10:27:17,700 to the `packages` configuration field. 2023-09-10T10:27:17,701 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,702 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,703 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,703 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,704 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,705 If you don't want 'publiforge.Openers.Publiset.Seeds' to be distributed and are 2023-09-10T10:27:17,705 already explicitly excluding 'publiforge.Openers.Publiset.Seeds' via 2023-09-10T10:27:17,706 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,706 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,706 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,707 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,708 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,709 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,710 even if it does not contain any `.py` files. 2023-09-10T10:27:17,710 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,711 directory, all directories are treated like packages. 2023-09-10T10:27:17,711 ******************************************************************************** 2023-09-10T10:27:17,712 !! 2023-09-10T10:27:17,712 check.warn(importable) 2023-09-10T10:27:17,713 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiset.Static.Css' is absent from the `packages` configuration. 2023-09-10T10:27:17,713 !! 2023-09-10T10:27:17,714 ******************************************************************************** 2023-09-10T10:27:17,714 ############################ 2023-09-10T10:27:17,715 # Package would be ignored # 2023-09-10T10:27:17,715 ############################ 2023-09-10T10:27:17,716 Python recognizes 'publiforge.Openers.Publiset.Static.Css' as an importable package[^1], 2023-09-10T10:27:17,716 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,717 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,718 package, please make sure that 'publiforge.Openers.Publiset.Static.Css' is explicitly added 2023-09-10T10:27:17,718 to the `packages` configuration field. 2023-09-10T10:27:17,719 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,720 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,720 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,721 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,722 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,723 If you don't want 'publiforge.Openers.Publiset.Static.Css' to be distributed and are 2023-09-10T10:27:17,724 already explicitly excluding 'publiforge.Openers.Publiset.Static.Css' via 2023-09-10T10:27:17,724 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,725 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,725 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,726 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,727 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,729 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,729 even if it does not contain any `.py` files. 2023-09-10T10:27:17,730 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,730 directory, all directories are treated like packages. 2023-09-10T10:27:17,730 ******************************************************************************** 2023-09-10T10:27:17,731 !! 2023-09-10T10:27:17,732 check.warn(importable) 2023-09-10T10:27:17,732 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiset.Static.Images' is absent from the `packages` configuration. 2023-09-10T10:27:17,732 !! 2023-09-10T10:27:17,733 ******************************************************************************** 2023-09-10T10:27:17,734 ############################ 2023-09-10T10:27:17,734 # Package would be ignored # 2023-09-10T10:27:17,735 ############################ 2023-09-10T10:27:17,735 Python recognizes 'publiforge.Openers.Publiset.Static.Images' as an importable package[^1], 2023-09-10T10:27:17,736 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,736 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,737 package, please make sure that 'publiforge.Openers.Publiset.Static.Images' is explicitly added 2023-09-10T10:27:17,737 to the `packages` configuration field. 2023-09-10T10:27:17,738 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,739 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,739 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,740 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,741 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,742 If you don't want 'publiforge.Openers.Publiset.Static.Images' to be distributed and are 2023-09-10T10:27:17,742 already explicitly excluding 'publiforge.Openers.Publiset.Static.Images' via 2023-09-10T10:27:17,743 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,743 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,744 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,745 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,746 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,747 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,747 even if it does not contain any `.py` files. 2023-09-10T10:27:17,748 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,748 directory, all directories are treated like packages. 2023-09-10T10:27:17,749 ******************************************************************************** 2023-09-10T10:27:17,750 !! 2023-09-10T10:27:17,750 check.warn(importable) 2023-09-10T10:27:17,751 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiset.Static.Js' is absent from the `packages` configuration. 2023-09-10T10:27:17,751 !! 2023-09-10T10:27:17,752 ******************************************************************************** 2023-09-10T10:27:17,753 ############################ 2023-09-10T10:27:17,754 # Package would be ignored # 2023-09-10T10:27:17,754 ############################ 2023-09-10T10:27:17,755 Python recognizes 'publiforge.Openers.Publiset.Static.Js' as an importable package[^1], 2023-09-10T10:27:17,756 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,757 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,757 package, please make sure that 'publiforge.Openers.Publiset.Static.Js' is explicitly added 2023-09-10T10:27:17,758 to the `packages` configuration field. 2023-09-10T10:27:17,758 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,759 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,759 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,760 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,761 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,762 If you don't want 'publiforge.Openers.Publiset.Static.Js' to be distributed and are 2023-09-10T10:27:17,762 already explicitly excluding 'publiforge.Openers.Publiset.Static.Js' via 2023-09-10T10:27:17,763 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,763 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,764 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,764 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,765 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,767 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,767 even if it does not contain any `.py` files. 2023-09-10T10:27:17,767 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,768 directory, all directories are treated like packages. 2023-09-10T10:27:17,768 ******************************************************************************** 2023-09-10T10:27:17,769 !! 2023-09-10T10:27:17,770 check.warn(importable) 2023-09-10T10:27:17,770 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiset.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:17,771 !! 2023-09-10T10:27:17,772 ******************************************************************************** 2023-09-10T10:27:17,772 ############################ 2023-09-10T10:27:17,773 # Package would be ignored # 2023-09-10T10:27:17,773 ############################ 2023-09-10T10:27:17,774 Python recognizes 'publiforge.Openers.Publiset.Variables' as an importable package[^1], 2023-09-10T10:27:17,774 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,775 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,776 package, please make sure that 'publiforge.Openers.Publiset.Variables' is explicitly added 2023-09-10T10:27:17,776 to the `packages` configuration field. 2023-09-10T10:27:17,777 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,777 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,778 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,779 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,780 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,781 If you don't want 'publiforge.Openers.Publiset.Variables' to be distributed and are 2023-09-10T10:27:17,782 already explicitly excluding 'publiforge.Openers.Publiset.Variables' via 2023-09-10T10:27:17,782 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,783 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,783 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,784 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,785 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,786 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,786 even if it does not contain any `.py` files. 2023-09-10T10:27:17,786 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,787 directory, all directories are treated like packages. 2023-09-10T10:27:17,787 ******************************************************************************** 2023-09-10T10:27:17,788 !! 2023-09-10T10:27:17,788 check.warn(importable) 2023-09-10T10:27:17,789 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Publiset.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:17,789 !! 2023-09-10T10:27:17,790 ******************************************************************************** 2023-09-10T10:27:17,790 ############################ 2023-09-10T10:27:17,791 # Package would be ignored # 2023-09-10T10:27:17,791 ############################ 2023-09-10T10:27:17,791 Python recognizes 'publiforge.Openers.Publiset.Xsl' as an importable package[^1], 2023-09-10T10:27:17,792 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,793 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,793 package, please make sure that 'publiforge.Openers.Publiset.Xsl' is explicitly added 2023-09-10T10:27:17,794 to the `packages` configuration field. 2023-09-10T10:27:17,795 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,795 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,796 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,797 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,798 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,799 If you don't want 'publiforge.Openers.Publiset.Xsl' to be distributed and are 2023-09-10T10:27:17,800 already explicitly excluding 'publiforge.Openers.Publiset.Xsl' via 2023-09-10T10:27:17,800 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,801 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,801 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,802 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,803 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,805 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,805 even if it does not contain any `.py` files. 2023-09-10T10:27:17,806 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,807 directory, all directories are treated like packages. 2023-09-10T10:27:17,807 ******************************************************************************** 2023-09-10T10:27:17,809 !! 2023-09-10T10:27:17,809 check.warn(importable) 2023-09-10T10:27:17,810 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Xml' is absent from the `packages` configuration. 2023-09-10T10:27:17,811 !! 2023-09-10T10:27:17,811 ******************************************************************************** 2023-09-10T10:27:17,812 ############################ 2023-09-10T10:27:17,812 # Package would be ignored # 2023-09-10T10:27:17,812 ############################ 2023-09-10T10:27:17,813 Python recognizes 'publiforge.Openers.Xml' as an importable package[^1], 2023-09-10T10:27:17,813 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,814 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,814 package, please make sure that 'publiforge.Openers.Xml' is explicitly added 2023-09-10T10:27:17,815 to the `packages` configuration field. 2023-09-10T10:27:17,815 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,816 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,816 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,817 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,818 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,819 If you don't want 'publiforge.Openers.Xml' to be distributed and are 2023-09-10T10:27:17,819 already explicitly excluding 'publiforge.Openers.Xml' via 2023-09-10T10:27:17,819 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,820 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,820 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,821 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,822 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,824 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,824 even if it does not contain any `.py` files. 2023-09-10T10:27:17,825 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,825 directory, all directories are treated like packages. 2023-09-10T10:27:17,826 ******************************************************************************** 2023-09-10T10:27:17,827 !! 2023-09-10T10:27:17,827 check.warn(importable) 2023-09-10T10:27:17,828 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Xml.Static.Css' is absent from the `packages` configuration. 2023-09-10T10:27:17,828 !! 2023-09-10T10:27:17,829 ******************************************************************************** 2023-09-10T10:27:17,829 ############################ 2023-09-10T10:27:17,830 # Package would be ignored # 2023-09-10T10:27:17,830 ############################ 2023-09-10T10:27:17,831 Python recognizes 'publiforge.Openers.Xml.Static.Css' as an importable package[^1], 2023-09-10T10:27:17,831 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,832 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,833 package, please make sure that 'publiforge.Openers.Xml.Static.Css' is explicitly added 2023-09-10T10:27:17,833 to the `packages` configuration field. 2023-09-10T10:27:17,835 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,835 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,836 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,837 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,838 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,838 If you don't want 'publiforge.Openers.Xml.Static.Css' to be distributed and are 2023-09-10T10:27:17,839 already explicitly excluding 'publiforge.Openers.Xml.Static.Css' via 2023-09-10T10:27:17,839 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,839 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,840 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,841 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,842 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,843 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,843 even if it does not contain any `.py` files. 2023-09-10T10:27:17,843 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,844 directory, all directories are treated like packages. 2023-09-10T10:27:17,844 ******************************************************************************** 2023-09-10T10:27:17,845 !! 2023-09-10T10:27:17,845 check.warn(importable) 2023-09-10T10:27:17,846 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Xml.Static.Images' is absent from the `packages` configuration. 2023-09-10T10:27:17,846 !! 2023-09-10T10:27:17,847 ******************************************************************************** 2023-09-10T10:27:17,848 ############################ 2023-09-10T10:27:17,849 # Package would be ignored # 2023-09-10T10:27:17,849 ############################ 2023-09-10T10:27:17,849 Python recognizes 'publiforge.Openers.Xml.Static.Images' as an importable package[^1], 2023-09-10T10:27:17,850 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,851 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,852 package, please make sure that 'publiforge.Openers.Xml.Static.Images' is explicitly added 2023-09-10T10:27:17,852 to the `packages` configuration field. 2023-09-10T10:27:17,853 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,854 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,855 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,855 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,856 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,857 If you don't want 'publiforge.Openers.Xml.Static.Images' to be distributed and are 2023-09-10T10:27:17,858 already explicitly excluding 'publiforge.Openers.Xml.Static.Images' via 2023-09-10T10:27:17,858 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,859 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,859 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,860 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,861 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,863 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,863 even if it does not contain any `.py` files. 2023-09-10T10:27:17,864 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,864 directory, all directories are treated like packages. 2023-09-10T10:27:17,865 ******************************************************************************** 2023-09-10T10:27:17,865 !! 2023-09-10T10:27:17,866 check.warn(importable) 2023-09-10T10:27:17,866 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Openers.Xml.Static.Js' is absent from the `packages` configuration. 2023-09-10T10:27:17,866 !! 2023-09-10T10:27:17,867 ******************************************************************************** 2023-09-10T10:27:17,868 ############################ 2023-09-10T10:27:17,868 # Package would be ignored # 2023-09-10T10:27:17,869 ############################ 2023-09-10T10:27:17,869 Python recognizes 'publiforge.Openers.Xml.Static.Js' as an importable package[^1], 2023-09-10T10:27:17,869 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,870 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,871 package, please make sure that 'publiforge.Openers.Xml.Static.Js' is explicitly added 2023-09-10T10:27:17,871 to the `packages` configuration field. 2023-09-10T10:27:17,872 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,872 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,873 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,873 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,874 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,875 If you don't want 'publiforge.Openers.Xml.Static.Js' to be distributed and are 2023-09-10T10:27:17,876 already explicitly excluding 'publiforge.Openers.Xml.Static.Js' via 2023-09-10T10:27:17,876 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,876 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,877 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,878 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,879 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,880 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,881 even if it does not contain any `.py` files. 2023-09-10T10:27:17,881 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,882 directory, all directories are treated like packages. 2023-09-10T10:27:17,882 ******************************************************************************** 2023-09-10T10:27:17,883 !! 2023-09-10T10:27:17,883 check.warn(importable) 2023-09-10T10:27:17,884 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.CharCount' is absent from the `packages` configuration. 2023-09-10T10:27:17,884 !! 2023-09-10T10:27:17,885 ******************************************************************************** 2023-09-10T10:27:17,886 ############################ 2023-09-10T10:27:17,886 # Package would be ignored # 2023-09-10T10:27:17,887 ############################ 2023-09-10T10:27:17,887 Python recognizes 'publiforge.Processors.CharCount' as an importable package[^1], 2023-09-10T10:27:17,887 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,889 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,889 package, please make sure that 'publiforge.Processors.CharCount' is explicitly added 2023-09-10T10:27:17,889 to the `packages` configuration field. 2023-09-10T10:27:17,890 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,890 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,891 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,891 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,892 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,893 If you don't want 'publiforge.Processors.CharCount' to be distributed and are 2023-09-10T10:27:17,893 already explicitly excluding 'publiforge.Processors.CharCount' via 2023-09-10T10:27:17,894 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,894 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,894 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,895 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,896 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,897 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,897 even if it does not contain any `.py` files. 2023-09-10T10:27:17,898 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,898 directory, all directories are treated like packages. 2023-09-10T10:27:17,899 ******************************************************************************** 2023-09-10T10:27:17,900 !! 2023-09-10T10:27:17,900 check.warn(importable) 2023-09-10T10:27:17,901 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.CharCount.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:17,901 !! 2023-09-10T10:27:17,902 ******************************************************************************** 2023-09-10T10:27:17,903 ############################ 2023-09-10T10:27:17,903 # Package would be ignored # 2023-09-10T10:27:17,904 ############################ 2023-09-10T10:27:17,904 Python recognizes 'publiforge.Processors.CharCount.Xsl' as an importable package[^1], 2023-09-10T10:27:17,904 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,905 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,906 package, please make sure that 'publiforge.Processors.CharCount.Xsl' is explicitly added 2023-09-10T10:27:17,906 to the `packages` configuration field. 2023-09-10T10:27:17,907 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,908 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,908 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,909 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,910 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,911 If you don't want 'publiforge.Processors.CharCount.Xsl' to be distributed and are 2023-09-10T10:27:17,912 already explicitly excluding 'publiforge.Processors.CharCount.Xsl' via 2023-09-10T10:27:17,912 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,913 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,914 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,914 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,915 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,916 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,916 even if it does not contain any `.py` files. 2023-09-10T10:27:17,917 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,917 directory, all directories are treated like packages. 2023-09-10T10:27:17,917 ******************************************************************************** 2023-09-10T10:27:17,918 !! 2023-09-10T10:27:17,919 check.warn(importable) 2023-09-10T10:27:17,919 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.CleanStorage' is absent from the `packages` configuration. 2023-09-10T10:27:17,919 !! 2023-09-10T10:27:17,920 ******************************************************************************** 2023-09-10T10:27:17,920 ############################ 2023-09-10T10:27:17,921 # Package would be ignored # 2023-09-10T10:27:17,921 ############################ 2023-09-10T10:27:17,922 Python recognizes 'publiforge.Processors.CleanStorage' as an importable package[^1], 2023-09-10T10:27:17,922 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,923 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,923 package, please make sure that 'publiforge.Processors.CleanStorage' is explicitly added 2023-09-10T10:27:17,924 to the `packages` configuration field. 2023-09-10T10:27:17,925 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,925 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,926 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,926 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,927 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,928 If you don't want 'publiforge.Processors.CleanStorage' to be distributed and are 2023-09-10T10:27:17,929 already explicitly excluding 'publiforge.Processors.CleanStorage' via 2023-09-10T10:27:17,929 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,930 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,930 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,931 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,932 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,933 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,934 even if it does not contain any `.py` files. 2023-09-10T10:27:17,934 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,935 directory, all directories are treated like packages. 2023-09-10T10:27:17,935 ******************************************************************************** 2023-09-10T10:27:17,936 !! 2023-09-10T10:27:17,937 check.warn(importable) 2023-09-10T10:27:17,937 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.CleanStorage.lib' is absent from the `packages` configuration. 2023-09-10T10:27:17,938 !! 2023-09-10T10:27:17,939 ******************************************************************************** 2023-09-10T10:27:17,939 ############################ 2023-09-10T10:27:17,940 # Package would be ignored # 2023-09-10T10:27:17,940 ############################ 2023-09-10T10:27:17,940 Python recognizes 'publiforge.Processors.CleanStorage.lib' as an importable package[^1], 2023-09-10T10:27:17,941 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,941 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,942 package, please make sure that 'publiforge.Processors.CleanStorage.lib' is explicitly added 2023-09-10T10:27:17,942 to the `packages` configuration field. 2023-09-10T10:27:17,943 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,943 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,944 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,944 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,945 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,946 If you don't want 'publiforge.Processors.CleanStorage.lib' to be distributed and are 2023-09-10T10:27:17,946 already explicitly excluding 'publiforge.Processors.CleanStorage.lib' via 2023-09-10T10:27:17,946 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,947 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,947 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,948 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,949 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,951 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,951 even if it does not contain any `.py` files. 2023-09-10T10:27:17,952 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,952 directory, all directories are treated like packages. 2023-09-10T10:27:17,953 ******************************************************************************** 2023-09-10T10:27:17,954 !! 2023-09-10T10:27:17,954 check.warn(importable) 2023-09-10T10:27:17,954 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.DTBookValid' is absent from the `packages` configuration. 2023-09-10T10:27:17,955 !! 2023-09-10T10:27:17,956 ******************************************************************************** 2023-09-10T10:27:17,956 ############################ 2023-09-10T10:27:17,957 # Package would be ignored # 2023-09-10T10:27:17,957 ############################ 2023-09-10T10:27:17,958 Python recognizes 'publiforge.Processors.DTBookValid' as an importable package[^1], 2023-09-10T10:27:17,958 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,959 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,959 package, please make sure that 'publiforge.Processors.DTBookValid' is explicitly added 2023-09-10T10:27:17,960 to the `packages` configuration field. 2023-09-10T10:27:17,961 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,961 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,962 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,963 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,965 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,965 If you don't want 'publiforge.Processors.DTBookValid' to be distributed and are 2023-09-10T10:27:17,966 already explicitly excluding 'publiforge.Processors.DTBookValid' via 2023-09-10T10:27:17,966 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,966 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,967 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,967 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,968 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,969 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,970 even if it does not contain any `.py` files. 2023-09-10T10:27:17,970 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,970 directory, all directories are treated like packages. 2023-09-10T10:27:17,971 ******************************************************************************** 2023-09-10T10:27:17,971 !! 2023-09-10T10:27:17,972 check.warn(importable) 2023-09-10T10:27:17,972 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.DTBookValid.RelaxNG' is absent from the `packages` configuration. 2023-09-10T10:27:17,973 !! 2023-09-10T10:27:17,973 ******************************************************************************** 2023-09-10T10:27:17,974 ############################ 2023-09-10T10:27:17,974 # Package would be ignored # 2023-09-10T10:27:17,975 ############################ 2023-09-10T10:27:17,975 Python recognizes 'publiforge.Processors.DTBookValid.RelaxNG' as an importable package[^1], 2023-09-10T10:27:17,976 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,977 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,977 package, please make sure that 'publiforge.Processors.DTBookValid.RelaxNG' is explicitly added 2023-09-10T10:27:17,978 to the `packages` configuration field. 2023-09-10T10:27:17,979 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,979 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,980 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,981 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,982 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:17,983 If you don't want 'publiforge.Processors.DTBookValid.RelaxNG' to be distributed and are 2023-09-10T10:27:17,983 already explicitly excluding 'publiforge.Processors.DTBookValid.RelaxNG' via 2023-09-10T10:27:17,984 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:17,984 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:17,984 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:17,985 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:17,986 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:17,988 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:17,989 even if it does not contain any `.py` files. 2023-09-10T10:27:17,989 On the other hand, currently there is no concept of package data 2023-09-10T10:27:17,990 directory, all directories are treated like packages. 2023-09-10T10:27:17,990 ******************************************************************************** 2023-09-10T10:27:17,991 !! 2023-09-10T10:27:17,991 check.warn(importable) 2023-09-10T10:27:17,991 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PackFilling' is absent from the `packages` configuration. 2023-09-10T10:27:17,992 !! 2023-09-10T10:27:17,992 ******************************************************************************** 2023-09-10T10:27:17,993 ############################ 2023-09-10T10:27:17,993 # Package would be ignored # 2023-09-10T10:27:17,993 ############################ 2023-09-10T10:27:17,994 Python recognizes 'publiforge.Processors.PackFilling' as an importable package[^1], 2023-09-10T10:27:17,994 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:17,995 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:17,995 package, please make sure that 'publiforge.Processors.PackFilling' is explicitly added 2023-09-10T10:27:17,996 to the `packages` configuration field. 2023-09-10T10:27:17,996 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:17,997 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:17,997 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:17,998 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:17,999 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,000 If you don't want 'publiforge.Processors.PackFilling' to be distributed and are 2023-09-10T10:27:18,000 already explicitly excluding 'publiforge.Processors.PackFilling' via 2023-09-10T10:27:18,000 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,001 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,001 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,002 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,003 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,005 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,005 even if it does not contain any `.py` files. 2023-09-10T10:27:18,006 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,006 directory, all directories are treated like packages. 2023-09-10T10:27:18,007 ******************************************************************************** 2023-09-10T10:27:18,008 !! 2023-09-10T10:27:18,008 check.warn(importable) 2023-09-10T10:27:18,009 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PackFilling.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,009 !! 2023-09-10T10:27:18,010 ******************************************************************************** 2023-09-10T10:27:18,010 ############################ 2023-09-10T10:27:18,011 # Package would be ignored # 2023-09-10T10:27:18,012 ############################ 2023-09-10T10:27:18,012 Python recognizes 'publiforge.Processors.PackFilling.Variables' as an importable package[^1], 2023-09-10T10:27:18,013 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,014 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,014 package, please make sure that 'publiforge.Processors.PackFilling.Variables' is explicitly added 2023-09-10T10:27:18,015 to the `packages` configuration field. 2023-09-10T10:27:18,015 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,016 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,016 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,017 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,018 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,019 If you don't want 'publiforge.Processors.PackFilling.Variables' to be distributed and are 2023-09-10T10:27:18,019 already explicitly excluding 'publiforge.Processors.PackFilling.Variables' via 2023-09-10T10:27:18,019 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,020 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,020 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,021 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,022 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,023 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,023 even if it does not contain any `.py` files. 2023-09-10T10:27:18,024 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,024 directory, all directories are treated like packages. 2023-09-10T10:27:18,025 ******************************************************************************** 2023-09-10T10:27:18,026 !! 2023-09-10T10:27:18,026 check.warn(importable) 2023-09-10T10:27:18,026 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PackFilling.lib' is absent from the `packages` configuration. 2023-09-10T10:27:18,027 !! 2023-09-10T10:27:18,028 ******************************************************************************** 2023-09-10T10:27:18,028 ############################ 2023-09-10T10:27:18,028 # Package would be ignored # 2023-09-10T10:27:18,029 ############################ 2023-09-10T10:27:18,029 Python recognizes 'publiforge.Processors.PackFilling.lib' as an importable package[^1], 2023-09-10T10:27:18,030 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,031 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,031 package, please make sure that 'publiforge.Processors.PackFilling.lib' is explicitly added 2023-09-10T10:27:18,032 to the `packages` configuration field. 2023-09-10T10:27:18,032 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,033 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,033 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,034 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,035 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,036 If you don't want 'publiforge.Processors.PackFilling.lib' to be distributed and are 2023-09-10T10:27:18,036 already explicitly excluding 'publiforge.Processors.PackFilling.lib' via 2023-09-10T10:27:18,037 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,037 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,038 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,039 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,039 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,040 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,041 even if it does not contain any `.py` files. 2023-09-10T10:27:18,041 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,041 directory, all directories are treated like packages. 2023-09-10T10:27:18,042 ******************************************************************************** 2023-09-10T10:27:18,042 !! 2023-09-10T10:27:18,043 check.warn(importable) 2023-09-10T10:27:18,043 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Parallel' is absent from the `packages` configuration. 2023-09-10T10:27:18,043 !! 2023-09-10T10:27:18,044 ******************************************************************************** 2023-09-10T10:27:18,044 ############################ 2023-09-10T10:27:18,045 # Package would be ignored # 2023-09-10T10:27:18,045 ############################ 2023-09-10T10:27:18,045 Python recognizes 'publiforge.Processors.Parallel' as an importable package[^1], 2023-09-10T10:27:18,046 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,047 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,047 package, please make sure that 'publiforge.Processors.Parallel' is explicitly added 2023-09-10T10:27:18,047 to the `packages` configuration field. 2023-09-10T10:27:18,048 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,048 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,049 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,050 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,050 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,051 If you don't want 'publiforge.Processors.Parallel' to be distributed and are 2023-09-10T10:27:18,052 already explicitly excluding 'publiforge.Processors.Parallel' via 2023-09-10T10:27:18,052 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,052 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,053 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,054 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,055 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,056 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,056 even if it does not contain any `.py` files. 2023-09-10T10:27:18,057 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,057 directory, all directories are treated like packages. 2023-09-10T10:27:18,058 ******************************************************************************** 2023-09-10T10:27:18,059 !! 2023-09-10T10:27:18,059 check.warn(importable) 2023-09-10T10:27:18,060 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Parallel.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,060 !! 2023-09-10T10:27:18,061 ******************************************************************************** 2023-09-10T10:27:18,062 ############################ 2023-09-10T10:27:18,062 # Package would be ignored # 2023-09-10T10:27:18,062 ############################ 2023-09-10T10:27:18,063 Python recognizes 'publiforge.Processors.Parallel.Variables' as an importable package[^1], 2023-09-10T10:27:18,063 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,064 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,064 package, please make sure that 'publiforge.Processors.Parallel.Variables' is explicitly added 2023-09-10T10:27:18,064 to the `packages` configuration field. 2023-09-10T10:27:18,065 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,065 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,066 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,066 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,067 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,068 If you don't want 'publiforge.Processors.Parallel.Variables' to be distributed and are 2023-09-10T10:27:18,068 already explicitly excluding 'publiforge.Processors.Parallel.Variables' via 2023-09-10T10:27:18,069 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,069 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,069 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,070 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,071 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,072 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,073 even if it does not contain any `.py` files. 2023-09-10T10:27:18,073 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,073 directory, all directories are treated like packages. 2023-09-10T10:27:18,074 ******************************************************************************** 2023-09-10T10:27:18,075 !! 2023-09-10T10:27:18,075 check.warn(importable) 2023-09-10T10:27:18,076 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publianim2Html5' is absent from the `packages` configuration. 2023-09-10T10:27:18,076 !! 2023-09-10T10:27:18,077 ******************************************************************************** 2023-09-10T10:27:18,077 ############################ 2023-09-10T10:27:18,078 # Package would be ignored # 2023-09-10T10:27:18,078 ############################ 2023-09-10T10:27:18,079 Python recognizes 'publiforge.Processors.Publianim2Html5' as an importable package[^1], 2023-09-10T10:27:18,079 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,080 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,080 package, please make sure that 'publiforge.Processors.Publianim2Html5' is explicitly added 2023-09-10T10:27:18,081 to the `packages` configuration field. 2023-09-10T10:27:18,082 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,082 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,083 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,084 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,085 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,086 If you don't want 'publiforge.Processors.Publianim2Html5' to be distributed and are 2023-09-10T10:27:18,086 already explicitly excluding 'publiforge.Processors.Publianim2Html5' via 2023-09-10T10:27:18,086 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,087 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,087 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,088 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,088 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,090 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,090 even if it does not contain any `.py` files. 2023-09-10T10:27:18,090 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,091 directory, all directories are treated like packages. 2023-09-10T10:27:18,091 ******************************************************************************** 2023-09-10T10:27:18,092 !! 2023-09-10T10:27:18,092 check.warn(importable) 2023-09-10T10:27:18,093 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publianim2Html5.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,093 !! 2023-09-10T10:27:18,094 ******************************************************************************** 2023-09-10T10:27:18,094 ############################ 2023-09-10T10:27:18,095 # Package would be ignored # 2023-09-10T10:27:18,095 ############################ 2023-09-10T10:27:18,096 Python recognizes 'publiforge.Processors.Publianim2Html5.Variables' as an importable package[^1], 2023-09-10T10:27:18,096 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,097 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,097 package, please make sure that 'publiforge.Processors.Publianim2Html5.Variables' is explicitly added 2023-09-10T10:27:18,098 to the `packages` configuration field. 2023-09-10T10:27:18,099 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,099 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,100 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,101 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,101 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,102 If you don't want 'publiforge.Processors.Publianim2Html5.Variables' to be distributed and are 2023-09-10T10:27:18,103 already explicitly excluding 'publiforge.Processors.Publianim2Html5.Variables' via 2023-09-10T10:27:18,103 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,104 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,104 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,105 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,106 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,107 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,108 even if it does not contain any `.py` files. 2023-09-10T10:27:18,108 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,109 directory, all directories are treated like packages. 2023-09-10T10:27:18,109 ******************************************************************************** 2023-09-10T10:27:18,110 !! 2023-09-10T10:27:18,110 check.warn(importable) 2023-09-10T10:27:18,110 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publianim2Html5.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,111 !! 2023-09-10T10:27:18,112 ******************************************************************************** 2023-09-10T10:27:18,112 ############################ 2023-09-10T10:27:18,112 # Package would be ignored # 2023-09-10T10:27:18,113 ############################ 2023-09-10T10:27:18,113 Python recognizes 'publiforge.Processors.Publianim2Html5.Xsl' as an importable package[^1], 2023-09-10T10:27:18,113 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,114 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,114 package, please make sure that 'publiforge.Processors.Publianim2Html5.Xsl' is explicitly added 2023-09-10T10:27:18,115 to the `packages` configuration field. 2023-09-10T10:27:18,116 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,116 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,116 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,117 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,118 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,119 If you don't want 'publiforge.Processors.Publianim2Html5.Xsl' to be distributed and are 2023-09-10T10:27:18,119 already explicitly excluding 'publiforge.Processors.Publianim2Html5.Xsl' via 2023-09-10T10:27:18,120 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,120 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,121 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,121 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,122 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,124 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,124 even if it does not contain any `.py` files. 2023-09-10T10:27:18,125 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,125 directory, all directories are treated like packages. 2023-09-10T10:27:18,126 ******************************************************************************** 2023-09-10T10:27:18,127 !! 2023-09-10T10:27:18,127 check.warn(importable) 2023-09-10T10:27:18,128 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2DTBook' is absent from the `packages` configuration. 2023-09-10T10:27:18,128 !! 2023-09-10T10:27:18,129 ******************************************************************************** 2023-09-10T10:27:18,129 ############################ 2023-09-10T10:27:18,130 # Package would be ignored # 2023-09-10T10:27:18,130 ############################ 2023-09-10T10:27:18,131 Python recognizes 'publiforge.Processors.Publidoc2DTBook' as an importable package[^1], 2023-09-10T10:27:18,131 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,133 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,133 package, please make sure that 'publiforge.Processors.Publidoc2DTBook' is explicitly added 2023-09-10T10:27:18,133 to the `packages` configuration field. 2023-09-10T10:27:18,134 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,134 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,135 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,135 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,136 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,137 If you don't want 'publiforge.Processors.Publidoc2DTBook' to be distributed and are 2023-09-10T10:27:18,137 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook' via 2023-09-10T10:27:18,137 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,138 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,138 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,139 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,140 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,141 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,141 even if it does not contain any `.py` files. 2023-09-10T10:27:18,141 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,142 directory, all directories are treated like packages. 2023-09-10T10:27:18,142 ******************************************************************************** 2023-09-10T10:27:18,143 !! 2023-09-10T10:27:18,144 check.warn(importable) 2023-09-10T10:27:18,144 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2DTBook.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,144 !! 2023-09-10T10:27:18,145 ******************************************************************************** 2023-09-10T10:27:18,146 ############################ 2023-09-10T10:27:18,146 # Package would be ignored # 2023-09-10T10:27:18,147 ############################ 2023-09-10T10:27:18,147 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Variables' as an importable package[^1], 2023-09-10T10:27:18,148 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,149 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,149 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Variables' is explicitly added 2023-09-10T10:27:18,150 to the `packages` configuration field. 2023-09-10T10:27:18,150 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,151 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,151 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,152 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,153 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,154 If you don't want 'publiforge.Processors.Publidoc2DTBook.Variables' to be distributed and are 2023-09-10T10:27:18,154 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Variables' via 2023-09-10T10:27:18,155 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,155 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,156 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,157 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,158 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,159 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,159 even if it does not contain any `.py` files. 2023-09-10T10:27:18,160 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,160 directory, all directories are treated like packages. 2023-09-10T10:27:18,161 ******************************************************************************** 2023-09-10T10:27:18,162 !! 2023-09-10T10:27:18,162 check.warn(importable) 2023-09-10T10:27:18,163 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2DTBook.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,163 !! 2023-09-10T10:27:18,164 ******************************************************************************** 2023-09-10T10:27:18,165 ############################ 2023-09-10T10:27:18,165 # Package would be ignored # 2023-09-10T10:27:18,166 ############################ 2023-09-10T10:27:18,166 Python recognizes 'publiforge.Processors.Publidoc2DTBook.Xsl' as an importable package[^1], 2023-09-10T10:27:18,166 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,167 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,168 package, please make sure that 'publiforge.Processors.Publidoc2DTBook.Xsl' is explicitly added 2023-09-10T10:27:18,168 to the `packages` configuration field. 2023-09-10T10:27:18,169 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,169 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,170 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,171 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,172 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,173 If you don't want 'publiforge.Processors.Publidoc2DTBook.Xsl' to be distributed and are 2023-09-10T10:27:18,173 already explicitly excluding 'publiforge.Processors.Publidoc2DTBook.Xsl' via 2023-09-10T10:27:18,173 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,174 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,174 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,175 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,176 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,177 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,178 even if it does not contain any `.py` files. 2023-09-10T10:27:18,178 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,179 directory, all directories are treated like packages. 2023-09-10T10:27:18,179 ******************************************************************************** 2023-09-10T10:27:18,180 !! 2023-09-10T10:27:18,181 check.warn(importable) 2023-09-10T10:27:18,181 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub2' is absent from the `packages` configuration. 2023-09-10T10:27:18,182 !! 2023-09-10T10:27:18,183 ******************************************************************************** 2023-09-10T10:27:18,183 ############################ 2023-09-10T10:27:18,183 # Package would be ignored # 2023-09-10T10:27:18,184 ############################ 2023-09-10T10:27:18,184 Python recognizes 'publiforge.Processors.Publidoc2EPub2' as an importable package[^1], 2023-09-10T10:27:18,185 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,185 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,186 package, please make sure that 'publiforge.Processors.Publidoc2EPub2' is explicitly added 2023-09-10T10:27:18,186 to the `packages` configuration field. 2023-09-10T10:27:18,187 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,187 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,188 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,188 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,189 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,190 If you don't want 'publiforge.Processors.Publidoc2EPub2' to be distributed and are 2023-09-10T10:27:18,190 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2' via 2023-09-10T10:27:18,191 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,191 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,192 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,192 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,193 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,195 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,195 even if it does not contain any `.py` files. 2023-09-10T10:27:18,196 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,196 directory, all directories are treated like packages. 2023-09-10T10:27:18,197 ******************************************************************************** 2023-09-10T10:27:18,197 !! 2023-09-10T10:27:18,198 check.warn(importable) 2023-09-10T10:27:18,199 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.Templates' is absent from the `packages` configuration. 2023-09-10T10:27:18,199 !! 2023-09-10T10:27:18,200 ******************************************************************************** 2023-09-10T10:27:18,201 ############################ 2023-09-10T10:27:18,201 # Package would be ignored # 2023-09-10T10:27:18,202 ############################ 2023-09-10T10:27:18,202 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates' as an importable package[^1], 2023-09-10T10:27:18,203 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,204 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,204 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates' is explicitly added 2023-09-10T10:27:18,205 to the `packages` configuration field. 2023-09-10T10:27:18,206 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,206 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,207 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,208 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,209 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,209 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates' to be distributed and are 2023-09-10T10:27:18,210 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates' via 2023-09-10T10:27:18,210 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,211 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,211 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,212 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,212 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,214 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,214 even if it does not contain any `.py` files. 2023-09-10T10:27:18,215 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,215 directory, all directories are treated like packages. 2023-09-10T10:27:18,216 ******************************************************************************** 2023-09-10T10:27:18,217 !! 2023-09-10T10:27:18,217 check.warn(importable) 2023-09-10T10:27:18,217 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' is absent from the `packages` configuration. 2023-09-10T10:27:18,218 !! 2023-09-10T10:27:18,219 ******************************************************************************** 2023-09-10T10:27:18,219 ############################ 2023-09-10T10:27:18,220 # Package would be ignored # 2023-09-10T10:27:18,220 ############################ 2023-09-10T10:27:18,220 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' as an importable package[^1], 2023-09-10T10:27:18,221 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,222 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,222 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' is explicitly added 2023-09-10T10:27:18,223 to the `packages` configuration field. 2023-09-10T10:27:18,224 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,224 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,225 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,226 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,227 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,227 If you don't want 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' to be distributed and are 2023-09-10T10:27:18,228 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Templates.OEBPS.Css' via 2023-09-10T10:27:18,228 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,229 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,229 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,231 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,232 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,233 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,233 even if it does not contain any `.py` files. 2023-09-10T10:27:18,234 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,234 directory, all directories are treated like packages. 2023-09-10T10:27:18,235 ******************************************************************************** 2023-09-10T10:27:18,236 !! 2023-09-10T10:27:18,236 check.warn(importable) 2023-09-10T10:27:18,237 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,237 !! 2023-09-10T10:27:18,238 ******************************************************************************** 2023-09-10T10:27:18,238 ############################ 2023-09-10T10:27:18,238 # Package would be ignored # 2023-09-10T10:27:18,239 ############################ 2023-09-10T10:27:18,239 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Variables' as an importable package[^1], 2023-09-10T10:27:18,240 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,240 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,241 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Variables' is explicitly added 2023-09-10T10:27:18,241 to the `packages` configuration field. 2023-09-10T10:27:18,242 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,242 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,243 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,244 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,245 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,246 If you don't want 'publiforge.Processors.Publidoc2EPub2.Variables' to be distributed and are 2023-09-10T10:27:18,246 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Variables' via 2023-09-10T10:27:18,247 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,247 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,248 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,249 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,250 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,252 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,252 even if it does not contain any `.py` files. 2023-09-10T10:27:18,252 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,253 directory, all directories are treated like packages. 2023-09-10T10:27:18,253 ******************************************************************************** 2023-09-10T10:27:18,254 !! 2023-09-10T10:27:18,255 check.warn(importable) 2023-09-10T10:27:18,255 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,256 !! 2023-09-10T10:27:18,257 ******************************************************************************** 2023-09-10T10:27:18,257 ############################ 2023-09-10T10:27:18,258 # Package would be ignored # 2023-09-10T10:27:18,258 ############################ 2023-09-10T10:27:18,259 Python recognizes 'publiforge.Processors.Publidoc2EPub2.Xsl' as an importable package[^1], 2023-09-10T10:27:18,260 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,260 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,261 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.Xsl' is explicitly added 2023-09-10T10:27:18,261 to the `packages` configuration field. 2023-09-10T10:27:18,262 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,262 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,263 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,263 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,264 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,265 If you don't want 'publiforge.Processors.Publidoc2EPub2.Xsl' to be distributed and are 2023-09-10T10:27:18,265 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.Xsl' via 2023-09-10T10:27:18,266 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,266 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,267 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,267 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,268 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,269 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,270 even if it does not contain any `.py` files. 2023-09-10T10:27:18,270 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,271 directory, all directories are treated like packages. 2023-09-10T10:27:18,271 ******************************************************************************** 2023-09-10T10:27:18,272 !! 2023-09-10T10:27:18,273 check.warn(importable) 2023-09-10T10:27:18,273 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.jars' is absent from the `packages` configuration. 2023-09-10T10:27:18,273 !! 2023-09-10T10:27:18,274 ******************************************************************************** 2023-09-10T10:27:18,275 ############################ 2023-09-10T10:27:18,275 # Package would be ignored # 2023-09-10T10:27:18,276 ############################ 2023-09-10T10:27:18,276 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars' as an importable package[^1], 2023-09-10T10:27:18,277 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,278 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,278 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars' is explicitly added 2023-09-10T10:27:18,279 to the `packages` configuration field. 2023-09-10T10:27:18,280 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,280 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,281 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,282 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,283 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,284 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars' to be distributed and are 2023-09-10T10:27:18,284 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars' via 2023-09-10T10:27:18,285 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,285 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,286 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,287 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,287 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,289 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,289 even if it does not contain any `.py` files. 2023-09-10T10:27:18,289 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,290 directory, all directories are treated like packages. 2023-09-10T10:27:18,290 ******************************************************************************** 2023-09-10T10:27:18,291 !! 2023-09-10T10:27:18,291 check.warn(importable) 2023-09-10T10:27:18,291 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.jars.lib' is absent from the `packages` configuration. 2023-09-10T10:27:18,292 !! 2023-09-10T10:27:18,293 ******************************************************************************** 2023-09-10T10:27:18,293 ############################ 2023-09-10T10:27:18,293 # Package would be ignored # 2023-09-10T10:27:18,294 ############################ 2023-09-10T10:27:18,294 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.lib' as an importable package[^1], 2023-09-10T10:27:18,295 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,295 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,296 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.lib' is explicitly added 2023-09-10T10:27:18,296 to the `packages` configuration field. 2023-09-10T10:27:18,297 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,298 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,298 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,299 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,300 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,301 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.lib' to be distributed and are 2023-09-10T10:27:18,302 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.lib' via 2023-09-10T10:27:18,302 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,302 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,303 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,304 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,305 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,307 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,307 even if it does not contain any `.py` files. 2023-09-10T10:27:18,308 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,308 directory, all directories are treated like packages. 2023-09-10T10:27:18,309 ******************************************************************************** 2023-09-10T10:27:18,310 !! 2023-09-10T10:27:18,310 check.warn(importable) 2023-09-10T10:27:18,311 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub2.jars.licenses' is absent from the `packages` configuration. 2023-09-10T10:27:18,311 !! 2023-09-10T10:27:18,312 ******************************************************************************** 2023-09-10T10:27:18,312 ############################ 2023-09-10T10:27:18,312 # Package would be ignored # 2023-09-10T10:27:18,313 ############################ 2023-09-10T10:27:18,313 Python recognizes 'publiforge.Processors.Publidoc2EPub2.jars.licenses' as an importable package[^1], 2023-09-10T10:27:18,313 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,314 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,315 package, please make sure that 'publiforge.Processors.Publidoc2EPub2.jars.licenses' is explicitly added 2023-09-10T10:27:18,315 to the `packages` configuration field. 2023-09-10T10:27:18,316 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,316 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,316 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,317 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,318 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,318 If you don't want 'publiforge.Processors.Publidoc2EPub2.jars.licenses' to be distributed and are 2023-09-10T10:27:18,319 already explicitly excluding 'publiforge.Processors.Publidoc2EPub2.jars.licenses' via 2023-09-10T10:27:18,319 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,320 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,320 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,321 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,322 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,324 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,324 even if it does not contain any `.py` files. 2023-09-10T10:27:18,325 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,325 directory, all directories are treated like packages. 2023-09-10T10:27:18,326 ******************************************************************************** 2023-09-10T10:27:18,327 !! 2023-09-10T10:27:18,327 check.warn(importable) 2023-09-10T10:27:18,328 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub3' is absent from the `packages` configuration. 2023-09-10T10:27:18,328 !! 2023-09-10T10:27:18,329 ******************************************************************************** 2023-09-10T10:27:18,329 ############################ 2023-09-10T10:27:18,330 # Package would be ignored # 2023-09-10T10:27:18,330 ############################ 2023-09-10T10:27:18,331 Python recognizes 'publiforge.Processors.Publidoc2EPub3' as an importable package[^1], 2023-09-10T10:27:18,331 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,332 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,333 package, please make sure that 'publiforge.Processors.Publidoc2EPub3' is explicitly added 2023-09-10T10:27:18,333 to the `packages` configuration field. 2023-09-10T10:27:18,334 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,334 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,335 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,335 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,336 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,337 If you don't want 'publiforge.Processors.Publidoc2EPub3' to be distributed and are 2023-09-10T10:27:18,337 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3' via 2023-09-10T10:27:18,337 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,338 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,338 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,339 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,339 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,340 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,341 even if it does not contain any `.py` files. 2023-09-10T10:27:18,341 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,341 directory, all directories are treated like packages. 2023-09-10T10:27:18,342 ******************************************************************************** 2023-09-10T10:27:18,343 !! 2023-09-10T10:27:18,343 check.warn(importable) 2023-09-10T10:27:18,343 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub3.Templates' is absent from the `packages` configuration. 2023-09-10T10:27:18,344 !! 2023-09-10T10:27:18,345 ******************************************************************************** 2023-09-10T10:27:18,345 ############################ 2023-09-10T10:27:18,346 # Package would be ignored # 2023-09-10T10:27:18,346 ############################ 2023-09-10T10:27:18,347 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates' as an importable package[^1], 2023-09-10T10:27:18,347 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,348 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,348 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates' is explicitly added 2023-09-10T10:27:18,349 to the `packages` configuration field. 2023-09-10T10:27:18,350 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,350 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,351 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,352 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,353 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,354 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates' to be distributed and are 2023-09-10T10:27:18,354 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates' via 2023-09-10T10:27:18,355 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,355 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,356 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,357 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,358 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,359 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,359 even if it does not contain any `.py` files. 2023-09-10T10:27:18,360 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,360 directory, all directories are treated like packages. 2023-09-10T10:27:18,361 ******************************************************************************** 2023-09-10T10:27:18,361 !! 2023-09-10T10:27:18,362 check.warn(importable) 2023-09-10T10:27:18,362 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' is absent from the `packages` configuration. 2023-09-10T10:27:18,362 !! 2023-09-10T10:27:18,363 ******************************************************************************** 2023-09-10T10:27:18,363 ############################ 2023-09-10T10:27:18,364 # Package would be ignored # 2023-09-10T10:27:18,364 ############################ 2023-09-10T10:27:18,365 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' as an importable package[^1], 2023-09-10T10:27:18,365 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,366 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,366 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' is explicitly added 2023-09-10T10:27:18,367 to the `packages` configuration field. 2023-09-10T10:27:18,368 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,369 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,369 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,370 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,372 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,373 If you don't want 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' to be distributed and are 2023-09-10T10:27:18,373 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Templates.OEBPS.Css' via 2023-09-10T10:27:18,374 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,375 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,375 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,376 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,378 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,379 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,380 even if it does not contain any `.py` files. 2023-09-10T10:27:18,380 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,381 directory, all directories are treated like packages. 2023-09-10T10:27:18,382 ******************************************************************************** 2023-09-10T10:27:18,383 !! 2023-09-10T10:27:18,383 check.warn(importable) 2023-09-10T10:27:18,384 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub3.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,385 !! 2023-09-10T10:27:18,386 ******************************************************************************** 2023-09-10T10:27:18,386 ############################ 2023-09-10T10:27:18,387 # Package would be ignored # 2023-09-10T10:27:18,388 ############################ 2023-09-10T10:27:18,388 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Variables' as an importable package[^1], 2023-09-10T10:27:18,389 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,390 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,390 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Variables' is explicitly added 2023-09-10T10:27:18,390 to the `packages` configuration field. 2023-09-10T10:27:18,391 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,392 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,392 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,393 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,394 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,395 If you don't want 'publiforge.Processors.Publidoc2EPub3.Variables' to be distributed and are 2023-09-10T10:27:18,395 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Variables' via 2023-09-10T10:27:18,396 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,396 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,397 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,398 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,399 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,401 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,401 even if it does not contain any `.py` files. 2023-09-10T10:27:18,402 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,403 directory, all directories are treated like packages. 2023-09-10T10:27:18,403 ******************************************************************************** 2023-09-10T10:27:18,405 !! 2023-09-10T10:27:18,405 check.warn(importable) 2023-09-10T10:27:18,406 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2EPub3.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,406 !! 2023-09-10T10:27:18,408 ******************************************************************************** 2023-09-10T10:27:18,408 ############################ 2023-09-10T10:27:18,409 # Package would be ignored # 2023-09-10T10:27:18,409 ############################ 2023-09-10T10:27:18,410 Python recognizes 'publiforge.Processors.Publidoc2EPub3.Xsl' as an importable package[^1], 2023-09-10T10:27:18,410 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,411 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,412 package, please make sure that 'publiforge.Processors.Publidoc2EPub3.Xsl' is explicitly added 2023-09-10T10:27:18,413 to the `packages` configuration field. 2023-09-10T10:27:18,414 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,414 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,415 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,416 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,418 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,419 If you don't want 'publiforge.Processors.Publidoc2EPub3.Xsl' to be distributed and are 2023-09-10T10:27:18,419 already explicitly excluding 'publiforge.Processors.Publidoc2EPub3.Xsl' via 2023-09-10T10:27:18,420 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,420 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,421 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,422 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,422 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,424 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,424 even if it does not contain any `.py` files. 2023-09-10T10:27:18,425 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,425 directory, all directories are treated like packages. 2023-09-10T10:27:18,426 ******************************************************************************** 2023-09-10T10:27:18,427 !! 2023-09-10T10:27:18,428 check.warn(importable) 2023-09-10T10:27:18,428 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Html5' is absent from the `packages` configuration. 2023-09-10T10:27:18,429 !! 2023-09-10T10:27:18,430 ******************************************************************************** 2023-09-10T10:27:18,430 ############################ 2023-09-10T10:27:18,431 # Package would be ignored # 2023-09-10T10:27:18,432 ############################ 2023-09-10T10:27:18,433 Python recognizes 'publiforge.Processors.Publidoc2Html5' as an importable package[^1], 2023-09-10T10:27:18,433 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,434 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,435 package, please make sure that 'publiforge.Processors.Publidoc2Html5' is explicitly added 2023-09-10T10:27:18,435 to the `packages` configuration field. 2023-09-10T10:27:18,437 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,437 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,438 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,439 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,440 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,441 If you don't want 'publiforge.Processors.Publidoc2Html5' to be distributed and are 2023-09-10T10:27:18,442 already explicitly excluding 'publiforge.Processors.Publidoc2Html5' via 2023-09-10T10:27:18,442 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,443 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,443 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,445 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,446 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,448 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,449 even if it does not contain any `.py` files. 2023-09-10T10:27:18,450 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,450 directory, all directories are treated like packages. 2023-09-10T10:27:18,451 ******************************************************************************** 2023-09-10T10:27:18,452 !! 2023-09-10T10:27:18,453 check.warn(importable) 2023-09-10T10:27:18,453 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Templates.Css' is absent from the `packages` configuration. 2023-09-10T10:27:18,454 !! 2023-09-10T10:27:18,455 ******************************************************************************** 2023-09-10T10:27:18,455 ############################ 2023-09-10T10:27:18,456 # Package would be ignored # 2023-09-10T10:27:18,456 ############################ 2023-09-10T10:27:18,456 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Css' as an importable package[^1], 2023-09-10T10:27:18,457 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,458 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,458 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Css' is explicitly added 2023-09-10T10:27:18,459 to the `packages` configuration field. 2023-09-10T10:27:18,460 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,461 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,461 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,462 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,463 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,464 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Css' to be distributed and are 2023-09-10T10:27:18,465 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Css' via 2023-09-10T10:27:18,465 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,466 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,466 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,467 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,469 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,470 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,471 even if it does not contain any `.py` files. 2023-09-10T10:27:18,471 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,472 directory, all directories are treated like packages. 2023-09-10T10:27:18,472 ******************************************************************************** 2023-09-10T10:27:18,473 !! 2023-09-10T10:27:18,473 check.warn(importable) 2023-09-10T10:27:18,474 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Templates.Images' is absent from the `packages` configuration. 2023-09-10T10:27:18,474 !! 2023-09-10T10:27:18,475 ******************************************************************************** 2023-09-10T10:27:18,476 ############################ 2023-09-10T10:27:18,476 # Package would be ignored # 2023-09-10T10:27:18,477 ############################ 2023-09-10T10:27:18,478 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Images' as an importable package[^1], 2023-09-10T10:27:18,478 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,480 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,480 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Images' is explicitly added 2023-09-10T10:27:18,480 to the `packages` configuration field. 2023-09-10T10:27:18,481 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,481 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,482 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,483 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,483 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,484 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Images' to be distributed and are 2023-09-10T10:27:18,484 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Images' via 2023-09-10T10:27:18,485 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,485 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,486 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,486 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,487 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,489 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,489 even if it does not contain any `.py` files. 2023-09-10T10:27:18,489 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,490 directory, all directories are treated like packages. 2023-09-10T10:27:18,490 ******************************************************************************** 2023-09-10T10:27:18,491 !! 2023-09-10T10:27:18,492 check.warn(importable) 2023-09-10T10:27:18,492 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Templates.Js' is absent from the `packages` configuration. 2023-09-10T10:27:18,493 !! 2023-09-10T10:27:18,494 ******************************************************************************** 2023-09-10T10:27:18,494 ############################ 2023-09-10T10:27:18,495 # Package would be ignored # 2023-09-10T10:27:18,495 ############################ 2023-09-10T10:27:18,496 Python recognizes 'publiforge.Processors.Publidoc2Html5.Templates.Js' as an importable package[^1], 2023-09-10T10:27:18,496 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,497 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,498 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Templates.Js' is explicitly added 2023-09-10T10:27:18,498 to the `packages` configuration field. 2023-09-10T10:27:18,499 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,500 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,500 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,501 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,502 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,503 If you don't want 'publiforge.Processors.Publidoc2Html5.Templates.Js' to be distributed and are 2023-09-10T10:27:18,504 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Templates.Js' via 2023-09-10T10:27:18,504 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,505 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,505 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,506 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,507 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,509 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,509 even if it does not contain any `.py` files. 2023-09-10T10:27:18,510 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,510 directory, all directories are treated like packages. 2023-09-10T10:27:18,511 ******************************************************************************** 2023-09-10T10:27:18,512 !! 2023-09-10T10:27:18,512 check.warn(importable) 2023-09-10T10:27:18,512 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,513 !! 2023-09-10T10:27:18,513 ******************************************************************************** 2023-09-10T10:27:18,514 ############################ 2023-09-10T10:27:18,514 # Package would be ignored # 2023-09-10T10:27:18,515 ############################ 2023-09-10T10:27:18,515 Python recognizes 'publiforge.Processors.Publidoc2Html5.Variables' as an importable package[^1], 2023-09-10T10:27:18,515 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,516 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,517 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Variables' is explicitly added 2023-09-10T10:27:18,517 to the `packages` configuration field. 2023-09-10T10:27:18,518 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,519 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,519 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,520 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,521 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,522 If you don't want 'publiforge.Processors.Publidoc2Html5.Variables' to be distributed and are 2023-09-10T10:27:18,522 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Variables' via 2023-09-10T10:27:18,523 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,524 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,524 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,525 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,526 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,527 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,528 even if it does not contain any `.py` files. 2023-09-10T10:27:18,529 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,529 directory, all directories are treated like packages. 2023-09-10T10:27:18,530 ******************************************************************************** 2023-09-10T10:27:18,531 !! 2023-09-10T10:27:18,531 check.warn(importable) 2023-09-10T10:27:18,532 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Html5.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,532 !! 2023-09-10T10:27:18,534 ******************************************************************************** 2023-09-10T10:27:18,534 ############################ 2023-09-10T10:27:18,534 # Package would be ignored # 2023-09-10T10:27:18,535 ############################ 2023-09-10T10:27:18,535 Python recognizes 'publiforge.Processors.Publidoc2Html5.Xsl' as an importable package[^1], 2023-09-10T10:27:18,535 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,536 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,537 package, please make sure that 'publiforge.Processors.Publidoc2Html5.Xsl' is explicitly added 2023-09-10T10:27:18,537 to the `packages` configuration field. 2023-09-10T10:27:18,538 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,538 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,539 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,539 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,540 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,541 If you don't want 'publiforge.Processors.Publidoc2Html5.Xsl' to be distributed and are 2023-09-10T10:27:18,541 already explicitly excluding 'publiforge.Processors.Publidoc2Html5.Xsl' via 2023-09-10T10:27:18,542 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,543 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,543 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,544 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,545 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,547 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,547 even if it does not contain any `.py` files. 2023-09-10T10:27:18,548 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,548 directory, all directories are treated like packages. 2023-09-10T10:27:18,549 ******************************************************************************** 2023-09-10T10:27:18,550 !! 2023-09-10T10:27:18,551 check.warn(importable) 2023-09-10T10:27:18,551 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Pdf' is absent from the `packages` configuration. 2023-09-10T10:27:18,552 !! 2023-09-10T10:27:18,553 ******************************************************************************** 2023-09-10T10:27:18,553 ############################ 2023-09-10T10:27:18,554 # Package would be ignored # 2023-09-10T10:27:18,554 ############################ 2023-09-10T10:27:18,554 Python recognizes 'publiforge.Processors.Publidoc2Pdf' as an importable package[^1], 2023-09-10T10:27:18,555 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,556 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,557 package, please make sure that 'publiforge.Processors.Publidoc2Pdf' is explicitly added 2023-09-10T10:27:18,557 to the `packages` configuration field. 2023-09-10T10:27:18,558 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,559 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,559 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,560 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,561 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,561 If you don't want 'publiforge.Processors.Publidoc2Pdf' to be distributed and are 2023-09-10T10:27:18,562 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf' via 2023-09-10T10:27:18,562 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,563 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,563 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,564 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,564 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,565 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,566 even if it does not contain any `.py` files. 2023-09-10T10:27:18,566 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,567 directory, all directories are treated like packages. 2023-09-10T10:27:18,567 ******************************************************************************** 2023-09-10T10:27:18,568 !! 2023-09-10T10:27:18,568 check.warn(importable) 2023-09-10T10:27:18,569 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Pdf.Fonts' is absent from the `packages` configuration. 2023-09-10T10:27:18,569 !! 2023-09-10T10:27:18,570 ******************************************************************************** 2023-09-10T10:27:18,571 ############################ 2023-09-10T10:27:18,571 # Package would be ignored # 2023-09-10T10:27:18,572 ############################ 2023-09-10T10:27:18,572 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Fonts' as an importable package[^1], 2023-09-10T10:27:18,573 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,574 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,574 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Fonts' is explicitly added 2023-09-10T10:27:18,575 to the `packages` configuration field. 2023-09-10T10:27:18,576 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,576 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,577 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,578 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,579 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,580 If you don't want 'publiforge.Processors.Publidoc2Pdf.Fonts' to be distributed and are 2023-09-10T10:27:18,580 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Fonts' via 2023-09-10T10:27:18,581 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,581 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,582 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,583 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,584 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,586 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,587 even if it does not contain any `.py` files. 2023-09-10T10:27:18,587 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,588 directory, all directories are treated like packages. 2023-09-10T10:27:18,588 ******************************************************************************** 2023-09-10T10:27:18,589 !! 2023-09-10T10:27:18,589 check.warn(importable) 2023-09-10T10:27:18,590 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Pdf.Regex' is absent from the `packages` configuration. 2023-09-10T10:27:18,590 !! 2023-09-10T10:27:18,591 ******************************************************************************** 2023-09-10T10:27:18,591 ############################ 2023-09-10T10:27:18,592 # Package would be ignored # 2023-09-10T10:27:18,592 ############################ 2023-09-10T10:27:18,592 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Regex' as an importable package[^1], 2023-09-10T10:27:18,593 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,594 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,594 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Regex' is explicitly added 2023-09-10T10:27:18,594 to the `packages` configuration field. 2023-09-10T10:27:18,595 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,596 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,596 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,597 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,598 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,599 If you don't want 'publiforge.Processors.Publidoc2Pdf.Regex' to be distributed and are 2023-09-10T10:27:18,600 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Regex' via 2023-09-10T10:27:18,600 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,601 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,601 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,602 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,603 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,605 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,605 even if it does not contain any `.py` files. 2023-09-10T10:27:18,606 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,606 directory, all directories are treated like packages. 2023-09-10T10:27:18,607 ******************************************************************************** 2023-09-10T10:27:18,608 !! 2023-09-10T10:27:18,608 check.warn(importable) 2023-09-10T10:27:18,609 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Pdf.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,609 !! 2023-09-10T10:27:18,610 ******************************************************************************** 2023-09-10T10:27:18,611 ############################ 2023-09-10T10:27:18,611 # Package would be ignored # 2023-09-10T10:27:18,612 ############################ 2023-09-10T10:27:18,612 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Variables' as an importable package[^1], 2023-09-10T10:27:18,613 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,614 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,615 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Variables' is explicitly added 2023-09-10T10:27:18,615 to the `packages` configuration field. 2023-09-10T10:27:18,616 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,616 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,616 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,617 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,618 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,619 If you don't want 'publiforge.Processors.Publidoc2Pdf.Variables' to be distributed and are 2023-09-10T10:27:18,619 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Variables' via 2023-09-10T10:27:18,619 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,620 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,620 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,621 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,622 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,623 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,623 even if it does not contain any `.py` files. 2023-09-10T10:27:18,624 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,625 directory, all directories are treated like packages. 2023-09-10T10:27:18,625 ******************************************************************************** 2023-09-10T10:27:18,626 !! 2023-09-10T10:27:18,627 check.warn(importable) 2023-09-10T10:27:18,627 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2Pdf.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,628 !! 2023-09-10T10:27:18,629 ******************************************************************************** 2023-09-10T10:27:18,630 ############################ 2023-09-10T10:27:18,630 # Package would be ignored # 2023-09-10T10:27:18,631 ############################ 2023-09-10T10:27:18,631 Python recognizes 'publiforge.Processors.Publidoc2Pdf.Xsl' as an importable package[^1], 2023-09-10T10:27:18,632 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,632 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,633 package, please make sure that 'publiforge.Processors.Publidoc2Pdf.Xsl' is explicitly added 2023-09-10T10:27:18,633 to the `packages` configuration field. 2023-09-10T10:27:18,634 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,635 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,635 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,636 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,637 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,639 If you don't want 'publiforge.Processors.Publidoc2Pdf.Xsl' to be distributed and are 2023-09-10T10:27:18,639 already explicitly excluding 'publiforge.Processors.Publidoc2Pdf.Xsl' via 2023-09-10T10:27:18,640 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,641 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,641 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,642 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,642 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,643 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,644 even if it does not contain any `.py` files. 2023-09-10T10:27:18,644 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,644 directory, all directories are treated like packages. 2023-09-10T10:27:18,645 ******************************************************************************** 2023-09-10T10:27:18,645 !! 2023-09-10T10:27:18,646 check.warn(importable) 2023-09-10T10:27:18,646 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2XHtml' is absent from the `packages` configuration. 2023-09-10T10:27:18,646 !! 2023-09-10T10:27:18,647 ******************************************************************************** 2023-09-10T10:27:18,648 ############################ 2023-09-10T10:27:18,648 # Package would be ignored # 2023-09-10T10:27:18,649 ############################ 2023-09-10T10:27:18,649 Python recognizes 'publiforge.Processors.Publidoc2XHtml' as an importable package[^1], 2023-09-10T10:27:18,649 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,650 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,651 package, please make sure that 'publiforge.Processors.Publidoc2XHtml' is explicitly added 2023-09-10T10:27:18,651 to the `packages` configuration field. 2023-09-10T10:27:18,652 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,653 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,653 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,655 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,656 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,657 If you don't want 'publiforge.Processors.Publidoc2XHtml' to be distributed and are 2023-09-10T10:27:18,658 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml' via 2023-09-10T10:27:18,658 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,659 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,659 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,660 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,661 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,663 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,663 even if it does not contain any `.py` files. 2023-09-10T10:27:18,664 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,664 directory, all directories are treated like packages. 2023-09-10T10:27:18,665 ******************************************************************************** 2023-09-10T10:27:18,666 !! 2023-09-10T10:27:18,667 check.warn(importable) 2023-09-10T10:27:18,667 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Regex' is absent from the `packages` configuration. 2023-09-10T10:27:18,668 !! 2023-09-10T10:27:18,669 ******************************************************************************** 2023-09-10T10:27:18,669 ############################ 2023-09-10T10:27:18,669 # Package would be ignored # 2023-09-10T10:27:18,670 ############################ 2023-09-10T10:27:18,670 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Regex' as an importable package[^1], 2023-09-10T10:27:18,670 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,671 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,672 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Regex' is explicitly added 2023-09-10T10:27:18,672 to the `packages` configuration field. 2023-09-10T10:27:18,673 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,673 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,673 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,674 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,675 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,676 If you don't want 'publiforge.Processors.Publidoc2XHtml.Regex' to be distributed and are 2023-09-10T10:27:18,676 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Regex' via 2023-09-10T10:27:18,677 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,677 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,678 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,679 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,680 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,681 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,682 even if it does not contain any `.py` files. 2023-09-10T10:27:18,683 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,683 directory, all directories are treated like packages. 2023-09-10T10:27:18,684 ******************************************************************************** 2023-09-10T10:27:18,685 !! 2023-09-10T10:27:18,685 check.warn(importable) 2023-09-10T10:27:18,686 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Scss' is absent from the `packages` configuration. 2023-09-10T10:27:18,686 !! 2023-09-10T10:27:18,687 ******************************************************************************** 2023-09-10T10:27:18,688 ############################ 2023-09-10T10:27:18,688 # Package would be ignored # 2023-09-10T10:27:18,689 ############################ 2023-09-10T10:27:18,689 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Scss' as an importable package[^1], 2023-09-10T10:27:18,690 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,691 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,691 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Scss' is explicitly added 2023-09-10T10:27:18,692 to the `packages` configuration field. 2023-09-10T10:27:18,693 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,693 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,694 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,695 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,696 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,696 If you don't want 'publiforge.Processors.Publidoc2XHtml.Scss' to be distributed and are 2023-09-10T10:27:18,697 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Scss' via 2023-09-10T10:27:18,697 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,697 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,698 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,698 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,699 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,700 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,701 even if it does not contain any `.py` files. 2023-09-10T10:27:18,701 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,701 directory, all directories are treated like packages. 2023-09-10T10:27:18,702 ******************************************************************************** 2023-09-10T10:27:18,703 !! 2023-09-10T10:27:18,703 check.warn(importable) 2023-09-10T10:27:18,703 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Templates.Css' is absent from the `packages` configuration. 2023-09-10T10:27:18,704 !! 2023-09-10T10:27:18,705 ******************************************************************************** 2023-09-10T10:27:18,705 ############################ 2023-09-10T10:27:18,706 # Package would be ignored # 2023-09-10T10:27:18,706 ############################ 2023-09-10T10:27:18,707 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Css' as an importable package[^1], 2023-09-10T10:27:18,707 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,708 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,709 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Css' is explicitly added 2023-09-10T10:27:18,710 to the `packages` configuration field. 2023-09-10T10:27:18,710 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,711 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,711 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,712 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,713 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,714 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Css' to be distributed and are 2023-09-10T10:27:18,715 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Css' via 2023-09-10T10:27:18,715 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,716 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,716 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,717 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,719 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,720 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,720 even if it does not contain any `.py` files. 2023-09-10T10:27:18,720 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,721 directory, all directories are treated like packages. 2023-09-10T10:27:18,721 ******************************************************************************** 2023-09-10T10:27:18,722 !! 2023-09-10T10:27:18,722 check.warn(importable) 2023-09-10T10:27:18,722 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Templates.Images' is absent from the `packages` configuration. 2023-09-10T10:27:18,723 !! 2023-09-10T10:27:18,723 ******************************************************************************** 2023-09-10T10:27:18,724 ############################ 2023-09-10T10:27:18,724 # Package would be ignored # 2023-09-10T10:27:18,724 ############################ 2023-09-10T10:27:18,725 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Images' as an importable package[^1], 2023-09-10T10:27:18,725 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,726 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,727 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Images' is explicitly added 2023-09-10T10:27:18,727 to the `packages` configuration field. 2023-09-10T10:27:18,729 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,729 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,730 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,731 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,732 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,733 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Images' to be distributed and are 2023-09-10T10:27:18,734 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Images' via 2023-09-10T10:27:18,734 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,735 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,735 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,736 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,737 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,739 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,739 even if it does not contain any `.py` files. 2023-09-10T10:27:18,740 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,740 directory, all directories are treated like packages. 2023-09-10T10:27:18,741 ******************************************************************************** 2023-09-10T10:27:18,741 !! 2023-09-10T10:27:18,742 check.warn(importable) 2023-09-10T10:27:18,742 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Templates.Js' is absent from the `packages` configuration. 2023-09-10T10:27:18,743 !! 2023-09-10T10:27:18,744 ******************************************************************************** 2023-09-10T10:27:18,745 ############################ 2023-09-10T10:27:18,745 # Package would be ignored # 2023-09-10T10:27:18,746 ############################ 2023-09-10T10:27:18,746 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Templates.Js' as an importable package[^1], 2023-09-10T10:27:18,747 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,747 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,748 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Templates.Js' is explicitly added 2023-09-10T10:27:18,748 to the `packages` configuration field. 2023-09-10T10:27:18,749 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,749 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,749 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,750 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,751 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,752 If you don't want 'publiforge.Processors.Publidoc2XHtml.Templates.Js' to be distributed and are 2023-09-10T10:27:18,752 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Templates.Js' via 2023-09-10T10:27:18,752 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,753 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,753 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,754 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,755 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,756 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,757 even if it does not contain any `.py` files. 2023-09-10T10:27:18,757 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,758 directory, all directories are treated like packages. 2023-09-10T10:27:18,758 ******************************************************************************** 2023-09-10T10:27:18,759 !! 2023-09-10T10:27:18,760 check.warn(importable) 2023-09-10T10:27:18,760 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,761 !! 2023-09-10T10:27:18,762 ******************************************************************************** 2023-09-10T10:27:18,762 ############################ 2023-09-10T10:27:18,763 # Package would be ignored # 2023-09-10T10:27:18,763 ############################ 2023-09-10T10:27:18,764 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Variables' as an importable package[^1], 2023-09-10T10:27:18,764 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,765 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,765 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Variables' is explicitly added 2023-09-10T10:27:18,766 to the `packages` configuration field. 2023-09-10T10:27:18,767 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,767 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,768 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,769 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,770 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,772 If you don't want 'publiforge.Processors.Publidoc2XHtml.Variables' to be distributed and are 2023-09-10T10:27:18,772 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Variables' via 2023-09-10T10:27:18,772 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,773 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,773 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,774 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,774 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,776 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,776 even if it does not contain any `.py` files. 2023-09-10T10:27:18,776 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,777 directory, all directories are treated like packages. 2023-09-10T10:27:18,777 ******************************************************************************** 2023-09-10T10:27:18,778 !! 2023-09-10T10:27:18,778 check.warn(importable) 2023-09-10T10:27:18,779 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publidoc2XHtml.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,779 !! 2023-09-10T10:27:18,780 ******************************************************************************** 2023-09-10T10:27:18,780 ############################ 2023-09-10T10:27:18,781 # Package would be ignored # 2023-09-10T10:27:18,781 ############################ 2023-09-10T10:27:18,782 Python recognizes 'publiforge.Processors.Publidoc2XHtml.Xsl' as an importable package[^1], 2023-09-10T10:27:18,782 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,783 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,783 package, please make sure that 'publiforge.Processors.Publidoc2XHtml.Xsl' is explicitly added 2023-09-10T10:27:18,784 to the `packages` configuration field. 2023-09-10T10:27:18,785 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,785 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,786 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,787 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,788 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,789 If you don't want 'publiforge.Processors.Publidoc2XHtml.Xsl' to be distributed and are 2023-09-10T10:27:18,789 already explicitly excluding 'publiforge.Processors.Publidoc2XHtml.Xsl' via 2023-09-10T10:27:18,790 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,790 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,791 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,792 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,793 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,794 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,795 even if it does not contain any `.py` files. 2023-09-10T10:27:18,795 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,796 directory, all directories are treated like packages. 2023-09-10T10:27:18,797 ******************************************************************************** 2023-09-10T10:27:18,798 !! 2023-09-10T10:27:18,798 check.warn(importable) 2023-09-10T10:27:18,799 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PublidocClean' is absent from the `packages` configuration. 2023-09-10T10:27:18,799 !! 2023-09-10T10:27:18,800 ******************************************************************************** 2023-09-10T10:27:18,800 ############################ 2023-09-10T10:27:18,801 # Package would be ignored # 2023-09-10T10:27:18,801 ############################ 2023-09-10T10:27:18,801 Python recognizes 'publiforge.Processors.PublidocClean' as an importable package[^1], 2023-09-10T10:27:18,802 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,802 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,803 package, please make sure that 'publiforge.Processors.PublidocClean' is explicitly added 2023-09-10T10:27:18,803 to the `packages` configuration field. 2023-09-10T10:27:18,804 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,804 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,805 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,806 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,806 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,807 If you don't want 'publiforge.Processors.PublidocClean' to be distributed and are 2023-09-10T10:27:18,808 already explicitly excluding 'publiforge.Processors.PublidocClean' via 2023-09-10T10:27:18,808 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,809 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,809 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,810 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,811 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,812 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,813 even if it does not contain any `.py` files. 2023-09-10T10:27:18,813 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,814 directory, all directories are treated like packages. 2023-09-10T10:27:18,814 ******************************************************************************** 2023-09-10T10:27:18,815 !! 2023-09-10T10:27:18,816 check.warn(importable) 2023-09-10T10:27:18,816 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PublidocClean.Regex' is absent from the `packages` configuration. 2023-09-10T10:27:18,816 !! 2023-09-10T10:27:18,817 ******************************************************************************** 2023-09-10T10:27:18,818 ############################ 2023-09-10T10:27:18,818 # Package would be ignored # 2023-09-10T10:27:18,819 ############################ 2023-09-10T10:27:18,820 Python recognizes 'publiforge.Processors.PublidocClean.Regex' as an importable package[^1], 2023-09-10T10:27:18,820 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,821 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,822 package, please make sure that 'publiforge.Processors.PublidocClean.Regex' is explicitly added 2023-09-10T10:27:18,822 to the `packages` configuration field. 2023-09-10T10:27:18,824 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,824 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,824 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,825 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,826 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,826 If you don't want 'publiforge.Processors.PublidocClean.Regex' to be distributed and are 2023-09-10T10:27:18,827 already explicitly excluding 'publiforge.Processors.PublidocClean.Regex' via 2023-09-10T10:27:18,827 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,827 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,828 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,828 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,829 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,830 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,830 even if it does not contain any `.py` files. 2023-09-10T10:27:18,831 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,831 directory, all directories are treated like packages. 2023-09-10T10:27:18,832 ******************************************************************************** 2023-09-10T10:27:18,832 !! 2023-09-10T10:27:18,833 check.warn(importable) 2023-09-10T10:27:18,833 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PublidocClean.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,834 !! 2023-09-10T10:27:18,835 ******************************************************************************** 2023-09-10T10:27:18,836 ############################ 2023-09-10T10:27:18,836 # Package would be ignored # 2023-09-10T10:27:18,837 ############################ 2023-09-10T10:27:18,837 Python recognizes 'publiforge.Processors.PublidocClean.Variables' as an importable package[^1], 2023-09-10T10:27:18,838 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,839 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,839 package, please make sure that 'publiforge.Processors.PublidocClean.Variables' is explicitly added 2023-09-10T10:27:18,840 to the `packages` configuration field. 2023-09-10T10:27:18,840 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,841 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,841 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,842 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,843 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,844 If you don't want 'publiforge.Processors.PublidocClean.Variables' to be distributed and are 2023-09-10T10:27:18,845 already explicitly excluding 'publiforge.Processors.PublidocClean.Variables' via 2023-09-10T10:27:18,845 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,846 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,846 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,847 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,848 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,849 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,849 even if it does not contain any `.py` files. 2023-09-10T10:27:18,850 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,850 directory, all directories are treated like packages. 2023-09-10T10:27:18,850 ******************************************************************************** 2023-09-10T10:27:18,851 !! 2023-09-10T10:27:18,851 check.warn(importable) 2023-09-10T10:27:18,851 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PublidocClean.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,852 !! 2023-09-10T10:27:18,852 ******************************************************************************** 2023-09-10T10:27:18,853 ############################ 2023-09-10T10:27:18,853 # Package would be ignored # 2023-09-10T10:27:18,853 ############################ 2023-09-10T10:27:18,854 Python recognizes 'publiforge.Processors.PublidocClean.Xsl' as an importable package[^1], 2023-09-10T10:27:18,854 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,855 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,855 package, please make sure that 'publiforge.Processors.PublidocClean.Xsl' is explicitly added 2023-09-10T10:27:18,856 to the `packages` configuration field. 2023-09-10T10:27:18,857 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,857 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,858 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,859 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,860 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,861 If you don't want 'publiforge.Processors.PublidocClean.Xsl' to be distributed and are 2023-09-10T10:27:18,861 already explicitly excluding 'publiforge.Processors.PublidocClean.Xsl' via 2023-09-10T10:27:18,862 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,862 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,863 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,864 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,865 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,866 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,867 even if it does not contain any `.py` files. 2023-09-10T10:27:18,867 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,868 directory, all directories are treated like packages. 2023-09-10T10:27:18,868 ******************************************************************************** 2023-09-10T10:27:18,869 !! 2023-09-10T10:27:18,870 check.warn(importable) 2023-09-10T10:27:18,870 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PublidocValid' is absent from the `packages` configuration. 2023-09-10T10:27:18,871 !! 2023-09-10T10:27:18,872 ******************************************************************************** 2023-09-10T10:27:18,872 ############################ 2023-09-10T10:27:18,873 # Package would be ignored # 2023-09-10T10:27:18,873 ############################ 2023-09-10T10:27:18,874 Python recognizes 'publiforge.Processors.PublidocValid' as an importable package[^1], 2023-09-10T10:27:18,874 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,874 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,875 package, please make sure that 'publiforge.Processors.PublidocValid' is explicitly added 2023-09-10T10:27:18,875 to the `packages` configuration field. 2023-09-10T10:27:18,876 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,876 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,876 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,877 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,878 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,878 If you don't want 'publiforge.Processors.PublidocValid' to be distributed and are 2023-09-10T10:27:18,879 already explicitly excluding 'publiforge.Processors.PublidocValid' via 2023-09-10T10:27:18,879 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,880 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,880 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,881 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,882 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,884 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,884 even if it does not contain any `.py` files. 2023-09-10T10:27:18,885 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,885 directory, all directories are treated like packages. 2023-09-10T10:27:18,886 ******************************************************************************** 2023-09-10T10:27:18,887 !! 2023-09-10T10:27:18,887 check.warn(importable) 2023-09-10T10:27:18,888 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.PublidocValid.RelaxNG' is absent from the `packages` configuration. 2023-09-10T10:27:18,889 !! 2023-09-10T10:27:18,890 ******************************************************************************** 2023-09-10T10:27:18,890 ############################ 2023-09-10T10:27:18,890 # Package would be ignored # 2023-09-10T10:27:18,891 ############################ 2023-09-10T10:27:18,891 Python recognizes 'publiforge.Processors.PublidocValid.RelaxNG' as an importable package[^1], 2023-09-10T10:27:18,892 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,893 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,893 package, please make sure that 'publiforge.Processors.PublidocValid.RelaxNG' is explicitly added 2023-09-10T10:27:18,893 to the `packages` configuration field. 2023-09-10T10:27:18,894 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,895 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,896 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,897 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,898 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,899 If you don't want 'publiforge.Processors.PublidocValid.RelaxNG' to be distributed and are 2023-09-10T10:27:18,899 already explicitly excluding 'publiforge.Processors.PublidocValid.RelaxNG' via 2023-09-10T10:27:18,899 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,900 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,900 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,901 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,901 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,902 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,903 even if it does not contain any `.py` files. 2023-09-10T10:27:18,903 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,903 directory, all directories are treated like packages. 2023-09-10T10:27:18,904 ******************************************************************************** 2023-09-10T10:27:18,904 !! 2023-09-10T10:27:18,905 check.warn(importable) 2023-09-10T10:27:18,905 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2EPub3' is absent from the `packages` configuration. 2023-09-10T10:27:18,905 !! 2023-09-10T10:27:18,906 ******************************************************************************** 2023-09-10T10:27:18,907 ############################ 2023-09-10T10:27:18,907 # Package would be ignored # 2023-09-10T10:27:18,908 ############################ 2023-09-10T10:27:18,908 Python recognizes 'publiforge.Processors.Publiquiz2EPub3' as an importable package[^1], 2023-09-10T10:27:18,909 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,910 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,910 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3' is explicitly added 2023-09-10T10:27:18,911 to the `packages` configuration field. 2023-09-10T10:27:18,912 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,912 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,913 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,914 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,915 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,916 If you don't want 'publiforge.Processors.Publiquiz2EPub3' to be distributed and are 2023-09-10T10:27:18,916 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3' via 2023-09-10T10:27:18,917 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,917 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,918 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,919 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,920 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,921 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,922 even if it does not contain any `.py` files. 2023-09-10T10:27:18,922 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,923 directory, all directories are treated like packages. 2023-09-10T10:27:18,924 ******************************************************************************** 2023-09-10T10:27:18,924 !! 2023-09-10T10:27:18,925 check.warn(importable) 2023-09-10T10:27:18,925 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2EPub3.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:18,925 !! 2023-09-10T10:27:18,926 ******************************************************************************** 2023-09-10T10:27:18,926 ############################ 2023-09-10T10:27:18,927 # Package would be ignored # 2023-09-10T10:27:18,927 ############################ 2023-09-10T10:27:18,927 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Variables' as an importable package[^1], 2023-09-10T10:27:18,928 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,929 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,929 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Variables' is explicitly added 2023-09-10T10:27:18,929 to the `packages` configuration field. 2023-09-10T10:27:18,930 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,930 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,931 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,931 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,933 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,934 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Variables' to be distributed and are 2023-09-10T10:27:18,934 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Variables' via 2023-09-10T10:27:18,935 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,936 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,936 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,937 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,939 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,940 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,941 even if it does not contain any `.py` files. 2023-09-10T10:27:18,941 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,942 directory, all directories are treated like packages. 2023-09-10T10:27:18,942 ******************************************************************************** 2023-09-10T10:27:18,948 !! 2023-09-10T10:27:18,948 check.warn(importable) 2023-09-10T10:27:18,949 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2EPub3.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:18,949 !! 2023-09-10T10:27:18,950 ******************************************************************************** 2023-09-10T10:27:18,951 ############################ 2023-09-10T10:27:18,951 # Package would be ignored # 2023-09-10T10:27:18,952 ############################ 2023-09-10T10:27:18,952 Python recognizes 'publiforge.Processors.Publiquiz2EPub3.Xsl' as an importable package[^1], 2023-09-10T10:27:18,953 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,954 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,954 package, please make sure that 'publiforge.Processors.Publiquiz2EPub3.Xsl' is explicitly added 2023-09-10T10:27:18,955 to the `packages` configuration field. 2023-09-10T10:27:18,956 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,956 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,957 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,957 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,958 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,958 If you don't want 'publiforge.Processors.Publiquiz2EPub3.Xsl' to be distributed and are 2023-09-10T10:27:18,959 already explicitly excluding 'publiforge.Processors.Publiquiz2EPub3.Xsl' via 2023-09-10T10:27:18,959 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,960 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,960 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,961 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,961 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,962 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,963 even if it does not contain any `.py` files. 2023-09-10T10:27:18,963 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,964 directory, all directories are treated like packages. 2023-09-10T10:27:18,964 ******************************************************************************** 2023-09-10T10:27:18,965 !! 2023-09-10T10:27:18,966 check.warn(importable) 2023-09-10T10:27:18,966 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5' is absent from the `packages` configuration. 2023-09-10T10:27:18,967 !! 2023-09-10T10:27:18,968 ******************************************************************************** 2023-09-10T10:27:18,968 ############################ 2023-09-10T10:27:18,969 # Package would be ignored # 2023-09-10T10:27:18,970 ############################ 2023-09-10T10:27:18,970 Python recognizes 'publiforge.Processors.Publiquiz2Html5' as an importable package[^1], 2023-09-10T10:27:18,971 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,972 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,972 package, please make sure that 'publiforge.Processors.Publiquiz2Html5' is explicitly added 2023-09-10T10:27:18,972 to the `packages` configuration field. 2023-09-10T10:27:18,973 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,974 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,974 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,975 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,976 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,977 If you don't want 'publiforge.Processors.Publiquiz2Html5' to be distributed and are 2023-09-10T10:27:18,978 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5' via 2023-09-10T10:27:18,978 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,978 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,979 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,980 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,981 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:18,982 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:18,982 even if it does not contain any `.py` files. 2023-09-10T10:27:18,982 On the other hand, currently there is no concept of package data 2023-09-10T10:27:18,983 directory, all directories are treated like packages. 2023-09-10T10:27:18,983 ******************************************************************************** 2023-09-10T10:27:18,984 !! 2023-09-10T10:27:18,984 check.warn(importable) 2023-09-10T10:27:18,984 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Scss' is absent from the `packages` configuration. 2023-09-10T10:27:18,985 !! 2023-09-10T10:27:18,986 ******************************************************************************** 2023-09-10T10:27:18,986 ############################ 2023-09-10T10:27:18,986 # Package would be ignored # 2023-09-10T10:27:18,987 ############################ 2023-09-10T10:27:18,987 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Scss' as an importable package[^1], 2023-09-10T10:27:18,987 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:18,988 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:18,989 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Scss' is explicitly added 2023-09-10T10:27:18,989 to the `packages` configuration field. 2023-09-10T10:27:18,990 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:18,991 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:18,991 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:18,992 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:18,993 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:18,995 If you don't want 'publiforge.Processors.Publiquiz2Html5.Scss' to be distributed and are 2023-09-10T10:27:18,995 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Scss' via 2023-09-10T10:27:18,996 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:18,996 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:18,997 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:18,997 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:18,998 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,000 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,000 even if it does not contain any `.py` files. 2023-09-10T10:27:19,001 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,001 directory, all directories are treated like packages. 2023-09-10T10:27:19,002 ******************************************************************************** 2023-09-10T10:27:19,003 !! 2023-09-10T10:27:19,003 check.warn(importable) 2023-09-10T10:27:19,004 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' is absent from the `packages` configuration. 2023-09-10T10:27:19,004 !! 2023-09-10T10:27:19,006 ******************************************************************************** 2023-09-10T10:27:19,006 ############################ 2023-09-10T10:27:19,006 # Package would be ignored # 2023-09-10T10:27:19,007 ############################ 2023-09-10T10:27:19,007 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' as an importable package[^1], 2023-09-10T10:27:19,007 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,008 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,009 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' is explicitly added 2023-09-10T10:27:19,009 to the `packages` configuration field. 2023-09-10T10:27:19,010 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,010 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,011 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,012 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,012 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,013 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' to be distributed and are 2023-09-10T10:27:19,013 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Audios' via 2023-09-10T10:27:19,014 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,014 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,015 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,016 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,017 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,018 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,019 even if it does not contain any `.py` files. 2023-09-10T10:27:19,020 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,020 directory, all directories are treated like packages. 2023-09-10T10:27:19,021 ******************************************************************************** 2023-09-10T10:27:19,022 !! 2023-09-10T10:27:19,022 check.warn(importable) 2023-09-10T10:27:19,023 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Css' is absent from the `packages` configuration. 2023-09-10T10:27:19,023 !! 2023-09-10T10:27:19,024 ******************************************************************************** 2023-09-10T10:27:19,025 ############################ 2023-09-10T10:27:19,025 # Package would be ignored # 2023-09-10T10:27:19,026 ############################ 2023-09-10T10:27:19,026 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Css' as an importable package[^1], 2023-09-10T10:27:19,026 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,027 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,028 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Css' is explicitly added 2023-09-10T10:27:19,028 to the `packages` configuration field. 2023-09-10T10:27:19,030 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,030 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,031 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,032 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,032 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,033 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Css' to be distributed and are 2023-09-10T10:27:19,033 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Css' via 2023-09-10T10:27:19,034 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,034 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,034 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,035 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,036 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,037 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,037 even if it does not contain any `.py` files. 2023-09-10T10:27:19,037 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,038 directory, all directories are treated like packages. 2023-09-10T10:27:19,038 ******************************************************************************** 2023-09-10T10:27:19,039 !! 2023-09-10T10:27:19,039 check.warn(importable) 2023-09-10T10:27:19,040 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' is absent from the `packages` configuration. 2023-09-10T10:27:19,040 !! 2023-09-10T10:27:19,041 ******************************************************************************** 2023-09-10T10:27:19,041 ############################ 2023-09-10T10:27:19,042 # Package would be ignored # 2023-09-10T10:27:19,042 ############################ 2023-09-10T10:27:19,043 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' as an importable package[^1], 2023-09-10T10:27:19,044 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,045 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,045 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' is explicitly added 2023-09-10T10:27:19,046 to the `packages` configuration field. 2023-09-10T10:27:19,047 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,047 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,048 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,049 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,049 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,050 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' to be distributed and are 2023-09-10T10:27:19,051 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Fonts' via 2023-09-10T10:27:19,051 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,052 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,052 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,053 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,055 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,056 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,056 even if it does not contain any `.py` files. 2023-09-10T10:27:19,057 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,057 directory, all directories are treated like packages. 2023-09-10T10:27:19,057 ******************************************************************************** 2023-09-10T10:27:19,058 !! 2023-09-10T10:27:19,058 check.warn(importable) 2023-09-10T10:27:19,059 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Images' is absent from the `packages` configuration. 2023-09-10T10:27:19,059 !! 2023-09-10T10:27:19,060 ******************************************************************************** 2023-09-10T10:27:19,060 ############################ 2023-09-10T10:27:19,060 # Package would be ignored # 2023-09-10T10:27:19,061 ############################ 2023-09-10T10:27:19,061 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Images' as an importable package[^1], 2023-09-10T10:27:19,061 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,062 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,062 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Images' is explicitly added 2023-09-10T10:27:19,063 to the `packages` configuration field. 2023-09-10T10:27:19,064 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,064 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,064 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,065 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,067 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,068 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Images' to be distributed and are 2023-09-10T10:27:19,068 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Images' via 2023-09-10T10:27:19,069 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,069 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,070 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,071 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,072 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,073 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,074 even if it does not contain any `.py` files. 2023-09-10T10:27:19,074 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,075 directory, all directories are treated like packages. 2023-09-10T10:27:19,075 ******************************************************************************** 2023-09-10T10:27:19,076 !! 2023-09-10T10:27:19,076 check.warn(importable) 2023-09-10T10:27:19,077 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Templates.Js' is absent from the `packages` configuration. 2023-09-10T10:27:19,078 !! 2023-09-10T10:27:19,079 ******************************************************************************** 2023-09-10T10:27:19,079 ############################ 2023-09-10T10:27:19,080 # Package would be ignored # 2023-09-10T10:27:19,081 ############################ 2023-09-10T10:27:19,081 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Templates.Js' as an importable package[^1], 2023-09-10T10:27:19,082 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,082 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,083 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Templates.Js' is explicitly added 2023-09-10T10:27:19,083 to the `packages` configuration field. 2023-09-10T10:27:19,084 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,084 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,084 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,085 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,086 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,086 If you don't want 'publiforge.Processors.Publiquiz2Html5.Templates.Js' to be distributed and are 2023-09-10T10:27:19,087 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Templates.Js' via 2023-09-10T10:27:19,087 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,088 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,088 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,089 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,089 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,091 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,091 even if it does not contain any `.py` files. 2023-09-10T10:27:19,092 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,092 directory, all directories are treated like packages. 2023-09-10T10:27:19,092 ******************************************************************************** 2023-09-10T10:27:19,094 !! 2023-09-10T10:27:19,094 check.warn(importable) 2023-09-10T10:27:19,095 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:19,095 !! 2023-09-10T10:27:19,096 ******************************************************************************** 2023-09-10T10:27:19,097 ############################ 2023-09-10T10:27:19,097 # Package would be ignored # 2023-09-10T10:27:19,098 ############################ 2023-09-10T10:27:19,098 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Variables' as an importable package[^1], 2023-09-10T10:27:19,099 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,100 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,100 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Variables' is explicitly added 2023-09-10T10:27:19,100 to the `packages` configuration field. 2023-09-10T10:27:19,101 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,102 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,102 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,103 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,104 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,106 If you don't want 'publiforge.Processors.Publiquiz2Html5.Variables' to be distributed and are 2023-09-10T10:27:19,106 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Variables' via 2023-09-10T10:27:19,106 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,107 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,107 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,108 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,108 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,109 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,110 even if it does not contain any `.py` files. 2023-09-10T10:27:19,110 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,110 directory, all directories are treated like packages. 2023-09-10T10:27:19,111 ******************************************************************************** 2023-09-10T10:27:19,112 !! 2023-09-10T10:27:19,112 check.warn(importable) 2023-09-10T10:27:19,112 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Html5.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:19,113 !! 2023-09-10T10:27:19,114 ******************************************************************************** 2023-09-10T10:27:19,114 ############################ 2023-09-10T10:27:19,114 # Package would be ignored # 2023-09-10T10:27:19,115 ############################ 2023-09-10T10:27:19,115 Python recognizes 'publiforge.Processors.Publiquiz2Html5.Xsl' as an importable package[^1], 2023-09-10T10:27:19,116 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,117 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,117 package, please make sure that 'publiforge.Processors.Publiquiz2Html5.Xsl' is explicitly added 2023-09-10T10:27:19,118 to the `packages` configuration field. 2023-09-10T10:27:19,119 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,119 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,120 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,121 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,122 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,123 If you don't want 'publiforge.Processors.Publiquiz2Html5.Xsl' to be distributed and are 2023-09-10T10:27:19,123 already explicitly excluding 'publiforge.Processors.Publiquiz2Html5.Xsl' via 2023-09-10T10:27:19,124 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,124 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,125 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,126 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,127 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,128 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,129 even if it does not contain any `.py` files. 2023-09-10T10:27:19,129 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,130 directory, all directories are treated like packages. 2023-09-10T10:27:19,131 ******************************************************************************** 2023-09-10T10:27:19,131 !! 2023-09-10T10:27:19,132 check.warn(importable) 2023-09-10T10:27:19,132 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12' is absent from the `packages` configuration. 2023-09-10T10:27:19,132 !! 2023-09-10T10:27:19,133 ******************************************************************************** 2023-09-10T10:27:19,134 ############################ 2023-09-10T10:27:19,134 # Package would be ignored # 2023-09-10T10:27:19,134 ############################ 2023-09-10T10:27:19,135 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12' as an importable package[^1], 2023-09-10T10:27:19,135 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,136 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,136 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12' is explicitly added 2023-09-10T10:27:19,136 to the `packages` configuration field. 2023-09-10T10:27:19,137 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,138 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,138 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,139 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,140 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,141 If you don't want 'publiforge.Processors.Publiquiz2Scorm12' to be distributed and are 2023-09-10T10:27:19,141 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12' via 2023-09-10T10:27:19,142 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,142 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,143 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,144 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,145 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,147 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,147 even if it does not contain any `.py` files. 2023-09-10T10:27:19,148 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,149 directory, all directories are treated like packages. 2023-09-10T10:27:19,149 ******************************************************************************** 2023-09-10T10:27:19,150 !! 2023-09-10T10:27:19,150 check.warn(importable) 2023-09-10T10:27:19,151 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Templates' is absent from the `packages` configuration. 2023-09-10T10:27:19,151 !! 2023-09-10T10:27:19,152 ******************************************************************************** 2023-09-10T10:27:19,153 ############################ 2023-09-10T10:27:19,153 # Package would be ignored # 2023-09-10T10:27:19,154 ############################ 2023-09-10T10:27:19,154 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates' as an importable package[^1], 2023-09-10T10:27:19,155 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,156 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,156 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates' is explicitly added 2023-09-10T10:27:19,157 to the `packages` configuration field. 2023-09-10T10:27:19,158 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,159 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,159 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,160 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,160 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,161 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates' to be distributed and are 2023-09-10T10:27:19,161 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates' via 2023-09-10T10:27:19,162 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,162 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,163 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,163 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,164 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,165 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,165 even if it does not contain any `.py` files. 2023-09-10T10:27:19,166 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,166 directory, all directories are treated like packages. 2023-09-10T10:27:19,167 ******************************************************************************** 2023-09-10T10:27:19,168 !! 2023-09-10T10:27:19,168 check.warn(importable) 2023-09-10T10:27:19,169 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' is absent from the `packages` configuration. 2023-09-10T10:27:19,169 !! 2023-09-10T10:27:19,170 ******************************************************************************** 2023-09-10T10:27:19,171 ############################ 2023-09-10T10:27:19,171 # Package would be ignored # 2023-09-10T10:27:19,172 ############################ 2023-09-10T10:27:19,172 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' as an importable package[^1], 2023-09-10T10:27:19,173 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,174 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,174 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' is explicitly added 2023-09-10T10:27:19,175 to the `packages` configuration field. 2023-09-10T10:27:19,176 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,176 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,177 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,178 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,179 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,180 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' to be distributed and are 2023-09-10T10:27:19,180 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Css' via 2023-09-10T10:27:19,181 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,182 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,182 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,183 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,184 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,185 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,185 even if it does not contain any `.py` files. 2023-09-10T10:27:19,185 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,186 directory, all directories are treated like packages. 2023-09-10T10:27:19,186 ******************************************************************************** 2023-09-10T10:27:19,187 !! 2023-09-10T10:27:19,187 check.warn(importable) 2023-09-10T10:27:19,187 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' is absent from the `packages` configuration. 2023-09-10T10:27:19,188 !! 2023-09-10T10:27:19,188 ******************************************************************************** 2023-09-10T10:27:19,189 ############################ 2023-09-10T10:27:19,189 # Package would be ignored # 2023-09-10T10:27:19,189 ############################ 2023-09-10T10:27:19,190 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' as an importable package[^1], 2023-09-10T10:27:19,190 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,191 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,191 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' is explicitly added 2023-09-10T10:27:19,192 to the `packages` configuration field. 2023-09-10T10:27:19,193 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,193 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,194 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,194 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,196 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,197 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' to be distributed and are 2023-09-10T10:27:19,197 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Images' via 2023-09-10T10:27:19,198 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,198 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,199 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,200 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,200 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,202 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,202 even if it does not contain any `.py` files. 2023-09-10T10:27:19,203 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,203 directory, all directories are treated like packages. 2023-09-10T10:27:19,204 ******************************************************************************** 2023-09-10T10:27:19,205 !! 2023-09-10T10:27:19,205 check.warn(importable) 2023-09-10T10:27:19,206 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' is absent from the `packages` configuration. 2023-09-10T10:27:19,207 !! 2023-09-10T10:27:19,208 ******************************************************************************** 2023-09-10T10:27:19,208 ############################ 2023-09-10T10:27:19,208 # Package would be ignored # 2023-09-10T10:27:19,209 ############################ 2023-09-10T10:27:19,209 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' as an importable package[^1], 2023-09-10T10:27:19,209 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,210 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,211 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' is explicitly added 2023-09-10T10:27:19,211 to the `packages` configuration field. 2023-09-10T10:27:19,212 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,212 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,212 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,213 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,214 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,215 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' to be distributed and are 2023-09-10T10:27:19,216 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Templates.Content.Js' via 2023-09-10T10:27:19,216 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,216 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,217 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,218 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,219 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,221 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,222 even if it does not contain any `.py` files. 2023-09-10T10:27:19,222 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,223 directory, all directories are treated like packages. 2023-09-10T10:27:19,224 ******************************************************************************** 2023-09-10T10:27:19,225 !! 2023-09-10T10:27:19,225 check.warn(importable) 2023-09-10T10:27:19,226 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:19,226 !! 2023-09-10T10:27:19,227 ******************************************************************************** 2023-09-10T10:27:19,228 ############################ 2023-09-10T10:27:19,228 # Package would be ignored # 2023-09-10T10:27:19,229 ############################ 2023-09-10T10:27:19,229 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Variables' as an importable package[^1], 2023-09-10T10:27:19,230 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,231 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,231 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Variables' is explicitly added 2023-09-10T10:27:19,232 to the `packages` configuration field. 2023-09-10T10:27:19,233 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,234 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,234 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,235 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,235 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,236 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Variables' to be distributed and are 2023-09-10T10:27:19,236 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Variables' via 2023-09-10T10:27:19,237 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,237 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,237 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,238 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,239 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,240 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,241 even if it does not contain any `.py` files. 2023-09-10T10:27:19,241 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,241 directory, all directories are treated like packages. 2023-09-10T10:27:19,242 ******************************************************************************** 2023-09-10T10:27:19,243 !! 2023-09-10T10:27:19,243 check.warn(importable) 2023-09-10T10:27:19,243 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm12.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:19,244 !! 2023-09-10T10:27:19,245 ******************************************************************************** 2023-09-10T10:27:19,245 ############################ 2023-09-10T10:27:19,245 # Package would be ignored # 2023-09-10T10:27:19,246 ############################ 2023-09-10T10:27:19,246 Python recognizes 'publiforge.Processors.Publiquiz2Scorm12.Xsl' as an importable package[^1], 2023-09-10T10:27:19,247 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,248 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,248 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm12.Xsl' is explicitly added 2023-09-10T10:27:19,249 to the `packages` configuration field. 2023-09-10T10:27:19,250 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,250 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,251 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,252 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,253 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,254 If you don't want 'publiforge.Processors.Publiquiz2Scorm12.Xsl' to be distributed and are 2023-09-10T10:27:19,254 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm12.Xsl' via 2023-09-10T10:27:19,254 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,255 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,256 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,257 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,258 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,259 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,260 even if it does not contain any `.py` files. 2023-09-10T10:27:19,260 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,260 directory, all directories are treated like packages. 2023-09-10T10:27:19,261 ******************************************************************************** 2023-09-10T10:27:19,261 !! 2023-09-10T10:27:19,262 check.warn(importable) 2023-09-10T10:27:19,262 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004' is absent from the `packages` configuration. 2023-09-10T10:27:19,262 !! 2023-09-10T10:27:19,263 ******************************************************************************** 2023-09-10T10:27:19,263 ############################ 2023-09-10T10:27:19,264 # Package would be ignored # 2023-09-10T10:27:19,264 ############################ 2023-09-10T10:27:19,264 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004' as an importable package[^1], 2023-09-10T10:27:19,265 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,265 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,266 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004' is explicitly added 2023-09-10T10:27:19,266 to the `packages` configuration field. 2023-09-10T10:27:19,267 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,268 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,268 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,269 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,271 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,272 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004' to be distributed and are 2023-09-10T10:27:19,272 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004' via 2023-09-10T10:27:19,273 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,273 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,274 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,275 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,276 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,277 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,277 even if it does not contain any `.py` files. 2023-09-10T10:27:19,278 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,278 directory, all directories are treated like packages. 2023-09-10T10:27:19,279 ******************************************************************************** 2023-09-10T10:27:19,280 !! 2023-09-10T10:27:19,280 check.warn(importable) 2023-09-10T10:27:19,281 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates' is absent from the `packages` configuration. 2023-09-10T10:27:19,281 !! 2023-09-10T10:27:19,282 ******************************************************************************** 2023-09-10T10:27:19,283 ############################ 2023-09-10T10:27:19,283 # Package would be ignored # 2023-09-10T10:27:19,284 ############################ 2023-09-10T10:27:19,285 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates' as an importable package[^1], 2023-09-10T10:27:19,285 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,286 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,286 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates' is explicitly added 2023-09-10T10:27:19,287 to the `packages` configuration field. 2023-09-10T10:27:19,288 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,288 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,288 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,289 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,290 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,291 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates' to be distributed and are 2023-09-10T10:27:19,291 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates' via 2023-09-10T10:27:19,292 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,292 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,292 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,293 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,294 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,295 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,297 even if it does not contain any `.py` files. 2023-09-10T10:27:19,297 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,298 directory, all directories are treated like packages. 2023-09-10T10:27:19,298 ******************************************************************************** 2023-09-10T10:27:19,299 !! 2023-09-10T10:27:19,300 check.warn(importable) 2023-09-10T10:27:19,300 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' is absent from the `packages` configuration. 2023-09-10T10:27:19,300 !! 2023-09-10T10:27:19,301 ******************************************************************************** 2023-09-10T10:27:19,302 ############################ 2023-09-10T10:27:19,302 # Package would be ignored # 2023-09-10T10:27:19,303 ############################ 2023-09-10T10:27:19,303 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' as an importable package[^1], 2023-09-10T10:27:19,303 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,304 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,305 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' is explicitly added 2023-09-10T10:27:19,305 to the `packages` configuration field. 2023-09-10T10:27:19,306 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,307 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,307 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,308 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,309 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,310 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' to be distributed and are 2023-09-10T10:27:19,310 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Css' via 2023-09-10T10:27:19,310 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,311 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,311 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,312 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,313 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,314 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,314 even if it does not contain any `.py` files. 2023-09-10T10:27:19,314 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,315 directory, all directories are treated like packages. 2023-09-10T10:27:19,315 ******************************************************************************** 2023-09-10T10:27:19,316 !! 2023-09-10T10:27:19,316 check.warn(importable) 2023-09-10T10:27:19,316 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' is absent from the `packages` configuration. 2023-09-10T10:27:19,317 !! 2023-09-10T10:27:19,318 ******************************************************************************** 2023-09-10T10:27:19,318 ############################ 2023-09-10T10:27:19,319 # Package would be ignored # 2023-09-10T10:27:19,319 ############################ 2023-09-10T10:27:19,319 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' as an importable package[^1], 2023-09-10T10:27:19,320 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,321 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,321 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' is explicitly added 2023-09-10T10:27:19,322 to the `packages` configuration field. 2023-09-10T10:27:19,323 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,323 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,324 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,325 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,326 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,327 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' to be distributed and are 2023-09-10T10:27:19,327 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.Content.Js' via 2023-09-10T10:27:19,328 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,328 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,329 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,330 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,331 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,333 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,333 even if it does not contain any `.py` files. 2023-09-10T10:27:19,334 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,334 directory, all directories are treated like packages. 2023-09-10T10:27:19,335 ******************************************************************************** 2023-09-10T10:27:19,335 !! 2023-09-10T10:27:19,336 check.warn(importable) 2023-09-10T10:27:19,336 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' is absent from the `packages` configuration. 2023-09-10T10:27:19,336 !! 2023-09-10T10:27:19,337 ******************************************************************************** 2023-09-10T10:27:19,338 ############################ 2023-09-10T10:27:19,338 # Package would be ignored # 2023-09-10T10:27:19,338 ############################ 2023-09-10T10:27:19,339 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' as an importable package[^1], 2023-09-10T10:27:19,339 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,340 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,341 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' is explicitly added 2023-09-10T10:27:19,341 to the `packages` configuration field. 2023-09-10T10:27:19,342 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,342 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,343 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,343 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,344 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,345 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' to be distributed and are 2023-09-10T10:27:19,346 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.common' via 2023-09-10T10:27:19,347 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,347 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,348 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,349 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,350 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,351 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,352 even if it does not contain any `.py` files. 2023-09-10T10:27:19,353 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,353 directory, all directories are treated like packages. 2023-09-10T10:27:19,354 ******************************************************************************** 2023-09-10T10:27:19,355 !! 2023-09-10T10:27:19,355 check.warn(importable) 2023-09-10T10:27:19,356 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' is absent from the `packages` configuration. 2023-09-10T10:27:19,356 !! 2023-09-10T10:27:19,357 ******************************************************************************** 2023-09-10T10:27:19,358 ############################ 2023-09-10T10:27:19,359 # Package would be ignored # 2023-09-10T10:27:19,359 ############################ 2023-09-10T10:27:19,360 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' as an importable package[^1], 2023-09-10T10:27:19,361 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,362 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,362 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' is explicitly added 2023-09-10T10:27:19,363 to the `packages` configuration field. 2023-09-10T10:27:19,363 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,364 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,364 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,365 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,366 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,367 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' to be distributed and are 2023-09-10T10:27:19,367 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.extend' via 2023-09-10T10:27:19,368 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,368 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,369 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,369 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,370 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,371 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,372 even if it does not contain any `.py` files. 2023-09-10T10:27:19,372 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,373 directory, all directories are treated like packages. 2023-09-10T10:27:19,373 ******************************************************************************** 2023-09-10T10:27:19,374 !! 2023-09-10T10:27:19,375 check.warn(importable) 2023-09-10T10:27:19,375 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' is absent from the `packages` configuration. 2023-09-10T10:27:19,375 !! 2023-09-10T10:27:19,376 ******************************************************************************** 2023-09-10T10:27:19,377 ############################ 2023-09-10T10:27:19,377 # Package would be ignored # 2023-09-10T10:27:19,378 ############################ 2023-09-10T10:27:19,378 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' as an importable package[^1], 2023-09-10T10:27:19,378 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,379 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,380 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' is explicitly added 2023-09-10T10:27:19,380 to the `packages` configuration field. 2023-09-10T10:27:19,381 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,382 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,382 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,384 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,385 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,386 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' to be distributed and are 2023-09-10T10:27:19,386 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.unique' via 2023-09-10T10:27:19,387 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,387 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,388 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,388 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,389 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,390 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,391 even if it does not contain any `.py` files. 2023-09-10T10:27:19,391 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,391 directory, all directories are treated like packages. 2023-09-10T10:27:19,392 ******************************************************************************** 2023-09-10T10:27:19,392 !! 2023-09-10T10:27:19,393 check.warn(importable) 2023-09-10T10:27:19,393 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' is absent from the `packages` configuration. 2023-09-10T10:27:19,394 !! 2023-09-10T10:27:19,394 ******************************************************************************** 2023-09-10T10:27:19,395 ############################ 2023-09-10T10:27:19,395 # Package would be ignored # 2023-09-10T10:27:19,396 ############################ 2023-09-10T10:27:19,396 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' as an importable package[^1], 2023-09-10T10:27:19,397 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,398 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,398 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' is explicitly added 2023-09-10T10:27:19,399 to the `packages` configuration field. 2023-09-10T10:27:19,400 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,401 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,401 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,402 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,403 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,404 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' to be distributed and are 2023-09-10T10:27:19,405 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Templates.vocab' via 2023-09-10T10:27:19,405 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,406 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,406 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,407 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,408 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,410 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,410 even if it does not contain any `.py` files. 2023-09-10T10:27:19,411 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,412 directory, all directories are treated like packages. 2023-09-10T10:27:19,413 ******************************************************************************** 2023-09-10T10:27:19,413 !! 2023-09-10T10:27:19,414 check.warn(importable) 2023-09-10T10:27:19,414 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:19,414 !! 2023-09-10T10:27:19,415 ******************************************************************************** 2023-09-10T10:27:19,415 ############################ 2023-09-10T10:27:19,416 # Package would be ignored # 2023-09-10T10:27:19,416 ############################ 2023-09-10T10:27:19,417 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Variables' as an importable package[^1], 2023-09-10T10:27:19,417 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,418 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,418 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Variables' is explicitly added 2023-09-10T10:27:19,419 to the `packages` configuration field. 2023-09-10T10:27:19,420 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,420 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,420 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,421 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,422 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,423 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Variables' to be distributed and are 2023-09-10T10:27:19,424 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Variables' via 2023-09-10T10:27:19,424 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,425 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,425 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,427 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,428 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,429 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,430 even if it does not contain any `.py` files. 2023-09-10T10:27:19,430 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,430 directory, all directories are treated like packages. 2023-09-10T10:27:19,431 ******************************************************************************** 2023-09-10T10:27:19,432 !! 2023-09-10T10:27:19,432 check.warn(importable) 2023-09-10T10:27:19,433 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:19,433 !! 2023-09-10T10:27:19,434 ******************************************************************************** 2023-09-10T10:27:19,435 ############################ 2023-09-10T10:27:19,435 # Package would be ignored # 2023-09-10T10:27:19,436 ############################ 2023-09-10T10:27:19,436 Python recognizes 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' as an importable package[^1], 2023-09-10T10:27:19,437 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,438 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,438 package, please make sure that 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' is explicitly added 2023-09-10T10:27:19,439 to the `packages` configuration field. 2023-09-10T10:27:19,439 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,440 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,440 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,441 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,442 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,442 If you don't want 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' to be distributed and are 2023-09-10T10:27:19,443 already explicitly excluding 'publiforge.Processors.Publiquiz2Scorm2004.Xsl' via 2023-09-10T10:27:19,443 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,443 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,444 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,445 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,445 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,447 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,447 even if it does not contain any `.py` files. 2023-09-10T10:27:19,448 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,448 directory, all directories are treated like packages. 2023-09-10T10:27:19,448 ******************************************************************************** 2023-09-10T10:27:19,449 !! 2023-09-10T10:27:19,450 check.warn(importable) 2023-09-10T10:27:19,450 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiset2Publidoc' is absent from the `packages` configuration. 2023-09-10T10:27:19,450 !! 2023-09-10T10:27:19,452 ******************************************************************************** 2023-09-10T10:27:19,452 ############################ 2023-09-10T10:27:19,453 # Package would be ignored # 2023-09-10T10:27:19,453 ############################ 2023-09-10T10:27:19,454 Python recognizes 'publiforge.Processors.Publiset2Publidoc' as an importable package[^1], 2023-09-10T10:27:19,454 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,455 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,456 package, please make sure that 'publiforge.Processors.Publiset2Publidoc' is explicitly added 2023-09-10T10:27:19,456 to the `packages` configuration field. 2023-09-10T10:27:19,457 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,458 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,458 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,459 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,460 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,461 If you don't want 'publiforge.Processors.Publiset2Publidoc' to be distributed and are 2023-09-10T10:27:19,461 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc' via 2023-09-10T10:27:19,462 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,462 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,463 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,464 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,465 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,466 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,466 even if it does not contain any `.py` files. 2023-09-10T10:27:19,466 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,467 directory, all directories are treated like packages. 2023-09-10T10:27:19,467 ******************************************************************************** 2023-09-10T10:27:19,468 !! 2023-09-10T10:27:19,468 check.warn(importable) 2023-09-10T10:27:19,468 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiset2Publidoc.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:19,469 !! 2023-09-10T10:27:19,469 ******************************************************************************** 2023-09-10T10:27:19,470 ############################ 2023-09-10T10:27:19,470 # Package would be ignored # 2023-09-10T10:27:19,471 ############################ 2023-09-10T10:27:19,471 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Variables' as an importable package[^1], 2023-09-10T10:27:19,471 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,472 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,473 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Variables' is explicitly added 2023-09-10T10:27:19,473 to the `packages` configuration field. 2023-09-10T10:27:19,474 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,474 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,475 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,475 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,476 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,477 If you don't want 'publiforge.Processors.Publiset2Publidoc.Variables' to be distributed and are 2023-09-10T10:27:19,478 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Variables' via 2023-09-10T10:27:19,478 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,479 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,479 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,480 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,481 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,482 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,483 even if it does not contain any `.py` files. 2023-09-10T10:27:19,483 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,484 directory, all directories are treated like packages. 2023-09-10T10:27:19,484 ******************************************************************************** 2023-09-10T10:27:19,485 !! 2023-09-10T10:27:19,485 check.warn(importable) 2023-09-10T10:27:19,486 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiset2Publidoc.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:19,486 !! 2023-09-10T10:27:19,487 ******************************************************************************** 2023-09-10T10:27:19,488 ############################ 2023-09-10T10:27:19,488 # Package would be ignored # 2023-09-10T10:27:19,488 ############################ 2023-09-10T10:27:19,489 Python recognizes 'publiforge.Processors.Publiset2Publidoc.Xsl' as an importable package[^1], 2023-09-10T10:27:19,489 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,490 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,490 package, please make sure that 'publiforge.Processors.Publiset2Publidoc.Xsl' is explicitly added 2023-09-10T10:27:19,491 to the `packages` configuration field. 2023-09-10T10:27:19,492 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,492 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,492 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,493 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,494 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,494 If you don't want 'publiforge.Processors.Publiset2Publidoc.Xsl' to be distributed and are 2023-09-10T10:27:19,495 already explicitly excluding 'publiforge.Processors.Publiset2Publidoc.Xsl' via 2023-09-10T10:27:19,495 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,496 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,496 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,497 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,498 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,499 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,499 even if it does not contain any `.py` files. 2023-09-10T10:27:19,500 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,500 directory, all directories are treated like packages. 2023-09-10T10:27:19,501 ******************************************************************************** 2023-09-10T10:27:19,502 !! 2023-09-10T10:27:19,502 check.warn(importable) 2023-09-10T10:27:19,503 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiset4Publidoc' is absent from the `packages` configuration. 2023-09-10T10:27:19,503 !! 2023-09-10T10:27:19,504 ******************************************************************************** 2023-09-10T10:27:19,504 ############################ 2023-09-10T10:27:19,505 # Package would be ignored # 2023-09-10T10:27:19,505 ############################ 2023-09-10T10:27:19,506 Python recognizes 'publiforge.Processors.Publiset4Publidoc' as an importable package[^1], 2023-09-10T10:27:19,506 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,507 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,508 package, please make sure that 'publiforge.Processors.Publiset4Publidoc' is explicitly added 2023-09-10T10:27:19,508 to the `packages` configuration field. 2023-09-10T10:27:19,509 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,510 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,510 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,511 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,512 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,512 If you don't want 'publiforge.Processors.Publiset4Publidoc' to be distributed and are 2023-09-10T10:27:19,513 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc' via 2023-09-10T10:27:19,513 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,513 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,514 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,514 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,515 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,516 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,517 even if it does not contain any `.py` files. 2023-09-10T10:27:19,517 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,517 directory, all directories are treated like packages. 2023-09-10T10:27:19,518 ******************************************************************************** 2023-09-10T10:27:19,519 !! 2023-09-10T10:27:19,519 check.warn(importable) 2023-09-10T10:27:19,519 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiset4Publidoc.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:19,520 !! 2023-09-10T10:27:19,521 ******************************************************************************** 2023-09-10T10:27:19,521 ############################ 2023-09-10T10:27:19,521 # Package would be ignored # 2023-09-10T10:27:19,522 ############################ 2023-09-10T10:27:19,522 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Variables' as an importable package[^1], 2023-09-10T10:27:19,523 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,524 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,524 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Variables' is explicitly added 2023-09-10T10:27:19,524 to the `packages` configuration field. 2023-09-10T10:27:19,526 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,526 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,526 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,527 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,528 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,529 If you don't want 'publiforge.Processors.Publiset4Publidoc.Variables' to be distributed and are 2023-09-10T10:27:19,530 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Variables' via 2023-09-10T10:27:19,530 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,531 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,531 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,532 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,533 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,535 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,535 even if it does not contain any `.py` files. 2023-09-10T10:27:19,536 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,536 directory, all directories are treated like packages. 2023-09-10T10:27:19,537 ******************************************************************************** 2023-09-10T10:27:19,537 !! 2023-09-10T10:27:19,538 check.warn(importable) 2023-09-10T10:27:19,538 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiset4Publidoc.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:19,538 !! 2023-09-10T10:27:19,539 ******************************************************************************** 2023-09-10T10:27:19,539 ############################ 2023-09-10T10:27:19,540 # Package would be ignored # 2023-09-10T10:27:19,540 ############################ 2023-09-10T10:27:19,540 Python recognizes 'publiforge.Processors.Publiset4Publidoc.Xsl' as an importable package[^1], 2023-09-10T10:27:19,541 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,542 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,542 package, please make sure that 'publiforge.Processors.Publiset4Publidoc.Xsl' is explicitly added 2023-09-10T10:27:19,542 to the `packages` configuration field. 2023-09-10T10:27:19,543 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,544 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,544 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,545 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,545 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,546 If you don't want 'publiforge.Processors.Publiset4Publidoc.Xsl' to be distributed and are 2023-09-10T10:27:19,547 already explicitly excluding 'publiforge.Processors.Publiset4Publidoc.Xsl' via 2023-09-10T10:27:19,547 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,547 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,548 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,549 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,550 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,551 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,552 even if it does not contain any `.py` files. 2023-09-10T10:27:19,552 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,553 directory, all directories are treated like packages. 2023-09-10T10:27:19,553 ******************************************************************************** 2023-09-10T10:27:19,554 !! 2023-09-10T10:27:19,555 check.warn(importable) 2023-09-10T10:27:19,555 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiset4Publiquiz' is absent from the `packages` configuration. 2023-09-10T10:27:19,556 !! 2023-09-10T10:27:19,557 ******************************************************************************** 2023-09-10T10:27:19,557 ############################ 2023-09-10T10:27:19,558 # Package would be ignored # 2023-09-10T10:27:19,558 ############################ 2023-09-10T10:27:19,559 Python recognizes 'publiforge.Processors.Publiset4Publiquiz' as an importable package[^1], 2023-09-10T10:27:19,559 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,561 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,561 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz' is explicitly added 2023-09-10T10:27:19,562 to the `packages` configuration field. 2023-09-10T10:27:19,562 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,563 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,563 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,564 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,564 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,565 If you don't want 'publiforge.Processors.Publiset4Publiquiz' to be distributed and are 2023-09-10T10:27:19,565 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz' via 2023-09-10T10:27:19,566 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,566 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,566 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,567 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,568 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,569 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,569 even if it does not contain any `.py` files. 2023-09-10T10:27:19,570 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,571 directory, all directories are treated like packages. 2023-09-10T10:27:19,571 ******************************************************************************** 2023-09-10T10:27:19,572 !! 2023-09-10T10:27:19,573 check.warn(importable) 2023-09-10T10:27:19,573 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Processors.Publiset4Publiquiz.Xsl' is absent from the `packages` configuration. 2023-09-10T10:27:19,574 !! 2023-09-10T10:27:19,575 ******************************************************************************** 2023-09-10T10:27:19,576 ############################ 2023-09-10T10:27:19,576 # Package would be ignored # 2023-09-10T10:27:19,577 ############################ 2023-09-10T10:27:19,577 Python recognizes 'publiforge.Processors.Publiset4Publiquiz.Xsl' as an importable package[^1], 2023-09-10T10:27:19,578 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,579 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,579 package, please make sure that 'publiforge.Processors.Publiset4Publiquiz.Xsl' is explicitly added 2023-09-10T10:27:19,580 to the `packages` configuration field. 2023-09-10T10:27:19,581 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,581 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,582 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,583 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,584 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,585 If you don't want 'publiforge.Processors.Publiset4Publiquiz.Xsl' to be distributed and are 2023-09-10T10:27:19,585 already explicitly excluding 'publiforge.Processors.Publiset4Publiquiz.Xsl' via 2023-09-10T10:27:19,586 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,587 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,587 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,588 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,588 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,589 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,590 even if it does not contain any `.py` files. 2023-09-10T10:27:19,590 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,590 directory, all directories are treated like packages. 2023-09-10T10:27:19,591 ******************************************************************************** 2023-09-10T10:27:19,591 !! 2023-09-10T10:27:19,592 check.warn(importable) 2023-09-10T10:27:19,592 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.RelaxNG' is absent from the `packages` configuration. 2023-09-10T10:27:19,593 !! 2023-09-10T10:27:19,593 ******************************************************************************** 2023-09-10T10:27:19,594 ############################ 2023-09-10T10:27:19,594 # Package would be ignored # 2023-09-10T10:27:19,595 ############################ 2023-09-10T10:27:19,595 Python recognizes 'publiforge.RelaxNG' as an importable package[^1], 2023-09-10T10:27:19,595 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,596 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,597 package, please make sure that 'publiforge.RelaxNG' is explicitly added 2023-09-10T10:27:19,598 to the `packages` configuration field. 2023-09-10T10:27:19,599 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,599 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,600 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,601 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,602 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,603 If you don't want 'publiforge.RelaxNG' to be distributed and are 2023-09-10T10:27:19,604 already explicitly excluding 'publiforge.RelaxNG' via 2023-09-10T10:27:19,604 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,605 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,605 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,606 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,607 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,609 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,609 even if it does not contain any `.py` files. 2023-09-10T10:27:19,610 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,610 directory, all directories are treated like packages. 2023-09-10T10:27:19,611 ******************************************************************************** 2023-09-10T10:27:19,612 !! 2023-09-10T10:27:19,612 check.warn(importable) 2023-09-10T10:27:19,613 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Static' is absent from the `packages` configuration. 2023-09-10T10:27:19,613 !! 2023-09-10T10:27:19,615 ******************************************************************************** 2023-09-10T10:27:19,615 ############################ 2023-09-10T10:27:19,615 # Package would be ignored # 2023-09-10T10:27:19,616 ############################ 2023-09-10T10:27:19,616 Python recognizes 'publiforge.Static' as an importable package[^1], 2023-09-10T10:27:19,616 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,617 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,617 package, please make sure that 'publiforge.Static' is explicitly added 2023-09-10T10:27:19,618 to the `packages` configuration field. 2023-09-10T10:27:19,618 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,619 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,619 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,620 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,621 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,621 If you don't want 'publiforge.Static' to be distributed and are 2023-09-10T10:27:19,622 already explicitly excluding 'publiforge.Static' via 2023-09-10T10:27:19,622 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,623 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,623 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,624 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,625 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,626 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,627 even if it does not contain any `.py` files. 2023-09-10T10:27:19,627 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,628 directory, all directories are treated like packages. 2023-09-10T10:27:19,629 ******************************************************************************** 2023-09-10T10:27:19,630 !! 2023-09-10T10:27:19,630 check.warn(importable) 2023-09-10T10:27:19,631 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Static.Css' is absent from the `packages` configuration. 2023-09-10T10:27:19,632 !! 2023-09-10T10:27:19,633 ******************************************************************************** 2023-09-10T10:27:19,633 ############################ 2023-09-10T10:27:19,634 # Package would be ignored # 2023-09-10T10:27:19,634 ############################ 2023-09-10T10:27:19,634 Python recognizes 'publiforge.Static.Css' as an importable package[^1], 2023-09-10T10:27:19,635 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,636 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,637 package, please make sure that 'publiforge.Static.Css' is explicitly added 2023-09-10T10:27:19,637 to the `packages` configuration field. 2023-09-10T10:27:19,638 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,639 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,639 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,640 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,642 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,642 If you don't want 'publiforge.Static.Css' to be distributed and are 2023-09-10T10:27:19,643 already explicitly excluding 'publiforge.Static.Css' via 2023-09-10T10:27:19,643 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,643 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,644 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,644 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,645 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,646 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,647 even if it does not contain any `.py` files. 2023-09-10T10:27:19,647 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,647 directory, all directories are treated like packages. 2023-09-10T10:27:19,648 ******************************************************************************** 2023-09-10T10:27:19,648 !! 2023-09-10T10:27:19,649 check.warn(importable) 2023-09-10T10:27:19,649 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Static.Images' is absent from the `packages` configuration. 2023-09-10T10:27:19,650 !! 2023-09-10T10:27:19,651 ******************************************************************************** 2023-09-10T10:27:19,651 ############################ 2023-09-10T10:27:19,652 # Package would be ignored # 2023-09-10T10:27:19,652 ############################ 2023-09-10T10:27:19,652 Python recognizes 'publiforge.Static.Images' as an importable package[^1], 2023-09-10T10:27:19,653 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,654 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,654 package, please make sure that 'publiforge.Static.Images' is explicitly added 2023-09-10T10:27:19,655 to the `packages` configuration field. 2023-09-10T10:27:19,656 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,656 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,657 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,658 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,659 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,660 If you don't want 'publiforge.Static.Images' to be distributed and are 2023-09-10T10:27:19,660 already explicitly excluding 'publiforge.Static.Images' via 2023-09-10T10:27:19,660 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,661 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,661 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,662 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,663 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,665 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,666 even if it does not contain any `.py` files. 2023-09-10T10:27:19,666 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,667 directory, all directories are treated like packages. 2023-09-10T10:27:19,667 ******************************************************************************** 2023-09-10T10:27:19,669 !! 2023-09-10T10:27:19,669 check.warn(importable) 2023-09-10T10:27:19,669 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Static.Images.MimeTypes' is absent from the `packages` configuration. 2023-09-10T10:27:19,670 !! 2023-09-10T10:27:19,670 ******************************************************************************** 2023-09-10T10:27:19,671 ############################ 2023-09-10T10:27:19,671 # Package would be ignored # 2023-09-10T10:27:19,672 ############################ 2023-09-10T10:27:19,672 Python recognizes 'publiforge.Static.Images.MimeTypes' as an importable package[^1], 2023-09-10T10:27:19,672 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,673 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,673 package, please make sure that 'publiforge.Static.Images.MimeTypes' is explicitly added 2023-09-10T10:27:19,674 to the `packages` configuration field. 2023-09-10T10:27:19,675 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,675 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,676 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,676 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,677 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,678 If you don't want 'publiforge.Static.Images.MimeTypes' to be distributed and are 2023-09-10T10:27:19,679 already explicitly excluding 'publiforge.Static.Images.MimeTypes' via 2023-09-10T10:27:19,679 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,680 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,680 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,681 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,682 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,684 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,685 even if it does not contain any `.py` files. 2023-09-10T10:27:19,685 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,686 directory, all directories are treated like packages. 2023-09-10T10:27:19,686 ******************************************************************************** 2023-09-10T10:27:19,687 !! 2023-09-10T10:27:19,688 check.warn(importable) 2023-09-10T10:27:19,688 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Static.Js' is absent from the `packages` configuration. 2023-09-10T10:27:19,689 !! 2023-09-10T10:27:19,690 ******************************************************************************** 2023-09-10T10:27:19,690 ############################ 2023-09-10T10:27:19,691 # Package would be ignored # 2023-09-10T10:27:19,691 ############################ 2023-09-10T10:27:19,692 Python recognizes 'publiforge.Static.Js' as an importable package[^1], 2023-09-10T10:27:19,692 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,693 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,694 package, please make sure that 'publiforge.Static.Js' is explicitly added 2023-09-10T10:27:19,694 to the `packages` configuration field. 2023-09-10T10:27:19,696 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,696 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,696 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,697 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,698 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,698 If you don't want 'publiforge.Static.Js' to be distributed and are 2023-09-10T10:27:19,699 already explicitly excluding 'publiforge.Static.Js' via 2023-09-10T10:27:19,699 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,700 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,700 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,701 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,701 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,702 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,703 even if it does not contain any `.py` files. 2023-09-10T10:27:19,703 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,704 directory, all directories are treated like packages. 2023-09-10T10:27:19,704 ******************************************************************************** 2023-09-10T10:27:19,705 !! 2023-09-10T10:27:19,706 check.warn(importable) 2023-09-10T10:27:19,706 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Static.Js.Tests' is absent from the `packages` configuration. 2023-09-10T10:27:19,707 !! 2023-09-10T10:27:19,708 ******************************************************************************** 2023-09-10T10:27:19,709 ############################ 2023-09-10T10:27:19,709 # Package would be ignored # 2023-09-10T10:27:19,710 ############################ 2023-09-10T10:27:19,710 Python recognizes 'publiforge.Static.Js.Tests' as an importable package[^1], 2023-09-10T10:27:19,711 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,712 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,712 package, please make sure that 'publiforge.Static.Js.Tests' is explicitly added 2023-09-10T10:27:19,713 to the `packages` configuration field. 2023-09-10T10:27:19,714 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,714 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,715 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,716 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,717 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,718 If you don't want 'publiforge.Static.Js.Tests' to be distributed and are 2023-09-10T10:27:19,719 already explicitly excluding 'publiforge.Static.Js.Tests' via 2023-09-10T10:27:19,719 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,720 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,720 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,721 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,722 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,724 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,724 even if it does not contain any `.py` files. 2023-09-10T10:27:19,725 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,725 directory, all directories are treated like packages. 2023-09-10T10:27:19,726 ******************************************************************************** 2023-09-10T10:27:19,726 !! 2023-09-10T10:27:19,727 check.warn(importable) 2023-09-10T10:27:19,727 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.Templates' is absent from the `packages` configuration. 2023-09-10T10:27:19,727 !! 2023-09-10T10:27:19,728 ******************************************************************************** 2023-09-10T10:27:19,728 ############################ 2023-09-10T10:27:19,729 # Package would be ignored # 2023-09-10T10:27:19,729 ############################ 2023-09-10T10:27:19,730 Python recognizes 'publiforge.Templates' as an importable package[^1], 2023-09-10T10:27:19,730 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,731 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,731 package, please make sure that 'publiforge.Templates' is explicitly added 2023-09-10T10:27:19,732 to the `packages` configuration field. 2023-09-10T10:27:19,733 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,733 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,733 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,735 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,736 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,737 If you don't want 'publiforge.Templates' to be distributed and are 2023-09-10T10:27:19,737 already explicitly excluding 'publiforge.Templates' via 2023-09-10T10:27:19,738 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,739 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,739 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,740 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,741 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,743 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,744 even if it does not contain any `.py` files. 2023-09-10T10:27:19,746 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,746 directory, all directories are treated like packages. 2023-09-10T10:27:19,747 ******************************************************************************** 2023-09-10T10:27:19,748 !! 2023-09-10T10:27:19,749 check.warn(importable) 2023-09-10T10:27:19,750 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge' is absent from the `packages` configuration. 2023-09-10T10:27:19,751 !! 2023-09-10T10:27:19,752 ******************************************************************************** 2023-09-10T10:27:19,753 ############################ 2023-09-10T10:27:19,754 # Package would be ignored # 2023-09-10T10:27:19,756 ############################ 2023-09-10T10:27:19,757 Python recognizes 'publiforge.scaffolds.Front.PubliForge' as an importable package[^1], 2023-09-10T10:27:19,757 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,759 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,760 package, please make sure that 'publiforge.scaffolds.Front.PubliForge' is explicitly added 2023-09-10T10:27:19,760 to the `packages` configuration field. 2023-09-10T10:27:19,762 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,762 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,763 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,764 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,765 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,766 If you don't want 'publiforge.scaffolds.Front.PubliForge' to be distributed and are 2023-09-10T10:27:19,767 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge' via 2023-09-10T10:27:19,769 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,769 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,770 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,770 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,773 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,775 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,775 even if it does not contain any `.py` files. 2023-09-10T10:27:19,776 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,776 directory, all directories are treated like packages. 2023-09-10T10:27:19,777 ******************************************************************************** 2023-09-10T10:27:19,778 !! 2023-09-10T10:27:19,778 check.warn(importable) 2023-09-10T10:27:19,779 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' is absent from the `packages` configuration. 2023-09-10T10:27:19,779 !! 2023-09-10T10:27:19,780 ******************************************************************************** 2023-09-10T10:27:19,781 ############################ 2023-09-10T10:27:19,782 # Package would be ignored # 2023-09-10T10:27:19,782 ############################ 2023-09-10T10:27:19,783 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' as an importable package[^1], 2023-09-10T10:27:19,783 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,784 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,785 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' is explicitly added 2023-09-10T10:27:19,785 to the `packages` configuration field. 2023-09-10T10:27:19,786 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,787 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,787 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,788 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,789 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,790 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' to be distributed and are 2023-09-10T10:27:19,791 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Apache' via 2023-09-10T10:27:19,792 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,792 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,792 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,793 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,794 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,796 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,796 even if it does not contain any `.py` files. 2023-09-10T10:27:19,797 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,797 directory, all directories are treated like packages. 2023-09-10T10:27:19,797 ******************************************************************************** 2023-09-10T10:27:19,798 !! 2023-09-10T10:27:19,799 check.warn(importable) 2023-09-10T10:27:19,799 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' is absent from the `packages` configuration. 2023-09-10T10:27:19,800 !! 2023-09-10T10:27:19,801 ******************************************************************************** 2023-09-10T10:27:19,801 ############################ 2023-09-10T10:27:19,801 # Package would be ignored # 2023-09-10T10:27:19,802 ############################ 2023-09-10T10:27:19,802 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' as an importable package[^1], 2023-09-10T10:27:19,803 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,804 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,804 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' is explicitly added 2023-09-10T10:27:19,805 to the `packages` configuration field. 2023-09-10T10:27:19,806 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,806 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,807 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,808 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,809 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,810 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' to be distributed and are 2023-09-10T10:27:19,810 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Mercurial' via 2023-09-10T10:27:19,811 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,811 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,812 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,813 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,814 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,815 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,816 even if it does not contain any `.py` files. 2023-09-10T10:27:19,816 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,817 directory, all directories are treated like packages. 2023-09-10T10:27:19,817 ******************************************************************************** 2023-09-10T10:27:19,819 !! 2023-09-10T10:27:19,819 check.warn(importable) 2023-09-10T10:27:19,820 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' is absent from the `packages` configuration. 2023-09-10T10:27:19,820 !! 2023-09-10T10:27:19,821 ******************************************************************************** 2023-09-10T10:27:19,821 ############################ 2023-09-10T10:27:19,822 # Package would be ignored # 2023-09-10T10:27:19,822 ############################ 2023-09-10T10:27:19,823 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' as an importable package[^1], 2023-09-10T10:27:19,823 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,824 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,825 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' is explicitly added 2023-09-10T10:27:19,825 to the `packages` configuration field. 2023-09-10T10:27:19,826 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,827 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,827 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,828 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,829 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,830 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' to be distributed and are 2023-09-10T10:27:19,831 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Projects' via 2023-09-10T10:27:19,831 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,832 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,832 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,833 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,834 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,836 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,836 even if it does not contain any `.py` files. 2023-09-10T10:27:19,837 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,837 directory, all directories are treated like packages. 2023-09-10T10:27:19,838 ******************************************************************************** 2023-09-10T10:27:19,839 !! 2023-09-10T10:27:19,839 check.warn(importable) 2023-09-10T10:27:19,840 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' is absent from the `packages` configuration. 2023-09-10T10:27:19,840 !! 2023-09-10T10:27:19,841 ******************************************************************************** 2023-09-10T10:27:19,842 ############################ 2023-09-10T10:27:19,842 # Package would be ignored # 2023-09-10T10:27:19,843 ############################ 2023-09-10T10:27:19,843 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' as an importable package[^1], 2023-09-10T10:27:19,844 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,845 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,845 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' is explicitly added 2023-09-10T10:27:19,846 to the `packages` configuration field. 2023-09-10T10:27:19,847 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,847 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,848 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,849 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,850 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,850 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' to be distributed and are 2023-09-10T10:27:19,851 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Storages' via 2023-09-10T10:27:19,851 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,852 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,852 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,853 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,854 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,856 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,856 even if it does not contain any `.py` files. 2023-09-10T10:27:19,857 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,857 directory, all directories are treated like packages. 2023-09-10T10:27:19,858 ******************************************************************************** 2023-09-10T10:27:19,859 !! 2023-09-10T10:27:19,859 check.warn(importable) 2023-09-10T10:27:19,860 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' is absent from the `packages` configuration. 2023-09-10T10:27:19,860 !! 2023-09-10T10:27:19,861 ******************************************************************************** 2023-09-10T10:27:19,862 ############################ 2023-09-10T10:27:19,862 # Package would be ignored # 2023-09-10T10:27:19,863 ############################ 2023-09-10T10:27:19,863 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' as an importable package[^1], 2023-09-10T10:27:19,864 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,865 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,865 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' is explicitly added 2023-09-10T10:27:19,866 to the `packages` configuration field. 2023-09-10T10:27:19,867 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,867 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,868 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,869 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,870 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,871 If you don't want 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' to be distributed and are 2023-09-10T10:27:19,872 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Configuration.Users' via 2023-09-10T10:27:19,872 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,873 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,874 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,874 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,875 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,877 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,877 even if it does not contain any `.py` files. 2023-09-10T10:27:19,878 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,878 directory, all directories are treated like packages. 2023-09-10T10:27:19,879 ******************************************************************************** 2023-09-10T10:27:19,880 !! 2023-09-10T10:27:19,881 check.warn(importable) 2023-09-10T10:27:19,881 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Static' is absent from the `packages` configuration. 2023-09-10T10:27:19,882 !! 2023-09-10T10:27:19,883 ******************************************************************************** 2023-09-10T10:27:19,884 ############################ 2023-09-10T10:27:19,884 # Package would be ignored # 2023-09-10T10:27:19,885 ############################ 2023-09-10T10:27:19,886 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static' as an importable package[^1], 2023-09-10T10:27:19,886 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,887 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,888 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static' is explicitly added 2023-09-10T10:27:19,889 to the `packages` configuration field. 2023-09-10T10:27:19,890 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,891 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,891 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,893 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,894 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,895 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static' to be distributed and are 2023-09-10T10:27:19,896 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static' via 2023-09-10T10:27:19,896 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,897 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,898 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,899 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,901 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,903 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,903 even if it does not contain any `.py` files. 2023-09-10T10:27:19,904 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,905 directory, all directories are treated like packages. 2023-09-10T10:27:19,905 ******************************************************************************** 2023-09-10T10:27:19,906 !! 2023-09-10T10:27:19,907 check.warn(importable) 2023-09-10T10:27:19,908 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Static.Css' is absent from the `packages` configuration. 2023-09-10T10:27:19,909 !! 2023-09-10T10:27:19,910 ******************************************************************************** 2023-09-10T10:27:19,910 ############################ 2023-09-10T10:27:19,911 # Package would be ignored # 2023-09-10T10:27:19,911 ############################ 2023-09-10T10:27:19,912 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static.Css' as an importable package[^1], 2023-09-10T10:27:19,913 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,914 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,914 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static.Css' is explicitly added 2023-09-10T10:27:19,915 to the `packages` configuration field. 2023-09-10T10:27:19,916 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,917 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,917 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,918 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,920 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,921 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static.Css' to be distributed and are 2023-09-10T10:27:19,922 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static.Css' via 2023-09-10T10:27:19,922 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,923 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,923 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,925 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,926 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,928 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,929 even if it does not contain any `.py` files. 2023-09-10T10:27:19,929 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,930 directory, all directories are treated like packages. 2023-09-10T10:27:19,931 ******************************************************************************** 2023-09-10T10:27:19,933 !! 2023-09-10T10:27:19,934 check.warn(importable) 2023-09-10T10:27:19,935 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.Front.PubliForge.Static.Images' is absent from the `packages` configuration. 2023-09-10T10:27:19,935 !! 2023-09-10T10:27:19,937 ******************************************************************************** 2023-09-10T10:27:19,937 ############################ 2023-09-10T10:27:19,938 # Package would be ignored # 2023-09-10T10:27:19,939 ############################ 2023-09-10T10:27:19,939 Python recognizes 'publiforge.scaffolds.Front.PubliForge.Static.Images' as an importable package[^1], 2023-09-10T10:27:19,940 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,941 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,942 package, please make sure that 'publiforge.scaffolds.Front.PubliForge.Static.Images' is explicitly added 2023-09-10T10:27:19,943 to the `packages` configuration field. 2023-09-10T10:27:19,944 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,945 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,946 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,947 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,948 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,949 If you don't want 'publiforge.scaffolds.Front.PubliForge.Static.Images' to be distributed and are 2023-09-10T10:27:19,950 already explicitly excluding 'publiforge.scaffolds.Front.PubliForge.Static.Images' via 2023-09-10T10:27:19,950 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,951 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,951 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,953 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,954 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,955 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,956 even if it does not contain any `.py` files. 2023-09-10T10:27:19,957 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,957 directory, all directories are treated like packages. 2023-09-10T10:27:19,958 ******************************************************************************** 2023-09-10T10:27:19,959 !! 2023-09-10T10:27:19,960 check.warn(importable) 2023-09-10T10:27:19,961 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.LePrisme' is absent from the `packages` configuration. 2023-09-10T10:27:19,961 !! 2023-09-10T10:27:19,963 ******************************************************************************** 2023-09-10T10:27:19,963 ############################ 2023-09-10T10:27:19,964 # Package would be ignored # 2023-09-10T10:27:19,965 ############################ 2023-09-10T10:27:19,965 Python recognizes 'publiforge.scaffolds.LePrisme' as an importable package[^1], 2023-09-10T10:27:19,966 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,967 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,968 package, please make sure that 'publiforge.scaffolds.LePrisme' is explicitly added 2023-09-10T10:27:19,968 to the `packages` configuration field. 2023-09-10T10:27:19,970 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,970 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,971 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,972 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,974 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,975 If you don't want 'publiforge.scaffolds.LePrisme' to be distributed and are 2023-09-10T10:27:19,976 already explicitly excluding 'publiforge.scaffolds.LePrisme' via 2023-09-10T10:27:19,976 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,977 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,977 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,978 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,980 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:19,981 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:19,982 even if it does not contain any `.py` files. 2023-09-10T10:27:19,982 On the other hand, currently there is no concept of package data 2023-09-10T10:27:19,982 directory, all directories are treated like packages. 2023-09-10T10:27:19,983 ******************************************************************************** 2023-09-10T10:27:19,984 !! 2023-09-10T10:27:19,984 check.warn(importable) 2023-09-10T10:27:19,985 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.LePrisme.Templates' is absent from the `packages` configuration. 2023-09-10T10:27:19,985 !! 2023-09-10T10:27:19,986 ******************************************************************************** 2023-09-10T10:27:19,986 ############################ 2023-09-10T10:27:19,987 # Package would be ignored # 2023-09-10T10:27:19,987 ############################ 2023-09-10T10:27:19,988 Python recognizes 'publiforge.scaffolds.LePrisme.Templates' as an importable package[^1], 2023-09-10T10:27:19,988 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:19,989 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:19,990 package, please make sure that 'publiforge.scaffolds.LePrisme.Templates' is explicitly added 2023-09-10T10:27:19,990 to the `packages` configuration field. 2023-09-10T10:27:19,991 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:19,991 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:19,992 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:19,993 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:19,994 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:19,995 If you don't want 'publiforge.scaffolds.LePrisme.Templates' to be distributed and are 2023-09-10T10:27:19,995 already explicitly excluding 'publiforge.scaffolds.LePrisme.Templates' via 2023-09-10T10:27:19,996 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:19,996 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:19,997 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:19,998 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:19,999 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:20,000 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:20,001 even if it does not contain any `.py` files. 2023-09-10T10:27:20,001 On the other hand, currently there is no concept of package data 2023-09-10T10:27:20,002 directory, all directories are treated like packages. 2023-09-10T10:27:20,002 ******************************************************************************** 2023-09-10T10:27:20,003 !! 2023-09-10T10:27:20,004 check.warn(importable) 2023-09-10T10:27:20,005 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.LePrisme.Variables' is absent from the `packages` configuration. 2023-09-10T10:27:20,005 !! 2023-09-10T10:27:20,006 ******************************************************************************** 2023-09-10T10:27:20,007 ############################ 2023-09-10T10:27:20,007 # Package would be ignored # 2023-09-10T10:27:20,008 ############################ 2023-09-10T10:27:20,009 Python recognizes 'publiforge.scaffolds.LePrisme.Variables' as an importable package[^1], 2023-09-10T10:27:20,009 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:20,010 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:20,011 package, please make sure that 'publiforge.scaffolds.LePrisme.Variables' is explicitly added 2023-09-10T10:27:20,011 to the `packages` configuration field. 2023-09-10T10:27:20,012 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:20,012 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:20,013 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:20,014 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:20,014 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:20,015 If you don't want 'publiforge.scaffolds.LePrisme.Variables' to be distributed and are 2023-09-10T10:27:20,016 already explicitly excluding 'publiforge.scaffolds.LePrisme.Variables' via 2023-09-10T10:27:20,016 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:20,017 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:20,017 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:20,018 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:20,019 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:20,021 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:20,021 even if it does not contain any `.py` files. 2023-09-10T10:27:20,022 On the other hand, currently there is no concept of package data 2023-09-10T10:27:20,022 directory, all directories are treated like packages. 2023-09-10T10:27:20,023 ******************************************************************************** 2023-09-10T10:27:20,024 !! 2023-09-10T10:27:20,024 check.warn(importable) 2023-09-10T10:27:20,025 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.scaffolds.LePrisme.lib' is absent from the `packages` configuration. 2023-09-10T10:27:20,025 !! 2023-09-10T10:27:20,026 ******************************************************************************** 2023-09-10T10:27:20,027 ############################ 2023-09-10T10:27:20,027 # Package would be ignored # 2023-09-10T10:27:20,028 ############################ 2023-09-10T10:27:20,028 Python recognizes 'publiforge.scaffolds.LePrisme.lib' as an importable package[^1], 2023-09-10T10:27:20,029 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:20,030 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:20,030 package, please make sure that 'publiforge.scaffolds.LePrisme.lib' is explicitly added 2023-09-10T10:27:20,031 to the `packages` configuration field. 2023-09-10T10:27:20,032 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:20,033 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:20,033 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:20,034 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:20,035 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:20,036 If you don't want 'publiforge.scaffolds.LePrisme.lib' to be distributed and are 2023-09-10T10:27:20,037 already explicitly excluding 'publiforge.scaffolds.LePrisme.lib' via 2023-09-10T10:27:20,037 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:20,038 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:20,038 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:20,039 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:20,040 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:20,042 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:20,042 even if it does not contain any `.py` files. 2023-09-10T10:27:20,042 On the other hand, currently there is no concept of package data 2023-09-10T10:27:20,043 directory, all directories are treated like packages. 2023-09-10T10:27:20,043 ******************************************************************************** 2023-09-10T10:27:20,044 !! 2023-09-10T10:27:20,045 check.warn(importable) 2023-09-10T10:27:20,045 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'publiforge.tests.Data' is absent from the `packages` configuration. 2023-09-10T10:27:20,046 !! 2023-09-10T10:27:20,046 ******************************************************************************** 2023-09-10T10:27:20,047 ############################ 2023-09-10T10:27:20,047 # Package would be ignored # 2023-09-10T10:27:20,048 ############################ 2023-09-10T10:27:20,048 Python recognizes 'publiforge.tests.Data' as an importable package[^1], 2023-09-10T10:27:20,049 but it is absent from setuptools' `packages` configuration. 2023-09-10T10:27:20,050 This leads to an ambiguous overall configuration. If you want to distribute this 2023-09-10T10:27:20,050 package, please make sure that 'publiforge.tests.Data' is explicitly added 2023-09-10T10:27:20,051 to the `packages` configuration field. 2023-09-10T10:27:20,052 Alternatively, you can also rely on setuptools' discovery methods 2023-09-10T10:27:20,052 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2023-09-10T10:27:20,053 instead of `find_packages(...)`/`find:`). 2023-09-10T10:27:20,054 You can read more about "package discovery" on setuptools documentation page: 2023-09-10T10:27:20,055 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2023-09-10T10:27:20,056 If you don't want 'publiforge.tests.Data' to be distributed and are 2023-09-10T10:27:20,056 already explicitly excluding 'publiforge.tests.Data' via 2023-09-10T10:27:20,057 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2023-09-10T10:27:20,057 you can try to use `exclude_package_data`, or `include-package-data=False` in 2023-09-10T10:27:20,058 combination with a more fine grained `package-data` configuration. 2023-09-10T10:27:20,059 You can read more about "package data files" on setuptools documentation page: 2023-09-10T10:27:20,060 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2023-09-10T10:27:20,062 [^1]: For Python, any directory (with suitable naming) can be imported, 2023-09-10T10:27:20,062 even if it does not contain any `.py` files. 2023-09-10T10:27:20,063 On the other hand, currently there is no concept of package data 2023-09-10T10:27:20,063 directory, all directories are treated like packages. 2023-09-10T10:27:20,064 ******************************************************************************** 2023-09-10T10:27:20,065 !! 2023-09-10T10:27:20,066 check.warn(importable) 2023-09-10T10:27:20,066 creating build/lib.linux-armv7l-cpython-311/publiforge/Locale 2023-09-10T10:27:20,067 copying publiforge/Locale/publiforge.pot -> build/lib.linux-armv7l-cpython-311/publiforge/Locale 2023-09-10T10:27:20,068 creating build/lib.linux-armv7l-cpython-311/publiforge/Locale/es 2023-09-10T10:27:20,068 creating build/lib.linux-armv7l-cpython-311/publiforge/Locale/es/LC_MESSAGES 2023-09-10T10:27:20,069 copying publiforge/Locale/es/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-311/publiforge/Locale/es/LC_MESSAGES 2023-09-10T10:27:20,069 copying publiforge/Locale/es/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-311/publiforge/Locale/es/LC_MESSAGES 2023-09-10T10:27:20,070 creating build/lib.linux-armv7l-cpython-311/publiforge/Locale/fr 2023-09-10T10:27:20,070 creating build/lib.linux-armv7l-cpython-311/publiforge/Locale/fr/LC_MESSAGES 2023-09-10T10:27:20,071 copying publiforge/Locale/fr/LC_MESSAGES/colander.mo -> build/lib.linux-armv7l-cpython-311/publiforge/Locale/fr/LC_MESSAGES 2023-09-10T10:27:20,071 copying publiforge/Locale/fr/LC_MESSAGES/colander.po -> build/lib.linux-armv7l-cpython-311/publiforge/Locale/fr/LC_MESSAGES 2023-09-10T10:27:20,072 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.mo -> build/lib.linux-armv7l-cpython-311/publiforge/Locale/fr/LC_MESSAGES 2023-09-10T10:27:20,072 copying publiforge/Locale/fr/LC_MESSAGES/publiforge.po -> build/lib.linux-armv7l-cpython-311/publiforge/Locale/fr/LC_MESSAGES 2023-09-10T10:27:20,073 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers 2023-09-10T10:27:20,073 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Image 2023-09-10T10:27:20,073 copying publiforge/Openers/Image/image.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Image 2023-09-10T10:27:20,074 copying publiforge/Openers/Image/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Image 2023-09-10T10:27:20,074 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/ImageEdit 2023-09-10T10:27:20,075 copying publiforge/Openers/ImageEdit/image.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/ImageEdit 2023-09-10T10:27:20,075 copying publiforge/Openers/ImageEdit/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/ImageEdit 2023-09-10T10:27:20,076 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Ini 2023-09-10T10:27:20,076 copying publiforge/Openers/Ini/ini.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Ini 2023-09-10T10:27:20,077 copying publiforge/Openers/Ini/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Ini 2023-09-10T10:27:20,077 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/NoMore 2023-09-10T10:27:20,078 copying publiforge/Openers/NoMore/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/NoMore 2023-09-10T10:27:20,079 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Plain 2023-09-10T10:27:20,079 copying publiforge/Openers/Plain/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Plain 2023-09-10T10:27:20,080 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc 2023-09-10T10:27:20,080 copying publiforge/Openers/Publidoc/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc 2023-09-10T10:27:20,081 copying publiforge/Openers/Publidoc/xml.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc 2023-09-10T10:27:20,081 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Maestro 2023-09-10T10:27:20,082 copying publiforge/Openers/Publidoc/Maestro/publidoc_render4maestro.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Maestro 2023-09-10T10:27:20,082 copying publiforge/Openers/Publidoc/Maestro/publidoc_xml4maestro.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Maestro 2023-09-10T10:27:20,083 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Regex 2023-09-10T10:27:20,083 copying publiforge/Openers/Publidoc/Regex/publidoc_save.regex -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Regex 2023-09-10T10:27:20,084 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Seeds 2023-09-10T10:27:20,085 copying publiforge/Openers/Publidoc/Seeds/publidoc_document.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Seeds 2023-09-10T10:27:20,085 copying publiforge/Openers/Publidoc/Seeds/publidoc_glossary.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Seeds 2023-09-10T10:27:20,086 copying publiforge/Openers/Publidoc/Seeds/publidoc_topic.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Seeds 2023-09-10T10:27:20,086 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Static 2023-09-10T10:27:20,086 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Static/Css 2023-09-10T10:27:20,087 copying publiforge/Openers/Publidoc/Static/Css/publidoc_opener.css -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Static/Css 2023-09-10T10:27:20,087 copying publiforge/Openers/Publidoc/Static/Css/publidoc_schema.css -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Static/Css 2023-09-10T10:27:20,088 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Static/Js 2023-09-10T10:27:20,088 copying publiforge/Openers/Publidoc/Static/Js/codemirror4publidoc_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Static/Js 2023-09-10T10:27:20,089 copying publiforge/Openers/Publidoc/Static/Js/publidoc_schema.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Static/Js 2023-09-10T10:27:20,089 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Variables 2023-09-10T10:27:20,090 copying publiforge/Openers/Publidoc/Variables/publidoc.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Variables 2023-09-10T10:27:20,090 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Xsl 2023-09-10T10:27:20,091 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Xsl 2023-09-10T10:27:20,091 copying publiforge/Openers/Publidoc/Xsl/publidoc_edit_base.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Xsl 2023-09-10T10:27:20,092 copying publiforge/Openers/Publidoc/Xsl/publidoc_overview.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Xsl 2023-09-10T10:27:20,092 copying publiforge/Openers/Publidoc/Xsl/publidoc_render.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Xsl 2023-09-10T10:27:20,093 copying publiforge/Openers/Publidoc/Xsl/publidoc_save.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Xsl 2023-09-10T10:27:20,093 copying publiforge/Openers/Publidoc/Xsl/publidoc_save_base.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publidoc/Xsl 2023-09-10T10:27:20,094 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz 2023-09-10T10:27:20,094 copying publiforge/Openers/Publiquiz/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz 2023-09-10T10:27:20,095 copying publiforge/Openers/Publiquiz/xml.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz 2023-09-10T10:27:20,095 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Regex 2023-09-10T10:27:20,096 copying publiforge/Openers/Publiquiz/Regex/publiquiz_save.regex -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Regex 2023-09-10T10:27:20,096 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,097 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-fill.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,097 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-media.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,098 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_blanks-select.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,098 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_categories.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,099 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-check.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,099 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_choices-radio.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,100 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_coloring.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,100 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_composite.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,101 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_correct-line.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,101 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_blanks-fill.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,101 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_blanks-select.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,102 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_choices-check.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,102 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_flashcard_choices-radio.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,103 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_matching.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,103 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing-categories.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,104 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_pointing.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,104 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_production.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,105 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_sort.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,106 copying publiforge/Openers/Publiquiz/Seeds/publiquiz_wordsearch.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Seeds 2023-09-10T10:27:20,106 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static 2023-09-10T10:27:20,107 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static/Css 2023-09-10T10:27:20,107 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_opener.css -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static/Css 2023-09-10T10:27:20,108 copying publiforge/Openers/Publiquiz/Static/Css/publiquiz_schema.css -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static/Css 2023-09-10T10:27:20,108 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static/Fonts 2023-09-10T10:27:20,109 copying publiforge/Openers/Publiquiz/Static/Fonts/FontAwesome.otf -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static/Fonts 2023-09-10T10:27:20,109 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static/Js 2023-09-10T10:27:20,110 copying publiforge/Openers/Publiquiz/Static/Js/codemirror4publiquiz_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static/Js 2023-09-10T10:27:20,110 copying publiforge/Openers/Publiquiz/Static/Js/publiquiz_schema.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Static/Js 2023-09-10T10:27:20,111 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Variables 2023-09-10T10:27:20,111 copying publiforge/Openers/Publiquiz/Variables/publiquiz.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Variables 2023-09-10T10:27:20,111 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Xsl 2023-09-10T10:27:20,112 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_edit.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Xsl 2023-09-10T10:27:20,112 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_overview.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Xsl 2023-09-10T10:27:20,113 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_render.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Xsl 2023-09-10T10:27:20,113 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_save.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Xsl 2023-09-10T10:27:20,114 copying publiforge/Openers/Publiquiz/Xsl/publiquiz_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiquiz/Xsl 2023-09-10T10:27:20,114 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset 2023-09-10T10:27:20,115 copying publiforge/Openers/Publiset/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset 2023-09-10T10:27:20,115 copying publiforge/Openers/Publiset/xml.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset 2023-09-10T10:27:20,116 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Regex 2023-09-10T10:27:20,116 copying publiforge/Openers/Publiset/Regex/publiset_save.regex -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Regex 2023-09-10T10:27:20,117 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Seeds 2023-09-10T10:27:20,117 copying publiforge/Openers/Publiset/Seeds/publiset_composition.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Seeds 2023-09-10T10:27:20,118 copying publiforge/Openers/Publiset/Seeds/publiset_selection.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Seeds 2023-09-10T10:27:20,119 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static 2023-09-10T10:27:20,119 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Css 2023-09-10T10:27:20,120 copying publiforge/Openers/Publiset/Static/Css/editor4publiset.css -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Css 2023-09-10T10:27:20,120 copying publiforge/Openers/Publiset/Static/Css/publiset_opener.css -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Css 2023-09-10T10:27:20,121 copying publiforge/Openers/Publiset/Static/Css/publiset_schema.css -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Css 2023-09-10T10:27:20,121 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Images 2023-09-10T10:27:20,121 copying publiforge/Openers/Publiset/Static/Images/editor4publiset.png -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Images 2023-09-10T10:27:20,122 copying publiforge/Openers/Publiset/Static/Images/editor4publiset.xcf -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Images 2023-09-10T10:27:20,122 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Js 2023-09-10T10:27:20,123 copying publiforge/Openers/Publiset/Static/Js/codemirror4publiset_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Js 2023-09-10T10:27:20,123 copying publiforge/Openers/Publiset/Static/Js/editor4publiset.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Js 2023-09-10T10:27:20,124 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_en.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Js 2023-09-10T10:27:20,124 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_fr.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Js 2023-09-10T10:27:20,125 copying publiforge/Openers/Publiset/Static/Js/editor4publiset_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Js 2023-09-10T10:27:20,125 copying publiforge/Openers/Publiset/Static/Js/publiset_schema.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Static/Js 2023-09-10T10:27:20,126 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Variables 2023-09-10T10:27:20,126 copying publiforge/Openers/Publiset/Variables/publiset.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Variables 2023-09-10T10:27:20,127 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Xsl 2023-09-10T10:27:20,127 copying publiforge/Openers/Publiset/Xsl/publiset_edit.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Xsl 2023-09-10T10:27:20,127 copying publiforge/Openers/Publiset/Xsl/publiset_overview.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Xsl 2023-09-10T10:27:20,128 copying publiforge/Openers/Publiset/Xsl/publiset_render.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Xsl 2023-09-10T10:27:20,128 copying publiforge/Openers/Publiset/Xsl/publiset_render_base.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Xsl 2023-09-10T10:27:20,129 copying publiforge/Openers/Publiset/Xsl/publiset_render_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Xsl 2023-09-10T10:27:20,129 copying publiforge/Openers/Publiset/Xsl/publiset_save.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Publiset/Xsl 2023-09-10T10:27:20,130 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml 2023-09-10T10:27:20,130 copying publiforge/Openers/Xml/opener.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml 2023-09-10T10:27:20,130 copying publiforge/Openers/Xml/xml.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml 2023-09-10T10:27:20,131 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static 2023-09-10T10:27:20,131 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Css 2023-09-10T10:27:20,132 copying publiforge/Openers/Xml/Static/Css/editor4xml.css -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Css 2023-09-10T10:27:20,132 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Images 2023-09-10T10:27:20,133 copying publiforge/Openers/Xml/Static/Images/e4x_folder.png -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Images 2023-09-10T10:27:20,133 copying publiforge/Openers/Xml/Static/Images/editor4xml.png -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Images 2023-09-10T10:27:20,134 copying publiforge/Openers/Xml/Static/Images/editor4xml.xcf -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Images 2023-09-10T10:27:20,134 creating build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Js 2023-09-10T10:27:20,134 copying publiforge/Openers/Xml/Static/Js/editor4xml.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Js 2023-09-10T10:27:20,135 copying publiforge/Openers/Xml/Static/Js/editor4xml_en.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Js 2023-09-10T10:27:20,135 copying publiforge/Openers/Xml/Static/Js/editor4xml_fr.js -> build/lib.linux-armv7l-cpython-311/publiforge/Openers/Xml/Static/Js 2023-09-10T10:27:20,136 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors 2023-09-10T10:27:20,136 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/CharCount 2023-09-10T10:27:20,137 copying publiforge/Processors/CharCount/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/CharCount 2023-09-10T10:27:20,137 copying publiforge/Processors/CharCount/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/CharCount 2023-09-10T10:27:20,138 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/CharCount/Xsl 2023-09-10T10:27:20,138 copying publiforge/Processors/CharCount/Xsl/charcount.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/CharCount/Xsl 2023-09-10T10:27:20,139 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/CleanStorage 2023-09-10T10:27:20,139 copying publiforge/Processors/CleanStorage/generator.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/CleanStorage 2023-09-10T10:27:20,140 copying publiforge/Processors/CleanStorage/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/CleanStorage 2023-09-10T10:27:20,140 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/CleanStorage/lib 2023-09-10T10:27:20,140 copying publiforge/Processors/CleanStorage/lib/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/CleanStorage/lib 2023-09-10T10:27:20,141 copying publiforge/Processors/CleanStorage/lib/clean_storage.py -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/CleanStorage/lib 2023-09-10T10:27:20,141 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/DTBookValid 2023-09-10T10:27:20,142 copying publiforge/Processors/DTBookValid/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/DTBookValid 2023-09-10T10:27:20,142 copying publiforge/Processors/DTBookValid/validator.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/DTBookValid 2023-09-10T10:27:20,142 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/DTBookValid/RelaxNG 2023-09-10T10:27:20,143 copying publiforge/Processors/DTBookValid/RelaxNG/dtbook-2005-3.rng -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/DTBookValid/RelaxNG 2023-09-10T10:27:20,143 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PackFilling 2023-09-10T10:27:20,144 copying publiforge/Processors/PackFilling/generator.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PackFilling 2023-09-10T10:27:20,144 copying publiforge/Processors/PackFilling/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PackFilling 2023-09-10T10:27:20,145 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PackFilling/Variables 2023-09-10T10:27:20,145 copying publiforge/Processors/PackFilling/Variables/packfilling.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PackFilling/Variables 2023-09-10T10:27:20,146 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PackFilling/lib 2023-09-10T10:27:20,146 copying publiforge/Processors/PackFilling/lib/__init__.py -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PackFilling/lib 2023-09-10T10:27:20,147 copying publiforge/Processors/PackFilling/lib/packfilling.py -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PackFilling/lib 2023-09-10T10:27:20,147 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Parallel 2023-09-10T10:27:20,148 copying publiforge/Processors/Parallel/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Parallel 2023-09-10T10:27:20,148 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Parallel/Variables 2023-09-10T10:27:20,149 copying publiforge/Processors/Parallel/Variables/parallel.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Parallel/Variables 2023-09-10T10:27:20,149 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publianim2Html5 2023-09-10T10:27:20,150 copying publiforge/Processors/Publianim2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publianim2Html5 2023-09-10T10:27:20,150 copying publiforge/Processors/Publianim2Html5/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publianim2Html5 2023-09-10T10:27:20,151 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publianim2Html5/Variables 2023-09-10T10:27:20,151 copying publiforge/Processors/Publianim2Html5/Variables/publianim2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publianim2Html5/Variables 2023-09-10T10:27:20,152 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publianim2Html5/Xsl 2023-09-10T10:27:20,152 copying publiforge/Processors/Publianim2Html5/Xsl/publianim2html5.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publianim2Html5/Xsl 2023-09-10T10:27:20,152 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook 2023-09-10T10:27:20,153 copying publiforge/Processors/Publidoc2DTBook/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook 2023-09-10T10:27:20,153 copying publiforge/Processors/Publidoc2DTBook/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook 2023-09-10T10:27:20,154 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook/Variables 2023-09-10T10:27:20,154 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_image.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook/Variables 2023-09-10T10:27:20,155 copying publiforge/Processors/Publidoc2DTBook/Variables/publidoc2dtbook_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook/Variables 2023-09-10T10:27:20,156 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook/Xsl 2023-09-10T10:27:20,157 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook/Xsl 2023-09-10T10:27:20,159 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_base.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook/Xsl 2023-09-10T10:27:20,162 copying publiforge/Processors/Publidoc2DTBook/Xsl/publidoc2dtbook_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2DTBook/Xsl 2023-09-10T10:27:20,164 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2 2023-09-10T10:27:20,165 copying publiforge/Processors/Publidoc2EPub2/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2 2023-09-10T10:27:20,167 copying publiforge/Processors/Publidoc2EPub2/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2 2023-09-10T10:27:20,169 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Templates 2023-09-10T10:27:20,170 copying publiforge/Processors/Publidoc2EPub2/Templates/mimetype -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Templates 2023-09-10T10:27:20,172 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2023-09-10T10:27:20,173 copying publiforge/Processors/Publidoc2EPub2/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Templates/META-INF 2023-09-10T10:27:20,175 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS 2023-09-10T10:27:20,176 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2023-09-10T10:27:20,177 copying publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Templates/OEBPS/Css 2023-09-10T10:27:20,179 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Variables 2023-09-10T10:27:20,180 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Variables 2023-09-10T10:27:20,182 copying publiforge/Processors/Publidoc2EPub2/Variables/publidoc2epub2_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Variables 2023-09-10T10:27:20,184 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Xsl 2023-09-10T10:27:20,185 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Xsl 2023-09-10T10:27:20,188 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_base.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Xsl 2023-09-10T10:27:20,190 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Xsl 2023-09-10T10:27:20,192 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ini.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Xsl 2023-09-10T10:27:20,194 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_ncx.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Xsl 2023-09-10T10:27:20,196 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_opf.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Xsl 2023-09-10T10:27:20,199 copying publiforge/Processors/Publidoc2EPub2/Xsl/publidoc2epub2_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/Xsl 2023-09-10T10:27:20,202 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars 2023-09-10T10:27:20,203 copying publiforge/Processors/Publidoc2EPub2/jars/COPYING.txt -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars 2023-09-10T10:27:20,206 copying publiforge/Processors/Publidoc2EPub2/jars/README.txt -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars 2023-09-10T10:27:20,208 copying publiforge/Processors/Publidoc2EPub2/jars/THIRD-PARTY.txt -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars 2023-09-10T10:27:20,210 copying publiforge/Processors/Publidoc2EPub2/jars/epubcheck.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars 2023-09-10T10:27:20,228 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,229 copying publiforge/Processors/Publidoc2EPub2/jars/lib/Saxon-HE-9.5.1-5.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,373 copying publiforge/Processors/Publidoc2EPub2/jars/lib/common-image-3.1.2.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,377 copying publiforge/Processors/Publidoc2EPub2/jars/lib/common-io-3.1.2.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,381 copying publiforge/Processors/Publidoc2EPub2/jars/lib/common-lang-3.1.2.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,386 copying publiforge/Processors/Publidoc2EPub2/jars/lib/commons-compress-1.5.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,392 copying publiforge/Processors/Publidoc2EPub2/jars/lib/guava-14.0.1.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,425 copying publiforge/Processors/Publidoc2EPub2/jars/lib/imageio-core-3.1.2.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,429 copying publiforge/Processors/Publidoc2EPub2/jars/lib/imageio-jpeg-3.1.2.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,433 copying publiforge/Processors/Publidoc2EPub2/jars/lib/imageio-metadata-3.1.2.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,436 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jackson-core-asl-1.9.12.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,442 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jackson-mapper-asl-1.9.12.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,456 copying publiforge/Processors/Publidoc2EPub2/jars/lib/jing-20120724.0.0.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,471 copying publiforge/Processors/Publidoc2EPub2/jars/lib/sac-1.3.jar -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/lib 2023-09-10T10:27:20,474 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/licenses 2023-09-10T10:27:20,475 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/Apache-2.0.txt -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/licenses 2023-09-10T10:27:20,478 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/BSD-3-Clause.txt -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/licenses 2023-09-10T10:27:20,480 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/MPL-1.0.txt -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/licenses 2023-09-10T10:27:20,483 copying publiforge/Processors/Publidoc2EPub2/jars/licenses/W3C.txt -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub2/jars/licenses 2023-09-10T10:27:20,485 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3 2023-09-10T10:27:20,486 copying publiforge/Processors/Publidoc2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3 2023-09-10T10:27:20,488 copying publiforge/Processors/Publidoc2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3 2023-09-10T10:27:20,490 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Templates 2023-09-10T10:27:20,491 copying publiforge/Processors/Publidoc2EPub3/Templates/mimetype -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Templates 2023-09-10T10:27:20,492 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2023-09-10T10:27:20,493 copying publiforge/Processors/Publidoc2EPub3/Templates/META-INF/container.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Templates/META-INF 2023-09-10T10:27:20,495 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS 2023-09-10T10:27:20,496 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2023-09-10T10:27:20,497 copying publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css/custom.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Templates/OEBPS/Css 2023-09-10T10:27:20,499 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Variables 2023-09-10T10:27:20,500 copying publiforge/Processors/Publidoc2EPub3/Variables/publidoc2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Variables 2023-09-10T10:27:20,502 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Xsl 2023-09-10T10:27:20,504 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Xsl 2023-09-10T10:27:20,506 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_nav.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Xsl 2023-09-10T10:27:20,509 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Xsl 2023-09-10T10:27:20,512 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_smil.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Xsl 2023-09-10T10:27:20,514 copying publiforge/Processors/Publidoc2EPub3/Xsl/publidoc2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2EPub3/Xsl 2023-09-10T10:27:20,517 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5 2023-09-10T10:27:20,518 copying publiforge/Processors/Publidoc2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5 2023-09-10T10:27:20,520 copying publiforge/Processors/Publidoc2Html5/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5 2023-09-10T10:27:20,521 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates 2023-09-10T10:27:20,522 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Css 2023-09-10T10:27:20,523 copying publiforge/Processors/Publidoc2Html5/Templates/Css/custom.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Css 2023-09-10T10:27:20,525 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Images 2023-09-10T10:27:20,526 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_en.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Images 2023-09-10T10:27:20,528 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_fr.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Images 2023-09-10T10:27:20,530 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Images 2023-09-10T10:27:20,532 copying publiforge/Processors/Publidoc2Html5/Templates/Images/audio_play.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Images 2023-09-10T10:27:20,534 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Js 2023-09-10T10:27:20,535 copying publiforge/Processors/Publidoc2Html5/Templates/Js/audio_player.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Templates/Js 2023-09-10T10:27:20,537 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Variables 2023-09-10T10:27:20,538 copying publiforge/Processors/Publidoc2Html5/Variables/publidoc2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Variables 2023-09-10T10:27:20,541 copying publiforge/Processors/Publidoc2Html5/Variables/publidoc2html5_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Variables 2023-09-10T10:27:20,543 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Xsl 2023-09-10T10:27:20,544 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Xsl 2023-09-10T10:27:20,546 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_ini.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Xsl 2023-09-10T10:27:20,551 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_media.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Xsl 2023-09-10T10:27:20,553 copying publiforge/Processors/Publidoc2Html5/Xsl/publidoc2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Html5/Xsl 2023-09-10T10:27:20,556 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf 2023-09-10T10:27:20,557 copying publiforge/Processors/Publidoc2Pdf/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf 2023-09-10T10:27:20,559 copying publiforge/Processors/Publidoc2Pdf/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf 2023-09-10T10:27:20,561 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Fonts 2023-09-10T10:27:20,562 copying publiforge/Processors/Publidoc2Pdf/Fonts/Script.otf -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Fonts 2023-09-10T10:27:20,575 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Regex 2023-09-10T10:27:20,576 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_post.regex -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Regex 2023-09-10T10:27:20,578 copying publiforge/Processors/Publidoc2Pdf/Regex/publidoc2pdf_pre.regex -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Regex 2023-09-10T10:27:20,580 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Variables 2023-09-10T10:27:20,582 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_dimension.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Variables 2023-09-10T10:27:20,584 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_font.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Variables 2023-09-10T10:27:20,587 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_image.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Variables 2023-09-10T10:27:20,589 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_layout.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Variables 2023-09-10T10:27:20,591 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Variables 2023-09-10T10:27:20,594 copying publiforge/Processors/Publidoc2Pdf/Variables/publidoc2pdf_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Variables 2023-09-10T10:27:20,596 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Xsl 2023-09-10T10:27:20,597 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Xsl 2023-09-10T10:27:20,600 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_base.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Xsl 2023-09-10T10:27:20,603 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Xsl 2023-09-10T10:27:20,605 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_ini.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Xsl 2023-09-10T10:27:20,608 copying publiforge/Processors/Publidoc2Pdf/Xsl/publidoc2pdf_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2Pdf/Xsl 2023-09-10T10:27:20,611 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml 2023-09-10T10:27:20,612 copying publiforge/Processors/Publidoc2XHtml/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml 2023-09-10T10:27:20,614 copying publiforge/Processors/Publidoc2XHtml/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml 2023-09-10T10:27:20,617 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Regex 2023-09-10T10:27:20,618 copying publiforge/Processors/Publidoc2XHtml/Regex/publidoc2xhtml_pre.regex -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Regex 2023-09-10T10:27:20,620 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,622 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_block.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,624 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_component.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,627 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_division.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,629 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_head.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,632 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_inline.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,634 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_section.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,636 copying publiforge/Processors/Publidoc2XHtml/Scss/_publidoc_top.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,639 copying publiforge/Processors/Publidoc2XHtml/Scss/publidoc.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Scss 2023-09-10T10:27:20,641 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates 2023-09-10T10:27:20,641 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Css 2023-09-10T10:27:20,643 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/custom.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Css 2023-09-10T10:27:20,646 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/publidoc.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Css 2023-09-10T10:27:20,649 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/publidoc.css.map -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Css 2023-09-10T10:27:20,651 copying publiforge/Processors/Publidoc2XHtml/Templates/Css/reset.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Css 2023-09-10T10:27:20,654 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,655 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/annotation.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,657 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,660 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,662 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/audio_play.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,664 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_next.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,667 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_previous.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,669 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/go_up.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,672 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/pulse.gif -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,674 copying publiforge/Processors/Publidoc2XHtml/Templates/Images/video.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Images 2023-09-10T10:27:20,677 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Js 2023-09-10T10:27:20,678 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/jquery.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Js 2023-09-10T10:27:20,683 copying publiforge/Processors/Publidoc2XHtml/Templates/Js/publidoc.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Templates/Js 2023-09-10T10:27:20,685 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Variables 2023-09-10T10:27:20,686 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Variables 2023-09-10T10:27:20,689 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_html.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Variables 2023-09-10T10:27:20,691 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_image.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Variables 2023-09-10T10:27:20,694 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_misc.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Variables 2023-09-10T10:27:20,696 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Variables 2023-09-10T10:27:20,699 copying publiforge/Processors/Publidoc2XHtml/Variables/publidoc2xhtml_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Variables 2023-09-10T10:27:20,702 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Xsl 2023-09-10T10:27:20,703 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Xsl 2023-09-10T10:27:20,706 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_base.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Xsl 2023-09-10T10:27:20,710 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Xsl 2023-09-10T10:27:20,713 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_ini.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Xsl 2023-09-10T10:27:20,716 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_media.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Xsl 2023-09-10T10:27:20,719 copying publiforge/Processors/Publidoc2XHtml/Xsl/publidoc2xhtml_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publidoc2XHtml/Xsl 2023-09-10T10:27:20,723 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean 2023-09-10T10:27:20,724 copying publiforge/Processors/PublidocClean/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean 2023-09-10T10:27:20,726 copying publiforge/Processors/PublidocClean/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean 2023-09-10T10:27:20,728 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean/Regex 2023-09-10T10:27:20,730 copying publiforge/Processors/PublidocClean/Regex/publidocclean_pre.regex -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean/Regex 2023-09-10T10:27:20,732 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean/Variables 2023-09-10T10:27:20,733 copying publiforge/Processors/PublidocClean/Variables/publidocclean.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean/Variables 2023-09-10T10:27:20,736 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean/Xsl 2023-09-10T10:27:20,737 copying publiforge/Processors/PublidocClean/Xsl/publidocclean.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocClean/Xsl 2023-09-10T10:27:20,740 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocValid 2023-09-10T10:27:20,741 copying publiforge/Processors/PublidocValid/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocValid 2023-09-10T10:27:20,743 copying publiforge/Processors/PublidocValid/validator.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocValid 2023-09-10T10:27:20,746 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocValid/RelaxNG 2023-09-10T10:27:20,747 copying publiforge/Processors/PublidocValid/RelaxNG/publianim.rng -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocValid/RelaxNG 2023-09-10T10:27:20,749 copying publiforge/Processors/PublidocValid/RelaxNG/publidoc.rng -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocValid/RelaxNG 2023-09-10T10:27:20,753 copying publiforge/Processors/PublidocValid/RelaxNG/publiquiz.rng -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocValid/RelaxNG 2023-09-10T10:27:20,758 copying publiforge/Processors/PublidocValid/RelaxNG/publiset.rng -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/PublidocValid/RelaxNG 2023-09-10T10:27:20,761 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3 2023-09-10T10:27:20,762 copying publiforge/Processors/Publiquiz2EPub3/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3 2023-09-10T10:27:20,764 copying publiforge/Processors/Publiquiz2EPub3/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3 2023-09-10T10:27:20,766 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3/Variables 2023-09-10T10:27:20,767 copying publiforge/Processors/Publiquiz2EPub3/Variables/publiquiz2epub3.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3/Variables 2023-09-10T10:27:20,769 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3/Xsl 2023-09-10T10:27:20,770 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3/Xsl 2023-09-10T10:27:20,772 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_opf.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3/Xsl 2023-09-10T10:27:20,775 copying publiforge/Processors/Publiquiz2EPub3/Xsl/publiquiz2epub3_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2EPub3/Xsl 2023-09-10T10:27:20,777 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5 2023-09-10T10:27:20,778 copying publiforge/Processors/Publiquiz2Html5/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5 2023-09-10T10:27:20,781 copying publiforge/Processors/Publiquiz2Html5/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5 2023-09-10T10:27:20,783 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache 2023-09-10T10:27:20,783 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,784 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_block.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,788 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_buttons.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,790 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_categories.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,794 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_choices.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,797 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_coloring.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,799 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_flashcard.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,802 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_matching.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,804 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_memory.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,808 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_pointing.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,810 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_production.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,812 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_engine_wordsearch.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,815 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_inline.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,818 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_section.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,821 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/_publiquiz_top.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,824 copying publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd/publiquiz.scssc -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/.sass-cache/e13eba139f5afebe33e79131c7fa1c6b89388dcd 2023-09-10T10:27:20,826 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,827 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_block.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,830 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_buttons.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,832 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_categories.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,834 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_choices.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,837 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_coloring.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,839 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_flashcard.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,841 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_matching.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,843 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_memory.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,846 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_pointing.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,848 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_production.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,850 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_engine_wordsearch.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,853 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_inline.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,855 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_section.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,857 copying publiforge/Processors/Publiquiz2Html5/Scss/_publiquiz_top.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,860 copying publiforge/Processors/Publiquiz2Html5/Scss/publiquiz.scss -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Scss 2023-09-10T10:27:20,862 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates 2023-09-10T10:27:20,863 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2023-09-10T10:27:20,864 copying publiforge/Processors/Publiquiz2Html5/Templates/Audios/right.mp3 -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2023-09-10T10:27:20,867 copying publiforge/Processors/Publiquiz2Html5/Templates/Audios/right.ogg -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2023-09-10T10:27:20,870 copying publiforge/Processors/Publiquiz2Html5/Templates/Audios/wrong.mp3 -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2023-09-10T10:27:20,873 copying publiforge/Processors/Publiquiz2Html5/Templates/Audios/wrong.ogg -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Audios 2023-09-10T10:27:20,876 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Css 2023-09-10T10:27:20,877 copying publiforge/Processors/Publiquiz2Html5/Templates/Css/publiquiz.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Css 2023-09-10T10:27:20,880 copying publiforge/Processors/Publiquiz2Html5/Templates/Css/publiquiz.css.map -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Css 2023-09-10T10:27:20,883 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2023-09-10T10:27:20,885 copying publiforge/Processors/Publiquiz2Html5/Templates/Fonts/FontAwesome.otf -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2023-09-10T10:27:20,889 copying publiforge/Processors/Publiquiz2Html5/Templates/Fonts/FontAwesome.ttf -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Fonts 2023-09-10T10:27:20,894 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Images 2023-09-10T10:27:20,895 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/back_card.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Images 2023-09-10T10:27:20,906 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/brush.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Images 2023-09-10T10:27:20,908 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/bucket.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Images 2023-09-10T10:27:20,910 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/close.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Images 2023-09-10T10:27:20,912 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/eraser.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Images 2023-09-10T10:27:20,914 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/highlighter.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Images 2023-09-10T10:27:20,916 copying publiforge/Processors/Publiquiz2Html5/Templates/Images/loading.gif -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Images 2023-09-10T10:27:20,919 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,920 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/code.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,922 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/memory.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,926 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/memory_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,928 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publianim_drawing.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,931 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,936 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_basics.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,942 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_coloring.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,944 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_correct_line.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,947 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_flashcard.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,950 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,952 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_matching_link.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,955 copying publiforge/Processors/Publiquiz2Html5/Templates/Js/publiquiz_wordsearch.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Templates/Js 2023-09-10T10:27:20,958 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Variables 2023-09-10T10:27:20,959 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Variables 2023-09-10T10:27:20,961 copying publiforge/Processors/Publiquiz2Html5/Variables/publiquiz2html5_quiz.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Variables 2023-09-10T10:27:20,963 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Xsl 2023-09-10T10:27:20,964 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Xsl 2023-09-10T10:27:20,967 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_base.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Xsl 2023-09-10T10:27:20,971 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Xsl 2023-09-10T10:27:20,974 copying publiforge/Processors/Publiquiz2Html5/Xsl/publiquiz2html5_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Html5/Xsl 2023-09-10T10:27:20,977 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12 2023-09-10T10:27:20,978 copying publiforge/Processors/Publiquiz2Scorm12/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12 2023-09-10T10:27:20,980 copying publiforge/Processors/Publiquiz2Scorm12/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12 2023-09-10T10:27:20,982 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates 2023-09-10T10:27:20,983 copying publiforge/Processors/Publiquiz2Scorm12/Templates/adlcp_rootv1p2.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates 2023-09-10T10:27:20,985 copying publiforge/Processors/Publiquiz2Scorm12/Templates/ims_xml.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates 2023-09-10T10:27:20,987 copying publiforge/Processors/Publiquiz2Scorm12/Templates/imscp_rootv1p1p2.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates 2023-09-10T10:27:20,990 copying publiforge/Processors/Publiquiz2Scorm12/Templates/imsmd_rootv1p2p1.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates 2023-09-10T10:27:20,992 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content 2023-09-10T10:27:20,993 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css 2023-09-10T10:27:20,994 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css/custom.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Css 2023-09-10T10:27:20,996 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2023-09-10T10:27:20,997 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images/audio_pause.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2023-09-10T10:27:21,000 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images/audio_play.png -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Images 2023-09-10T10:27:21,001 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2023-09-10T10:27:21,002 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2023-09-10T10:27:21,005 copying publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js/scorm_apiwrapper.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Templates/Content/Js 2023-09-10T10:27:21,007 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Variables 2023-09-10T10:27:21,008 copying publiforge/Processors/Publiquiz2Scorm12/Variables/publiquiz2scorm12.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Variables 2023-09-10T10:27:21,010 copying publiforge/Processors/Publiquiz2Scorm12/Variables/publiquiz2scorm12_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Variables 2023-09-10T10:27:21,012 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Xsl 2023-09-10T10:27:21,013 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Xsl 2023-09-10T10:27:21,015 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Xsl 2023-09-10T10:27:21,017 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_ims.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Xsl 2023-09-10T10:27:21,020 copying publiforge/Processors/Publiquiz2Scorm12/Xsl/publiquiz2scorm12_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm12/Xsl 2023-09-10T10:27:21,021 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004 2023-09-10T10:27:21,022 copying publiforge/Processors/Publiquiz2Scorm2004/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004 2023-09-10T10:27:21,024 copying publiforge/Processors/Publiquiz2Scorm2004/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004 2023-09-10T10:27:21,026 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,027 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/XMLSchema.dtd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,030 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlcp_v1p3.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,033 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlnav_v1p3.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,035 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/adlseq_v1p3.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,037 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/datatypes.dtd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,040 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/ims_xml.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,042 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imscp_v1p1.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,044 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,047 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0auxresource.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,049 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0control.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,051 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0delivery.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,053 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0limit.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,055 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0objective.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,057 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0random.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,058 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0rollup.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,060 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0seqrule.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,063 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/imsss_v1p0util.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,065 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lom.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,067 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomCustom.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,069 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomLoose.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,071 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/lomStrict.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,073 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/xml.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates 2023-09-10T10:27:21,075 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content 2023-09-10T10:27:21,076 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css 2023-09-10T10:27:21,077 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css/custom.css -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Css 2023-09-10T10:27:21,079 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2023-09-10T10:27:21,080 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js/publiquiz_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2023-09-10T10:27:21,083 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js/scorm_apiwrapper.js -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/Content/Js 2023-09-10T10:27:21,086 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2023-09-10T10:27:21,087 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/anyElement.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2023-09-10T10:27:21,089 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/dataTypes.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2023-09-10T10:27:21,091 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/elementNames.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2023-09-10T10:27:21,094 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/elementTypes.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2023-09-10T10:27:21,097 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/rootElement.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2023-09-10T10:27:21,099 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/vocabTypes.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2023-09-10T10:27:21,102 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/common/vocabValues.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/common 2023-09-10T10:27:21,104 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2023-09-10T10:27:21,105 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/extend/custom.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2023-09-10T10:27:21,107 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/extend/strict.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/extend 2023-09-10T10:27:21,109 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2023-09-10T10:27:21,110 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/unique/loose.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2023-09-10T10:27:21,112 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/unique/strict.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/unique 2023-09-10T10:27:21,115 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2023-09-10T10:27:21,116 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/custom.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2023-09-10T10:27:21,118 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/loose.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2023-09-10T10:27:21,121 copying publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab/strict.xsd -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Templates/vocab 2023-09-10T10:27:21,123 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Variables 2023-09-10T10:27:21,124 copying publiforge/Processors/Publiquiz2Scorm2004/Variables/publiquiz2scorm2004.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Variables 2023-09-10T10:27:21,126 copying publiforge/Processors/Publiquiz2Scorm2004/Variables/publiquiz2scorm2004_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Variables 2023-09-10T10:27:21,128 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2023-09-10T10:27:21,129 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2023-09-10T10:27:21,132 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_i18n.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2023-09-10T10:27:21,134 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_ims.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2023-09-10T10:27:21,137 copying publiforge/Processors/Publiquiz2Scorm2004/Xsl/publiquiz2scorm2004_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiquiz2Scorm2004/Xsl 2023-09-10T10:27:21,139 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc 2023-09-10T10:27:21,140 copying publiforge/Processors/Publiset2Publidoc/leprisme.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc 2023-09-10T10:27:21,142 copying publiforge/Processors/Publiset2Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc 2023-09-10T10:27:21,144 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Variables 2023-09-10T10:27:21,145 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_image.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Variables 2023-09-10T10:27:21,147 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Variables 2023-09-10T10:27:21,149 copying publiforge/Processors/Publiset2Publidoc/Variables/publiset2publidoc_multimedia.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Variables 2023-09-10T10:27:21,151 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Xsl 2023-09-10T10:27:21,152 copying publiforge/Processors/Publiset2Publidoc/Xsl/composition.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Xsl 2023-09-10T10:27:21,154 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Xsl 2023-09-10T10:27:21,156 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc_ini.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Xsl 2023-09-10T10:27:21,159 copying publiforge/Processors/Publiset2Publidoc/Xsl/publiset2publidoc_template.inc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset2Publidoc/Xsl 2023-09-10T10:27:21,161 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc 2023-09-10T10:27:21,162 copying publiforge/Processors/Publiset4Publidoc/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc 2023-09-10T10:27:21,164 copying publiforge/Processors/Publiset4Publidoc/publiseter.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc 2023-09-10T10:27:21,166 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc/Variables 2023-09-10T10:27:21,167 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_meta.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc/Variables 2023-09-10T10:27:21,169 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc/Variables 2023-09-10T10:27:21,171 copying publiforge/Processors/Publiset4Publidoc/Variables/publiset4publidoc_schema.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc/Variables 2023-09-10T10:27:21,173 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc/Xsl 2023-09-10T10:27:21,174 copying publiforge/Processors/Publiset4Publidoc/Xsl/publiset4publidoc.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publidoc/Xsl 2023-09-10T10:27:21,177 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publiquiz 2023-09-10T10:27:21,178 copying publiforge/Processors/Publiset4Publiquiz/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publiquiz 2023-09-10T10:27:21,180 copying publiforge/Processors/Publiset4Publiquiz/publiseter.ini -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publiquiz 2023-09-10T10:27:21,182 creating build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publiquiz/Xsl 2023-09-10T10:27:21,183 copying publiforge/Processors/Publiset4Publiquiz/Xsl/publiset4publiquiz.xsl -> build/lib.linux-armv7l-cpython-311/publiforge/Processors/Publiset4Publiquiz/Xsl 2023-09-10T10:27:21,186 creating build/lib.linux-armv7l-cpython-311/publiforge/RelaxNG 2023-09-10T10:27:21,187 copying publiforge/RelaxNG/publiforge.rnc -> build/lib.linux-armv7l-cpython-311/publiforge/RelaxNG 2023-09-10T10:27:21,189 copying publiforge/RelaxNG/publiforge.rng -> build/lib.linux-armv7l-cpython-311/publiforge/RelaxNG 2023-09-10T10:27:21,193 creating build/lib.linux-armv7l-cpython-311/publiforge/Static 2023-09-10T10:27:21,193 copying publiforge/Static/favicon.ico -> build/lib.linux-armv7l-cpython-311/publiforge/Static 2023-09-10T10:27:21,196 copying publiforge/Static/robots.txt -> build/lib.linux-armv7l-cpython-311/publiforge/Static 2023-09-10T10:27:21,197 creating build/lib.linux-armv7l-cpython-311/publiforge/Static/Css 2023-09-10T10:27:21,198 copying publiforge/Static/Css/base.css -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Css 2023-09-10T10:27:21,201 copying publiforge/Static/Css/codemirror.css -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Css 2023-09-10T10:27:21,204 copying publiforge/Static/Css/login.css -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Css 2023-09-10T10:27:21,206 copying publiforge/Static/Css/pygments.css -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Css 2023-09-10T10:27:21,208 copying publiforge/Static/Css/reset.css -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Css 2023-09-10T10:27:21,210 creating build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,211 copying publiforge/Static/Images/action_add.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,213 copying publiforge/Static/Images/action_add_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,215 copying publiforge/Static/Images/action_browse.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,217 copying publiforge/Static/Images/action_browse_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,219 copying publiforge/Static/Images/action_build.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,221 copying publiforge/Static/Images/action_build_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,223 copying publiforge/Static/Images/action_cancel.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,225 copying publiforge/Static/Images/action_create.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,227 copying publiforge/Static/Images/action_dashboard_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,230 copying publiforge/Static/Images/action_delete.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,232 copying publiforge/Static/Images/action_delete_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,234 copying publiforge/Static/Images/action_diff.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,235 copying publiforge/Static/Images/action_diff_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,237 copying publiforge/Static/Images/action_display.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,239 copying publiforge/Static/Images/action_display_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,241 copying publiforge/Static/Images/action_down_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,243 copying publiforge/Static/Images/action_download.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,246 copying publiforge/Static/Images/action_download_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,248 copying publiforge/Static/Images/action_duplicate.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,250 copying publiforge/Static/Images/action_edit_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,252 copying publiforge/Static/Images/action_export.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,253 copying publiforge/Static/Images/action_export_csv.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,255 copying publiforge/Static/Images/action_export_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,257 copying publiforge/Static/Images/action_filter.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,259 copying publiforge/Static/Images/action_help_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,261 copying publiforge/Static/Images/action_history_empty.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,263 copying publiforge/Static/Images/action_import.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,265 copying publiforge/Static/Images/action_info.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,267 copying publiforge/Static/Images/action_info_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,269 copying publiforge/Static/Images/action_log.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,271 copying publiforge/Static/Images/action_log_empty.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,273 copying publiforge/Static/Images/action_log_empty_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,275 copying publiforge/Static/Images/action_mkdir.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,277 copying publiforge/Static/Images/action_next.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,279 copying publiforge/Static/Images/action_next_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,281 copying publiforge/Static/Images/action_note.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,283 copying publiforge/Static/Images/action_note_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,285 copying publiforge/Static/Images/action_overview_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,286 copying publiforge/Static/Images/action_overview_on.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,289 copying publiforge/Static/Images/action_pack.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,291 copying publiforge/Static/Images/action_pipe.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,293 copying publiforge/Static/Images/action_progress_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,295 copying publiforge/Static/Images/action_remove.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,297 copying publiforge/Static/Images/action_remove_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,299 copying publiforge/Static/Images/action_rename_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,301 copying publiforge/Static/Images/action_render.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,303 copying publiforge/Static/Images/action_render_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,305 copying publiforge/Static/Images/action_reset_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,307 copying publiforge/Static/Images/action_save.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,309 copying publiforge/Static/Images/action_search.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,311 copying publiforge/Static/Images/action_select.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,313 copying publiforge/Static/Images/action_select_get.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,315 copying publiforge/Static/Images/action_select_get_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,317 copying publiforge/Static/Images/action_select_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,319 copying publiforge/Static/Images/action_start.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,321 copying publiforge/Static/Images/action_start_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,323 copying publiforge/Static/Images/action_stop.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,325 copying publiforge/Static/Images/action_stop_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,327 copying publiforge/Static/Images/action_synchronize.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,329 copying publiforge/Static/Images/action_synchronize_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,331 copying publiforge/Static/Images/action_take.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,333 copying publiforge/Static/Images/action_take_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,335 copying publiforge/Static/Images/action_up_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,337 copying publiforge/Static/Images/action_upload.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,339 copying publiforge/Static/Images/action_upload_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,341 copying publiforge/Static/Images/action_view.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,343 copying publiforge/Static/Images/action_view_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,345 copying publiforge/Static/Images/admin.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,347 copying publiforge/Static/Images/back.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,349 copying publiforge/Static/Images/breadcrumbs_top.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,351 copying publiforge/Static/Images/build.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,353 copying publiforge/Static/Images/build22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,356 copying publiforge/Static/Images/build32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,358 copying publiforge/Static/Images/build72.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,360 copying publiforge/Static/Images/build72_over.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,363 copying publiforge/Static/Images/build96.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,365 copying publiforge/Static/Images/check.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,367 copying publiforge/Static/Images/close_dark.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,369 copying publiforge/Static/Images/close_light.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,371 copying publiforge/Static/Images/collapse_closed.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,373 copying publiforge/Static/Images/collapse_current_closed.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,375 copying publiforge/Static/Images/collapse_current_open.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,378 copying publiforge/Static/Images/collapse_open.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,379 copying publiforge/Static/Images/edit32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,381 copying publiforge/Static/Images/equal.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,383 copying publiforge/Static/Images/extractor.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,385 copying publiforge/Static/Images/extractor22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,388 copying publiforge/Static/Images/extractor32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,391 copying publiforge/Static/Images/flash_alert.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,394 copying publiforge/Static/Images/flash_info.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,397 copying publiforge/Static/Images/folder.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,400 copying publiforge/Static/Images/folder22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,403 copying publiforge/Static/Images/folder32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,406 copying publiforge/Static/Images/footer_top.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,410 copying publiforge/Static/Images/go_first.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,413 copying publiforge/Static/Images/go_first_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,416 copying publiforge/Static/Images/go_last.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,419 copying publiforge/Static/Images/go_last_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,422 copying publiforge/Static/Images/go_next.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,425 copying publiforge/Static/Images/go_next_file.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,429 copying publiforge/Static/Images/go_next_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,432 copying publiforge/Static/Images/go_next_search.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,435 copying publiforge/Static/Images/go_previous.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,438 copying publiforge/Static/Images/go_previous_file.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,441 copying publiforge/Static/Images/go_previous_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,445 copying publiforge/Static/Images/go_previous_search.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,448 copying publiforge/Static/Images/go_top.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,451 copying publiforge/Static/Images/go_top22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,454 copying publiforge/Static/Images/group.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,457 copying publiforge/Static/Images/group22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,460 copying publiforge/Static/Images/group32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,463 copying publiforge/Static/Images/history.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,467 copying publiforge/Static/Images/history22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,470 copying publiforge/Static/Images/history32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,473 copying publiforge/Static/Images/in_menu_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,477 copying publiforge/Static/Images/in_menu_on.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,480 copying publiforge/Static/Images/indexer.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,483 copying publiforge/Static/Images/indexer22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,486 copying publiforge/Static/Images/indexer32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,489 copying publiforge/Static/Images/info.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,491 copying publiforge/Static/Images/info22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,494 copying publiforge/Static/Images/info32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,496 copying publiforge/Static/Images/job.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,498 copying publiforge/Static/Images/job22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,501 copying publiforge/Static/Images/job32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,503 copying publiforge/Static/Images/left_title.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,505 copying publiforge/Static/Images/light_green.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,508 copying publiforge/Static/Images/light_grey.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,510 copying publiforge/Static/Images/light_red.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,513 copying publiforge/Static/Images/light_yellow.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,515 copying publiforge/Static/Images/link.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,517 copying publiforge/Static/Images/link22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,519 copying publiforge/Static/Images/link32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,522 copying publiforge/Static/Images/list_header.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,524 copying publiforge/Static/Images/log_download.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,526 copying publiforge/Static/Images/log_error.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,529 copying publiforge/Static/Images/log_info.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,531 copying publiforge/Static/Images/log_warning.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,533 copying publiforge/Static/Images/logout.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,536 copying publiforge/Static/Images/notfound.jpg -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,539 copying publiforge/Static/Images/open_false.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,541 copying publiforge/Static/Images/open_true.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,543 copying publiforge/Static/Images/opener22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,546 copying publiforge/Static/Images/opener32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,548 copying publiforge/Static/Images/overview_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,551 copying publiforge/Static/Images/overview_on.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,553 copying publiforge/Static/Images/pack.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,555 copying publiforge/Static/Images/pack22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,558 copying publiforge/Static/Images/pack32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,560 copying publiforge/Static/Images/pack72.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,563 copying publiforge/Static/Images/pack72_over.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,565 copying publiforge/Static/Images/pack96.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,568 copying publiforge/Static/Images/processing.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,571 copying publiforge/Static/Images/processing22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,573 copying publiforge/Static/Images/processing32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,576 copying publiforge/Static/Images/progress.gif -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,579 copying publiforge/Static/Images/project.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,581 copying publiforge/Static/Images/project22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,584 copying publiforge/Static/Images/project32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,586 copying publiforge/Static/Images/publiforge.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,589 copying publiforge/Static/Images/pyramid.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,591 copying publiforge/Static/Images/role.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,594 copying publiforge/Static/Images/role22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,596 copying publiforge/Static/Images/role32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,599 copying publiforge/Static/Images/search.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,601 copying publiforge/Static/Images/search22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,604 copying publiforge/Static/Images/search32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,606 copying publiforge/Static/Images/selection.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,609 copying publiforge/Static/Images/selection_remove_one.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,611 copying publiforge/Static/Images/selection_remove_sure.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,613 copying publiforge/Static/Images/sort_asc.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,616 copying publiforge/Static/Images/sort_desc.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,618 copying publiforge/Static/Images/sort_down.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,620 copying publiforge/Static/Images/sort_down_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,623 copying publiforge/Static/Images/sort_up.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,625 copying publiforge/Static/Images/sort_up_off.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,627 copying publiforge/Static/Images/storage.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,630 copying publiforge/Static/Images/storage22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,632 copying publiforge/Static/Images/storage32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,634 copying publiforge/Static/Images/tab.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,637 copying publiforge/Static/Images/task.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,639 copying publiforge/Static/Images/task22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,641 copying publiforge/Static/Images/task32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,644 copying publiforge/Static/Images/task72.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,646 copying publiforge/Static/Images/task72_over.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,649 copying publiforge/Static/Images/task96.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,652 copying publiforge/Static/Images/up.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,654 copying publiforge/Static/Images/user.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,656 copying publiforge/Static/Images/user22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,659 copying publiforge/Static/Images/user32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,661 copying publiforge/Static/Images/user_pre.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,663 copying publiforge/Static/Images/valid-xhtml.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,666 copying publiforge/Static/Images/value.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,668 copying publiforge/Static/Images/value22.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,671 copying publiforge/Static/Images/value32.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,673 copying publiforge/Static/Images/vcss.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,676 copying publiforge/Static/Images/wait_build.gif -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,678 copying publiforge/Static/Images/wait_slow.gif -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,681 copying publiforge/Static/Images/wait_synchro.gif -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,683 copying publiforge/Static/Images/wcag1aa.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images 2023-09-10T10:27:21,685 creating build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,686 copying publiforge/Static/Images/MimeTypes/css.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,689 copying publiforge/Static/Images/MimeTypes/csv.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,691 copying publiforge/Static/Images/MimeTypes/epub+zip.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,694 copying publiforge/Static/Images/MimeTypes/folder.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,696 copying publiforge/Static/Images/MimeTypes/font-woff.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,698 copying publiforge/Static/Images/MimeTypes/gif.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,701 copying publiforge/Static/Images/MimeTypes/html.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,703 copying publiforge/Static/Images/MimeTypes/indesign-idml.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,706 copying publiforge/Static/Images/MimeTypes/indesign-indd.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,708 copying publiforge/Static/Images/MimeTypes/javascript.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,711 copying publiforge/Static/Images/MimeTypes/jpeg.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,713 copying publiforge/Static/Images/MimeTypes/mp4.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,715 copying publiforge/Static/Images/MimeTypes/mpeg.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,718 copying publiforge/Static/Images/MimeTypes/msword.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,720 copying publiforge/Static/Images/MimeTypes/octet-stream.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,723 copying publiforge/Static/Images/MimeTypes/ogg.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,726 copying publiforge/Static/Images/MimeTypes/pdf.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,728 copying publiforge/Static/Images/MimeTypes/plain.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,731 copying publiforge/Static/Images/MimeTypes/png.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,733 copying publiforge/Static/Images/MimeTypes/postscript.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,735 copying publiforge/Static/Images/MimeTypes/relaxng.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,738 copying publiforge/Static/Images/MimeTypes/svg+xml.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,740 copying publiforge/Static/Images/MimeTypes/tiff.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,743 copying publiforge/Static/Images/MimeTypes/unknown.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,745 copying publiforge/Static/Images/MimeTypes/vnd.ms-excel.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,747 copying publiforge/Static/Images/MimeTypes/vnd.ms-opentype.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,749 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.spreadsheet.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,751 copying publiforge/Static/Images/MimeTypes/vnd.oasis.opendocument.text.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,753 copying publiforge/Static/Images/MimeTypes/x-msdos-program.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,754 copying publiforge/Static/Images/MimeTypes/x-msvideo.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,756 copying publiforge/Static/Images/MimeTypes/x-python.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,758 copying publiforge/Static/Images/MimeTypes/x-shockwave-flash.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,761 copying publiforge/Static/Images/MimeTypes/x-tar.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,763 copying publiforge/Static/Images/MimeTypes/x-wav.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,765 copying publiforge/Static/Images/MimeTypes/xml-dtd.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,767 copying publiforge/Static/Images/MimeTypes/xml.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,769 copying publiforge/Static/Images/MimeTypes/zip.png -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Images/MimeTypes 2023-09-10T10:27:21,771 creating build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,772 copying publiforge/Static/Js/base.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,775 copying publiforge/Static/Js/bld_progress.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,777 copying publiforge/Static/Js/bld_results.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,779 copying publiforge/Static/Js/bld_view.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,782 copying publiforge/Static/Js/codemirror.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,787 copying publiforge/Static/Js/codemirror4ini.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,789 copying publiforge/Static/Js/codemirror4xml.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,792 copying publiforge/Static/Js/codemirror_loader.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,794 copying publiforge/Static/Js/jquery.cookie.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,797 copying publiforge/Static/Js/jquery.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,800 copying publiforge/Static/Js/prc_edit.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,803 copying publiforge/Static/Js/stg_browse.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,805 copying publiforge/Static/Js/stg_edit.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,807 copying publiforge/Static/Js/stg_index.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,810 copying publiforge/Static/Js/tsk_index.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js 2023-09-10T10:27:21,811 creating build/lib.linux-armv7l-cpython-311/publiforge/Static/Js/Tests 2023-09-10T10:27:21,812 copying publiforge/Static/Js/Tests/index.html -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js/Tests 2023-09-10T10:27:21,815 copying publiforge/Static/Js/Tests/qunit.css -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js/Tests 2023-09-10T10:27:21,818 copying publiforge/Static/Js/Tests/qunit.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js/Tests 2023-09-10T10:27:21,822 copying publiforge/Static/Js/Tests/tests.js -> build/lib.linux-armv7l-cpython-311/publiforge/Static/Js/Tests 2023-09-10T10:27:21,825 creating build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,825 copying publiforge/Templates/base.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,828 copying publiforge/Templates/bld_launch.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,830 copying publiforge/Templates/bld_output.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,832 copying publiforge/Templates/bld_pack.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,834 copying publiforge/Templates/bld_processing.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,836 copying publiforge/Templates/bld_progress.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,838 copying publiforge/Templates/bld_results.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,841 copying publiforge/Templates/bld_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,843 copying publiforge/Templates/error.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,845 copying publiforge/Templates/fil_display.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,848 copying publiforge/Templates/fil_info.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,850 copying publiforge/Templates/fil_modify.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,852 copying publiforge/Templates/fil_search.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,855 copying publiforge/Templates/fil_vcs_params.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,857 copying publiforge/Templates/files_edit.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,859 copying publiforge/Templates/files_view.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,861 copying publiforge/Templates/flash.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,863 copying publiforge/Templates/grp_admin.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,866 copying publiforge/Templates/grp_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,868 copying publiforge/Templates/grp_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,870 copying publiforge/Templates/home.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,872 copying publiforge/Templates/idx_admin.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,875 copying publiforge/Templates/idx_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,877 copying publiforge/Templates/idx_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,879 copying publiforge/Templates/job_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,882 copying publiforge/Templates/job_index.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,884 copying publiforge/Templates/job_log.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,886 copying publiforge/Templates/job_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,888 copying publiforge/Templates/login.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,890 copying publiforge/Templates/maintenance.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,892 copying publiforge/Templates/mbr_edit.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,894 copying publiforge/Templates/mbr_groups_edit.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,896 copying publiforge/Templates/mbr_groups_paging.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,898 copying publiforge/Templates/mbr_groups_view.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,900 copying publiforge/Templates/mbr_paging.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,902 copying publiforge/Templates/mbr_view.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,904 copying publiforge/Templates/pck_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,906 copying publiforge/Templates/pck_events.macro.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,908 copying publiforge/Templates/pck_index.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,911 copying publiforge/Templates/pck_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,913 copying publiforge/Templates/prc_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,915 copying publiforge/Templates/prc_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,918 copying publiforge/Templates/prj_admin.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,920 copying publiforge/Templates/prj_dashboard.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,922 copying publiforge/Templates/prj_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,924 copying publiforge/Templates/prj_index.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,926 copying publiforge/Templates/prj_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,929 copying publiforge/Templates/rol_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,931 copying publiforge/Templates/rol_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,934 copying publiforge/Templates/sit_admin.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,936 copying publiforge/Templates/stg_admin.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,938 copying publiforge/Templates/stg_browse.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,941 copying publiforge/Templates/stg_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,944 copying publiforge/Templates/stg_index.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,946 copying publiforge/Templates/stg_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,949 copying publiforge/Templates/tsk_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,951 copying publiforge/Templates/tsk_index.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,954 copying publiforge/Templates/tsk_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,956 copying publiforge/Templates/usr_admin.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,959 copying publiforge/Templates/usr_edit.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,961 copying publiforge/Templates/usr_view.pt -> build/lib.linux-armv7l-cpython-311/publiforge/Templates 2023-09-10T10:27:21,964 copying publiforge/tests/test.ini -> build/lib.linux-armv7l-cpython-311/publiforge/tests 2023-09-10T10:27:21,966 creating build/lib.linux-armv7l-cpython-311/publiforge/tests/Data 2023-09-10T10:27:21,967 copying publiforge/tests/Data/processor.xml -> build/lib.linux-armv7l-cpython-311/publiforge/tests/Data 2023-09-10T10:27:21,969 copying publiforge/tests/Data/test.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/tests/Data 2023-09-10T10:27:21,971 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front 2023-09-10T10:27:21,972 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge 2023-09-10T10:27:21,973 copying publiforge/scaffolds/Front/PubliForge/development.ini_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge 2023-09-10T10:27:21,975 copying publiforge/scaffolds/Front/PubliForge/pf+package+.ini_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge 2023-09-10T10:27:21,978 copying publiforge/scaffolds/Front/PubliForge/pf+package+.wsgi_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge 2023-09-10T10:27:21,980 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration 2023-09-10T10:27:21,980 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Apache 2023-09-10T10:27:21,981 copying publiforge/scaffolds/Front/PubliForge/Configuration/Apache/+package+.publiforge.conf_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Apache 2023-09-10T10:27:21,984 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2023-09-10T10:27:21,985 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/hgwebdir.conf_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2023-09-10T10:27:21,987 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/hgwebdir.wsgi_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2023-09-10T10:27:21,989 copying publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial/users_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Mercurial 2023-09-10T10:27:21,991 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Projects 2023-09-10T10:27:21,992 copying publiforge/scaffolds/Front/PubliForge/Configuration/Projects/+pfproject_id+.pfprj.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Projects 2023-09-10T10:27:21,994 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2023-09-10T10:27:21,995 copying publiforge/scaffolds/Front/PubliForge/Configuration/Storages/+storage+.hg.pfstg.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2023-09-10T10:27:21,998 copying publiforge/scaffolds/Front/PubliForge/Configuration/Storages/+storage+.local.pfstg.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2023-09-10T10:27:22,000 copying publiforge/scaffolds/Front/PubliForge/Configuration/Storages/result.pfstg.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2023-09-10T10:27:22,002 copying publiforge/scaffolds/Front/PubliForge/Configuration/Storages/sandbox.pfstg.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Storages 2023-09-10T10:27:22,004 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Users 2023-09-10T10:27:22,005 copying publiforge/scaffolds/Front/PubliForge/Configuration/Users/+package+.pfusr.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Configuration/Users 2023-09-10T10:27:22,007 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Static 2023-09-10T10:27:22,008 copying publiforge/scaffolds/Front/PubliForge/Static/favicon.ico -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Static 2023-09-10T10:27:22,010 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Static/Css 2023-09-10T10:27:22,011 copying publiforge/scaffolds/Front/PubliForge/Static/Css/+package+.css_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Static/Css 2023-09-10T10:27:22,013 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Static/Images 2023-09-10T10:27:22,014 copying publiforge/scaffolds/Front/PubliForge/Static/Images/+package+.png -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/Front/PubliForge/Static/Images 2023-09-10T10:27:22,016 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme 2023-09-10T10:27:22,017 copying publiforge/scaffolds/LePrisme/+package+.pfprc.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme 2023-09-10T10:27:22,019 copying publiforge/scaffolds/LePrisme/leprisme.ini_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme 2023-09-10T10:27:22,021 copying publiforge/scaffolds/LePrisme/processor.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme 2023-09-10T10:27:22,023 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/Templates 2023-09-10T10:27:22,024 copying publiforge/scaffolds/LePrisme/Templates/dummy1.txt -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/Templates 2023-09-10T10:27:22,026 copying publiforge/scaffolds/LePrisme/Templates/dummy2.txt -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/Templates 2023-09-10T10:27:22,028 copying publiforge/scaffolds/LePrisme/Templates/dummy3.txt -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/Templates 2023-09-10T10:27:22,030 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/Variables 2023-09-10T10:27:22,031 copying publiforge/scaffolds/LePrisme/Variables/+package+.pfvar.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/Variables 2023-09-10T10:27:22,033 copying publiforge/scaffolds/LePrisme/Variables/+package+_available.pfvar.xml_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/Variables 2023-09-10T10:27:22,035 copying publiforge/scaffolds/LePrisme/Variables/+package+_module.pfvar.xml -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/Variables 2023-09-10T10:27:22,037 creating build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/lib 2023-09-10T10:27:22,038 copying publiforge/scaffolds/LePrisme/lib/__init__.py_tmpl -> build/lib.linux-armv7l-cpython-311/publiforge/scaffolds/LePrisme/lib 2023-09-10T10:27:22,040 copying publiforge/lib/rsync/_librsync.c -> build/lib.linux-armv7l-cpython-311/publiforge/lib/rsync 2023-09-10T10:27:22,053 running build_ext 2023-09-10T10:27:22,606 building 'publiforge.lib.rsync._librsync' extension 2023-09-10T10:27:22,607 creating build/temp.linux-armv7l-cpython-311 2023-09-10T10:27:22,608 creating build/temp.linux-armv7l-cpython-311/publiforge 2023-09-10T10:27:22,609 creating build/temp.linux-armv7l-cpython-311/publiforge/lib 2023-09-10T10:27:22,609 creating build/temp.linux-armv7l-cpython-311/publiforge/lib/rsync 2023-09-10T10:27:22,610 arm-linux-gnueabihf-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -I/usr/include/python3.11 -c publiforge/lib/rsync/_librsync.c -o build/temp.linux-armv7l-cpython-311/publiforge/lib/rsync/_librsync.o 2023-09-10T10:27:22,966 publiforge/lib/rsync/_librsync.c:26:10: fatal error: librsync.h: No such file or directory 2023-09-10T10:27:22,967 26 | #include 2023-09-10T10:27:22,968 | ^~~~~~~~~~~~ 2023-09-10T10:27:22,968 compilation terminated. 2023-09-10T10:27:22,970 error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1 2023-09-10T10:27:23,135 ERROR: [present-rich] python setup.py bdist_wheel exited with 1 2023-09-10T10:27:23,148 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2023-09-10T10:27:23,148 exec(compile('"'"''"'"''"'"' 2023-09-10T10:27:23,148 # This is -- a caller that pip uses to run setup.py 2023-09-10T10:27:23,148 # 2023-09-10T10:27:23,148 # - It imports setuptools before invoking setup.py, to enable projects that directly 2023-09-10T10:27:23,148 # import from `distutils.core` to work with newer packaging standards. 2023-09-10T10:27:23,148 # - It provides a clear error message when setuptools is not installed. 2023-09-10T10:27:23,148 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2023-09-10T10:27:23,148 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2023-09-10T10:27:23,148 # manifest_maker: standard file '"'"'-c'"'"' not found". 2023-09-10T10:27:23,148 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2023-09-10T10:27:23,148 import os, sys, tokenize 2023-09-10T10:27:23,148 2023-09-10T10:27:23,148 try: 2023-09-10T10:27:23,148 import setuptools 2023-09-10T10:27:23,148 except ImportError as error: 2023-09-10T10:27:23,148 print( 2023-09-10T10:27:23,148 "ERROR: Can not execute `setup.py` since setuptools is not available in " 2023-09-10T10:27:23,148 "the build environment.", 2023-09-10T10:27:23,148 file=sys.stderr, 2023-09-10T10:27:23,148 ) 2023-09-10T10:27:23,148 sys.exit(1) 2023-09-10T10:27:23,148 2023-09-10T10:27:23,148 __file__ = %r 2023-09-10T10:27:23,148 sys.argv[0] = __file__ 2023-09-10T10:27:23,148 2023-09-10T10:27:23,148 if os.path.exists(__file__): 2023-09-10T10:27:23,148 filename = __file__ 2023-09-10T10:27:23,148 with tokenize.open(__file__) as f: 2023-09-10T10:27:23,148 setup_py_code = f.read() 2023-09-10T10:27:23,148 else: 2023-09-10T10:27:23,148 filename = "" 2023-09-10T10:27:23,148 setup_py_code = "from setuptools import setup; setup()" 2023-09-10T10:27:23,148 2023-09-10T10:27:23,148 exec(compile(setup_py_code, filename, "exec")) 2023-09-10T10:27:23,148 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-znht63uh/publiforge_2a7b16393a8d4da68d908348b59ff7c1/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-c5rvjd6q[/] 2023-09-10T10:27:23,148 [bold magenta]cwd[/]: /tmp/pip-wheel-znht63uh/publiforge_2a7b16393a8d4da68d908348b59ff7c1/ 2023-09-10T10:27:23,149 Building wheel for publiforge (setup.py): finished with status 'error' 2023-09-10T10:27:23,150 ERROR: Failed building wheel for publiforge 2023-09-10T10:27:23,151 Running setup.py clean for publiforge 2023-09-10T10:27:23,152 Running command python setup.py clean 2023-09-10T10:27:23,671 /usr/local/lib/python3.11/dist-packages/setuptools/_distutils/dist.py:265: UserWarning: Unknown distribution option: 'message_extractors' 2023-09-10T10:27:23,671 warnings.warn(msg) 2023-09-10T10:27:24,468 running clean 2023-09-10T10:27:24,516 removing 'build/temp.linux-armv7l-cpython-311' (and everything under it) 2023-09-10T10:27:24,519 removing 'build/lib.linux-armv7l-cpython-311' (and everything under it) 2023-09-10T10:27:24,850 'build/bdist.linux-armv7l' does not exist -- can't clean it 2023-09-10T10:27:24,851 'build/scripts-3.11' does not exist -- can't clean it 2023-09-10T10:27:24,851 removing 'build' 2023-09-10T10:27:24,961 Failed to build publiforge 2023-09-10T10:27:24,962 ERROR: Failed to build one or more wheels 2023-09-10T10:27:24,964 Exception information: 2023-09-10T10:27:24,964 Traceback (most recent call last): 2023-09-10T10:27:24,964 File "/usr/local/lib/python3.11/dist-packages/pip/_internal/cli/base_command.py", line 180, in exc_logging_wrapper 2023-09-10T10:27:24,964 status = run_func(*args) 2023-09-10T10:27:24,964 ^^^^^^^^^^^^^^^ 2023-09-10T10:27:24,964 File "/usr/local/lib/python3.11/dist-packages/pip/_internal/cli/req_command.py", line 248, in wrapper 2023-09-10T10:27:24,964 return func(self, options, args) 2023-09-10T10:27:24,964 ^^^^^^^^^^^^^^^^^^^^^^^^^ 2023-09-10T10:27:24,964 File "/usr/local/lib/python3.11/dist-packages/pip/_internal/commands/wheel.py", line 181, in run 2023-09-10T10:27:24,964 raise CommandError("Failed to build one or more wheels") 2023-09-10T10:27:24,964 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2023-09-10T10:27:24,966 Removed build tracker: '/tmp/pip-build-tracker-6aunmirc'