2025-05-30T11:28:02,880 Created temporary directory: /tmp/pip-build-tracker-sbdk8obr 2025-05-30T11:28:02,881 Initialized build tracking at /tmp/pip-build-tracker-sbdk8obr 2025-05-30T11:28:02,882 Created build tracker: /tmp/pip-build-tracker-sbdk8obr 2025-05-30T11:28:02,882 Entered build tracker: /tmp/pip-build-tracker-sbdk8obr 2025-05-30T11:28:02,883 Created temporary directory: /tmp/pip-wheel-gh23j5uh 2025-05-30T11:28:02,887 Created temporary directory: /tmp/pip-ephem-wheel-cache-y85g4q_e 2025-05-30T11:28:02,943 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-05-30T11:28:02,945 2 location(s) to search for versions of plone-mls-core: 2025-05-30T11:28:02,945 * https://pypi.org/simple/plone-mls-core/ 2025-05-30T11:28:02,945 * https://www.piwheels.org/simple/plone-mls-core/ 2025-05-30T11:28:02,946 Fetching project page and analyzing links: https://pypi.org/simple/plone-mls-core/ 2025-05-30T11:28:02,947 Getting page https://pypi.org/simple/plone-mls-core/ 2025-05-30T11:28:02,949 Found index url https://pypi.org/simple/ 2025-05-30T11:28:03,177 Fetched page https://pypi.org/simple/plone-mls-core/ as application/vnd.pypi.simple.v1+json 2025-05-30T11:28:03,181 Found link https://files.pythonhosted.org/packages/1d/39/400116f3cc318a15025570b44d15cd63796538f72fb2d47d4741613e9911/plone.mls.core-0.4.1.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.4.1 2025-05-30T11:28:03,183 Found link https://files.pythonhosted.org/packages/c8/27/49ac4bea8bc6177d4d74e8bb8932cb160934f2bf1f8844d36dc296171e20/plone.mls.core-0.4.2.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.4.2 2025-05-30T11:28:03,184 Found link https://files.pythonhosted.org/packages/91/04/d300ab564a53fd90c319649289fcb8680c25461d3c34057a9f9847cc852b/plone.mls.core-0.5.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.5 2025-05-30T11:28:03,185 Found link https://files.pythonhosted.org/packages/07/7e/818e961c22f8aa9f71028a2540205c049a7bcdad0ec63435ab7c7d02717f/plone.mls.core-0.5.1.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.5.1 2025-05-30T11:28:03,186 Found link https://files.pythonhosted.org/packages/5c/20/3af9aace384118b79b0ec24f4f774521c9348915958aee2ecc5b3ca2ac5b/plone.mls.core-0.5.2.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.5.2 2025-05-30T11:28:03,187 Found link https://files.pythonhosted.org/packages/e6/28/502c563825a381362a362a497f73789cb2aff25c91336a91d5d5e5782e58/plone.mls.core-0.5.3.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.5.3 2025-05-30T11:28:03,188 Found link https://files.pythonhosted.org/packages/98/d6/c2e4a5b149a94b6f882429d1be0b412716a43d90a16ef4b77654189c63a3/plone.mls.core-0.5.4.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.5.4 2025-05-30T11:28:03,189 Found link https://files.pythonhosted.org/packages/0d/5a/c69bc28853b855e4db01d83309c447291dbcbcb0fb202f45d9e5fdec2be0/plone.mls.core-0.6.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.6 2025-05-30T11:28:03,190 Found link https://files.pythonhosted.org/packages/58/45/f47b5627191204775784107e36a53ccfa52b8b08780323982ff1c2a5a442/plone.mls.core-0.7.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.7 2025-05-30T11:28:03,191 Found link https://files.pythonhosted.org/packages/19/d3/4def5eb6ea16ae214c352cae5c04c0fd8f351db752a290408fab2592b9d4/plone.mls.core-0.7.1.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.7.1 2025-05-30T11:28:03,192 Found link https://files.pythonhosted.org/packages/aa/7a/b064dc8ec3c0072819af6f1cfb71e3babe096ccdac61e00d02151af48c4d/plone.mls.core-0.7.2.tar.gz (from https://pypi.org/simple/plone-mls-core/), version: 0.7.2 2025-05-30T11:28:03,193 Fetching project page and analyzing links: https://www.piwheels.org/simple/plone-mls-core/ 2025-05-30T11:28:03,194 Getting page https://www.piwheels.org/simple/plone-mls-core/ 2025-05-30T11:28:03,195 Found index url https://www.piwheels.org/simple/ 2025-05-30T11:28:03,361 WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:992)'))': /simple/plone-mls-core/ 2025-05-30T11:28:04,021 WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:992)'))': /simple/plone-mls-core/ 2025-05-30T11:28:05,193 WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:992)'))': /simple/plone-mls-core/ 2025-05-30T11:28:07,369 WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:992)'))': /simple/plone-mls-core/ 2025-05-30T11:28:11,542 WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:992)'))': /simple/plone-mls-core/ 2025-05-30T11:28:11,711 Could not fetch URL https://www.piwheels.org/simple/plone-mls-core/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='www.piwheels.org', port=443): Max retries exceeded with url: /simple/plone-mls-core/ (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:992)'))) - skipping 2025-05-30T11:28:11,713 Skipping link: not a file: https://www.piwheels.org/simple/plone-mls-core/ 2025-05-30T11:28:11,714 Skipping link: not a file: https://pypi.org/simple/plone-mls-core/ 2025-05-30T11:28:11,737 Given no hashes to check 1 links for project 'plone-mls-core': discarding no candidates 2025-05-30T11:28:11,739 Collecting plone-mls-core==0.7.2 2025-05-30T11:28:11,741 Created temporary directory: /tmp/pip-unpack-dr17to4w 2025-05-30T11:28:11,963 Downloading plone.mls.core-0.7.2.tar.gz (28 kB) 2025-05-30T11:28:12,151 Added plone-mls-core==0.7.2 from https://files.pythonhosted.org/packages/aa/7a/b064dc8ec3c0072819af6f1cfb71e3babe096ccdac61e00d02151af48c4d/plone.mls.core-0.7.2.tar.gz to build tracker '/tmp/pip-build-tracker-sbdk8obr' 2025-05-30T11:28:12,154 Running setup.py (path:/tmp/pip-wheel-gh23j5uh/plone-mls-core_b7b016272a764c2e82dbfd8c55171163/setup.py) egg_info for package plone-mls-core 2025-05-30T11:28:12,156 Created temporary directory: /tmp/pip-pip-egg-info-xzvub8na 2025-05-30T11:28:12,156 Preparing metadata (setup.py): started 2025-05-30T11:28:12,158 Running command python setup.py egg_info 2025-05-30T11:28:13,062 /usr/local/lib/python3.11/dist-packages/setuptools/dist.py:804: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. 2025-05-30T11:28:13,062 !! 2025-05-30T11:28:13,064 ******************************************************************************** 2025-05-30T11:28:13,064 Please replace its usage with implicit namespaces (PEP 420). 2025-05-30T11:28:13,066 See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. 2025-05-30T11:28:13,066 ******************************************************************************** 2025-05-30T11:28:13,068 !! 2025-05-30T11:28:13,068 ep.load()(self, ep.name, value) 2025-05-30T11:28:13,069 /usr/local/lib/python3.11/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-05-30T11:28:13,070 !! 2025-05-30T11:28:13,071 ******************************************************************************** 2025-05-30T11:28:13,072 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-05-30T11:28:13,073 License :: OSI Approved :: GNU General Public License v2 (GPLv2) 2025-05-30T11:28:13,074 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-05-30T11:28:13,074 ******************************************************************************** 2025-05-30T11:28:13,075 !! 2025-05-30T11:28:13,076 self._finalize_license_expression() 2025-05-30T11:28:13,097 running egg_info 2025-05-30T11:28:13,124 creating /tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info 2025-05-30T11:28:13,125 writing /tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/PKG-INFO 2025-05-30T11:28:13,130 writing dependency_links to /tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/dependency_links.txt 2025-05-30T11:28:13,131 writing entry points to /tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/entry_points.txt 2025-05-30T11:28:13,132 writing namespace_packages to /tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/namespace_packages.txt 2025-05-30T11:28:13,134 writing requirements to /tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/requires.txt 2025-05-30T11:28:13,135 writing top-level names to /tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/top_level.txt 2025-05-30T11:28:13,137 writing manifest file '/tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/SOURCES.txt' 2025-05-30T11:28:13,232 reading manifest file '/tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/SOURCES.txt' 2025-05-30T11:28:13,234 reading manifest template 'MANIFEST.in' 2025-05-30T11:28:13,257 warning: no previously-included files matching '*.pyc' found anywhere in distribution 2025-05-30T11:28:13,258 no previously-included directories found matching 'docs/build' 2025-05-30T11:28:13,264 writing manifest file '/tmp/pip-pip-egg-info-xzvub8na/plone.mls.core.egg-info/SOURCES.txt' 2025-05-30T11:28:13,374 Preparing metadata (setup.py): finished with status 'done' 2025-05-30T11:28:13,378 Source in /tmp/pip-wheel-gh23j5uh/plone-mls-core_b7b016272a764c2e82dbfd8c55171163 has version 0.7.2, which satisfies requirement plone-mls-core==0.7.2 from https://files.pythonhosted.org/packages/aa/7a/b064dc8ec3c0072819af6f1cfb71e3babe096ccdac61e00d02151af48c4d/plone.mls.core-0.7.2.tar.gz 2025-05-30T11:28:13,379 Removed plone-mls-core==0.7.2 from https://files.pythonhosted.org/packages/aa/7a/b064dc8ec3c0072819af6f1cfb71e3babe096ccdac61e00d02151af48c4d/plone.mls.core-0.7.2.tar.gz from build tracker '/tmp/pip-build-tracker-sbdk8obr' 2025-05-30T11:28:13,386 Created temporary directory: /tmp/pip-unpack-04x3mq3p 2025-05-30T11:28:13,387 Created temporary directory: /tmp/pip-unpack-mb1duu3p 2025-05-30T11:28:13,388 Building wheels for collected packages: plone-mls-core 2025-05-30T11:28:13,392 Created temporary directory: /tmp/pip-wheel-n3wxpcwm 2025-05-30T11:28:13,393 DEPRECATION: Building 'plone-mls-core' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'plone-mls-core'. Discussion can be found at https://github.com/pypa/pip/issues/6334 2025-05-30T11:28:13,395 Building wheel for plone-mls-core (setup.py): started 2025-05-30T11:28:13,396 Destination directory: /tmp/pip-wheel-n3wxpcwm 2025-05-30T11:28:13,397 Running command python setup.py bdist_wheel 2025-05-30T11:28:14,242 /usr/local/lib/python3.11/dist-packages/setuptools/dist.py:804: SetuptoolsDeprecationWarning: The namespace_packages parameter is deprecated. 2025-05-30T11:28:14,242 !! 2025-05-30T11:28:14,243 ******************************************************************************** 2025-05-30T11:28:14,244 Please replace its usage with implicit namespaces (PEP 420). 2025-05-30T11:28:14,246 See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages for details. 2025-05-30T11:28:14,246 ******************************************************************************** 2025-05-30T11:28:14,247 !! 2025-05-30T11:28:14,248 ep.load()(self, ep.name, value) 2025-05-30T11:28:14,248 /usr/local/lib/python3.11/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-05-30T11:28:14,249 !! 2025-05-30T11:28:14,250 ******************************************************************************** 2025-05-30T11:28:14,250 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-05-30T11:28:14,251 License :: OSI Approved :: GNU General Public License v2 (GPLv2) 2025-05-30T11:28:14,252 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-05-30T11:28:14,253 ******************************************************************************** 2025-05-30T11:28:14,254 !! 2025-05-30T11:28:14,254 self._finalize_license_expression() 2025-05-30T11:28:14,255 running bdist_wheel 2025-05-30T11:28:14,384 running build 2025-05-30T11:28:14,385 running build_py 2025-05-30T11:28:14,417 creating build/lib/plone 2025-05-30T11:28:14,419 copying src/plone/__init__.py -> build/lib/plone 2025-05-30T11:28:14,421 creating build/lib/plone/mls 2025-05-30T11:28:14,423 copying src/plone/mls/__init__.py -> build/lib/plone/mls 2025-05-30T11:28:14,426 creating build/lib/plone/mls/core 2025-05-30T11:28:14,427 copying src/plone/mls/core/__init__.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,430 copying src/plone/mls/core/i18n.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,433 copying src/plone/mls/core/api.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,435 copying src/plone/mls/core/navigation.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,438 copying src/plone/mls/core/interfaces.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,440 copying src/plone/mls/core/testing.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,442 copying src/plone/mls/core/setuphandlers.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,444 copying src/plone/mls/core/migration.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,446 copying src/plone/mls/core/config.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,448 copying src/plone/mls/core/utils.py -> build/lib/plone/mls/core 2025-05-30T11:28:14,451 creating build/lib/plone/mls/core/browser 2025-05-30T11:28:14,452 copying src/plone/mls/core/browser/__init__.py -> build/lib/plone/mls/core/browser 2025-05-30T11:28:14,455 copying src/plone/mls/core/browser/interfaces.py -> build/lib/plone/mls/core/browser 2025-05-30T11:28:14,457 copying src/plone/mls/core/browser/localconfig.py -> build/lib/plone/mls/core/browser 2025-05-30T11:28:14,460 copying src/plone/mls/core/browser/controlpanel.py -> build/lib/plone/mls/core/browser 2025-05-30T11:28:14,462 creating build/lib/plone/mls/core/tests 2025-05-30T11:28:14,464 copying src/plone/mls/core/tests/__init__.py -> build/lib/plone/mls/core/tests 2025-05-30T11:28:14,466 copying src/plone/mls/core/tests/test_controlpanel.py -> build/lib/plone/mls/core/tests 2025-05-30T11:28:14,468 copying src/plone/mls/core/tests/test_setup.py -> build/lib/plone/mls/core/tests 2025-05-30T11:28:14,471 copying src/plone/mls/core/tests/test_registry.py -> build/lib/plone/mls/core/tests 2025-05-30T11:28:14,472 running egg_info 2025-05-30T11:28:14,503 writing src/plone.mls.core.egg-info/PKG-INFO 2025-05-30T11:28:14,507 writing dependency_links to src/plone.mls.core.egg-info/dependency_links.txt 2025-05-30T11:28:14,509 writing entry points to src/plone.mls.core.egg-info/entry_points.txt 2025-05-30T11:28:14,510 writing namespace_packages to src/plone.mls.core.egg-info/namespace_packages.txt 2025-05-30T11:28:14,512 writing requirements to src/plone.mls.core.egg-info/requires.txt 2025-05-30T11:28:14,513 writing top-level names to src/plone.mls.core.egg-info/top_level.txt 2025-05-30T11:28:14,549 reading manifest file 'src/plone.mls.core.egg-info/SOURCES.txt' 2025-05-30T11:28:14,555 reading manifest template 'MANIFEST.in' 2025-05-30T11:28:14,571 warning: no previously-included files matching '*.pyc' found anywhere in distribution 2025-05-30T11:28:14,571 no previously-included directories found matching 'docs/build' 2025-05-30T11:28:14,578 writing manifest file 'src/plone.mls.core.egg-info/SOURCES.txt' 2025-05-30T11:28:14,580 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.browser.resources' is absent from the `packages` configuration. 2025-05-30T11:28:14,581 !! 2025-05-30T11:28:14,582 ******************************************************************************** 2025-05-30T11:28:14,583 ############################ 2025-05-30T11:28:14,583 # Package would be ignored # 2025-05-30T11:28:14,584 ############################ 2025-05-30T11:28:14,584 Python recognizes 'plone.mls.core.browser.resources' as an importable package[^1], 2025-05-30T11:28:14,585 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,586 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,586 package, please make sure that 'plone.mls.core.browser.resources' is explicitly added 2025-05-30T11:28:14,587 to the `packages` configuration field. 2025-05-30T11:28:14,588 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,589 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,590 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,591 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,592 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,593 If you don't want 'plone.mls.core.browser.resources' to be distributed and are 2025-05-30T11:28:14,593 already explicitly excluding 'plone.mls.core.browser.resources' via 2025-05-30T11:28:14,594 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,595 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,595 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,596 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,597 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,599 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,599 even if it does not contain any `.py` files. 2025-05-30T11:28:14,600 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,600 directory, all directories are treated like packages. 2025-05-30T11:28:14,601 ******************************************************************************** 2025-05-30T11:28:14,602 !! 2025-05-30T11:28:14,602 check.warn(importable) 2025-05-30T11:28:14,603 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales' is absent from the `packages` configuration. 2025-05-30T11:28:14,603 !! 2025-05-30T11:28:14,605 ******************************************************************************** 2025-05-30T11:28:14,605 ############################ 2025-05-30T11:28:14,606 # Package would be ignored # 2025-05-30T11:28:14,606 ############################ 2025-05-30T11:28:14,607 Python recognizes 'plone.mls.core.locales' as an importable package[^1], 2025-05-30T11:28:14,608 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,609 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,610 package, please make sure that 'plone.mls.core.locales' is explicitly added 2025-05-30T11:28:14,610 to the `packages` configuration field. 2025-05-30T11:28:14,611 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,611 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,612 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,613 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,614 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,615 If you don't want 'plone.mls.core.locales' to be distributed and are 2025-05-30T11:28:14,615 already explicitly excluding 'plone.mls.core.locales' via 2025-05-30T11:28:14,615 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,616 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,616 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,617 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,618 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,620 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,621 even if it does not contain any `.py` files. 2025-05-30T11:28:14,621 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,622 directory, all directories are treated like packages. 2025-05-30T11:28:14,623 ******************************************************************************** 2025-05-30T11:28:14,624 !! 2025-05-30T11:28:14,624 check.warn(importable) 2025-05-30T11:28:14,625 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.ar.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,626 !! 2025-05-30T11:28:14,627 ******************************************************************************** 2025-05-30T11:28:14,628 ############################ 2025-05-30T11:28:14,628 # Package would be ignored # 2025-05-30T11:28:14,629 ############################ 2025-05-30T11:28:14,630 Python recognizes 'plone.mls.core.locales.ar.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,631 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,632 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,632 package, please make sure that 'plone.mls.core.locales.ar.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,633 to the `packages` configuration field. 2025-05-30T11:28:14,634 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,634 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,635 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,636 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,637 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,638 If you don't want 'plone.mls.core.locales.ar.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,639 already explicitly excluding 'plone.mls.core.locales.ar.LC_MESSAGES' via 2025-05-30T11:28:14,640 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,640 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,641 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,642 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,643 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,644 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,644 even if it does not contain any `.py` files. 2025-05-30T11:28:14,645 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,645 directory, all directories are treated like packages. 2025-05-30T11:28:14,646 ******************************************************************************** 2025-05-30T11:28:14,646 !! 2025-05-30T11:28:14,647 check.warn(importable) 2025-05-30T11:28:14,647 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.cmn.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,648 !! 2025-05-30T11:28:14,649 ******************************************************************************** 2025-05-30T11:28:14,649 ############################ 2025-05-30T11:28:14,650 # Package would be ignored # 2025-05-30T11:28:14,650 ############################ 2025-05-30T11:28:14,650 Python recognizes 'plone.mls.core.locales.cmn.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,651 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,652 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,652 package, please make sure that 'plone.mls.core.locales.cmn.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,653 to the `packages` configuration field. 2025-05-30T11:28:14,654 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,654 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,655 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,656 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,657 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,658 If you don't want 'plone.mls.core.locales.cmn.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,659 already explicitly excluding 'plone.mls.core.locales.cmn.LC_MESSAGES' via 2025-05-30T11:28:14,660 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,660 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,661 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,662 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,663 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,665 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,665 even if it does not contain any `.py` files. 2025-05-30T11:28:14,666 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,666 directory, all directories are treated like packages. 2025-05-30T11:28:14,667 ******************************************************************************** 2025-05-30T11:28:14,668 !! 2025-05-30T11:28:14,669 check.warn(importable) 2025-05-30T11:28:14,669 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.de.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,670 !! 2025-05-30T11:28:14,671 ******************************************************************************** 2025-05-30T11:28:14,672 ############################ 2025-05-30T11:28:14,672 # Package would be ignored # 2025-05-30T11:28:14,673 ############################ 2025-05-30T11:28:14,673 Python recognizes 'plone.mls.core.locales.de.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,674 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,674 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,675 package, please make sure that 'plone.mls.core.locales.de.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,675 to the `packages` configuration field. 2025-05-30T11:28:14,676 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,677 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,677 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,678 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,679 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,680 If you don't want 'plone.mls.core.locales.de.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,680 already explicitly excluding 'plone.mls.core.locales.de.LC_MESSAGES' via 2025-05-30T11:28:14,681 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,681 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,682 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,683 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,684 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,686 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,687 even if it does not contain any `.py` files. 2025-05-30T11:28:14,688 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,689 directory, all directories are treated like packages. 2025-05-30T11:28:14,689 ******************************************************************************** 2025-05-30T11:28:14,691 !! 2025-05-30T11:28:14,692 check.warn(importable) 2025-05-30T11:28:14,692 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.en.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,693 !! 2025-05-30T11:28:14,694 ******************************************************************************** 2025-05-30T11:28:14,695 ############################ 2025-05-30T11:28:14,696 # Package would be ignored # 2025-05-30T11:28:14,696 ############################ 2025-05-30T11:28:14,697 Python recognizes 'plone.mls.core.locales.en.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,698 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,699 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,700 package, please make sure that 'plone.mls.core.locales.en.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,700 to the `packages` configuration field. 2025-05-30T11:28:14,702 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,702 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,703 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,705 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,706 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,707 If you don't want 'plone.mls.core.locales.en.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,707 already explicitly excluding 'plone.mls.core.locales.en.LC_MESSAGES' via 2025-05-30T11:28:14,708 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,708 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,709 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,710 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,711 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,713 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,713 even if it does not contain any `.py` files. 2025-05-30T11:28:14,714 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,714 directory, all directories are treated like packages. 2025-05-30T11:28:14,715 ******************************************************************************** 2025-05-30T11:28:14,716 !! 2025-05-30T11:28:14,717 check.warn(importable) 2025-05-30T11:28:14,717 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.es.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,718 !! 2025-05-30T11:28:14,719 ******************************************************************************** 2025-05-30T11:28:14,720 ############################ 2025-05-30T11:28:14,720 # Package would be ignored # 2025-05-30T11:28:14,721 ############################ 2025-05-30T11:28:14,721 Python recognizes 'plone.mls.core.locales.es.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,722 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,723 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,724 package, please make sure that 'plone.mls.core.locales.es.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,724 to the `packages` configuration field. 2025-05-30T11:28:14,725 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,726 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,726 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,728 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,729 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,730 If you don't want 'plone.mls.core.locales.es.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,731 already explicitly excluding 'plone.mls.core.locales.es.LC_MESSAGES' via 2025-05-30T11:28:14,731 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,732 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,733 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,734 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,735 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,737 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,738 even if it does not contain any `.py` files. 2025-05-30T11:28:14,739 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,740 directory, all directories are treated like packages. 2025-05-30T11:28:14,740 ******************************************************************************** 2025-05-30T11:28:14,741 !! 2025-05-30T11:28:14,742 check.warn(importable) 2025-05-30T11:28:14,742 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.et.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,743 !! 2025-05-30T11:28:14,744 ******************************************************************************** 2025-05-30T11:28:14,745 ############################ 2025-05-30T11:28:14,745 # Package would be ignored # 2025-05-30T11:28:14,746 ############################ 2025-05-30T11:28:14,746 Python recognizes 'plone.mls.core.locales.et.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,747 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,748 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,749 package, please make sure that 'plone.mls.core.locales.et.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,749 to the `packages` configuration field. 2025-05-30T11:28:14,751 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,751 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,752 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,753 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,754 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,755 If you don't want 'plone.mls.core.locales.et.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,756 already explicitly excluding 'plone.mls.core.locales.et.LC_MESSAGES' via 2025-05-30T11:28:14,756 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,757 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,758 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,759 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,760 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,762 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,762 even if it does not contain any `.py` files. 2025-05-30T11:28:14,763 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,764 directory, all directories are treated like packages. 2025-05-30T11:28:14,764 ******************************************************************************** 2025-05-30T11:28:14,766 !! 2025-05-30T11:28:14,766 check.warn(importable) 2025-05-30T11:28:14,767 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.fr.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,767 !! 2025-05-30T11:28:14,769 ******************************************************************************** 2025-05-30T11:28:14,769 ############################ 2025-05-30T11:28:14,770 # Package would be ignored # 2025-05-30T11:28:14,770 ############################ 2025-05-30T11:28:14,771 Python recognizes 'plone.mls.core.locales.fr.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,771 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,773 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,773 package, please make sure that 'plone.mls.core.locales.fr.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,774 to the `packages` configuration field. 2025-05-30T11:28:14,775 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,775 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,776 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,777 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,778 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,779 If you don't want 'plone.mls.core.locales.fr.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,780 already explicitly excluding 'plone.mls.core.locales.fr.LC_MESSAGES' via 2025-05-30T11:28:14,780 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,781 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,782 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,783 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,784 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,786 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,787 even if it does not contain any `.py` files. 2025-05-30T11:28:14,787 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,788 directory, all directories are treated like packages. 2025-05-30T11:28:14,789 ******************************************************************************** 2025-05-30T11:28:14,790 !! 2025-05-30T11:28:14,790 check.warn(importable) 2025-05-30T11:28:14,791 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.it.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,791 !! 2025-05-30T11:28:14,792 ******************************************************************************** 2025-05-30T11:28:14,793 ############################ 2025-05-30T11:28:14,794 # Package would be ignored # 2025-05-30T11:28:14,794 ############################ 2025-05-30T11:28:14,795 Python recognizes 'plone.mls.core.locales.it.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,795 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,797 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,797 package, please make sure that 'plone.mls.core.locales.it.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,798 to the `packages` configuration field. 2025-05-30T11:28:14,799 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,799 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,800 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,801 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,802 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,803 If you don't want 'plone.mls.core.locales.it.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,804 already explicitly excluding 'plone.mls.core.locales.it.LC_MESSAGES' via 2025-05-30T11:28:14,805 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,805 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,806 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,807 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,808 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,809 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,810 even if it does not contain any `.py` files. 2025-05-30T11:28:14,810 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,811 directory, all directories are treated like packages. 2025-05-30T11:28:14,811 ******************************************************************************** 2025-05-30T11:28:14,812 !! 2025-05-30T11:28:14,813 check.warn(importable) 2025-05-30T11:28:14,813 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.ja.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,814 !! 2025-05-30T11:28:14,815 ******************************************************************************** 2025-05-30T11:28:14,815 ############################ 2025-05-30T11:28:14,816 # Package would be ignored # 2025-05-30T11:28:14,816 ############################ 2025-05-30T11:28:14,816 Python recognizes 'plone.mls.core.locales.ja.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,817 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,818 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,819 package, please make sure that 'plone.mls.core.locales.ja.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,819 to the `packages` configuration field. 2025-05-30T11:28:14,820 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,821 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,821 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,822 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,824 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,825 If you don't want 'plone.mls.core.locales.ja.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,825 already explicitly excluding 'plone.mls.core.locales.ja.LC_MESSAGES' via 2025-05-30T11:28:14,826 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,827 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,827 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,828 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,830 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,831 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,832 even if it does not contain any `.py` files. 2025-05-30T11:28:14,832 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,833 directory, all directories are treated like packages. 2025-05-30T11:28:14,834 ******************************************************************************** 2025-05-30T11:28:14,835 !! 2025-05-30T11:28:14,835 check.warn(importable) 2025-05-30T11:28:14,836 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.pt.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,837 !! 2025-05-30T11:28:14,838 ******************************************************************************** 2025-05-30T11:28:14,838 ############################ 2025-05-30T11:28:14,839 # Package would be ignored # 2025-05-30T11:28:14,840 ############################ 2025-05-30T11:28:14,840 Python recognizes 'plone.mls.core.locales.pt.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,840 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,841 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,842 package, please make sure that 'plone.mls.core.locales.pt.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,842 to the `packages` configuration field. 2025-05-30T11:28:14,843 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,844 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,844 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,845 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,846 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,847 If you don't want 'plone.mls.core.locales.pt.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,848 already explicitly excluding 'plone.mls.core.locales.pt.LC_MESSAGES' via 2025-05-30T11:28:14,848 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,849 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,849 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,850 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,851 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,853 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,854 even if it does not contain any `.py` files. 2025-05-30T11:28:14,854 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,855 directory, all directories are treated like packages. 2025-05-30T11:28:14,855 ******************************************************************************** 2025-05-30T11:28:14,856 !! 2025-05-30T11:28:14,857 check.warn(importable) 2025-05-30T11:28:14,858 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.ru.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,858 !! 2025-05-30T11:28:14,859 ******************************************************************************** 2025-05-30T11:28:14,860 ############################ 2025-05-30T11:28:14,861 # Package would be ignored # 2025-05-30T11:28:14,861 ############################ 2025-05-30T11:28:14,862 Python recognizes 'plone.mls.core.locales.ru.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,862 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,863 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,864 package, please make sure that 'plone.mls.core.locales.ru.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,865 to the `packages` configuration field. 2025-05-30T11:28:14,866 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,866 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,867 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,869 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,870 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,871 If you don't want 'plone.mls.core.locales.ru.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,872 already explicitly excluding 'plone.mls.core.locales.ru.LC_MESSAGES' via 2025-05-30T11:28:14,872 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,873 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,873 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,874 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,875 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,877 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,877 even if it does not contain any `.py` files. 2025-05-30T11:28:14,878 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,878 directory, all directories are treated like packages. 2025-05-30T11:28:14,879 ******************************************************************************** 2025-05-30T11:28:14,880 !! 2025-05-30T11:28:14,880 check.warn(importable) 2025-05-30T11:28:14,881 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.vi.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,881 !! 2025-05-30T11:28:14,883 ******************************************************************************** 2025-05-30T11:28:14,883 ############################ 2025-05-30T11:28:14,884 # Package would be ignored # 2025-05-30T11:28:14,885 ############################ 2025-05-30T11:28:14,885 Python recognizes 'plone.mls.core.locales.vi.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,886 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,888 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,888 package, please make sure that 'plone.mls.core.locales.vi.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,889 to the `packages` configuration field. 2025-05-30T11:28:14,890 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,891 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,891 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,893 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,894 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,895 If you don't want 'plone.mls.core.locales.vi.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,895 already explicitly excluding 'plone.mls.core.locales.vi.LC_MESSAGES' via 2025-05-30T11:28:14,896 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,897 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,897 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,899 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,900 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,902 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,903 even if it does not contain any `.py` files. 2025-05-30T11:28:14,903 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,904 directory, all directories are treated like packages. 2025-05-30T11:28:14,905 ******************************************************************************** 2025-05-30T11:28:14,906 !! 2025-05-30T11:28:14,906 check.warn(importable) 2025-05-30T11:28:14,907 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,907 !! 2025-05-30T11:28:14,908 ******************************************************************************** 2025-05-30T11:28:14,909 ############################ 2025-05-30T11:28:14,909 # Package would be ignored # 2025-05-30T11:28:14,910 ############################ 2025-05-30T11:28:14,910 Python recognizes 'plone.mls.core.locales.vi_VN.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,911 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,912 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,912 package, please make sure that 'plone.mls.core.locales.vi_VN.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,913 to the `packages` configuration field. 2025-05-30T11:28:14,914 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,914 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,915 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,916 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,917 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,918 If you don't want 'plone.mls.core.locales.vi_VN.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,919 already explicitly excluding 'plone.mls.core.locales.vi_VN.LC_MESSAGES' via 2025-05-30T11:28:14,919 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,920 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,921 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,922 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,923 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,925 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,926 even if it does not contain any `.py` files. 2025-05-30T11:28:14,926 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,927 directory, all directories are treated like packages. 2025-05-30T11:28:14,927 ******************************************************************************** 2025-05-30T11:28:14,929 !! 2025-05-30T11:28:14,929 check.warn(importable) 2025-05-30T11:28:14,930 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.zh.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,930 !! 2025-05-30T11:28:14,932 ******************************************************************************** 2025-05-30T11:28:14,932 ############################ 2025-05-30T11:28:14,933 # Package would be ignored # 2025-05-30T11:28:14,934 ############################ 2025-05-30T11:28:14,934 Python recognizes 'plone.mls.core.locales.zh.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,935 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,937 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,937 package, please make sure that 'plone.mls.core.locales.zh.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,938 to the `packages` configuration field. 2025-05-30T11:28:14,939 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,939 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,939 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,940 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,941 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,942 If you don't want 'plone.mls.core.locales.zh.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,942 already explicitly excluding 'plone.mls.core.locales.zh.LC_MESSAGES' via 2025-05-30T11:28:14,943 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,943 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,944 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,945 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,945 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,947 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,947 even if it does not contain any `.py` files. 2025-05-30T11:28:14,948 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,948 directory, all directories are treated like packages. 2025-05-30T11:28:14,949 ******************************************************************************** 2025-05-30T11:28:14,950 !! 2025-05-30T11:28:14,951 check.warn(importable) 2025-05-30T11:28:14,951 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.locales.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. 2025-05-30T11:28:14,952 !! 2025-05-30T11:28:14,953 ******************************************************************************** 2025-05-30T11:28:14,954 ############################ 2025-05-30T11:28:14,955 # Package would be ignored # 2025-05-30T11:28:14,955 ############################ 2025-05-30T11:28:14,956 Python recognizes 'plone.mls.core.locales.zh_TW.LC_MESSAGES' as an importable package[^1], 2025-05-30T11:28:14,956 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,958 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,958 package, please make sure that 'plone.mls.core.locales.zh_TW.LC_MESSAGES' is explicitly added 2025-05-30T11:28:14,959 to the `packages` configuration field. 2025-05-30T11:28:14,960 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,960 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,961 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,962 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,963 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,964 If you don't want 'plone.mls.core.locales.zh_TW.LC_MESSAGES' to be distributed and are 2025-05-30T11:28:14,965 already explicitly excluding 'plone.mls.core.locales.zh_TW.LC_MESSAGES' via 2025-05-30T11:28:14,965 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,966 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,967 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,968 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,968 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,970 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,970 even if it does not contain any `.py` files. 2025-05-30T11:28:14,971 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,971 directory, all directories are treated like packages. 2025-05-30T11:28:14,971 ******************************************************************************** 2025-05-30T11:28:14,972 !! 2025-05-30T11:28:14,973 check.warn(importable) 2025-05-30T11:28:14,973 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.profiles.base' is absent from the `packages` configuration. 2025-05-30T11:28:14,974 !! 2025-05-30T11:28:14,975 ******************************************************************************** 2025-05-30T11:28:14,975 ############################ 2025-05-30T11:28:14,975 # Package would be ignored # 2025-05-30T11:28:14,976 ############################ 2025-05-30T11:28:14,976 Python recognizes 'plone.mls.core.profiles.base' as an importable package[^1], 2025-05-30T11:28:14,977 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:14,978 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:14,978 package, please make sure that 'plone.mls.core.profiles.base' is explicitly added 2025-05-30T11:28:14,979 to the `packages` configuration field. 2025-05-30T11:28:14,980 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:14,981 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:14,981 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:14,983 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:14,984 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:14,985 If you don't want 'plone.mls.core.profiles.base' to be distributed and are 2025-05-30T11:28:14,986 already explicitly excluding 'plone.mls.core.profiles.base' via 2025-05-30T11:28:14,986 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:14,987 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:14,988 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:14,989 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:14,990 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:14,992 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:14,992 even if it does not contain any `.py` files. 2025-05-30T11:28:14,993 On the other hand, currently there is no concept of package data 2025-05-30T11:28:14,994 directory, all directories are treated like packages. 2025-05-30T11:28:14,994 ******************************************************************************** 2025-05-30T11:28:14,995 !! 2025-05-30T11:28:14,996 check.warn(importable) 2025-05-30T11:28:14,997 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.profiles.plone4' is absent from the `packages` configuration. 2025-05-30T11:28:14,997 !! 2025-05-30T11:28:14,999 ******************************************************************************** 2025-05-30T11:28:14,999 ############################ 2025-05-30T11:28:14,999 # Package would be ignored # 2025-05-30T11:28:15,000 ############################ 2025-05-30T11:28:15,000 Python recognizes 'plone.mls.core.profiles.plone4' as an importable package[^1], 2025-05-30T11:28:15,001 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:15,002 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:15,002 package, please make sure that 'plone.mls.core.profiles.plone4' is explicitly added 2025-05-30T11:28:15,003 to the `packages` configuration field. 2025-05-30T11:28:15,004 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:15,004 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:15,004 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:15,005 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:15,006 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:15,007 If you don't want 'plone.mls.core.profiles.plone4' to be distributed and are 2025-05-30T11:28:15,008 already explicitly excluding 'plone.mls.core.profiles.plone4' via 2025-05-30T11:28:15,008 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:15,009 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:15,010 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:15,011 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:15,012 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:15,014 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:15,014 even if it does not contain any `.py` files. 2025-05-30T11:28:15,015 On the other hand, currently there is no concept of package data 2025-05-30T11:28:15,015 directory, all directories are treated like packages. 2025-05-30T11:28:15,016 ******************************************************************************** 2025-05-30T11:28:15,017 !! 2025-05-30T11:28:15,017 check.warn(importable) 2025-05-30T11:28:15,018 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.profiles.plone5' is absent from the `packages` configuration. 2025-05-30T11:28:15,019 !! 2025-05-30T11:28:15,020 ******************************************************************************** 2025-05-30T11:28:15,020 ############################ 2025-05-30T11:28:15,021 # Package would be ignored # 2025-05-30T11:28:15,021 ############################ 2025-05-30T11:28:15,022 Python recognizes 'plone.mls.core.profiles.plone5' as an importable package[^1], 2025-05-30T11:28:15,023 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:15,024 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:15,024 package, please make sure that 'plone.mls.core.profiles.plone5' is explicitly added 2025-05-30T11:28:15,025 to the `packages` configuration field. 2025-05-30T11:28:15,026 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:15,026 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:15,027 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:15,028 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:15,029 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:15,030 If you don't want 'plone.mls.core.profiles.plone5' to be distributed and are 2025-05-30T11:28:15,031 already explicitly excluding 'plone.mls.core.profiles.plone5' via 2025-05-30T11:28:15,031 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:15,031 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:15,032 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:15,033 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:15,034 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:15,036 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:15,036 even if it does not contain any `.py` files. 2025-05-30T11:28:15,037 On the other hand, currently there is no concept of package data 2025-05-30T11:28:15,037 directory, all directories are treated like packages. 2025-05-30T11:28:15,038 ******************************************************************************** 2025-05-30T11:28:15,039 !! 2025-05-30T11:28:15,039 check.warn(importable) 2025-05-30T11:28:15,040 /usr/local/lib/python3.11/dist-packages/setuptools/command/build_py.py:212: _Warning: Package 'plone.mls.core.profiles' is absent from the `packages` configuration. 2025-05-30T11:28:15,040 !! 2025-05-30T11:28:15,042 ******************************************************************************** 2025-05-30T11:28:15,042 ############################ 2025-05-30T11:28:15,043 # Package would be ignored # 2025-05-30T11:28:15,043 ############################ 2025-05-30T11:28:15,044 Python recognizes 'plone.mls.core.profiles' as an importable package[^1], 2025-05-30T11:28:15,045 but it is absent from setuptools' `packages` configuration. 2025-05-30T11:28:15,046 This leads to an ambiguous overall configuration. If you want to distribute this 2025-05-30T11:28:15,046 package, please make sure that 'plone.mls.core.profiles' is explicitly added 2025-05-30T11:28:15,047 to the `packages` configuration field. 2025-05-30T11:28:15,048 Alternatively, you can also rely on setuptools' discovery methods 2025-05-30T11:28:15,049 (for example by using `find_namespace_packages(...)`/`find_namespace:` 2025-05-30T11:28:15,049 instead of `find_packages(...)`/`find:`). 2025-05-30T11:28:15,051 You can read more about "package discovery" on setuptools documentation page: 2025-05-30T11:28:15,052 - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html 2025-05-30T11:28:15,053 If you don't want 'plone.mls.core.profiles' to be distributed and are 2025-05-30T11:28:15,053 already explicitly excluding 'plone.mls.core.profiles' via 2025-05-30T11:28:15,054 `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, 2025-05-30T11:28:15,055 you can try to use `exclude_package_data`, or `include-package-data=False` in 2025-05-30T11:28:15,055 combination with a more fine grained `package-data` configuration. 2025-05-30T11:28:15,057 You can read more about "package data files" on setuptools documentation page: 2025-05-30T11:28:15,058 - https://setuptools.pypa.io/en/latest/userguide/datafiles.html 2025-05-30T11:28:15,060 [^1]: For Python, any directory (with suitable naming) can be imported, 2025-05-30T11:28:15,060 even if it does not contain any `.py` files. 2025-05-30T11:28:15,061 On the other hand, currently there is no concept of package data 2025-05-30T11:28:15,061 directory, all directories are treated like packages. 2025-05-30T11:28:15,062 ******************************************************************************** 2025-05-30T11:28:15,063 !! 2025-05-30T11:28:15,064 check.warn(importable) 2025-05-30T11:28:15,064 copying src/plone/mls/core/configure.zcml -> build/lib/plone/mls/core 2025-05-30T11:28:15,065 copying src/plone/mls/core/permissions.zcml -> build/lib/plone/mls/core 2025-05-30T11:28:15,065 copying src/plone/mls/core/profiles.zcml -> build/lib/plone/mls/core 2025-05-30T11:28:15,066 creating build/lib/plone/mls/core/locales 2025-05-30T11:28:15,066 copying src/plone/mls/core/locales/manual.pot -> build/lib/plone/mls/core/locales 2025-05-30T11:28:15,067 copying src/plone/mls/core/locales/plone.mls.core.pot -> build/lib/plone/mls/core/locales 2025-05-30T11:28:15,067 creating build/lib/plone/mls/core/locales/ar/LC_MESSAGES 2025-05-30T11:28:15,068 copying src/plone/mls/core/locales/ar/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/ar/LC_MESSAGES 2025-05-30T11:28:15,069 creating build/lib/plone/mls/core/locales/cmn/LC_MESSAGES 2025-05-30T11:28:15,069 copying src/plone/mls/core/locales/cmn/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/cmn/LC_MESSAGES 2025-05-30T11:28:15,070 creating build/lib/plone/mls/core/locales/de/LC_MESSAGES 2025-05-30T11:28:15,070 copying src/plone/mls/core/locales/de/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/de/LC_MESSAGES 2025-05-30T11:28:15,071 creating build/lib/plone/mls/core/locales/en/LC_MESSAGES 2025-05-30T11:28:15,071 copying src/plone/mls/core/locales/en/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/en/LC_MESSAGES 2025-05-30T11:28:15,072 creating build/lib/plone/mls/core/locales/es/LC_MESSAGES 2025-05-30T11:28:15,073 copying src/plone/mls/core/locales/es/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/es/LC_MESSAGES 2025-05-30T11:28:15,073 creating build/lib/plone/mls/core/locales/et/LC_MESSAGES 2025-05-30T11:28:15,074 copying src/plone/mls/core/locales/et/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/et/LC_MESSAGES 2025-05-30T11:28:15,074 creating build/lib/plone/mls/core/locales/fr/LC_MESSAGES 2025-05-30T11:28:15,075 copying src/plone/mls/core/locales/fr/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/fr/LC_MESSAGES 2025-05-30T11:28:15,076 creating build/lib/plone/mls/core/locales/it/LC_MESSAGES 2025-05-30T11:28:15,076 copying src/plone/mls/core/locales/it/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/it/LC_MESSAGES 2025-05-30T11:28:15,077 creating build/lib/plone/mls/core/locales/ja/LC_MESSAGES 2025-05-30T11:28:15,077 copying src/plone/mls/core/locales/ja/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/ja/LC_MESSAGES 2025-05-30T11:28:15,078 creating build/lib/plone/mls/core/locales/pt/LC_MESSAGES 2025-05-30T11:28:15,079 copying src/plone/mls/core/locales/pt/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/pt/LC_MESSAGES 2025-05-30T11:28:15,079 creating build/lib/plone/mls/core/locales/ru/LC_MESSAGES 2025-05-30T11:28:15,080 copying src/plone/mls/core/locales/ru/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/ru/LC_MESSAGES 2025-05-30T11:28:15,080 creating build/lib/plone/mls/core/locales/vi/LC_MESSAGES 2025-05-30T11:28:15,081 copying src/plone/mls/core/locales/vi/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/vi/LC_MESSAGES 2025-05-30T11:28:15,082 creating build/lib/plone/mls/core/locales/vi_VN/LC_MESSAGES 2025-05-30T11:28:15,082 copying src/plone/mls/core/locales/vi_VN/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/vi_VN/LC_MESSAGES 2025-05-30T11:28:15,083 creating build/lib/plone/mls/core/locales/zh/LC_MESSAGES 2025-05-30T11:28:15,083 copying src/plone/mls/core/locales/zh/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/zh/LC_MESSAGES 2025-05-30T11:28:15,084 creating build/lib/plone/mls/core/locales/zh_TW/LC_MESSAGES 2025-05-30T11:28:15,085 copying src/plone/mls/core/locales/zh_TW/LC_MESSAGES/plone.mls.core.po -> build/lib/plone/mls/core/locales/zh_TW/LC_MESSAGES 2025-05-30T11:28:15,085 creating build/lib/plone/mls/core/profiles/base 2025-05-30T11:28:15,086 copying src/plone/mls/core/profiles/base/metadata.xml -> build/lib/plone/mls/core/profiles/base 2025-05-30T11:28:15,086 creating build/lib/plone/mls/core/profiles/plone4 2025-05-30T11:28:15,087 copying src/plone/mls/core/profiles/plone4/actions.xml -> build/lib/plone/mls/core/profiles/plone4 2025-05-30T11:28:15,087 copying src/plone/mls/core/profiles/plone4/browserlayer.xml -> build/lib/plone/mls/core/profiles/plone4 2025-05-30T11:28:15,088 copying src/plone/mls/core/profiles/plone4/jsregistry.xml -> build/lib/plone/mls/core/profiles/plone4 2025-05-30T11:28:15,088 copying src/plone/mls/core/profiles/plone4/metadata.xml -> build/lib/plone/mls/core/profiles/plone4 2025-05-30T11:28:15,089 copying src/plone/mls/core/profiles/plone4/registry.xml -> build/lib/plone/mls/core/profiles/plone4 2025-05-30T11:28:15,089 creating build/lib/plone/mls/core/profiles/plone5 2025-05-30T11:28:15,090 copying src/plone/mls/core/profiles/plone5/actions.xml -> build/lib/plone/mls/core/profiles/plone5 2025-05-30T11:28:15,090 copying src/plone/mls/core/profiles/plone5/browserlayer.xml -> build/lib/plone/mls/core/profiles/plone5 2025-05-30T11:28:15,091 copying src/plone/mls/core/profiles/plone5/metadata.xml -> build/lib/plone/mls/core/profiles/plone5 2025-05-30T11:28:15,091 copying src/plone/mls/core/profiles/plone5/registry.xml -> build/lib/plone/mls/core/profiles/plone5 2025-05-30T11:28:15,092 creating build/lib/plone/mls/core/profiles/uninstall-base 2025-05-30T11:28:15,092 copying src/plone/mls/core/profiles/uninstall-base/import_steps.xml -> build/lib/plone/mls/core/profiles/uninstall-base 2025-05-30T11:28:15,093 copying src/plone/mls/core/profiles/uninstall-base/plone.mls.core_uninstall.txt -> build/lib/plone/mls/core/profiles/uninstall-base 2025-05-30T11:28:15,093 copying src/plone/mls/core/profiles/uninstall-base/registry.xml -> build/lib/plone/mls/core/profiles/uninstall-base 2025-05-30T11:28:15,094 creating build/lib/plone/mls/core/profiles/uninstall-plone4 2025-05-30T11:28:15,095 copying src/plone/mls/core/profiles/uninstall-plone4/metadata.xml -> build/lib/plone/mls/core/profiles/uninstall-plone4 2025-05-30T11:28:15,095 creating build/lib/plone/mls/core/profiles/uninstall-plone5 2025-05-30T11:28:15,096 copying src/plone/mls/core/profiles/uninstall-plone5/metadata.xml -> build/lib/plone/mls/core/profiles/uninstall-plone5 2025-05-30T11:28:15,096 copying src/plone/mls/core/browser/configure.zcml -> build/lib/plone/mls/core/browser 2025-05-30T11:28:15,097 creating build/lib/plone/mls/core/browser/resources 2025-05-30T11:28:15,098 copying src/plone/mls/core/browser/resources/icon.png -> build/lib/plone/mls/core/browser/resources 2025-05-30T11:28:15,098 copying src/plone/mls/core/browser/resources/plone_mls_core.js -> build/lib/plone/mls/core/browser/resources 2025-05-30T11:28:15,099 /usr/local/lib/python3.11/dist-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated. 2025-05-30T11:28:15,100 !! 2025-05-30T11:28:15,101 ******************************************************************************** 2025-05-30T11:28:15,101 Please avoid running ``setup.py`` directly. 2025-05-30T11:28:15,102 Instead, use pypa/build, pypa/installer or other 2025-05-30T11:28:15,103 standards-based tools. 2025-05-30T11:28:15,104 By 2025-Oct-31, you need to update your project and remove deprecated calls 2025-05-30T11:28:15,105 or your builds will no longer be supported. 2025-05-30T11:28:15,106 See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. 2025-05-30T11:28:15,106 ******************************************************************************** 2025-05-30T11:28:15,107 !! 2025-05-30T11:28:15,108 self.initialize_options() 2025-05-30T11:28:15,109 installing to build/bdist.linux-armv7l/wheel 2025-05-30T11:28:15,110 running install 2025-05-30T11:28:15,110 running install_lib 2025-05-30T11:28:15,111 Skipping installation of build/bdist.linux-armv7l/wheel/./plone/__init__.py (namespace package) 2025-05-30T11:28:15,111 Skipping installation of build/bdist.linux-armv7l/wheel/./plone/mls/__init__.py (namespace package) 2025-05-30T11:28:15,112 copying plone/mls/core/__init__.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,112 copying plone/mls/core/i18n.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,113 copying plone/mls/core/api.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,113 copying plone/mls/core/navigation.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,114 copying plone/mls/core/interfaces.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,114 copying plone/mls/core/profiles.zcml -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,115 copying plone/mls/core/testing.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,115 copying plone/mls/core/configure.zcml -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,116 copying plone/mls/core/setuphandlers.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,117 copying plone/mls/core/migration.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,117 copying plone/mls/core/config.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,118 copying plone/mls/core/utils.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,118 copying plone/mls/core/permissions.zcml -> build/bdist.linux-armv7l/wheel/./plone/mls/core 2025-05-30T11:28:15,119 copying plone/mls/core/profiles/plone4/registry.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone4 2025-05-30T11:28:15,120 copying plone/mls/core/profiles/plone4/jsregistry.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone4 2025-05-30T11:28:15,120 copying plone/mls/core/profiles/plone4/browserlayer.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone4 2025-05-30T11:28:15,121 copying plone/mls/core/profiles/plone4/actions.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone4 2025-05-30T11:28:15,122 copying plone/mls/core/profiles/plone4/metadata.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone4 2025-05-30T11:28:15,122 copying plone/mls/core/profiles/uninstall-base/registry.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/uninstall-base 2025-05-30T11:28:15,123 copying plone/mls/core/profiles/uninstall-base/import_steps.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/uninstall-base 2025-05-30T11:28:15,123 copying plone/mls/core/profiles/uninstall-base/plone.mls.core_uninstall.txt -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/uninstall-base 2025-05-30T11:28:15,124 copying plone/mls/core/profiles/uninstall-plone5/metadata.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/uninstall-plone5 2025-05-30T11:28:15,125 copying plone/mls/core/profiles/plone5/registry.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone5 2025-05-30T11:28:15,125 copying plone/mls/core/profiles/plone5/browserlayer.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone5 2025-05-30T11:28:15,126 copying plone/mls/core/profiles/plone5/actions.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone5 2025-05-30T11:28:15,126 copying plone/mls/core/profiles/plone5/metadata.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/plone5 2025-05-30T11:28:15,127 copying plone/mls/core/profiles/base/metadata.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/base 2025-05-30T11:28:15,128 copying plone/mls/core/profiles/uninstall-plone4/metadata.xml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/profiles/uninstall-plone4 2025-05-30T11:28:15,129 copying plone/mls/core/browser/__init__.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core/browser 2025-05-30T11:28:15,130 copying plone/mls/core/browser/interfaces.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core/browser 2025-05-30T11:28:15,130 copying plone/mls/core/browser/configure.zcml -> build/bdist.linux-armv7l/wheel/./plone/mls/core/browser 2025-05-30T11:28:15,131 copying plone/mls/core/browser/localconfig.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core/browser 2025-05-30T11:28:15,131 copying plone/mls/core/browser/controlpanel.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core/browser 2025-05-30T11:28:15,135 copying plone/mls/core/browser/resources/icon.png -> build/bdist.linux-armv7l/wheel/./plone/mls/core/browser/resources 2025-05-30T11:28:15,137 copying plone/mls/core/browser/resources/plone_mls_core.js -> build/bdist.linux-armv7l/wheel/./plone/mls/core/browser/resources 2025-05-30T11:28:15,141 copying plone/mls/core/tests/__init__.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core/tests 2025-05-30T11:28:15,144 copying plone/mls/core/tests/test_controlpanel.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core/tests 2025-05-30T11:28:15,146 copying plone/mls/core/tests/test_setup.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core/tests 2025-05-30T11:28:15,149 copying plone/mls/core/tests/test_registry.py -> build/bdist.linux-armv7l/wheel/./plone/mls/core/tests 2025-05-30T11:28:15,152 copying plone/mls/core/locales/plone.mls.core.pot -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales 2025-05-30T11:28:15,155 copying plone/mls/core/locales/manual.pot -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales 2025-05-30T11:28:15,159 copying plone/mls/core/locales/et/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/et/LC_MESSAGES 2025-05-30T11:28:15,165 copying plone/mls/core/locales/vi/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/vi/LC_MESSAGES 2025-05-30T11:28:15,170 copying plone/mls/core/locales/ar/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/ar/LC_MESSAGES 2025-05-30T11:28:15,175 copying plone/mls/core/locales/ru/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/ru/LC_MESSAGES 2025-05-30T11:28:15,181 copying plone/mls/core/locales/es/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/es/LC_MESSAGES 2025-05-30T11:28:15,186 copying plone/mls/core/locales/fr/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/fr/LC_MESSAGES 2025-05-30T11:28:15,192 copying plone/mls/core/locales/zh_TW/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/zh_TW/LC_MESSAGES 2025-05-30T11:28:15,197 copying plone/mls/core/locales/it/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/it/LC_MESSAGES 2025-05-30T11:28:15,203 copying plone/mls/core/locales/en/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/en/LC_MESSAGES 2025-05-30T11:28:15,208 copying plone/mls/core/locales/zh/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/zh/LC_MESSAGES 2025-05-30T11:28:15,213 copying plone/mls/core/locales/ja/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/ja/LC_MESSAGES 2025-05-30T11:28:15,219 copying plone/mls/core/locales/de/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/de/LC_MESSAGES 2025-05-30T11:28:15,224 copying plone/mls/core/locales/vi_VN/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/vi_VN/LC_MESSAGES 2025-05-30T11:28:15,230 copying plone/mls/core/locales/cmn/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/cmn/LC_MESSAGES 2025-05-30T11:28:15,235 copying plone/mls/core/locales/pt/LC_MESSAGES/plone.mls.core.po -> build/bdist.linux-armv7l/wheel/./plone/mls/core/locales/pt/LC_MESSAGES 2025-05-30T11:28:15,240 running install_egg_info 2025-05-30T11:28:15,276 Copying src/plone.mls.core.egg-info to build/bdist.linux-armv7l/wheel/./plone.mls.core-0.7.2-py3.11.egg-info 2025-05-30T11:28:15,292 Installing build/bdist.linux-armv7l/wheel/./plone.mls.core-0.7.2-py3.11-nspkg.pth 2025-05-30T11:28:15,293 running install_scripts 2025-05-30T11:28:15,309 creating build/bdist.linux-armv7l/wheel/plone_mls_core-0.7.2.dist-info/WHEEL 2025-05-30T11:28:15,312 creating '/tmp/pip-wheel-n3wxpcwm/plone_mls_core-0.7.2-py3-none-any.whl' and adding 'build/bdist.linux-armv7l/wheel' to it 2025-05-30T11:28:15,315 adding 'plone.mls.core-0.7.2-py3.11-nspkg.pth' 2025-05-30T11:28:15,318 adding 'plone/mls/core/__init__.py' 2025-05-30T11:28:15,320 adding 'plone/mls/core/api.py' 2025-05-30T11:28:15,321 adding 'plone/mls/core/config.py' 2025-05-30T11:28:15,323 adding 'plone/mls/core/configure.zcml' 2025-05-30T11:28:15,324 adding 'plone/mls/core/i18n.py' 2025-05-30T11:28:15,326 adding 'plone/mls/core/interfaces.py' 2025-05-30T11:28:15,327 adding 'plone/mls/core/migration.py' 2025-05-30T11:28:15,329 adding 'plone/mls/core/navigation.py' 2025-05-30T11:28:15,331 adding 'plone/mls/core/permissions.zcml' 2025-05-30T11:28:15,332 adding 'plone/mls/core/profiles.zcml' 2025-05-30T11:28:15,334 adding 'plone/mls/core/setuphandlers.py' 2025-05-30T11:28:15,335 adding 'plone/mls/core/testing.py' 2025-05-30T11:28:15,337 adding 'plone/mls/core/utils.py' 2025-05-30T11:28:15,339 adding 'plone/mls/core/browser/__init__.py' 2025-05-30T11:28:15,340 adding 'plone/mls/core/browser/configure.zcml' 2025-05-30T11:28:15,342 adding 'plone/mls/core/browser/controlpanel.py' 2025-05-30T11:28:15,343 adding 'plone/mls/core/browser/interfaces.py' 2025-05-30T11:28:15,344 adding 'plone/mls/core/browser/localconfig.py' 2025-05-30T11:28:15,346 adding 'plone/mls/core/browser/resources/icon.png' 2025-05-30T11:28:15,348 adding 'plone/mls/core/browser/resources/plone_mls_core.js' 2025-05-30T11:28:15,350 adding 'plone/mls/core/locales/manual.pot' 2025-05-30T11:28:15,351 adding 'plone/mls/core/locales/plone.mls.core.pot' 2025-05-30T11:28:15,354 adding 'plone/mls/core/locales/ar/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,356 adding 'plone/mls/core/locales/cmn/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,359 adding 'plone/mls/core/locales/de/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,362 adding 'plone/mls/core/locales/en/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,364 adding 'plone/mls/core/locales/es/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,367 adding 'plone/mls/core/locales/et/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,370 adding 'plone/mls/core/locales/fr/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,372 adding 'plone/mls/core/locales/it/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,375 adding 'plone/mls/core/locales/ja/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,377 adding 'plone/mls/core/locales/pt/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,380 adding 'plone/mls/core/locales/ru/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,383 adding 'plone/mls/core/locales/vi/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,385 adding 'plone/mls/core/locales/vi_VN/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,388 adding 'plone/mls/core/locales/zh/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,390 adding 'plone/mls/core/locales/zh_TW/LC_MESSAGES/plone.mls.core.po' 2025-05-30T11:28:15,393 adding 'plone/mls/core/profiles/base/metadata.xml' 2025-05-30T11:28:15,395 adding 'plone/mls/core/profiles/plone4/actions.xml' 2025-05-30T11:28:15,396 adding 'plone/mls/core/profiles/plone4/browserlayer.xml' 2025-05-30T11:28:15,397 adding 'plone/mls/core/profiles/plone4/jsregistry.xml' 2025-05-30T11:28:15,399 adding 'plone/mls/core/profiles/plone4/metadata.xml' 2025-05-30T11:28:15,400 adding 'plone/mls/core/profiles/plone4/registry.xml' 2025-05-30T11:28:15,402 adding 'plone/mls/core/profiles/plone5/actions.xml' 2025-05-30T11:28:15,403 adding 'plone/mls/core/profiles/plone5/browserlayer.xml' 2025-05-30T11:28:15,405 adding 'plone/mls/core/profiles/plone5/metadata.xml' 2025-05-30T11:28:15,406 adding 'plone/mls/core/profiles/plone5/registry.xml' 2025-05-30T11:28:15,408 adding 'plone/mls/core/profiles/uninstall-base/import_steps.xml' 2025-05-30T11:28:15,409 adding 'plone/mls/core/profiles/uninstall-base/plone.mls.core_uninstall.txt' 2025-05-30T11:28:15,410 adding 'plone/mls/core/profiles/uninstall-base/registry.xml' 2025-05-30T11:28:15,412 adding 'plone/mls/core/profiles/uninstall-plone4/metadata.xml' 2025-05-30T11:28:15,414 adding 'plone/mls/core/profiles/uninstall-plone5/metadata.xml' 2025-05-30T11:28:15,416 adding 'plone/mls/core/tests/__init__.py' 2025-05-30T11:28:15,417 adding 'plone/mls/core/tests/test_controlpanel.py' 2025-05-30T11:28:15,419 adding 'plone/mls/core/tests/test_registry.py' 2025-05-30T11:28:15,420 adding 'plone/mls/core/tests/test_setup.py' 2025-05-30T11:28:15,423 adding 'plone_mls_core-0.7.2.dist-info/METADATA' 2025-05-30T11:28:15,424 adding 'plone_mls_core-0.7.2.dist-info/WHEEL' 2025-05-30T11:28:15,425 adding 'plone_mls_core-0.7.2.dist-info/entry_points.txt' 2025-05-30T11:28:15,426 adding 'plone_mls_core-0.7.2.dist-info/namespace_packages.txt' 2025-05-30T11:28:15,427 adding 'plone_mls_core-0.7.2.dist-info/top_level.txt' 2025-05-30T11:28:15,428 adding 'plone_mls_core-0.7.2.dist-info/RECORD' 2025-05-30T11:28:15,431 removing build/bdist.linux-armv7l/wheel 2025-05-30T11:28:15,579 Building wheel for plone-mls-core (setup.py): finished with status 'done' 2025-05-30T11:28:15,582 Created wheel for plone-mls-core: filename=plone_mls_core-0.7.2-py3-none-any.whl size=47526 sha256=dbc28db36b96789346ab9df4e1e9d17a9c1e69e59e6e9f9a684730b39ed0990b 2025-05-30T11:28:15,583 Stored in directory: /tmp/pip-ephem-wheel-cache-y85g4q_e/wheels/02/92/83/71c8ce1767e1a9300cadb4fd5df506fdd12646c43609024cf1 2025-05-30T11:28:15,598 Successfully built plone-mls-core 2025-05-30T11:28:15,604 Removed build tracker: '/tmp/pip-build-tracker-sbdk8obr'