=>> Building www/py-django-cms build started at Sat Jun 6 16:53:31 JST 2026 port directory: /usr/ports/www/py-django-cms package name: py311-django-cms-5.0.6 building for: FreeBSD curamd64-setuptools-job-01 16.0-CURRENT FreeBSD 16.0-CURRENT 1600018 amd64 maintained by: wen@FreeBSD.org Makefile datestamp: -rw-r--r-- 1 root wheel 1376 May 2 10:26 /usr/ports/www/py-django-cms/Makefile Ports top last git commit: a8b187544 Ports top unclean checkout: yes Port dir last git commit: a8b187544 Port dir unclean checkout: no Poudriere version: poudriere-git-3.4.4 Host OSVERSION: 1600018 Jail OSVERSION: 1600018 Job Id: 01 ---Begin Environment--- SHELL=/bin/sh OSVERSION=1600018 UNAME_v=FreeBSD 16.0-CURRENT 1600018 UNAME_r=16.0-CURRENT BLOCKSIZE=K MAIL=/var/mail/root MM_CHARSET=UTF-8 LANG=C.UTF-8 STATUS=1 HOME=/root PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin MAKE_OBJDIR_CHECK_WRITABLE=0 LOCALBASE=/usr/local USER=root POUDRIERE_NAME=poudriere-git LIBEXECPREFIX=/usr/local/libexec/poudriere POUDRIERE_VERSION=3.4.4 MASTERMNT=/usr/local/poudriere/data/.m/curamd64-setuptools/ref LC_COLLATE=C POUDRIERE_BUILD_TYPE=bulk PACKAGE_BUILDING=yes SAVED_TERM=tmux-256color GID=0 OUTPUT_REDIRECTED_STDERR=4 OUTPUT_REDIRECTED=1 UID=0 PWD=/usr/local/poudriere/data/.m/curamd64-setuptools/01/.p OUTPUT_REDIRECTED_STDOUT=3 P_PORTS_FEATURES=FLAVORS SUBPACKAGES SELECTED_OPTIONS MASTERNAME=curamd64-setuptools SCRIPTPREFIX=/usr/local/share/poudriere SCRIPTNAME=bulk.sh OLDPWD=/usr/local/poudriere/data/.m/curamd64-setuptools/ref/.p/pool POUDRIERE_PKGNAME=poudriere-git-3.4.4 SCRIPTPATH=/usr/local/share/poudriere/bulk.sh POUDRIEREPATH=/usr/local/bin/poudriere ---End Environment--- ---Begin Poudriere Port Flags/Env--- PORT_FLAGS= PKGENV= FLAVOR=py311 MAKE_ARGS= FLAVOR=py311 ---End Poudriere Port Flags/Env--- ---Begin OPTIONS List--- ===> The following configuration options are available for py311-django-cms-5.0.6: ====> Options available for the multi DATABASE: you have to choose at least one of them MYSQL=off: MySQL database support PGSQL=off: PostgreSQL database support SQLITE=on: SQLite database support ===> Use 'make config' to modify these settings ---End OPTIONS List--- --MAINTAINER-- wen@FreeBSD.org --End MAINTAINER-- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- --CONFIGURE_ENV-- PYTHON="/usr/local/bin/python3.11" XDG_DATA_HOME=/wrkdirs/usr/ports/www/py-django-cms/work-py311 XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/py-django-cms/work-py311 XDG_CACHE_HOME=/wrkdirs/usr/ports/www/py-django-cms/work-py311/.cache HOME=/wrkdirs/usr/ports/www/py-django-cms/work-py311 TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/www/py-django-cms/work-py311/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/www/py-django-cms/work-py311/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV-- --MAKE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/www/py-django-cms/work-py311 XDG_CONFIG_HOME=/wrkdirs/usr/ports/www/py-django-cms/work-py311 XDG_CACHE_HOME=/wrkdirs/usr/ports/www/py-django-cms/work-py311/.cache HOME=/wrkdirs/usr/ports/www/py-django-cms/work-py311 TMPDIR="/tmp" PATH=/wrkdirs/usr/ports/www/py-django-cms/work-py311/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/www/py-django-cms/work-py311/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES LDSHARED="cc -shared" PYTHONDONTWRITEBYTECODE= PYTHONOPTIMIZE= PREFIX=/usr/local LOCALBASE=/usr/local CC="cc" CFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing " CPP="cpp" CPPFLAGS="" LDFLAGS=" " LIBS="" CXX="c++" CXXFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing " BSD_INSTALL_PROGRAM="install -s -m 555" BSD_INSTALL_LIB="install -s -m 0644" BSD_INSTALL_SCRIPT="install -m 555" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" --End MAKE_ENV-- --PLIST_SUB-- PYTHON_INCLUDEDIR=include/python3.11 PYTHON_LIBDIR=lib/python3.11 PYTHON_PLATFORM=freebsd16 PYTHON_SITELIBDIR=lib/python3.11/site-packages PYTHON_SUFFIX=311 PYTHON_BASESUFFIX=311 PYTHON_TAG=.cpython-311 PYTHON_SOABI=.cpython-311 PYTHON_VER=3.11 PYTHON_BASEVER=3.11 PYTHON_VERSION=python3.11 PYTHON2="@comment " PYTHON3="" OSREL=16.0 PREFIX=%D LOCALBASE=/usr/local RESETPREFIX=/usr/local LIB32DIR=lib DOCSDIR="share/doc/django-cms" EXAMPLESDIR="share/examples/django-cms" DATADIR="share/django-cms" WWWDIR="www/django-cms" ETCDIR="etc/django-cms" --End PLIST_SUB-- --SUB_LIST-- PYTHON_INCLUDEDIR=/usr/local/include/python3.11 PYTHON_LIBDIR=/usr/local/lib/python3.11 PYTHON_PLATFORM=freebsd16 PYTHON_SITELIBDIR=/usr/local/lib/python3.11/site-packages PYTHON_SUFFIX=311 PYTHON_BASESUFFIX=311 PYTHON_TAG=.cpython-311 PYTHON_SOABI=.cpython-311 PYTHON_VER=3.11 PYTHON_BASEVER=3.11 PYTHON_VERSION=python3.11 PYTHON2="@comment " PYTHON3="" PREFIX=/usr/local LOCALBASE=/usr/local DATADIR=/usr/local/share/django-cms DOCSDIR=/usr/local/share/doc/django-cms EXAMPLESDIR=/usr/local/share/examples/django-cms WWWDIR=/usr/local/www/django-cms ETCDIR=/usr/local/etc/django-cms --End SUB_LIST-- ---Begin make.conf--- DEFAULT_VERSIONS+= magick=7-x11 DEFAULT_VERSIONS+= pgsql=18 DEFAULT_VERSIONS+= ssl=openssl japanese_fcitx5_mozc_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_UNSET= JAWIKI x11_wm_hikari_SET= GAMMA INPUTMETHOD LAYERSHELL SCREENCOPY VIRTUALINPUT X11 .if $(.CURDIR:M*/x11-wm/hikari) WITH_DEBUG= YES .endif USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs PORTSDIR=/usr/ports PACKAGES=/packages DISTDIR=/distfiles FORCE_PACKAGE=yes PACKAGE_BUILDING=yes PACKAGE_BUILDING_FLAVORS=yes #### #### DEFAULT_VERSIONS+= magick=7-x11 DEFAULT_VERSIONS+= pgsql=18 DEFAULT_VERSIONS+= ssl=openssl japanese_fcitx5_mozc_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_SET= EDICT2 PERSONALNAME PLACENAME SUDACHIDICT UTDIC japanese_mozc_server_UNSET= JAWIKI x11_wm_hikari_SET= GAMMA INPUTMETHOD LAYERSHELL SCREENCOPY VIRTUALINPUT X11 .if $(.CURDIR:M*/x11-wm/hikari) WITH_DEBUG= YES .endif #### Misc Poudriere #### .include "/etc/make.conf.ports_env" DISABLE_MAKE_JOBS=poudriere ---End make.conf--- --Resource limits-- cpu time (seconds, -t) unlimited file size (512-blocks, -f) unlimited data seg size (kbytes, -d) 33554432 stack size (kbytes, -s) 524288 core file size (512-blocks, -c) unlimited max memory size (kbytes, -m) unlimited locked memory (kbytes, -l) unlimited max user processes (-u) 12099 open files (-n) 8192 virtual mem size (kbytes, -v) unlimited swap limit (kbytes, -w) unlimited socket buffer size (bytes, -b) unlimited pseudo-terminals (-p) unlimited kqueues (-k) unlimited umtx shared locks (-o) unlimited pipebuf (-y) unlimited --End resource limits-- =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> License BSD3CLAUSE accepted by the user =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py311-django-cms-5.0.6 depends on file: /usr/local/sbin/pkg - not found ===> Installing existing package /packages/All/pkg-2.7.5.pkg [curamd64-setuptools-job-01] Installing pkg-2.7.5... [curamd64-setuptools-job-01] Extracting pkg-2.7.5: .......... done ===> py311-django-cms-5.0.6 depends on file: /usr/local/sbin/pkg - found ===> Returning to build of py311-django-cms-5.0.6 =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=root UID=0 GID=0 ===> License BSD3CLAUSE accepted by the user => django_cms-5.0.6.tar.gz doesn't seem to exist in /portdistfiles. => Attempting to fetch https://files.pythonhosted.org/packages/source/d/django_cms/django_cms-5.0.6.tar.gz django_cms-5.0.6.tar.gz 5309 kB 2851 kBps 02s ===> Fetching all distfiles required by py311-django-cms-5.0.6 for building =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=root UID=0 GID=0 ===> License BSD3CLAUSE accepted by the user ===> Fetching all distfiles required by py311-django-cms-5.0.6 for building => SHA256 Checksum OK for django_cms-5.0.6.tar.gz. =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> License BSD3CLAUSE accepted by the user ===> Fetching all distfiles required by py311-django-cms-5.0.6 for building ===> Extracting for py311-django-cms-5.0.6 => SHA256 Checksum OK for django_cms-5.0.6.tar.gz. =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Patching for py311-django-cms-5.0.6 =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py311-django-cms-5.0.6 depends on package: py311-setuptools>=63.1.0 - not found ===> Installing existing package /packages/All/py311-setuptools-81.0.0.pkg [curamd64-setuptools-job-01] Installing py311-setuptools-81.0.0... [curamd64-setuptools-job-01] `-- Installing py311-more-itertools-10.6.0... [curamd64-setuptools-job-01] | `-- Installing python311-3.11.15_2... [curamd64-setuptools-job-01] | | `-- Installing gettext-runtime-1.0... [curamd64-setuptools-job-01] | | `-- Installing indexinfo-0.3.1_1... [curamd64-setuptools-job-01] | | `-- Extracting indexinfo-0.3.1_1: .... done [curamd64-setuptools-job-01] | | `-- Extracting gettext-runtime-1.0: .......... done [curamd64-setuptools-job-01] | | `-- Installing libffi-3.5.1... [curamd64-setuptools-job-01] | | `-- Extracting libffi-3.5.1: .......... done [curamd64-setuptools-job-01] | | `-- Installing mpdecimal-4.0.1... [curamd64-setuptools-job-01] | | `-- Extracting mpdecimal-4.0.1: .......... done [curamd64-setuptools-job-01] | | `-- Installing openssl-3.0.20,1... [curamd64-setuptools-job-01] | | `-- Extracting openssl-3.0.20,1: .......... done [curamd64-setuptools-job-01] | | `-- Installing readline-8.3.3... [curamd64-setuptools-job-01] | | `-- Extracting readline-8.3.3: .......... done [curamd64-setuptools-job-01] | `-- Extracting python311-3.11.15_2: .......... done [curamd64-setuptools-job-01] `-- Extracting py311-more-itertools-10.6.0: .......... done [curamd64-setuptools-job-01] `-- Installing py311-packaging-26.2... [curamd64-setuptools-job-01] `-- Extracting py311-packaging-26.2: .......... done [curamd64-setuptools-job-01] `-- Installing py311-wheel-0.47.0... [curamd64-setuptools-job-01] `-- Extracting py311-wheel-0.47.0: .......... done [curamd64-setuptools-job-01] Extracting py311-setuptools-81.0.0: .......... done ===== Message from python311-3.11.15_2: -- Note that some standard Python modules are provided as separate ports as they require additional dependencies. They are available as: py311-gdbm databases/py-gdbm@py311 py311-sqlite3 databases/py-sqlite3@py311 py311-tkinter x11-toolkits/py-tkinter@py311 ===> py311-django-cms-5.0.6 depends on package: py311-setuptools>=63.1.0 - found ===> Returning to build of py311-django-cms-5.0.6 ===> py311-django-cms-5.0.6 depends on file: /usr/local/bin/python3.11 - found =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Configuring for py311-django-cms-5.0.6 /usr/local/lib/python3.11/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running config =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Building for py311-django-cms-5.0.6 /usr/local/lib/python3.11/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running build running build_py creating build/lib/cms copying cms/__init__.py -> build/lib/cms copying cms/__main__.py -> build/lib/cms copying cms/api.py -> build/lib/cms copying cms/app_base.py -> build/lib/cms copying cms/app_registration.py -> build/lib/cms copying cms/apphook_pool.py -> build/lib/cms copying cms/appresolver.py -> build/lib/cms copying cms/apps.py -> build/lib/cms copying cms/cms_config.py -> build/lib/cms copying cms/cms_menus.py -> build/lib/cms copying cms/cms_plugins.py -> build/lib/cms copying cms/cms_toolbars.py -> build/lib/cms copying cms/cms_wizards.py -> build/lib/cms copying cms/constants.py -> build/lib/cms copying cms/context_processors.py -> build/lib/cms copying cms/exceptions.py -> build/lib/cms copying cms/menu_bases.py -> build/lib/cms copying cms/page_rendering.py -> build/lib/cms copying cms/plugin_base.py -> build/lib/cms copying cms/plugin_pool.py -> build/lib/cms copying cms/plugin_processors.py -> build/lib/cms copying cms/plugin_rendering.py -> build/lib/cms copying cms/templates.py -> build/lib/cms copying cms/toolbar_base.py -> build/lib/cms copying cms/toolbar_pool.py -> build/lib/cms copying cms/urls.py -> build/lib/cms copying cms/views.py -> build/lib/cms creating build/lib/menus copying menus/__init__.py -> build/lib/menus copying menus/apps.py -> build/lib/menus copying menus/base.py -> build/lib/menus copying menus/exceptions.py -> build/lib/menus copying menus/menu_pool.py -> build/lib/menus copying menus/models.py -> build/lib/menus copying menus/modifiers.py -> build/lib/menus copying menus/utils.py -> build/lib/menus creating build/lib/cms/admin copying cms/admin/__init__.py -> build/lib/cms/admin copying cms/admin/forms.py -> build/lib/cms/admin copying cms/admin/pageadmin.py -> build/lib/cms/admin copying cms/admin/permissionadmin.py -> build/lib/cms/admin copying cms/admin/placeholderadmin.py -> build/lib/cms/admin copying cms/admin/settingsadmin.py -> build/lib/cms/admin copying cms/admin/static_placeholder.py -> build/lib/cms/admin copying cms/admin/useradmin.py -> build/lib/cms/admin copying cms/admin/utils.py -> build/lib/cms/admin creating build/lib/cms/cache copying cms/cache/__init__.py -> build/lib/cms/cache copying cms/cache/choices.py -> build/lib/cms/cache copying cms/cache/page.py -> build/lib/cms/cache copying cms/cache/permissions.py -> build/lib/cms/cache copying cms/cache/placeholder.py -> build/lib/cms/cache creating build/lib/cms/extensions copying cms/extensions/__init__.py -> build/lib/cms/extensions copying cms/extensions/admin.py -> build/lib/cms/extensions copying cms/extensions/extension_pool.py -> build/lib/cms/extensions copying cms/extensions/models.py -> build/lib/cms/extensions copying cms/extensions/toolbar.py -> build/lib/cms/extensions creating build/lib/cms/forms copying cms/forms/__init__.py -> build/lib/cms/forms copying cms/forms/fields.py -> build/lib/cms/forms copying cms/forms/login.py -> build/lib/cms/forms copying cms/forms/utils.py -> build/lib/cms/forms copying cms/forms/validators.py -> build/lib/cms/forms copying cms/forms/widgets.py -> build/lib/cms/forms copying cms/forms/wizards.py -> build/lib/cms/forms creating build/lib/cms/management copying cms/management/__init__.py -> build/lib/cms/management copying cms/management/djangocms.py -> build/lib/cms/management creating build/lib/cms/models copying cms/models/__init__.py -> build/lib/cms/models copying cms/models/aliaspluginmodel.py -> build/lib/cms/models copying cms/models/apphooks_reload.py -> build/lib/cms/models copying cms/models/contentmodels.py -> build/lib/cms/models copying cms/models/fields.py -> build/lib/cms/models copying cms/models/managers.py -> build/lib/cms/models copying cms/models/pagemodel.py -> build/lib/cms/models copying cms/models/permissionmodels.py -> build/lib/cms/models copying cms/models/placeholdermodel.py -> build/lib/cms/models copying cms/models/placeholderpluginmodel.py -> build/lib/cms/models copying cms/models/pluginmodel.py -> build/lib/cms/models copying cms/models/query.py -> build/lib/cms/models copying cms/models/settingmodels.py -> build/lib/cms/models copying cms/models/static_placeholder.py -> build/lib/cms/models creating build/lib/cms/middleware copying cms/middleware/__init__.py -> build/lib/cms/middleware copying cms/middleware/language.py -> build/lib/cms/middleware copying cms/middleware/page.py -> build/lib/cms/middleware copying cms/middleware/toolbar.py -> build/lib/cms/middleware copying cms/middleware/user.py -> build/lib/cms/middleware copying cms/middleware/utils.py -> build/lib/cms/middleware creating build/lib/cms/migrations copying cms/migrations/0001_initial.py -> build/lib/cms/migrations copying cms/migrations/0002_auto_20140816_1918.py -> build/lib/cms/migrations copying cms/migrations/0003_auto_20140926_2347.py -> build/lib/cms/migrations copying cms/migrations/0004_auto_20140924_1038.py -> build/lib/cms/migrations copying cms/migrations/0005_auto_20140924_1039.py -> build/lib/cms/migrations copying cms/migrations/0006_auto_20140924_1110.py -> build/lib/cms/migrations copying cms/migrations/0007_auto_20141028_1559.py -> build/lib/cms/migrations copying cms/migrations/0008_auto_20150121_0059.py -> build/lib/cms/migrations copying cms/migrations/0008_auto_20150208_2149.py -> build/lib/cms/migrations copying cms/migrations/0009_merge.py -> build/lib/cms/migrations copying cms/migrations/0010_migrate_use_structure.py -> build/lib/cms/migrations copying cms/migrations/0011_auto_20150419_1006.py -> build/lib/cms/migrations copying cms/migrations/0012_auto_20150607_2207.py -> build/lib/cms/migrations copying cms/migrations/0013_urlconfrevision.py -> build/lib/cms/migrations copying cms/migrations/0014_auto_20160404_1908.py -> build/lib/cms/migrations copying cms/migrations/0015_auto_20160421_0000.py -> build/lib/cms/migrations copying cms/migrations/0016_auto_20160608_1535.py -> build/lib/cms/migrations copying cms/migrations/0017_pagetype.py -> build/lib/cms/migrations copying cms/migrations/0018_create_pagenode.py -> build/lib/cms/migrations copying cms/migrations/0019_set_pagenode.py -> build/lib/cms/migrations copying cms/migrations/0020_old_tree_cleanup.py -> build/lib/cms/migrations copying cms/migrations/0021_auto_20180507_1432.py -> build/lib/cms/migrations copying cms/migrations/0022_auto_20180620_1551.py -> build/lib/cms/migrations copying cms/migrations/0023_placeholder_source_field.py -> build/lib/cms/migrations copying cms/migrations/0024_set_plugin_absolute_position.py -> build/lib/cms/migrations copying cms/migrations/0025_remove_plugin_tree_fields.py -> build/lib/cms/migrations copying cms/migrations/0026_title_placeholders.py -> build/lib/cms/migrations copying cms/migrations/0031_remove_fields.py -> build/lib/cms/migrations copying cms/migrations/0027_title_placeholders_data_migration.py -> build/lib/cms/migrations copying cms/migrations/0028_remove_page_placeholders.py -> build/lib/cms/migrations copying cms/migrations/0029_create_title_fields_and_url_model.py -> build/lib/cms/migrations copying cms/migrations/0030_auto_20180810_0629.py -> build/lib/cms/migrations copying cms/migrations/0032_remove_title_to_pagecontent.py -> build/lib/cms/migrations copying cms/migrations/0033_placeholder_source_data_migration.py -> build/lib/cms/migrations copying cms/migrations/0034_remove_pagecontent_placeholders.py -> build/lib/cms/migrations copying cms/migrations/0035_auto_20230822_2208.py -> build/lib/cms/migrations copying cms/migrations/0035_auto_20230822_2208_squashed_0036_auto_20240311_1028.py -> build/lib/cms/migrations copying cms/migrations/0036_auto_20240311_1028.py -> build/lib/cms/migrations copying cms/migrations/0037_merge_page_treenode.py -> build/lib/cms/migrations copying cms/migrations/0038_alter_page_site.py -> build/lib/cms/migrations copying cms/migrations/0039_remove_page_languages_alter_pageurl_unique_together.py -> build/lib/cms/migrations copying cms/migrations/0040_alter_pageuser_created_by_and_more.py -> build/lib/cms/migrations copying cms/migrations/0041_alter_pageurl_unique_together_pageurl_site_and_more.py -> build/lib/cms/migrations copying cms/migrations/__init__.py -> build/lib/cms/migrations creating build/lib/cms/operations copying cms/operations/__init__.py -> build/lib/cms/operations copying cms/operations/helpers.py -> build/lib/cms/operations creating build/lib/cms/signals copying cms/signals/__init__.py -> build/lib/cms/signals copying cms/signals/apphook.py -> build/lib/cms/signals copying cms/signals/log_entries.py -> build/lib/cms/signals copying cms/signals/pagecontent.py -> build/lib/cms/signals copying cms/signals/permissions.py -> build/lib/cms/signals creating build/lib/cms/sitemaps copying cms/sitemaps/__init__.py -> build/lib/cms/sitemaps copying cms/sitemaps/cms_sitemap.py -> build/lib/cms/sitemaps creating build/lib/cms/templatetags copying cms/templatetags/__init__.py -> build/lib/cms/templatetags copying cms/templatetags/cms_admin.py -> build/lib/cms/templatetags copying cms/templatetags/cms_alias_tags.py -> build/lib/cms/templatetags copying cms/templatetags/cms_js_tags.py -> build/lib/cms/templatetags copying cms/templatetags/cms_static.py -> build/lib/cms/templatetags copying cms/templatetags/cms_tags.py -> build/lib/cms/templatetags creating build/lib/cms/test_utils copying cms/test_utils/__init__.py -> build/lib/cms/test_utils copying cms/test_utils/runners.py -> build/lib/cms/test_utils copying cms/test_utils/testcases.py -> build/lib/cms/test_utils copying cms/test_utils/tmpdir.py -> build/lib/cms/test_utils creating build/lib/cms/tests copying cms/tests/__init__.py -> build/lib/cms/tests copying cms/tests/test_admin.py -> build/lib/cms/tests copying cms/tests/test_api.py -> build/lib/cms/tests copying cms/tests/test_app_registration.py -> build/lib/cms/tests copying cms/tests/test_apphook_reload_language_variants.py -> build/lib/cms/tests copying cms/tests/test_apphooks.py -> build/lib/cms/tests copying cms/tests/test_cache.py -> build/lib/cms/tests copying cms/tests/test_check.py -> build/lib/cms/tests copying cms/tests/test_cms_config_wizards.py -> build/lib/cms/tests copying cms/tests/test_extensions.py -> build/lib/cms/tests copying cms/tests/test_fixture_loading.py -> build/lib/cms/tests copying cms/tests/test_forms.py -> build/lib/cms/tests copying cms/tests/test_grouper_admin.py -> build/lib/cms/tests copying cms/tests/test_helpers.py -> build/lib/cms/tests copying cms/tests/test_i18n.py -> build/lib/cms/tests copying cms/tests/test_log_entries.py -> build/lib/cms/tests copying cms/tests/test_mail.py -> build/lib/cms/tests copying cms/tests/test_management.py -> build/lib/cms/tests copying cms/tests/test_menu.py -> build/lib/cms/tests copying cms/tests/test_menu_page_viewperm.py -> build/lib/cms/tests copying cms/tests/test_menu_page_viewperm_staff.py -> build/lib/cms/tests copying cms/tests/test_menu_utils.py -> build/lib/cms/tests copying cms/tests/test_migrations.py -> build/lib/cms/tests copying cms/tests/test_multilingual.py -> build/lib/cms/tests copying cms/tests/test_navextender.py -> build/lib/cms/tests copying cms/tests/test_nested_plugins.py -> build/lib/cms/tests copying cms/tests/test_no_i18n.py -> build/lib/cms/tests copying cms/tests/test_nonroot.py -> build/lib/cms/tests copying cms/tests/test_page.py -> build/lib/cms/tests copying cms/tests/test_page_admin.py -> build/lib/cms/tests copying cms/tests/test_page_user_admin.py -> build/lib/cms/tests copying cms/tests/test_page_user_group_admin.py -> build/lib/cms/tests copying cms/tests/test_permissions.py -> build/lib/cms/tests copying cms/tests/test_permmod.py -> build/lib/cms/tests copying cms/tests/test_placeholder.py -> build/lib/cms/tests copying cms/tests/test_placeholder_admin.py -> build/lib/cms/tests copying cms/tests/test_placeholder_app_admin.py -> build/lib/cms/tests copying cms/tests/test_placeholder_checks.py -> build/lib/cms/tests copying cms/tests/test_placeholder_operation_signals.py -> build/lib/cms/tests copying cms/tests/test_plugin_renderers.py -> build/lib/cms/tests copying cms/tests/test_plugins.py -> build/lib/cms/tests copying cms/tests/test_po.py -> build/lib/cms/tests copying cms/tests/test_rendering.py -> build/lib/cms/tests copying cms/tests/test_security.py -> build/lib/cms/tests copying cms/tests/test_settings.py -> build/lib/cms/tests copying cms/tests/test_signals.py -> build/lib/cms/tests copying cms/tests/test_site.py -> build/lib/cms/tests copying cms/tests/test_sitemap.py -> build/lib/cms/tests copying cms/tests/test_static_analysis.py -> build/lib/cms/tests copying cms/tests/test_templates.py -> build/lib/cms/tests copying cms/tests/test_toolbar.py -> build/lib/cms/tests copying cms/tests/test_templatetags.py -> build/lib/cms/tests copying cms/tests/test_toolbar_enabled_models.py -> build/lib/cms/tests copying cms/tests/test_toolbar_pool.py -> build/lib/cms/tests copying cms/tests/test_urlutils.py -> build/lib/cms/tests copying cms/tests/test_views.py -> build/lib/cms/tests copying cms/tests/test_widgets.py -> build/lib/cms/tests copying cms/tests/test_wizards.py -> build/lib/cms/tests creating build/lib/cms/toolbar copying cms/toolbar/__init__.py -> build/lib/cms/toolbar copying cms/toolbar/items.py -> build/lib/cms/toolbar copying cms/toolbar/toolbar.py -> build/lib/cms/toolbar copying cms/toolbar/utils.py -> build/lib/cms/toolbar creating build/lib/cms/utils copying cms/utils/__init__.py -> build/lib/cms/utils copying cms/utils/admin.py -> build/lib/cms/utils copying cms/utils/apphook_reload.py -> build/lib/cms/utils copying cms/utils/check.py -> build/lib/cms/utils copying cms/utils/conf.py -> build/lib/cms/utils copying cms/utils/decorators.py -> build/lib/cms/utils copying cms/utils/encoder.py -> build/lib/cms/utils copying cms/utils/helpers.py -> build/lib/cms/utils copying cms/utils/i18n.py -> build/lib/cms/utils copying cms/utils/mail.py -> build/lib/cms/utils copying cms/utils/page.py -> build/lib/cms/utils copying cms/utils/page_permissions.py -> build/lib/cms/utils copying cms/utils/permissions.py -> build/lib/cms/utils copying cms/utils/placeholder.py -> build/lib/cms/utils copying cms/utils/plugins.py -> build/lib/cms/utils copying cms/utils/request_ip_resolvers.py -> build/lib/cms/utils copying cms/utils/setup.py -> build/lib/cms/utils copying cms/utils/urlutils.py -> build/lib/cms/utils creating build/lib/cms/wizards copying cms/wizards/__init__.py -> build/lib/cms/wizards copying cms/wizards/forms.py -> build/lib/cms/wizards copying cms/wizards/helpers.py -> build/lib/cms/wizards copying cms/wizards/urls.py -> build/lib/cms/wizards copying cms/wizards/views.py -> build/lib/cms/wizards copying cms/wizards/wizard_base.py -> build/lib/cms/wizards copying cms/wizards/wizard_pool.py -> build/lib/cms/wizards creating build/lib/cms/management/commands copying cms/management/commands/__init__.py -> build/lib/cms/management/commands copying cms/management/commands/cms.py -> build/lib/cms/management/commands copying cms/management/commands/startcmsproject.py -> build/lib/cms/management/commands creating build/lib/cms/management/commands/subcommands copying cms/management/commands/subcommands/__init__.py -> build/lib/cms/management/commands/subcommands copying cms/management/commands/subcommands/base.py -> build/lib/cms/management/commands/subcommands copying cms/management/commands/subcommands/check.py -> build/lib/cms/management/commands/subcommands copying cms/management/commands/subcommands/copy.py -> build/lib/cms/management/commands/subcommands copying cms/management/commands/subcommands/delete_orphaned_plugins.py -> build/lib/cms/management/commands/subcommands copying cms/management/commands/subcommands/list.py -> build/lib/cms/management/commands/subcommands copying cms/management/commands/subcommands/tree.py -> build/lib/cms/management/commands/subcommands copying cms/management/commands/subcommands/uninstall.py -> build/lib/cms/management/commands/subcommands creating build/lib/cms/test_utils/fixtures copying cms/test_utils/fixtures/__init__.py -> build/lib/cms/test_utils/fixtures copying cms/test_utils/fixtures/fakemlng.py -> build/lib/cms/test_utils/fixtures copying cms/test_utils/fixtures/menus.py -> build/lib/cms/test_utils/fixtures copying cms/test_utils/fixtures/navextenders.py -> build/lib/cms/test_utils/fixtures copying cms/test_utils/fixtures/templatetags.py -> build/lib/cms/test_utils/fixtures creating build/lib/cms/test_utils/project copying cms/test_utils/project/__init__.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/cms_urls_for_apphook_tests.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/fourth_cms_urls_for_apphook_tests.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/fourth_urls_for_apphook_tests.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/models.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/noadmin_urls.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/nonroot_urls.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/placeholderapp_urls.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/second_cms_urls_for_apphook_tests.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/second_urls_for_apphook_tests.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/template_backends.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/third_cms_urls_for_apphook_tests.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/third_urls_for_apphook_tests.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/urls.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/urls_2.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/urls_3.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/urls_for_apphook_tests.py -> build/lib/cms/test_utils/project copying cms/test_utils/project/urls_no18n.py -> build/lib/cms/test_utils/project creating build/lib/cms/test_utils/util copying cms/test_utils/util/__init__.py -> build/lib/cms/test_utils/util copying cms/test_utils/util/context_managers.py -> build/lib/cms/test_utils/util copying cms/test_utils/util/fuzzy_int.py -> build/lib/cms/test_utils/util copying cms/test_utils/util/grouper.py -> build/lib/cms/test_utils/util copying cms/test_utils/util/menu_extender.py -> build/lib/cms/test_utils/util copying cms/test_utils/util/mock.py -> build/lib/cms/test_utils/util copying cms/test_utils/util/static_analysis.py -> build/lib/cms/test_utils/util creating build/lib/cms/test_utils/project/app_using_non_feature copying cms/test_utils/project/app_using_non_feature/__init__.py -> build/lib/cms/test_utils/project/app_using_non_feature copying cms/test_utils/project/app_using_non_feature/admin.py -> build/lib/cms/test_utils/project/app_using_non_feature copying cms/test_utils/project/app_using_non_feature/apps.py -> build/lib/cms/test_utils/project/app_using_non_feature copying cms/test_utils/project/app_using_non_feature/cms_config.py -> build/lib/cms/test_utils/project/app_using_non_feature copying cms/test_utils/project/app_using_non_feature/models.py -> build/lib/cms/test_utils/project/app_using_non_feature copying cms/test_utils/project/app_using_non_feature/views.py -> build/lib/cms/test_utils/project/app_using_non_feature creating build/lib/cms/test_utils/project/app_with_bad_cms_file copying cms/test_utils/project/app_with_bad_cms_file/__init__.py -> build/lib/cms/test_utils/project/app_with_bad_cms_file copying cms/test_utils/project/app_with_bad_cms_file/admin.py -> build/lib/cms/test_utils/project/app_with_bad_cms_file copying cms/test_utils/project/app_with_bad_cms_file/apps.py -> build/lib/cms/test_utils/project/app_with_bad_cms_file copying cms/test_utils/project/app_with_bad_cms_file/cms_config.py -> build/lib/cms/test_utils/project/app_with_bad_cms_file copying cms/test_utils/project/app_with_bad_cms_file/models.py -> build/lib/cms/test_utils/project/app_with_bad_cms_file copying cms/test_utils/project/app_with_bad_cms_file/views.py -> build/lib/cms/test_utils/project/app_with_bad_cms_file creating build/lib/cms/test_utils/project/app_with_cms_config copying cms/test_utils/project/app_with_cms_config/__init__.py -> build/lib/cms/test_utils/project/app_with_cms_config copying cms/test_utils/project/app_with_cms_config/admin.py -> build/lib/cms/test_utils/project/app_with_cms_config copying cms/test_utils/project/app_with_cms_config/apps.py -> build/lib/cms/test_utils/project/app_with_cms_config copying cms/test_utils/project/app_with_cms_config/cms_config.py -> build/lib/cms/test_utils/project/app_with_cms_config copying cms/test_utils/project/app_with_cms_config/models.py -> build/lib/cms/test_utils/project/app_with_cms_config copying cms/test_utils/project/app_with_cms_config/views.py -> build/lib/cms/test_utils/project/app_with_cms_config creating build/lib/cms/test_utils/project/app_with_cms_feature copying cms/test_utils/project/app_with_cms_feature/__init__.py -> build/lib/cms/test_utils/project/app_with_cms_feature copying cms/test_utils/project/app_with_cms_feature/admin.py -> build/lib/cms/test_utils/project/app_with_cms_feature copying cms/test_utils/project/app_with_cms_feature/apps.py -> build/lib/cms/test_utils/project/app_with_cms_feature copying cms/test_utils/project/app_with_cms_feature/cms_config.py -> build/lib/cms/test_utils/project/app_with_cms_feature copying cms/test_utils/project/app_with_cms_feature/models.py -> build/lib/cms/test_utils/project/app_with_cms_feature copying cms/test_utils/project/app_with_cms_feature/views.py -> build/lib/cms/test_utils/project/app_with_cms_feature creating build/lib/cms/test_utils/project/app_with_cms_feature_and_config copying cms/test_utils/project/app_with_cms_feature_and_config/__init__.py -> build/lib/cms/test_utils/project/app_with_cms_feature_and_config copying cms/test_utils/project/app_with_cms_feature_and_config/admin.py -> build/lib/cms/test_utils/project/app_with_cms_feature_and_config copying cms/test_utils/project/app_with_cms_feature_and_config/apps.py -> build/lib/cms/test_utils/project/app_with_cms_feature_and_config copying cms/test_utils/project/app_with_cms_feature_and_config/cms_config.py -> build/lib/cms/test_utils/project/app_with_cms_feature_and_config copying cms/test_utils/project/app_with_cms_feature_and_config/models.py -> build/lib/cms/test_utils/project/app_with_cms_feature_and_config copying cms/test_utils/project/app_with_cms_feature_and_config/views.py -> build/lib/cms/test_utils/project/app_with_cms_feature_and_config creating build/lib/cms/test_utils/project/app_with_feature_not_implemented copying cms/test_utils/project/app_with_feature_not_implemented/__init__.py -> build/lib/cms/test_utils/project/app_with_feature_not_implemented copying cms/test_utils/project/app_with_feature_not_implemented/admin.py -> build/lib/cms/test_utils/project/app_with_feature_not_implemented copying cms/test_utils/project/app_with_feature_not_implemented/apps.py -> build/lib/cms/test_utils/project/app_with_feature_not_implemented copying cms/test_utils/project/app_with_feature_not_implemented/cms_config.py -> build/lib/cms/test_utils/project/app_with_feature_not_implemented copying cms/test_utils/project/app_with_feature_not_implemented/models.py -> build/lib/cms/test_utils/project/app_with_feature_not_implemented copying cms/test_utils/project/app_with_feature_not_implemented/views.py -> build/lib/cms/test_utils/project/app_with_feature_not_implemented creating build/lib/cms/test_utils/project/app_with_two_cms_config_classes copying cms/test_utils/project/app_with_two_cms_config_classes/__init__.py -> build/lib/cms/test_utils/project/app_with_two_cms_config_classes copying cms/test_utils/project/app_with_two_cms_config_classes/admin.py -> build/lib/cms/test_utils/project/app_with_two_cms_config_classes copying cms/test_utils/project/app_with_two_cms_config_classes/apps.py -> build/lib/cms/test_utils/project/app_with_two_cms_config_classes copying cms/test_utils/project/app_with_two_cms_config_classes/cms_config.py -> build/lib/cms/test_utils/project/app_with_two_cms_config_classes copying cms/test_utils/project/app_with_two_cms_config_classes/models.py -> build/lib/cms/test_utils/project/app_with_two_cms_config_classes copying cms/test_utils/project/app_with_two_cms_config_classes/views.py -> build/lib/cms/test_utils/project/app_with_two_cms_config_classes creating build/lib/cms/test_utils/project/app_with_two_cms_feature_classes copying cms/test_utils/project/app_with_two_cms_feature_classes/__init__.py -> build/lib/cms/test_utils/project/app_with_two_cms_feature_classes copying cms/test_utils/project/app_with_two_cms_feature_classes/admin.py -> build/lib/cms/test_utils/project/app_with_two_cms_feature_classes copying cms/test_utils/project/app_with_two_cms_feature_classes/apps.py -> build/lib/cms/test_utils/project/app_with_two_cms_feature_classes copying cms/test_utils/project/app_with_two_cms_feature_classes/cms_config.py -> build/lib/cms/test_utils/project/app_with_two_cms_feature_classes copying cms/test_utils/project/app_with_two_cms_feature_classes/models.py -> build/lib/cms/test_utils/project/app_with_two_cms_feature_classes copying cms/test_utils/project/app_with_two_cms_feature_classes/views.py -> build/lib/cms/test_utils/project/app_with_two_cms_feature_classes creating build/lib/cms/test_utils/project/app_without_cms_app_class copying cms/test_utils/project/app_without_cms_app_class/__init__.py -> build/lib/cms/test_utils/project/app_without_cms_app_class copying cms/test_utils/project/app_without_cms_app_class/admin.py -> build/lib/cms/test_utils/project/app_without_cms_app_class copying cms/test_utils/project/app_without_cms_app_class/apps.py -> build/lib/cms/test_utils/project/app_without_cms_app_class copying cms/test_utils/project/app_without_cms_app_class/cms_config.py -> build/lib/cms/test_utils/project/app_without_cms_app_class copying cms/test_utils/project/app_without_cms_app_class/models.py -> build/lib/cms/test_utils/project/app_without_cms_app_class copying cms/test_utils/project/app_without_cms_app_class/views.py -> build/lib/cms/test_utils/project/app_without_cms_app_class creating build/lib/cms/test_utils/project/app_without_cms_file copying cms/test_utils/project/app_without_cms_file/__init__.py -> build/lib/cms/test_utils/project/app_without_cms_file copying cms/test_utils/project/app_without_cms_file/admin.py -> build/lib/cms/test_utils/project/app_without_cms_file copying cms/test_utils/project/app_without_cms_file/apps.py -> build/lib/cms/test_utils/project/app_without_cms_file copying cms/test_utils/project/app_without_cms_file/models.py -> build/lib/cms/test_utils/project/app_without_cms_file copying cms/test_utils/project/app_without_cms_file/views.py -> build/lib/cms/test_utils/project/app_without_cms_file creating build/lib/cms/test_utils/project/backwards_wizards copying cms/test_utils/project/backwards_wizards/__init__.py -> build/lib/cms/test_utils/project/backwards_wizards copying cms/test_utils/project/backwards_wizards/cms_wizards.py -> build/lib/cms/test_utils/project/backwards_wizards copying cms/test_utils/project/backwards_wizards/wizards.py -> build/lib/cms/test_utils/project/backwards_wizards creating build/lib/cms/test_utils/project/brokenpluginapp copying cms/test_utils/project/brokenpluginapp/__init__.py -> build/lib/cms/test_utils/project/brokenpluginapp copying cms/test_utils/project/brokenpluginapp/cms_plugins.py -> build/lib/cms/test_utils/project/brokenpluginapp creating build/lib/cms/test_utils/project/bunch_of_plugins copying cms/test_utils/project/bunch_of_plugins/__init__.py -> build/lib/cms/test_utils/project/bunch_of_plugins copying cms/test_utils/project/bunch_of_plugins/models.py -> build/lib/cms/test_utils/project/bunch_of_plugins creating build/lib/cms/test_utils/project/custom_templates copying cms/test_utils/project/custom_templates/__init__.py -> build/lib/cms/test_utils/project/custom_templates creating build/lib/cms/test_utils/project/customuserapp copying cms/test_utils/project/customuserapp/__init__.py -> build/lib/cms/test_utils/project/customuserapp copying cms/test_utils/project/customuserapp/admin.py -> build/lib/cms/test_utils/project/customuserapp copying cms/test_utils/project/customuserapp/models.py -> build/lib/cms/test_utils/project/customuserapp creating build/lib/cms/test_utils/project/emailuserapp copying cms/test_utils/project/emailuserapp/__init__.py -> build/lib/cms/test_utils/project/emailuserapp copying cms/test_utils/project/emailuserapp/admin.py -> build/lib/cms/test_utils/project/emailuserapp copying cms/test_utils/project/emailuserapp/forms.py -> build/lib/cms/test_utils/project/emailuserapp copying cms/test_utils/project/emailuserapp/models.py -> build/lib/cms/test_utils/project/emailuserapp creating build/lib/cms/test_utils/project/extensionapp copying cms/test_utils/project/extensionapp/__init__.py -> build/lib/cms/test_utils/project/extensionapp copying cms/test_utils/project/extensionapp/admin.py -> build/lib/cms/test_utils/project/extensionapp copying cms/test_utils/project/extensionapp/cms_toolbars.py -> build/lib/cms/test_utils/project/extensionapp copying cms/test_utils/project/extensionapp/models.py -> build/lib/cms/test_utils/project/extensionapp creating build/lib/cms/test_utils/project/fakemlng copying cms/test_utils/project/fakemlng/__init__.py -> build/lib/cms/test_utils/project/fakemlng copying cms/test_utils/project/fakemlng/models.py -> build/lib/cms/test_utils/project/fakemlng creating build/lib/cms/test_utils/project/mti_pluginapp copying cms/test_utils/project/mti_pluginapp/__init__.py -> build/lib/cms/test_utils/project/mti_pluginapp copying cms/test_utils/project/mti_pluginapp/cms_plugins.py -> build/lib/cms/test_utils/project/mti_pluginapp copying cms/test_utils/project/mti_pluginapp/models.py -> build/lib/cms/test_utils/project/mti_pluginapp creating build/lib/cms/test_utils/project/nested_plugins_app copying cms/test_utils/project/nested_plugins_app/__init__.py -> build/lib/cms/test_utils/project/nested_plugins_app copying cms/test_utils/project/nested_plugins_app/cms_plugins.py -> build/lib/cms/test_utils/project/nested_plugins_app creating build/lib/cms/test_utils/project/objectpermissionsapp copying cms/test_utils/project/objectpermissionsapp/__init__.py -> build/lib/cms/test_utils/project/objectpermissionsapp copying cms/test_utils/project/objectpermissionsapp/backends.py -> build/lib/cms/test_utils/project/objectpermissionsapp copying cms/test_utils/project/objectpermissionsapp/models.py -> build/lib/cms/test_utils/project/objectpermissionsapp creating build/lib/cms/test_utils/project/placeholder_relation_field_app copying cms/test_utils/project/placeholder_relation_field_app/__init__.py -> build/lib/cms/test_utils/project/placeholder_relation_field_app copying cms/test_utils/project/placeholder_relation_field_app/admin.py -> build/lib/cms/test_utils/project/placeholder_relation_field_app copying cms/test_utils/project/placeholder_relation_field_app/models.py -> build/lib/cms/test_utils/project/placeholder_relation_field_app copying cms/test_utils/project/placeholder_relation_field_app/urls.py -> build/lib/cms/test_utils/project/placeholder_relation_field_app copying cms/test_utils/project/placeholder_relation_field_app/views.py -> build/lib/cms/test_utils/project/placeholder_relation_field_app creating build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/__init__.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/admin.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/cms_apps.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/cms_config.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/cms_plugins.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/cms_toolbars.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/exceptions.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/models.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/urls.py -> build/lib/cms/test_utils/project/placeholderapp copying cms/test_utils/project/placeholderapp/views.py -> build/lib/cms/test_utils/project/placeholderapp creating build/lib/cms/test_utils/project/pluginapp copying cms/test_utils/project/pluginapp/__init__.py -> build/lib/cms/test_utils/project/pluginapp creating build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/__init__.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/admin.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/cms_apps.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/cms_config.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/cms_menus.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/cms_toolbars.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/cms_wizards.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/forms.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/models.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/ns_urls.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/urls.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/urls2.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/urls_childapp.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/urls_example.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/urls_excluded.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/urls_extra.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/urls_parentapp.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/urls_sample_config.py -> build/lib/cms/test_utils/project/sampleapp copying cms/test_utils/project/sampleapp/views.py -> build/lib/cms/test_utils/project/sampleapp creating build/lib/cms/test_utils/project/pluginapp/plugins copying cms/test_utils/project/pluginapp/plugins/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins creating build/lib/cms/test_utils/project/pluginapp/plugins/caching copying cms/test_utils/project/pluginapp/plugins/caching/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/caching copying cms/test_utils/project/pluginapp/plugins/caching/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/caching copying cms/test_utils/project/pluginapp/plugins/caching/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/caching creating build/lib/cms/test_utils/project/pluginapp/plugins/extra_context copying cms/test_utils/project/pluginapp/plugins/extra_context/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/extra_context copying cms/test_utils/project/pluginapp/plugins/extra_context/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/extra_context copying cms/test_utils/project/pluginapp/plugins/extra_context/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/extra_context creating build/lib/cms/test_utils/project/pluginapp/plugins/link copying cms/test_utils/project/pluginapp/plugins/link/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/link copying cms/test_utils/project/pluginapp/plugins/link/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/link copying cms/test_utils/project/pluginapp/plugins/link/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/link creating build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel copying cms/test_utils/project/pluginapp/plugins/manytomany_rel/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel copying cms/test_utils/project/pluginapp/plugins/manytomany_rel/admin.py -> build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel copying cms/test_utils/project/pluginapp/plugins/manytomany_rel/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel copying cms/test_utils/project/pluginapp/plugins/manytomany_rel/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel creating build/lib/cms/test_utils/project/pluginapp/plugins/meta copying cms/test_utils/project/pluginapp/plugins/meta/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/meta copying cms/test_utils/project/pluginapp/plugins/meta/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/meta copying cms/test_utils/project/pluginapp/plugins/meta/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/meta creating build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn copying cms/test_utils/project/pluginapp/plugins/multicolumn/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn copying cms/test_utils/project/pluginapp/plugins/multicolumn/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn copying cms/test_utils/project/pluginapp/plugins/multicolumn/forms.py -> build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn copying cms/test_utils/project/pluginapp/plugins/multicolumn/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn creating build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap copying cms/test_utils/project/pluginapp/plugins/multiwrap/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap copying cms/test_utils/project/pluginapp/plugins/multiwrap/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap copying cms/test_utils/project/pluginapp/plugins/multiwrap/forms.py -> build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap copying cms/test_utils/project/pluginapp/plugins/multiwrap/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap creating build/lib/cms/test_utils/project/pluginapp/plugins/no_custom_model copying cms/test_utils/project/pluginapp/plugins/no_custom_model/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/no_custom_model copying cms/test_utils/project/pluginapp/plugins/no_custom_model/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/no_custom_model copying cms/test_utils/project/pluginapp/plugins/no_custom_model/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/no_custom_model creating build/lib/cms/test_utils/project/pluginapp/plugins/one_thing copying cms/test_utils/project/pluginapp/plugins/one_thing/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/one_thing copying cms/test_utils/project/pluginapp/plugins/one_thing/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/one_thing creating build/lib/cms/test_utils/project/pluginapp/plugins/revdesc copying cms/test_utils/project/pluginapp/plugins/revdesc/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/revdesc copying cms/test_utils/project/pluginapp/plugins/revdesc/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/revdesc copying cms/test_utils/project/pluginapp/plugins/revdesc/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/revdesc creating build/lib/cms/test_utils/project/pluginapp/plugins/style copying cms/test_utils/project/pluginapp/plugins/style/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/style copying cms/test_utils/project/pluginapp/plugins/style/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/style copying cms/test_utils/project/pluginapp/plugins/style/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/style creating build/lib/cms/test_utils/project/pluginapp/plugins/validation copying cms/test_utils/project/pluginapp/plugins/validation/__init__.py -> build/lib/cms/test_utils/project/pluginapp/plugins/validation copying cms/test_utils/project/pluginapp/plugins/validation/cms_plugins.py -> build/lib/cms/test_utils/project/pluginapp/plugins/validation copying cms/test_utils/project/pluginapp/plugins/validation/models.py -> build/lib/cms/test_utils/project/pluginapp/plugins/validation creating build/lib/cms/utils/compat copying cms/utils/compat/__init__.py -> build/lib/cms/utils/compat copying cms/utils/compat/dj.py -> build/lib/cms/utils/compat copying cms/utils/compat/forms.py -> build/lib/cms/utils/compat copying cms/utils/compat/response.py -> build/lib/cms/utils/compat copying cms/utils/compat/warnings.py -> build/lib/cms/utils/compat creating build/lib/menus/migrations copying menus/migrations/0001_initial.py -> build/lib/menus/migrations copying menus/migrations/__init__.py -> build/lib/menus/migrations creating build/lib/menus/templatetags copying menus/templatetags/__init__.py -> build/lib/menus/templatetags copying menus/templatetags/menu_tags.py -> build/lib/menus/templatetags running egg_info writing django_cms.egg-info/PKG-INFO writing dependency_links to django_cms.egg-info/dependency_links.txt writing entry points to django_cms.egg-info/entry_points.txt writing requirements to django_cms.egg-info/requires.txt writing top-level names to django_cms.egg-info/top_level.txt reading manifest file 'django_cms.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'CHANGELOG.txt' warning: no files found matching '*' under directory 'cms/plugins' warning: no files found matching '*' under directory 'stacks/templates' warning: no previously-included files matching '*.pyc' found under directory '*' warning: no previously-included files matching '*.scssc' found under directory '*' adding license file 'LICENSE' adding license file 'AUTHORS' writing manifest file 'django_cms.egg-info/SOURCES.txt' /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ar_SA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ar_SA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ar_SA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ar_SA.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ar_SA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.cmn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.cmn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.cmn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.cmn.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.cmn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.cs_CZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.cs_CZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.cs_CZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.cs_CZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.cs_CZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.en_HK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.en_HK.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.en_HK.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.en_HK.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.en_HK.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.en_US.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.en_US.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.en_US.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.en_US.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.en_US.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.es_BO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.es_BO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.es_BO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.es_BO.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.es_BO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.es_DO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.es_DO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.es_DO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.es_DO.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.es_DO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fi_FI.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fi_FI.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fi_FI.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fi_FI.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fi_FI.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fr_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fr_CA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fr_CA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fr_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fr_CA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fr_FR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fr_FR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fr_FR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fr_FR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fr_FR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.gu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.gu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.gu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.gu.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.gu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ko_KR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ko_KR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ko_KR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ko_KR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ko_KR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ku_IQ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ku_IQ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ku_IQ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ku_IQ.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ku_IQ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.lt_LT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.lt_LT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.lt_LT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.lt_LT.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.lt_LT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.mn_MN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.mn_MN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.mn_MN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.mn_MN.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.mn_MN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.mt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.mt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.mt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.mt.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.mt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.no.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.no.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.no.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.no.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.no.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ro_RO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ro_RO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ro_RO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ro_RO.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ro_RO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ru_RU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ru_RU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ru_RU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ru_RU.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ru_RU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sk_SK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sk_SK.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sk_SK.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sk_SK.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sk_SK.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sl_SI.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sl_SI.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sl_SI.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sl_SI.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sl_SI.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sq_AL.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sq_AL.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sq_AL.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sq_AL.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sq_AL.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale' to be distributed and are already explicitly excluding 'cms.locale' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.th_TH.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.th_TH.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.th_TH.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.th_TH.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.th_TH.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.tlh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.tlh.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.tlh.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.tlh.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.tlh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.zh.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.zh.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.css' to be distributed and are already explicitly excluding 'cms.static.cms.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.fonts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.fonts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.fonts' to be distributed and are already explicitly excluding 'cms.static.cms.fonts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.fonts.src' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.fonts.src' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.fonts.src' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.fonts.src' to be distributed and are already explicitly excluding 'cms.static.cms.fonts.src' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img' to be distributed and are already explicitly excluding 'cms.static.cms.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img.icons.filetypes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img.icons.filetypes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img.icons.filetypes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img.icons.filetypes' to be distributed and are already explicitly excluding 'cms.static.cms.img.icons.filetypes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img.icons.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img.icons.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img.icons.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img.icons.plugins' to be distributed and are already explicitly excluding 'cms.static.cms.img.icons.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img.pagetree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img.pagetree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img.pagetree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img.pagetree' to be distributed and are already explicitly excluding 'cms.static.cms.img.pagetree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img.toolbar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img.toolbar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img.toolbar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img.toolbar' to be distributed and are already explicitly excluding 'cms.static.cms.img.toolbar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js' to be distributed and are already explicitly excluding 'cms.static.cms.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.admin' to be distributed and are already explicitly excluding 'cms.static.cms.js.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.dist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.dist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.dist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.dist' to be distributed and are already explicitly excluding 'cms.static.cms.js.dist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.libs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.libs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.libs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.libs' to be distributed and are already explicitly excluding 'cms.static.cms.js.libs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.libs.jstree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.libs.jstree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.libs.jstree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.libs.jstree' to be distributed and are already explicitly excluding 'cms.static.cms.js.libs.jstree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.modules' to be distributed and are already explicitly excluding 'cms.static.cms.js.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.modules.shortcuts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.modules.shortcuts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.modules.shortcuts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.modules.shortcuts' to be distributed and are already explicitly excluding 'cms.static.cms.js.modules.shortcuts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.polyfills' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.polyfills' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.polyfills' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.polyfills' to be distributed and are already explicitly excluding 'cms.static.cms.js.polyfills' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.select2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.select2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.select2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.select2' to be distributed and are already explicitly excluding 'cms.static.cms.js.select2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.widgets' to be distributed and are already explicitly excluding 'cms.static.cms.js.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass' to be distributed and are already explicitly excluding 'cms.static.cms.sass' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.components' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.components' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.components' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.components' to be distributed and are already explicitly excluding 'cms.static.cms.sass.components' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.components.pagetree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.components.pagetree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.components.pagetree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.components.pagetree' to be distributed and are already explicitly excluding 'cms.static.cms.sass.components.pagetree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.libs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.libs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.libs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.libs' to be distributed and are already explicitly excluding 'cms.static.cms.sass.libs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.mixins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.mixins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.mixins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.mixins' to be distributed and are already explicitly excluding 'cms.static.cms.sass.mixins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.settings' to be distributed and are already explicitly excluding 'cms.static.cms.sass.settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.extensions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.extensions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.extensions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.extensions' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.extensions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.grouper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.grouper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.grouper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.grouper' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.grouper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.icons' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.icons' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.icons' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.icons' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.icons' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.mail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.mail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.mail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.mail' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.mail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.page' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.page' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.page' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.page' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.page' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.page.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.page.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.page.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.page.includes' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.page.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.page.plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.page.plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.page.plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.page.plugin' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.page.plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.page.tree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.page.tree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.page.tree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.page.tree' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.page.tree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.usersettings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.usersettings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.usersettings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.usersettings' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.usersettings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms' to be distributed and are already explicitly excluding 'cms.templates.cms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.headless' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.headless' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.headless' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.headless' to be distributed and are already explicitly excluding 'cms.templates.cms.headless' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.plugins' to be distributed and are already explicitly excluding 'cms.templates.cms.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.toolbar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.toolbar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.toolbar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.toolbar' to be distributed and are already explicitly excluding 'cms.templates.cms.toolbar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.toolbar.items' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.toolbar.items' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.toolbar.items' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.toolbar.items' to be distributed and are already explicitly excluding 'cms.templates.cms.toolbar.items' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.widgets' to be distributed and are already explicitly excluding 'cms.templates.cms.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.wizards' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.wizards' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.wizards' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.wizards' to be distributed and are already explicitly excluding 'cms.templates.cms.wizards' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.wizards.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.wizards.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.wizards.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.wizards.includes' to be distributed and are already explicitly excluding 'cms.templates.cms.wizards.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'menus.templates.menu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'menus.templates.menu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'menus.templates.menu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'menus.templates.menu' to be distributed and are already explicitly excluding 'menus.templates.menu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/cms/locale/af/LC_MESSAGES copying cms/locale/af/LC_MESSAGES/django.mo -> build/lib/cms/locale/af/LC_MESSAGES copying cms/locale/af/LC_MESSAGES/django.po -> build/lib/cms/locale/af/LC_MESSAGES copying cms/locale/af/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/af/LC_MESSAGES copying cms/locale/af/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/af/LC_MESSAGES creating build/lib/cms/locale/ar/LC_MESSAGES copying cms/locale/ar/LC_MESSAGES/django.mo -> build/lib/cms/locale/ar/LC_MESSAGES copying cms/locale/ar/LC_MESSAGES/django.po -> build/lib/cms/locale/ar/LC_MESSAGES copying cms/locale/ar/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ar/LC_MESSAGES copying cms/locale/ar/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ar/LC_MESSAGES creating build/lib/cms/locale/ar_SA/LC_MESSAGES copying cms/locale/ar_SA/LC_MESSAGES/django.mo -> build/lib/cms/locale/ar_SA/LC_MESSAGES copying cms/locale/ar_SA/LC_MESSAGES/django.po -> build/lib/cms/locale/ar_SA/LC_MESSAGES copying cms/locale/ar_SA/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ar_SA/LC_MESSAGES copying cms/locale/ar_SA/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ar_SA/LC_MESSAGES creating build/lib/cms/locale/be/LC_MESSAGES copying cms/locale/be/LC_MESSAGES/django.mo -> build/lib/cms/locale/be/LC_MESSAGES copying cms/locale/be/LC_MESSAGES/django.po -> build/lib/cms/locale/be/LC_MESSAGES copying cms/locale/be/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/be/LC_MESSAGES copying cms/locale/be/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/be/LC_MESSAGES creating build/lib/cms/locale/bg/LC_MESSAGES copying cms/locale/bg/LC_MESSAGES/django.mo -> build/lib/cms/locale/bg/LC_MESSAGES copying cms/locale/bg/LC_MESSAGES/django.po -> build/lib/cms/locale/bg/LC_MESSAGES copying cms/locale/bg/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/bg/LC_MESSAGES copying cms/locale/bg/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/bg/LC_MESSAGES creating build/lib/cms/locale/bn/LC_MESSAGES copying cms/locale/bn/LC_MESSAGES/django.mo -> build/lib/cms/locale/bn/LC_MESSAGES copying cms/locale/bn/LC_MESSAGES/django.po -> build/lib/cms/locale/bn/LC_MESSAGES copying cms/locale/bn/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/bn/LC_MESSAGES copying cms/locale/bn/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/bn/LC_MESSAGES creating build/lib/cms/locale/ca/LC_MESSAGES copying cms/locale/ca/LC_MESSAGES/django.mo -> build/lib/cms/locale/ca/LC_MESSAGES copying cms/locale/ca/LC_MESSAGES/django.po -> build/lib/cms/locale/ca/LC_MESSAGES copying cms/locale/ca/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ca/LC_MESSAGES copying cms/locale/ca/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ca/LC_MESSAGES creating build/lib/cms/locale/cmn/LC_MESSAGES copying cms/locale/cmn/LC_MESSAGES/django.mo -> build/lib/cms/locale/cmn/LC_MESSAGES copying cms/locale/cmn/LC_MESSAGES/django.po -> build/lib/cms/locale/cmn/LC_MESSAGES copying cms/locale/cmn/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/cmn/LC_MESSAGES copying cms/locale/cmn/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/cmn/LC_MESSAGES creating build/lib/cms/locale/cs/LC_MESSAGES copying cms/locale/cs/LC_MESSAGES/django.mo -> build/lib/cms/locale/cs/LC_MESSAGES copying cms/locale/cs/LC_MESSAGES/django.po -> build/lib/cms/locale/cs/LC_MESSAGES copying cms/locale/cs/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/cs/LC_MESSAGES copying cms/locale/cs/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/cs/LC_MESSAGES creating build/lib/cms/locale/cs_CZ/LC_MESSAGES copying cms/locale/cs_CZ/LC_MESSAGES/django.mo -> build/lib/cms/locale/cs_CZ/LC_MESSAGES copying cms/locale/cs_CZ/LC_MESSAGES/django.po -> build/lib/cms/locale/cs_CZ/LC_MESSAGES copying cms/locale/cs_CZ/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/cs_CZ/LC_MESSAGES copying cms/locale/cs_CZ/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/cs_CZ/LC_MESSAGES creating build/lib/cms/locale/cy/LC_MESSAGES copying cms/locale/cy/LC_MESSAGES/django.mo -> build/lib/cms/locale/cy/LC_MESSAGES copying cms/locale/cy/LC_MESSAGES/django.po -> build/lib/cms/locale/cy/LC_MESSAGES copying cms/locale/cy/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/cy/LC_MESSAGES copying cms/locale/cy/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/cy/LC_MESSAGES creating build/lib/cms/locale/da/LC_MESSAGES copying cms/locale/da/LC_MESSAGES/django.mo -> build/lib/cms/locale/da/LC_MESSAGES copying cms/locale/da/LC_MESSAGES/django.po -> build/lib/cms/locale/da/LC_MESSAGES copying cms/locale/da/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/da/LC_MESSAGES copying cms/locale/da/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/da/LC_MESSAGES creating build/lib/cms/locale/de/LC_MESSAGES copying cms/locale/de/LC_MESSAGES/django.mo -> build/lib/cms/locale/de/LC_MESSAGES copying cms/locale/de/LC_MESSAGES/django.po -> build/lib/cms/locale/de/LC_MESSAGES copying cms/locale/de/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/de/LC_MESSAGES copying cms/locale/de/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/de/LC_MESSAGES creating build/lib/cms/locale/el/LC_MESSAGES copying cms/locale/el/LC_MESSAGES/django.mo -> build/lib/cms/locale/el/LC_MESSAGES copying cms/locale/el/LC_MESSAGES/django.po -> build/lib/cms/locale/el/LC_MESSAGES copying cms/locale/el/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/el/LC_MESSAGES copying cms/locale/el/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/el/LC_MESSAGES creating build/lib/cms/locale/en/LC_MESSAGES copying cms/locale/en/LC_MESSAGES/django.mo -> build/lib/cms/locale/en/LC_MESSAGES copying cms/locale/en/LC_MESSAGES/django.po -> build/lib/cms/locale/en/LC_MESSAGES copying cms/locale/en/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/en/LC_MESSAGES copying cms/locale/en/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/en/LC_MESSAGES creating build/lib/cms/locale/en_GB/LC_MESSAGES copying cms/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/cms/locale/en_GB/LC_MESSAGES copying cms/locale/en_GB/LC_MESSAGES/django.po -> build/lib/cms/locale/en_GB/LC_MESSAGES copying cms/locale/en_GB/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/en_GB/LC_MESSAGES copying cms/locale/en_GB/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/en_GB/LC_MESSAGES creating build/lib/cms/locale/en_HK/LC_MESSAGES copying cms/locale/en_HK/LC_MESSAGES/django.mo -> build/lib/cms/locale/en_HK/LC_MESSAGES copying cms/locale/en_HK/LC_MESSAGES/django.po -> build/lib/cms/locale/en_HK/LC_MESSAGES copying cms/locale/en_HK/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/en_HK/LC_MESSAGES copying cms/locale/en_HK/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/en_HK/LC_MESSAGES creating build/lib/cms/locale/en_US/LC_MESSAGES copying cms/locale/en_US/LC_MESSAGES/django.mo -> build/lib/cms/locale/en_US/LC_MESSAGES copying cms/locale/en_US/LC_MESSAGES/django.po -> build/lib/cms/locale/en_US/LC_MESSAGES copying cms/locale/en_US/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/en_US/LC_MESSAGES copying cms/locale/en_US/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/en_US/LC_MESSAGES creating build/lib/cms/locale/eo/LC_MESSAGES copying cms/locale/eo/LC_MESSAGES/django.mo -> build/lib/cms/locale/eo/LC_MESSAGES copying cms/locale/eo/LC_MESSAGES/django.po -> build/lib/cms/locale/eo/LC_MESSAGES copying cms/locale/eo/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/eo/LC_MESSAGES copying cms/locale/eo/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/eo/LC_MESSAGES creating build/lib/cms/locale/es/LC_MESSAGES copying cms/locale/es/LC_MESSAGES/django.mo -> build/lib/cms/locale/es/LC_MESSAGES copying cms/locale/es/LC_MESSAGES/django.po -> build/lib/cms/locale/es/LC_MESSAGES copying cms/locale/es/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/es/LC_MESSAGES copying cms/locale/es/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/es/LC_MESSAGES creating build/lib/cms/locale/es_AR/LC_MESSAGES copying cms/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/cms/locale/es_AR/LC_MESSAGES copying cms/locale/es_AR/LC_MESSAGES/django.po -> build/lib/cms/locale/es_AR/LC_MESSAGES copying cms/locale/es_AR/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/es_AR/LC_MESSAGES copying cms/locale/es_AR/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/es_AR/LC_MESSAGES creating build/lib/cms/locale/es_BO/LC_MESSAGES copying cms/locale/es_BO/LC_MESSAGES/django.mo -> build/lib/cms/locale/es_BO/LC_MESSAGES copying cms/locale/es_BO/LC_MESSAGES/django.po -> build/lib/cms/locale/es_BO/LC_MESSAGES copying cms/locale/es_BO/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/es_BO/LC_MESSAGES copying cms/locale/es_BO/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/es_BO/LC_MESSAGES creating build/lib/cms/locale/es_DO/LC_MESSAGES copying cms/locale/es_DO/LC_MESSAGES/django.mo -> build/lib/cms/locale/es_DO/LC_MESSAGES copying cms/locale/es_DO/LC_MESSAGES/django.po -> build/lib/cms/locale/es_DO/LC_MESSAGES copying cms/locale/es_DO/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/es_DO/LC_MESSAGES copying cms/locale/es_DO/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/es_DO/LC_MESSAGES creating build/lib/cms/locale/et/LC_MESSAGES copying cms/locale/et/LC_MESSAGES/django.mo -> build/lib/cms/locale/et/LC_MESSAGES copying cms/locale/et/LC_MESSAGES/django.po -> build/lib/cms/locale/et/LC_MESSAGES copying cms/locale/et/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/et/LC_MESSAGES copying cms/locale/et/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/et/LC_MESSAGES creating build/lib/cms/locale/eu/LC_MESSAGES copying cms/locale/eu/LC_MESSAGES/django.mo -> build/lib/cms/locale/eu/LC_MESSAGES copying cms/locale/eu/LC_MESSAGES/django.po -> build/lib/cms/locale/eu/LC_MESSAGES copying cms/locale/eu/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/eu/LC_MESSAGES copying cms/locale/eu/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/eu/LC_MESSAGES creating build/lib/cms/locale/fa/LC_MESSAGES copying cms/locale/fa/LC_MESSAGES/django.mo -> build/lib/cms/locale/fa/LC_MESSAGES copying cms/locale/fa/LC_MESSAGES/django.po -> build/lib/cms/locale/fa/LC_MESSAGES copying cms/locale/fa/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/fa/LC_MESSAGES copying cms/locale/fa/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/fa/LC_MESSAGES creating build/lib/cms/locale/fa_IR/LC_MESSAGES copying cms/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/cms/locale/fa_IR/LC_MESSAGES copying cms/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/cms/locale/fa_IR/LC_MESSAGES copying cms/locale/fa_IR/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/fa_IR/LC_MESSAGES copying cms/locale/fa_IR/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/fa_IR/LC_MESSAGES creating build/lib/cms/locale/fi/LC_MESSAGES copying cms/locale/fi/LC_MESSAGES/django.mo -> build/lib/cms/locale/fi/LC_MESSAGES copying cms/locale/fi/LC_MESSAGES/django.po -> build/lib/cms/locale/fi/LC_MESSAGES copying cms/locale/fi/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/fi/LC_MESSAGES copying cms/locale/fi/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/fi/LC_MESSAGES creating build/lib/cms/locale/fi_FI/LC_MESSAGES copying cms/locale/fi_FI/LC_MESSAGES/django.mo -> build/lib/cms/locale/fi_FI/LC_MESSAGES copying cms/locale/fi_FI/LC_MESSAGES/django.po -> build/lib/cms/locale/fi_FI/LC_MESSAGES copying cms/locale/fi_FI/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/fi_FI/LC_MESSAGES copying cms/locale/fi_FI/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/fi_FI/LC_MESSAGES creating build/lib/cms/locale/fr/LC_MESSAGES copying cms/locale/fr/LC_MESSAGES/django.mo -> build/lib/cms/locale/fr/LC_MESSAGES copying cms/locale/fr/LC_MESSAGES/django.po -> build/lib/cms/locale/fr/LC_MESSAGES copying cms/locale/fr/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/fr/LC_MESSAGES copying cms/locale/fr/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/fr/LC_MESSAGES creating build/lib/cms/locale/fr_CA/LC_MESSAGES copying cms/locale/fr_CA/LC_MESSAGES/django.mo -> build/lib/cms/locale/fr_CA/LC_MESSAGES copying cms/locale/fr_CA/LC_MESSAGES/django.po -> build/lib/cms/locale/fr_CA/LC_MESSAGES copying cms/locale/fr_CA/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/fr_CA/LC_MESSAGES copying cms/locale/fr_CA/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/fr_CA/LC_MESSAGES creating build/lib/cms/locale/fr_FR/LC_MESSAGES copying cms/locale/fr_FR/LC_MESSAGES/django.mo -> build/lib/cms/locale/fr_FR/LC_MESSAGES copying cms/locale/fr_FR/LC_MESSAGES/django.po -> build/lib/cms/locale/fr_FR/LC_MESSAGES copying cms/locale/fr_FR/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/fr_FR/LC_MESSAGES copying cms/locale/fr_FR/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/fr_FR/LC_MESSAGES creating build/lib/cms/locale/ga/LC_MESSAGES copying cms/locale/ga/LC_MESSAGES/django.mo -> build/lib/cms/locale/ga/LC_MESSAGES copying cms/locale/ga/LC_MESSAGES/django.po -> build/lib/cms/locale/ga/LC_MESSAGES copying cms/locale/ga/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ga/LC_MESSAGES copying cms/locale/ga/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ga/LC_MESSAGES creating build/lib/cms/locale/gl/LC_MESSAGES copying cms/locale/gl/LC_MESSAGES/django.mo -> build/lib/cms/locale/gl/LC_MESSAGES copying cms/locale/gl/LC_MESSAGES/django.po -> build/lib/cms/locale/gl/LC_MESSAGES copying cms/locale/gl/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/gl/LC_MESSAGES copying cms/locale/gl/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/gl/LC_MESSAGES creating build/lib/cms/locale/gu/LC_MESSAGES copying cms/locale/gu/LC_MESSAGES/django.mo -> build/lib/cms/locale/gu/LC_MESSAGES copying cms/locale/gu/LC_MESSAGES/django.po -> build/lib/cms/locale/gu/LC_MESSAGES copying cms/locale/gu/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/gu/LC_MESSAGES copying cms/locale/gu/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/gu/LC_MESSAGES creating build/lib/cms/locale/he/LC_MESSAGES copying cms/locale/he/LC_MESSAGES/django.mo -> build/lib/cms/locale/he/LC_MESSAGES copying cms/locale/he/LC_MESSAGES/django.po -> build/lib/cms/locale/he/LC_MESSAGES copying cms/locale/he/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/he/LC_MESSAGES copying cms/locale/he/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/he/LC_MESSAGES creating build/lib/cms/locale/hi/LC_MESSAGES copying cms/locale/hi/LC_MESSAGES/django.mo -> build/lib/cms/locale/hi/LC_MESSAGES copying cms/locale/hi/LC_MESSAGES/django.po -> build/lib/cms/locale/hi/LC_MESSAGES copying cms/locale/hi/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/hi/LC_MESSAGES copying cms/locale/hi/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/hi/LC_MESSAGES creating build/lib/cms/locale/hr/LC_MESSAGES copying cms/locale/hr/LC_MESSAGES/django.mo -> build/lib/cms/locale/hr/LC_MESSAGES copying cms/locale/hr/LC_MESSAGES/django.po -> build/lib/cms/locale/hr/LC_MESSAGES copying cms/locale/hr/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/hr/LC_MESSAGES copying cms/locale/hr/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/hr/LC_MESSAGES creating build/lib/cms/locale/hu/LC_MESSAGES copying cms/locale/hu/LC_MESSAGES/django.mo -> build/lib/cms/locale/hu/LC_MESSAGES copying cms/locale/hu/LC_MESSAGES/django.po -> build/lib/cms/locale/hu/LC_MESSAGES copying cms/locale/hu/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/hu/LC_MESSAGES copying cms/locale/hu/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/hu/LC_MESSAGES creating build/lib/cms/locale/id/LC_MESSAGES copying cms/locale/id/LC_MESSAGES/django.mo -> build/lib/cms/locale/id/LC_MESSAGES copying cms/locale/id/LC_MESSAGES/django.po -> build/lib/cms/locale/id/LC_MESSAGES copying cms/locale/id/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/id/LC_MESSAGES copying cms/locale/id/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/id/LC_MESSAGES creating build/lib/cms/locale/is/LC_MESSAGES copying cms/locale/is/LC_MESSAGES/django.mo -> build/lib/cms/locale/is/LC_MESSAGES copying cms/locale/is/LC_MESSAGES/django.po -> build/lib/cms/locale/is/LC_MESSAGES copying cms/locale/is/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/is/LC_MESSAGES copying cms/locale/is/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/is/LC_MESSAGES creating build/lib/cms/locale/is_IS/LC_MESSAGES copying cms/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/cms/locale/is_IS/LC_MESSAGES copying cms/locale/is_IS/LC_MESSAGES/django.po -> build/lib/cms/locale/is_IS/LC_MESSAGES copying cms/locale/is_IS/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/is_IS/LC_MESSAGES copying cms/locale/is_IS/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/is_IS/LC_MESSAGES creating build/lib/cms/locale/it/LC_MESSAGES copying cms/locale/it/LC_MESSAGES/django.mo -> build/lib/cms/locale/it/LC_MESSAGES copying cms/locale/it/LC_MESSAGES/django.po -> build/lib/cms/locale/it/LC_MESSAGES copying cms/locale/it/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/it/LC_MESSAGES copying cms/locale/it/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/it/LC_MESSAGES creating build/lib/cms/locale/ja/LC_MESSAGES copying cms/locale/ja/LC_MESSAGES/django.mo -> build/lib/cms/locale/ja/LC_MESSAGES copying cms/locale/ja/LC_MESSAGES/django.po -> build/lib/cms/locale/ja/LC_MESSAGES copying cms/locale/ja/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ja/LC_MESSAGES copying cms/locale/ja/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ja/LC_MESSAGES creating build/lib/cms/locale/ka/LC_MESSAGES copying cms/locale/ka/LC_MESSAGES/django.mo -> build/lib/cms/locale/ka/LC_MESSAGES copying cms/locale/ka/LC_MESSAGES/django.po -> build/lib/cms/locale/ka/LC_MESSAGES copying cms/locale/ka/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ka/LC_MESSAGES copying cms/locale/ka/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ka/LC_MESSAGES creating build/lib/cms/locale/kk/LC_MESSAGES copying cms/locale/kk/LC_MESSAGES/django.mo -> build/lib/cms/locale/kk/LC_MESSAGES copying cms/locale/kk/LC_MESSAGES/django.po -> build/lib/cms/locale/kk/LC_MESSAGES copying cms/locale/kk/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/kk/LC_MESSAGES copying cms/locale/kk/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/kk/LC_MESSAGES creating build/lib/cms/locale/km/LC_MESSAGES copying cms/locale/km/LC_MESSAGES/django.mo -> build/lib/cms/locale/km/LC_MESSAGES copying cms/locale/km/LC_MESSAGES/django.po -> build/lib/cms/locale/km/LC_MESSAGES copying cms/locale/km/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/km/LC_MESSAGES copying cms/locale/km/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/km/LC_MESSAGES creating build/lib/cms/locale/ko/LC_MESSAGES copying cms/locale/ko/LC_MESSAGES/django.mo -> build/lib/cms/locale/ko/LC_MESSAGES copying cms/locale/ko/LC_MESSAGES/django.po -> build/lib/cms/locale/ko/LC_MESSAGES copying cms/locale/ko/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ko/LC_MESSAGES copying cms/locale/ko/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ko/LC_MESSAGES creating build/lib/cms/locale/ko_KR/LC_MESSAGES copying cms/locale/ko_KR/LC_MESSAGES/django.mo -> build/lib/cms/locale/ko_KR/LC_MESSAGES copying cms/locale/ko_KR/LC_MESSAGES/django.po -> build/lib/cms/locale/ko_KR/LC_MESSAGES copying cms/locale/ko_KR/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ko_KR/LC_MESSAGES copying cms/locale/ko_KR/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ko_KR/LC_MESSAGES creating build/lib/cms/locale/ku_IQ/LC_MESSAGES copying cms/locale/ku_IQ/LC_MESSAGES/django.mo -> build/lib/cms/locale/ku_IQ/LC_MESSAGES copying cms/locale/ku_IQ/LC_MESSAGES/django.po -> build/lib/cms/locale/ku_IQ/LC_MESSAGES copying cms/locale/ku_IQ/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ku_IQ/LC_MESSAGES copying cms/locale/ku_IQ/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ku_IQ/LC_MESSAGES creating build/lib/cms/locale/ky/LC_MESSAGES copying cms/locale/ky/LC_MESSAGES/django.mo -> build/lib/cms/locale/ky/LC_MESSAGES copying cms/locale/ky/LC_MESSAGES/django.po -> build/lib/cms/locale/ky/LC_MESSAGES copying cms/locale/ky/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ky/LC_MESSAGES copying cms/locale/ky/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ky/LC_MESSAGES creating build/lib/cms/locale/lt/LC_MESSAGES copying cms/locale/lt/LC_MESSAGES/django.mo -> build/lib/cms/locale/lt/LC_MESSAGES copying cms/locale/lt/LC_MESSAGES/django.po -> build/lib/cms/locale/lt/LC_MESSAGES copying cms/locale/lt/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/lt/LC_MESSAGES copying cms/locale/lt/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/lt/LC_MESSAGES creating build/lib/cms/locale/lt_LT/LC_MESSAGES copying cms/locale/lt_LT/LC_MESSAGES/django.mo -> build/lib/cms/locale/lt_LT/LC_MESSAGES copying cms/locale/lt_LT/LC_MESSAGES/django.po -> build/lib/cms/locale/lt_LT/LC_MESSAGES copying cms/locale/lt_LT/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/lt_LT/LC_MESSAGES copying cms/locale/lt_LT/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/lt_LT/LC_MESSAGES creating build/lib/cms/locale/lv/LC_MESSAGES copying cms/locale/lv/LC_MESSAGES/django.mo -> build/lib/cms/locale/lv/LC_MESSAGES copying cms/locale/lv/LC_MESSAGES/django.po -> build/lib/cms/locale/lv/LC_MESSAGES copying cms/locale/lv/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/lv/LC_MESSAGES copying cms/locale/lv/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/lv/LC_MESSAGES creating build/lib/cms/locale/ml/LC_MESSAGES copying cms/locale/ml/LC_MESSAGES/django.mo -> build/lib/cms/locale/ml/LC_MESSAGES copying cms/locale/ml/LC_MESSAGES/django.po -> build/lib/cms/locale/ml/LC_MESSAGES copying cms/locale/ml/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ml/LC_MESSAGES copying cms/locale/ml/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ml/LC_MESSAGES creating build/lib/cms/locale/mn/LC_MESSAGES copying cms/locale/mn/LC_MESSAGES/django.mo -> build/lib/cms/locale/mn/LC_MESSAGES copying cms/locale/mn/LC_MESSAGES/django.po -> build/lib/cms/locale/mn/LC_MESSAGES copying cms/locale/mn/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/mn/LC_MESSAGES copying cms/locale/mn/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/mn/LC_MESSAGES creating build/lib/cms/locale/mn_MN/LC_MESSAGES copying cms/locale/mn_MN/LC_MESSAGES/django.mo -> build/lib/cms/locale/mn_MN/LC_MESSAGES copying cms/locale/mn_MN/LC_MESSAGES/django.po -> build/lib/cms/locale/mn_MN/LC_MESSAGES copying cms/locale/mn_MN/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/mn_MN/LC_MESSAGES copying cms/locale/mn_MN/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/mn_MN/LC_MESSAGES creating build/lib/cms/locale/ms/LC_MESSAGES copying cms/locale/ms/LC_MESSAGES/django.mo -> build/lib/cms/locale/ms/LC_MESSAGES copying cms/locale/ms/LC_MESSAGES/django.po -> build/lib/cms/locale/ms/LC_MESSAGES copying cms/locale/ms/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ms/LC_MESSAGES copying cms/locale/ms/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ms/LC_MESSAGES creating build/lib/cms/locale/mt/LC_MESSAGES copying cms/locale/mt/LC_MESSAGES/django.mo -> build/lib/cms/locale/mt/LC_MESSAGES copying cms/locale/mt/LC_MESSAGES/django.po -> build/lib/cms/locale/mt/LC_MESSAGES copying cms/locale/mt/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/mt/LC_MESSAGES copying cms/locale/mt/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/mt/LC_MESSAGES creating build/lib/cms/locale/nb/LC_MESSAGES copying cms/locale/nb/LC_MESSAGES/django.mo -> build/lib/cms/locale/nb/LC_MESSAGES copying cms/locale/nb/LC_MESSAGES/django.po -> build/lib/cms/locale/nb/LC_MESSAGES copying cms/locale/nb/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/nb/LC_MESSAGES copying cms/locale/nb/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/nb/LC_MESSAGES creating build/lib/cms/locale/nl/LC_MESSAGES copying cms/locale/nl/LC_MESSAGES/django.mo -> build/lib/cms/locale/nl/LC_MESSAGES copying cms/locale/nl/LC_MESSAGES/django.po -> build/lib/cms/locale/nl/LC_MESSAGES copying cms/locale/nl/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/nl/LC_MESSAGES copying cms/locale/nl/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/nl/LC_MESSAGES creating build/lib/cms/locale/no/LC_MESSAGES copying cms/locale/no/LC_MESSAGES/django.mo -> build/lib/cms/locale/no/LC_MESSAGES copying cms/locale/no/LC_MESSAGES/django.po -> build/lib/cms/locale/no/LC_MESSAGES copying cms/locale/no/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/no/LC_MESSAGES copying cms/locale/no/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/no/LC_MESSAGES creating build/lib/cms/locale/pap/LC_MESSAGES copying cms/locale/pap/LC_MESSAGES/django.mo -> build/lib/cms/locale/pap/LC_MESSAGES copying cms/locale/pap/LC_MESSAGES/django.po -> build/lib/cms/locale/pap/LC_MESSAGES copying cms/locale/pap/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/pap/LC_MESSAGES copying cms/locale/pap/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/pap/LC_MESSAGES creating build/lib/cms/locale/pl/LC_MESSAGES copying cms/locale/pl/LC_MESSAGES/django.mo -> build/lib/cms/locale/pl/LC_MESSAGES copying cms/locale/pl/LC_MESSAGES/django.po -> build/lib/cms/locale/pl/LC_MESSAGES copying cms/locale/pl/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/pl/LC_MESSAGES copying cms/locale/pl/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/pl/LC_MESSAGES creating build/lib/cms/locale/pt/LC_MESSAGES copying cms/locale/pt/LC_MESSAGES/django.mo -> build/lib/cms/locale/pt/LC_MESSAGES copying cms/locale/pt/LC_MESSAGES/django.po -> build/lib/cms/locale/pt/LC_MESSAGES copying cms/locale/pt/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/pt/LC_MESSAGES copying cms/locale/pt/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/pt/LC_MESSAGES creating build/lib/cms/locale/pt_BR/LC_MESSAGES copying cms/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/cms/locale/pt_BR/LC_MESSAGES copying cms/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/cms/locale/pt_BR/LC_MESSAGES copying cms/locale/pt_BR/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/pt_BR/LC_MESSAGES copying cms/locale/pt_BR/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/pt_BR/LC_MESSAGES creating build/lib/cms/locale/pt_PT/LC_MESSAGES copying cms/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/cms/locale/pt_PT/LC_MESSAGES copying cms/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/cms/locale/pt_PT/LC_MESSAGES copying cms/locale/pt_PT/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/pt_PT/LC_MESSAGES copying cms/locale/pt_PT/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/pt_PT/LC_MESSAGES creating build/lib/cms/locale/ro/LC_MESSAGES copying cms/locale/ro/LC_MESSAGES/django.mo -> build/lib/cms/locale/ro/LC_MESSAGES copying cms/locale/ro/LC_MESSAGES/django.po -> build/lib/cms/locale/ro/LC_MESSAGES copying cms/locale/ro/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ro/LC_MESSAGES copying cms/locale/ro/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ro/LC_MESSAGES creating build/lib/cms/locale/ro_RO/LC_MESSAGES copying cms/locale/ro_RO/LC_MESSAGES/django.mo -> build/lib/cms/locale/ro_RO/LC_MESSAGES copying cms/locale/ro_RO/LC_MESSAGES/django.po -> build/lib/cms/locale/ro_RO/LC_MESSAGES copying cms/locale/ro_RO/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ro_RO/LC_MESSAGES copying cms/locale/ro_RO/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ro_RO/LC_MESSAGES creating build/lib/cms/locale/ru/LC_MESSAGES copying cms/locale/ru/LC_MESSAGES/django.mo -> build/lib/cms/locale/ru/LC_MESSAGES copying cms/locale/ru/LC_MESSAGES/django.po -> build/lib/cms/locale/ru/LC_MESSAGES copying cms/locale/ru/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ru/LC_MESSAGES copying cms/locale/ru/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ru/LC_MESSAGES creating build/lib/cms/locale/ru_RU/LC_MESSAGES copying cms/locale/ru_RU/LC_MESSAGES/django.mo -> build/lib/cms/locale/ru_RU/LC_MESSAGES copying cms/locale/ru_RU/LC_MESSAGES/django.po -> build/lib/cms/locale/ru_RU/LC_MESSAGES copying cms/locale/ru_RU/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ru_RU/LC_MESSAGES copying cms/locale/ru_RU/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ru_RU/LC_MESSAGES creating build/lib/cms/locale/sk/LC_MESSAGES copying cms/locale/sk/LC_MESSAGES/django.mo -> build/lib/cms/locale/sk/LC_MESSAGES copying cms/locale/sk/LC_MESSAGES/django.po -> build/lib/cms/locale/sk/LC_MESSAGES copying cms/locale/sk/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sk/LC_MESSAGES copying cms/locale/sk/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sk/LC_MESSAGES creating build/lib/cms/locale/sk_SK/LC_MESSAGES copying cms/locale/sk_SK/LC_MESSAGES/django.mo -> build/lib/cms/locale/sk_SK/LC_MESSAGES copying cms/locale/sk_SK/LC_MESSAGES/django.po -> build/lib/cms/locale/sk_SK/LC_MESSAGES copying cms/locale/sk_SK/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sk_SK/LC_MESSAGES copying cms/locale/sk_SK/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sk_SK/LC_MESSAGES creating build/lib/cms/locale/sl/LC_MESSAGES copying cms/locale/sl/LC_MESSAGES/django.mo -> build/lib/cms/locale/sl/LC_MESSAGES copying cms/locale/sl/LC_MESSAGES/django.po -> build/lib/cms/locale/sl/LC_MESSAGES copying cms/locale/sl/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sl/LC_MESSAGES copying cms/locale/sl/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sl/LC_MESSAGES creating build/lib/cms/locale/sl_SI/LC_MESSAGES copying cms/locale/sl_SI/LC_MESSAGES/django.mo -> build/lib/cms/locale/sl_SI/LC_MESSAGES copying cms/locale/sl_SI/LC_MESSAGES/django.po -> build/lib/cms/locale/sl_SI/LC_MESSAGES copying cms/locale/sl_SI/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sl_SI/LC_MESSAGES copying cms/locale/sl_SI/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sl_SI/LC_MESSAGES creating build/lib/cms/locale/sq/LC_MESSAGES copying cms/locale/sq/LC_MESSAGES/django.mo -> build/lib/cms/locale/sq/LC_MESSAGES copying cms/locale/sq/LC_MESSAGES/django.po -> build/lib/cms/locale/sq/LC_MESSAGES copying cms/locale/sq/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sq/LC_MESSAGES copying cms/locale/sq/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sq/LC_MESSAGES creating build/lib/cms/locale/sq_AL/LC_MESSAGES copying cms/locale/sq_AL/LC_MESSAGES/django.mo -> build/lib/cms/locale/sq_AL/LC_MESSAGES copying cms/locale/sq_AL/LC_MESSAGES/django.po -> build/lib/cms/locale/sq_AL/LC_MESSAGES copying cms/locale/sq_AL/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sq_AL/LC_MESSAGES copying cms/locale/sq_AL/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sq_AL/LC_MESSAGES creating build/lib/cms/locale/sr/LC_MESSAGES copying cms/locale/sr/LC_MESSAGES/django.mo -> build/lib/cms/locale/sr/LC_MESSAGES copying cms/locale/sr/LC_MESSAGES/django.po -> build/lib/cms/locale/sr/LC_MESSAGES copying cms/locale/sr/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sr/LC_MESSAGES copying cms/locale/sr/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sr/LC_MESSAGES creating build/lib/cms/locale/sr@latin/LC_MESSAGES copying cms/locale/sr@latin/LC_MESSAGES/django.mo -> build/lib/cms/locale/sr@latin/LC_MESSAGES copying cms/locale/sr@latin/LC_MESSAGES/django.po -> build/lib/cms/locale/sr@latin/LC_MESSAGES copying cms/locale/sr@latin/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sr@latin/LC_MESSAGES copying cms/locale/sr@latin/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sr@latin/LC_MESSAGES creating build/lib/cms/locale/sv/LC_MESSAGES copying cms/locale/sv/LC_MESSAGES/django.mo -> build/lib/cms/locale/sv/LC_MESSAGES copying cms/locale/sv/LC_MESSAGES/django.po -> build/lib/cms/locale/sv/LC_MESSAGES copying cms/locale/sv/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/sv/LC_MESSAGES copying cms/locale/sv/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/sv/LC_MESSAGES creating build/lib/cms/locale/ta/LC_MESSAGES copying cms/locale/ta/LC_MESSAGES/django.mo -> build/lib/cms/locale/ta/LC_MESSAGES copying cms/locale/ta/LC_MESSAGES/django.po -> build/lib/cms/locale/ta/LC_MESSAGES copying cms/locale/ta/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ta/LC_MESSAGES copying cms/locale/ta/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ta/LC_MESSAGES creating build/lib/cms/locale/th/LC_MESSAGES copying cms/locale/th/LC_MESSAGES/django.mo -> build/lib/cms/locale/th/LC_MESSAGES copying cms/locale/th/LC_MESSAGES/django.po -> build/lib/cms/locale/th/LC_MESSAGES copying cms/locale/th/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/th/LC_MESSAGES copying cms/locale/th/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/th/LC_MESSAGES creating build/lib/cms/locale/th_TH/LC_MESSAGES copying cms/locale/th_TH/LC_MESSAGES/django.mo -> build/lib/cms/locale/th_TH/LC_MESSAGES copying cms/locale/th_TH/LC_MESSAGES/django.po -> build/lib/cms/locale/th_TH/LC_MESSAGES copying cms/locale/th_TH/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/th_TH/LC_MESSAGES copying cms/locale/th_TH/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/th_TH/LC_MESSAGES creating build/lib/cms/locale/tlh/LC_MESSAGES copying cms/locale/tlh/LC_MESSAGES/django.mo -> build/lib/cms/locale/tlh/LC_MESSAGES copying cms/locale/tlh/LC_MESSAGES/django.po -> build/lib/cms/locale/tlh/LC_MESSAGES copying cms/locale/tlh/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/tlh/LC_MESSAGES copying cms/locale/tlh/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/tlh/LC_MESSAGES creating build/lib/cms/locale/tr/LC_MESSAGES copying cms/locale/tr/LC_MESSAGES/django.mo -> build/lib/cms/locale/tr/LC_MESSAGES copying cms/locale/tr/LC_MESSAGES/django.po -> build/lib/cms/locale/tr/LC_MESSAGES copying cms/locale/tr/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/tr/LC_MESSAGES copying cms/locale/tr/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/tr/LC_MESSAGES creating build/lib/cms/locale/tr_TR/LC_MESSAGES copying cms/locale/tr_TR/LC_MESSAGES/django.mo -> build/lib/cms/locale/tr_TR/LC_MESSAGES copying cms/locale/tr_TR/LC_MESSAGES/django.po -> build/lib/cms/locale/tr_TR/LC_MESSAGES copying cms/locale/tr_TR/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/tr_TR/LC_MESSAGES copying cms/locale/tr_TR/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/tr_TR/LC_MESSAGES creating build/lib/cms/locale/ug/LC_MESSAGES copying cms/locale/ug/LC_MESSAGES/django.mo -> build/lib/cms/locale/ug/LC_MESSAGES copying cms/locale/ug/LC_MESSAGES/django.po -> build/lib/cms/locale/ug/LC_MESSAGES copying cms/locale/ug/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ug/LC_MESSAGES copying cms/locale/ug/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ug/LC_MESSAGES creating build/lib/cms/locale/uk/LC_MESSAGES copying cms/locale/uk/LC_MESSAGES/django.mo -> build/lib/cms/locale/uk/LC_MESSAGES copying cms/locale/uk/LC_MESSAGES/django.po -> build/lib/cms/locale/uk/LC_MESSAGES copying cms/locale/uk/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/uk/LC_MESSAGES copying cms/locale/uk/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/uk/LC_MESSAGES creating build/lib/cms/locale/ur/LC_MESSAGES copying cms/locale/ur/LC_MESSAGES/django.mo -> build/lib/cms/locale/ur/LC_MESSAGES copying cms/locale/ur/LC_MESSAGES/django.po -> build/lib/cms/locale/ur/LC_MESSAGES copying cms/locale/ur/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/ur/LC_MESSAGES copying cms/locale/ur/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/ur/LC_MESSAGES creating build/lib/cms/locale/vi/LC_MESSAGES copying cms/locale/vi/LC_MESSAGES/django.mo -> build/lib/cms/locale/vi/LC_MESSAGES copying cms/locale/vi/LC_MESSAGES/django.po -> build/lib/cms/locale/vi/LC_MESSAGES copying cms/locale/vi/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/vi/LC_MESSAGES copying cms/locale/vi/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/vi/LC_MESSAGES creating build/lib/cms/locale/vi_VN/LC_MESSAGES copying cms/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/cms/locale/vi_VN/LC_MESSAGES copying cms/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/cms/locale/vi_VN/LC_MESSAGES copying cms/locale/vi_VN/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/vi_VN/LC_MESSAGES copying cms/locale/vi_VN/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/vi_VN/LC_MESSAGES creating build/lib/cms/locale/zh-Hans/LC_MESSAGES copying cms/locale/zh-Hans/LC_MESSAGES/django.mo -> build/lib/cms/locale/zh-Hans/LC_MESSAGES copying cms/locale/zh-Hans/LC_MESSAGES/django.po -> build/lib/cms/locale/zh-Hans/LC_MESSAGES copying cms/locale/zh-Hans/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/zh-Hans/LC_MESSAGES copying cms/locale/zh-Hans/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/zh-Hans/LC_MESSAGES creating build/lib/cms/locale/zh/LC_MESSAGES copying cms/locale/zh/LC_MESSAGES/django.mo -> build/lib/cms/locale/zh/LC_MESSAGES copying cms/locale/zh/LC_MESSAGES/django.po -> build/lib/cms/locale/zh/LC_MESSAGES copying cms/locale/zh/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/zh/LC_MESSAGES copying cms/locale/zh/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/zh/LC_MESSAGES creating build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES copying cms/locale/zh_CN.GB2312/LC_MESSAGES/django.mo -> build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES copying cms/locale/zh_CN.GB2312/LC_MESSAGES/django.po -> build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES copying cms/locale/zh_CN.GB2312/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES copying cms/locale/zh_CN.GB2312/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES creating build/lib/cms/locale/zh_CN/LC_MESSAGES copying cms/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/cms/locale/zh_CN/LC_MESSAGES copying cms/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/cms/locale/zh_CN/LC_MESSAGES copying cms/locale/zh_CN/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/zh_CN/LC_MESSAGES copying cms/locale/zh_CN/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/zh_CN/LC_MESSAGES creating build/lib/cms/locale/zh_TW/LC_MESSAGES copying cms/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/cms/locale/zh_TW/LC_MESSAGES copying cms/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/cms/locale/zh_TW/LC_MESSAGES copying cms/locale/zh_TW/LC_MESSAGES/djangojs.mo -> build/lib/cms/locale/zh_TW/LC_MESSAGES copying cms/locale/zh_TW/LC_MESSAGES/djangojs.po -> build/lib/cms/locale/zh_TW/LC_MESSAGES creating build/lib/cms/static/cms/css/5.0.6 copying cms/static/cms/css/5.0.6/cms.admin.css -> build/lib/cms/static/cms/css/5.0.6 copying cms/static/cms/css/5.0.6/cms.base.css -> build/lib/cms/static/cms/css/5.0.6 copying cms/static/cms/css/5.0.6/cms.headless.css -> build/lib/cms/static/cms/css/5.0.6 copying cms/static/cms/css/5.0.6/cms.pagetree.css -> build/lib/cms/static/cms/css/5.0.6 copying cms/static/cms/css/5.0.6/cms.welcome.css -> build/lib/cms/static/cms/css/5.0.6 copying cms/static/cms/css/5.0.6/cms.wizard.css -> build/lib/cms/static/cms/css/5.0.6 creating build/lib/cms/static/cms/fonts/5.0.6 copying cms/static/cms/fonts/5.0.6/django-cms-iconfont.eot -> build/lib/cms/static/cms/fonts/5.0.6 copying cms/static/cms/fonts/5.0.6/django-cms-iconfont.svg -> build/lib/cms/static/cms/fonts/5.0.6 copying cms/static/cms/fonts/5.0.6/django-cms-iconfont.ttf -> build/lib/cms/static/cms/fonts/5.0.6 copying cms/static/cms/fonts/5.0.6/django-cms-iconfont.woff -> build/lib/cms/static/cms/fonts/5.0.6 copying cms/static/cms/fonts/5.0.6/django-cms-iconfont.woff2 -> build/lib/cms/static/cms/fonts/5.0.6 creating build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/_template.svgz -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/advanced-settings.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/alias.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/apphook.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/archive.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/arrow-right.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/arrow-wide.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/arrow.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/bin.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/broadcast-off.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/broadcast-on.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/check-circle.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/check-o.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/check-square.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/check.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/close.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/cogs.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/comment.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/compare.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/copy.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/cut.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/edit-new.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/edit.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/eye.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/forbidden.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/handler.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/highlight.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/home.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/info.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/layers.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/list-ol.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/loader.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/lock.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/logo.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/manage-versions.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/menu.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/minimize.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/minus-circle.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/minus-square-o.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/minus-square.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/minus.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/moderate.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/paste.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/pencil.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/pin.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/plugins.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/plus-circle.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/plus-square-o.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/plus.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/publish.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/puzzle.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/redo.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/rename.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/scissors.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/search.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/settings.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/sitemap.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/squares.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/theme-auto.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/theme-dark.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/theme-light.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/undo.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/unlock.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/unpublish.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/view.svg -> build/lib/cms/static/cms/fonts/src copying cms/static/cms/fonts/src/window.svg -> build/lib/cms/static/cms/fonts/src creating build/lib/cms/static/cms/img copying cms/static/cms/img/favicon.png -> build/lib/cms/static/cms/img copying cms/static/cms/img/loader.gif -> build/lib/cms/static/cms/img copying cms/static/cms/img/loader@2x.gif -> build/lib/cms/static/cms/img creating build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/flv.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/gif.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/html.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/java.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/jpg.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/mp3.png -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/ods.png -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/odt.png -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/pdf.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/php.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/png.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/swf.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/tgz.png -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/ttf.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/txt.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/txt.png -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/wav.gif -> build/lib/cms/static/cms/img/icons/filetypes copying cms/static/cms/img/icons/filetypes/zip.png -> build/lib/cms/static/cms/img/icons/filetypes creating build/lib/cms/static/cms/img/icons/plugins copying cms/static/cms/img/icons/plugins/file.png -> build/lib/cms/static/cms/img/icons/plugins copying cms/static/cms/img/icons/plugins/get_flash_player.gif -> build/lib/cms/static/cms/img/icons/plugins copying cms/static/cms/img/icons/plugins/image.png -> build/lib/cms/static/cms/img/icons/plugins copying cms/static/cms/img/icons/plugins/link.png -> build/lib/cms/static/cms/img/icons/plugins copying cms/static/cms/img/icons/plugins/snippet.png -> build/lib/cms/static/cms/img/icons/plugins creating build/lib/cms/static/cms/img/pagetree copying cms/static/cms/img/pagetree/tree-li-drag.gif -> build/lib/cms/static/cms/img/pagetree creating build/lib/cms/static/cms/img/toolbar copying cms/static/cms/img/toolbar/render_model_add.png -> build/lib/cms/static/cms/img/toolbar copying cms/static/cms/img/toolbar/render_model_icon.png -> build/lib/cms/static/cms/img/toolbar copying cms/static/cms/img/toolbar/render_model_placeholder.png -> build/lib/cms/static/cms/img/toolbar creating build/lib/cms/static/cms/js copying cms/static/cms/js/admin.base.js -> build/lib/cms/static/cms/js copying cms/static/cms/js/admin.changeform.js -> build/lib/cms/static/cms/js copying cms/static/cms/js/admin.pagetree.js -> build/lib/cms/static/cms/js copying cms/static/cms/js/toolbar.js -> build/lib/cms/static/cms/js creating build/lib/cms/static/cms/js/admin copying cms/static/cms/js/admin/actions.js -> build/lib/cms/static/cms/js/admin copying cms/static/cms/js/admin/language-selector.js -> build/lib/cms/static/cms/js/admin creating build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.admin.base.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.admin.changeform.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.admin.pagetree.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.admin.widget.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.forms.apphookselect.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.forms.pageselectwidget.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.forms.pagesmartlinkwidget.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.forms.slugwidget.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 copying cms/static/cms/js/dist/5.0.6/bundle.toolbar.min.js -> build/lib/cms/static/cms/js/dist/5.0.6 creating build/lib/cms/static/cms/js/libs copying cms/static/cms/js/libs/class.min.js -> build/lib/cms/static/cms/js/libs copying cms/static/cms/js/libs/jquery.min.js -> build/lib/cms/static/cms/js/libs copying cms/static/cms/js/libs/pep.js -> build/lib/cms/static/cms/js/libs creating build/lib/cms/static/cms/js/libs/jstree copying cms/static/cms/js/libs/jstree/jstree.grid.min.js -> build/lib/cms/static/cms/js/libs/jstree copying cms/static/cms/js/libs/jstree/jstree.min.js -> build/lib/cms/static/cms/js/libs/jstree creating build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.base.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.changeform.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.changetracker.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.clipboard.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.messages.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.modal.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.navigation.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.pagetree.dropdown.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.pagetree.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.pagetree.stickyheader.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.plugins.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.sideframe.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.structureboard.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.toolbar.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.tooltip.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/cms.wizards.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/dropdown.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/get-dist-path.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/jquery.noconflict.post.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/jquery.noconflict.pre.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/jquery.transition.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/jquery.trap.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/jquery.ui.custom.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/jquery.ui.nestedsortable.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/jquery.ui.touchpunch.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/keyboard.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/loader.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/nextuntil.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/preload-images.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/scrollbar.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/slug.js -> build/lib/cms/static/cms/js/modules copying cms/static/cms/js/modules/tmpl.js -> build/lib/cms/static/cms/js/modules creating build/lib/cms/static/cms/js/modules/shortcuts copying cms/static/cms/js/modules/shortcuts/create-modal.js -> build/lib/cms/static/cms/js/modules/shortcuts copying cms/static/cms/js/modules/shortcuts/help.html -> build/lib/cms/static/cms/js/modules/shortcuts copying cms/static/cms/js/modules/shortcuts/help.js -> build/lib/cms/static/cms/js/modules/shortcuts copying cms/static/cms/js/modules/shortcuts/index.js -> build/lib/cms/static/cms/js/modules/shortcuts copying cms/static/cms/js/modules/shortcuts/placeholders.js -> build/lib/cms/static/cms/js/modules/shortcuts copying cms/static/cms/js/modules/shortcuts/toolbar.js -> build/lib/cms/static/cms/js/modules/shortcuts creating build/lib/cms/static/cms/js/polyfills copying cms/static/cms/js/polyfills/array.prototype.findindex.js -> build/lib/cms/static/cms/js/polyfills copying cms/static/cms/js/polyfills/domparser.js -> build/lib/cms/static/cms/js/polyfills copying cms/static/cms/js/polyfills/function.prototype.bind.js -> build/lib/cms/static/cms/js/polyfills creating build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/LICENSE -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/README.md -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2-bootstrap.css -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2-spinner.gif -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2.css -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2.png -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ar.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_az.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_bg.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ca.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_cs.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_da.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_de.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_el.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_en.js.template -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_es.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_et.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_eu.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_fa.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_fi.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_fr.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_gl.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_he.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_hr.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_hu.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_id.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_is.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_it.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ja.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ka.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ko.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_lt.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_lv.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_mk.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ms.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_nl.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_no.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_pl.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_pt-BR.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_pt-PT.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ro.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_rs.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ru.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_sk.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_sv.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_th.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_tr.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_ug-CN.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_uk.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_vi.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_zh-CN.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2_locale_zh-TW.js -> build/lib/cms/static/cms/js/select2 copying cms/static/cms/js/select2/select2x2.png -> build/lib/cms/static/cms/js/select2 creating build/lib/cms/static/cms/js/widgets copying cms/static/cms/js/widgets/forms.apphookselect.js -> build/lib/cms/static/cms/js/widgets copying cms/static/cms/js/widgets/forms.pageselectwidget.js -> build/lib/cms/static/cms/js/widgets copying cms/static/cms/js/widgets/forms.pagesmartlinkwidget.js -> build/lib/cms/static/cms/js/widgets copying cms/static/cms/js/widgets/forms.slugwidget.js -> build/lib/cms/static/cms/js/widgets copying cms/static/cms/js/widgets/wizard.pagetypeselect.js -> build/lib/cms/static/cms/js/widgets creating build/lib/cms/static/cms/sass copying cms/static/cms/sass/cms.admin.scss -> build/lib/cms/static/cms/sass copying cms/static/cms/sass/cms.base.scss -> build/lib/cms/static/cms/sass copying cms/static/cms/sass/cms.headless.scss -> build/lib/cms/static/cms/sass copying cms/static/cms/sass/cms.pagetree.scss -> build/lib/cms/static/cms/sass copying cms/static/cms/sass/cms.welcome.scss -> build/lib/cms/static/cms/sass copying cms/static/cms/sass/cms.wizard.scss -> build/lib/cms/static/cms/sass creating build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_animation.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_button.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_clipboard.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_content.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_dark-mode-toggle.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_dialog.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_dropdown.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_general.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_hovertooltip.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_iconography.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_loader.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_modal.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_pluginpicker.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_reset.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_shortcuts.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_sideframe.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_structureboard.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_subnav.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_toolbar.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_tooltip.scss -> build/lib/cms/static/cms/sass/components copying cms/static/cms/sass/components/_welcome.scss -> build/lib/cms/static/cms/sass/components creating build/lib/cms/static/cms/sass/components/pagetree copying cms/static/cms/sass/components/pagetree/_all.scss -> build/lib/cms/static/cms/sass/components/pagetree copying cms/static/cms/sass/components/pagetree/_dropdown.scss -> build/lib/cms/static/cms/sass/components/pagetree copying cms/static/cms/sass/components/pagetree/_legend.scss -> build/lib/cms/static/cms/sass/components/pagetree copying cms/static/cms/sass/components/pagetree/_node-state.scss -> build/lib/cms/static/cms/sass/components/pagetree copying cms/static/cms/sass/components/pagetree/_tree.scss -> build/lib/cms/static/cms/sass/components/pagetree creating build/lib/cms/static/cms/sass/libs copying cms/static/cms/sass/libs/_iconfont.scss -> build/lib/cms/static/cms/sass/libs copying cms/static/cms/sass/libs/_rtl_patch.scss -> build/lib/cms/static/cms/sass/libs creating build/lib/cms/static/cms/sass/mixins copying cms/static/cms/sass/mixins/_all.scss -> build/lib/cms/static/cms/sass/mixins copying cms/static/cms/sass/mixins/_buttons.scss -> build/lib/cms/static/cms/sass/mixins copying cms/static/cms/sass/mixins/_custom.scss -> build/lib/cms/static/cms/sass/mixins copying cms/static/cms/sass/mixins/_retina.scss -> build/lib/cms/static/cms/sass/mixins copying cms/static/cms/sass/mixins/_zindex.scss -> build/lib/cms/static/cms/sass/mixins creating build/lib/cms/static/cms/sass/settings copying cms/static/cms/sass/settings/_all.scss -> build/lib/cms/static/cms/sass/settings copying cms/static/cms/sass/settings/_cms.scss -> build/lib/cms/static/cms/sass/settings copying cms/static/cms/sass/settings/_pagetree.scss -> build/lib/cms/static/cms/sass/settings creating build/lib/cms/templates/admin/cms/extensions copying cms/templates/admin/cms/extensions/change_form.html -> build/lib/cms/templates/admin/cms/extensions creating build/lib/cms/templates/admin/cms/grouper copying cms/templates/admin/cms/grouper/change_form.html -> build/lib/cms/templates/admin/cms/grouper copying cms/templates/admin/cms/grouper/change_list.html -> build/lib/cms/templates/admin/cms/grouper copying cms/templates/admin/cms/grouper/content_inline.html -> build/lib/cms/templates/admin/cms/grouper creating build/lib/cms/templates/admin/cms/icons copying cms/templates/admin/cms/icons/base.html -> build/lib/cms/templates/admin/cms/icons creating build/lib/cms/templates/admin/cms/mail copying cms/templates/admin/cms/mail/base.html -> build/lib/cms/templates/admin/cms/mail copying cms/templates/admin/cms/mail/base.txt -> build/lib/cms/templates/admin/cms/mail copying cms/templates/admin/cms/mail/page_user_change.html -> build/lib/cms/templates/admin/cms/mail copying cms/templates/admin/cms/mail/page_user_change.txt -> build/lib/cms/templates/admin/cms/mail creating build/lib/cms/templates/admin/cms/page copying cms/templates/admin/cms/page/change_form.html -> build/lib/cms/templates/admin/cms/page copying cms/templates/admin/cms/page/close_frame.html -> build/lib/cms/templates/admin/cms/page copying cms/templates/admin/cms/page/delete_confirmation.html -> build/lib/cms/templates/admin/cms/page copying cms/templates/admin/cms/page/delete_summary.html -> build/lib/cms/templates/admin/cms/page copying cms/templates/admin/cms/page/permissions.html -> build/lib/cms/templates/admin/cms/page copying cms/templates/admin/cms/page/submit_row.html -> build/lib/cms/templates/admin/cms/page creating build/lib/cms/templates/admin/cms/page/includes copying cms/templates/admin/cms/page/includes/fieldset.html -> build/lib/cms/templates/admin/cms/page/includes creating build/lib/cms/templates/admin/cms/page/plugin copying cms/templates/admin/cms/page/plugin/change_form.html -> build/lib/cms/templates/admin/cms/page/plugin copying cms/templates/admin/cms/page/plugin/confirm_form.html -> build/lib/cms/templates/admin/cms/page/plugin copying cms/templates/admin/cms/page/plugin/delete_confirmation.html -> build/lib/cms/templates/admin/cms/page/plugin copying cms/templates/admin/cms/page/plugin/error_form.html -> build/lib/cms/templates/admin/cms/page/plugin copying cms/templates/admin/cms/page/plugin/submit_line.html -> build/lib/cms/templates/admin/cms/page/plugin creating build/lib/cms/templates/admin/cms/page/tree copying cms/templates/admin/cms/page/tree/actions_dropdown.html -> build/lib/cms/templates/admin/cms/page/tree copying cms/templates/admin/cms/page/tree/base.html -> build/lib/cms/templates/admin/cms/page/tree copying cms/templates/admin/cms/page/tree/copy_premissions.html -> build/lib/cms/templates/admin/cms/page/tree copying cms/templates/admin/cms/page/tree/filter.html -> build/lib/cms/templates/admin/cms/page/tree copying cms/templates/admin/cms/page/tree/indicator_legend.html -> build/lib/cms/templates/admin/cms/page/tree copying cms/templates/admin/cms/page/tree/indicator_menu.html -> build/lib/cms/templates/admin/cms/page/tree copying cms/templates/admin/cms/page/tree/legend.html -> build/lib/cms/templates/admin/cms/page/tree copying cms/templates/admin/cms/page/tree/menu.html -> build/lib/cms/templates/admin/cms/page/tree creating build/lib/cms/templates/admin/cms/usersettings copying cms/templates/admin/cms/usersettings/change_form.html -> build/lib/cms/templates/admin/cms/usersettings creating build/lib/cms/templates/cms copying cms/templates/cms/content.html -> build/lib/cms/templates/cms copying cms/templates/cms/dummy.html -> build/lib/cms/templates/cms copying cms/templates/cms/noapphook.html -> build/lib/cms/templates/cms copying cms/templates/cms/welcome.html -> build/lib/cms/templates/cms creating build/lib/cms/templates/cms/headless copying cms/templates/cms/headless/placeholder.html -> build/lib/cms/templates/cms/headless creating build/lib/cms/templates/cms/plugins copying cms/templates/cms/plugins/alias.html -> build/lib/cms/templates/cms/plugins creating build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/clipboard.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/content.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/dragbar.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/dragitem.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/dragitem_extra_menu.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/dragitem_menu.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/plugin.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/render_plugin_block.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/structure.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/toolbar.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/toolbar_javascript.html -> build/lib/cms/templates/cms/toolbar copying cms/templates/cms/toolbar/toolbar_with_structure.html -> build/lib/cms/templates/cms/toolbar creating build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/break.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/button.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/button_list.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/button_modal.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/button_sideframe.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/dark_mode_toggle.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/dropdown.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/dropdown_button.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/item_ajax.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/item_link.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/item_modal.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/item_sideframe.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/live_draft.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/login.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/logo.html -> build/lib/cms/templates/cms/toolbar/items copying cms/templates/cms/toolbar/items/menu.html -> build/lib/cms/templates/cms/toolbar/items creating build/lib/cms/templates/cms/widgets copying cms/templates/cms/widgets/applicationconfigselect.html -> build/lib/cms/templates/cms/widgets copying cms/templates/cms/widgets/pageselectwidget.html -> build/lib/cms/templates/cms/widgets copying cms/templates/cms/widgets/pagesmartlinkwidget.html -> build/lib/cms/templates/cms/widgets creating build/lib/cms/templates/cms/wizards copying cms/templates/cms/wizards/base.html -> build/lib/cms/templates/cms/wizards copying cms/templates/cms/wizards/create.html -> build/lib/cms/templates/cms/wizards copying cms/templates/cms/wizards/start.html -> build/lib/cms/templates/cms/wizards copying cms/templates/cms/wizards/wizardoptionwidget.html -> build/lib/cms/templates/cms/wizards creating build/lib/cms/templates/cms/wizards/includes copying cms/templates/cms/wizards/includes/form_fields.html -> build/lib/cms/templates/cms/wizards/includes creating build/lib/menus/templates/menu copying menus/templates/menu/breadcrumb.html -> build/lib/menus/templates/menu copying menus/templates/menu/dummy.html -> build/lib/menus/templates/menu copying menus/templates/menu/empty.html -> build/lib/menus/templates/menu copying menus/templates/menu/language_chooser.html -> build/lib/menus/templates/menu copying menus/templates/menu/menu.html -> build/lib/menus/templates/menu copying menus/templates/menu/sub_menu.html -> build/lib/menus/templates/menu =========================================================================== =================================================== ===== env: USE_PACKAGE_DEPENDS_ONLY=1 USER=root UID=0 GID=0 ===> py311-django-cms-5.0.6 depends on package: py311-django42>=2.2 - not found ===> Installing existing package /packages/All/py311-django42-4.2.30.pkg [curamd64-setuptools-job-01] Installing py311-django42-4.2.30... [curamd64-setuptools-job-01] `-- Installing py311-asgiref-3.11.1... [curamd64-setuptools-job-01] `-- Extracting py311-asgiref-3.11.1: .......... done [curamd64-setuptools-job-01] `-- Installing py311-sqlite3-3.11.15_10... [curamd64-setuptools-job-01] | `-- Installing sqlite3-3.50.4_2,1... [curamd64-setuptools-job-01] | | `-- Installing libedit-3.1.20251016_1,1... [curamd64-setuptools-job-01] | | `-- Extracting libedit-3.1.20251016_1,1: .......... done [curamd64-setuptools-job-01] | `-- Extracting sqlite3-3.50.4_2,1: .......... done [curamd64-setuptools-job-01] `-- Extracting py311-sqlite3-3.11.15_10: ......... done [curamd64-setuptools-job-01] `-- Installing py311-sqlparse-0.5.5... [curamd64-setuptools-job-01] `-- Extracting py311-sqlparse-0.5.5: .......... done [curamd64-setuptools-job-01] Extracting py311-django42-4.2.30: .......... done ===== Message from py311-django42-4.2.30: -- ===> NOTICE: This port is deprecated; you may wish to reconsider installing it: Django 4.2 is now in Extended Support, receives security fixes only and will reach End-Of-Life in April 2026. Upgrade to a later Django version. See https://www.djangoproject.com/download/. It is scheduled to be removed on or after 2026-05-31. ===> py311-django-cms-5.0.6 depends on package: py311-django42>=2.2 - found ===> Returning to build of py311-django-cms-5.0.6 ===> py311-django-cms-5.0.6 depends on package: py311-djangocms-admin-style>=1.2 - not found ===> Installing existing package /packages/All/py311-djangocms-admin-style-3.3.1_2.pkg [curamd64-setuptools-job-01] Installing py311-djangocms-admin-style-3.3.1_2... [curamd64-setuptools-job-01] Extracting py311-djangocms-admin-style-3.3.1_2: .......... done ===> py311-django-cms-5.0.6 depends on package: py311-djangocms-admin-style>=1.2 - found ===> Returning to build of py311-django-cms-5.0.6 ===> py311-django-cms-5.0.6 depends on package: py311-django-classy-tags>=0.7.2 - not found ===> Installing existing package /packages/All/py311-django-classy-tags-4.1.0_2.pkg [curamd64-setuptools-job-01] Installing py311-django-classy-tags-4.1.0_2... [curamd64-setuptools-job-01] Extracting py311-django-classy-tags-4.1.0_2: .......... done ===> py311-django-cms-5.0.6 depends on package: py311-django-classy-tags>=0.7.2 - found ===> Returning to build of py311-django-cms-5.0.6 ===> py311-django-cms-5.0.6 depends on package: py311-django-formtools>=2.1 - not found ===> Installing existing package /packages/All/py311-django-formtools-2.3_1.pkg [curamd64-setuptools-job-01] Installing py311-django-formtools-2.3_1... [curamd64-setuptools-job-01] Extracting py311-django-formtools-2.3_1: .......... done ===> py311-django-cms-5.0.6 depends on package: py311-django-formtools>=2.1 - found ===> Returning to build of py311-django-cms-5.0.6 ===> py311-django-cms-5.0.6 depends on package: py311-django-sekizai>=0.7 - not found ===> Installing existing package /packages/All/py311-django-sekizai-4.1.0_2.pkg [curamd64-setuptools-job-01] Installing py311-django-sekizai-4.1.0_2... [curamd64-setuptools-job-01] Extracting py311-django-sekizai-4.1.0_2: .......... done ===> py311-django-cms-5.0.6 depends on package: py311-django-sekizai>=0.7 - found ===> Returning to build of py311-django-cms-5.0.6 ===> py311-django-cms-5.0.6 depends on package: py311-django-treebeard>=4.3 - not found ===> Installing existing package /packages/All/py311-django-treebeard-4.8.0.pkg [curamd64-setuptools-job-01] Installing py311-django-treebeard-4.8.0... [curamd64-setuptools-job-01] Extracting py311-django-treebeard-4.8.0: .......... done ===> py311-django-cms-5.0.6 depends on package: py311-django-treebeard>=4.3 - found ===> Returning to build of py311-django-cms-5.0.6 ===> py311-django-cms-5.0.6 depends on package: py311-packaging>0 - found ===> py311-django-cms-5.0.6 depends on package: py311-sqlite3>0 - found ===> py311-django-cms-5.0.6 depends on file: /usr/local/bin/python3.11 - found =========================================================================== =================================================== ===== env: NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Staging for py311-django-cms-5.0.6 ===> Generating temporary packing list /usr/local/lib/python3.11/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running install /usr/local/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running build running build_py running egg_info writing django_cms.egg-info/PKG-INFO writing dependency_links to django_cms.egg-info/dependency_links.txt writing entry points to django_cms.egg-info/entry_points.txt writing requirements to django_cms.egg-info/requires.txt writing top-level names to django_cms.egg-info/top_level.txt reading manifest file 'django_cms.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'CHANGELOG.txt' warning: no files found matching '*' under directory 'cms/plugins' warning: no files found matching '*' under directory 'stacks/templates' warning: no previously-included files matching '*.pyc' found under directory '*' warning: no previously-included files matching '*.scssc' found under directory '*' adding license file 'LICENSE' adding license file 'AUTHORS' writing manifest file 'django_cms.egg-info/SOURCES.txt' /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ar_SA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ar_SA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ar_SA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ar_SA.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ar_SA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.cmn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.cmn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.cmn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.cmn.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.cmn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.cs_CZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.cs_CZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.cs_CZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.cs_CZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.cs_CZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.en_HK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.en_HK.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.en_HK.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.en_HK.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.en_HK.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.en_US.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.en_US.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.en_US.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.en_US.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.en_US.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.es_BO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.es_BO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.es_BO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.es_BO.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.es_BO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.es_DO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.es_DO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.es_DO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.es_DO.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.es_DO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fi_FI.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fi_FI.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fi_FI.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fi_FI.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fi_FI.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fr_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fr_CA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fr_CA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fr_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fr_CA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.fr_FR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.fr_FR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.fr_FR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.fr_FR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.fr_FR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.gu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.gu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.gu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.gu.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.gu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.is_IS.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.is_IS.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.is_IS.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ko_KR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ko_KR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ko_KR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ko_KR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ko_KR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ku_IQ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ku_IQ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ku_IQ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ku_IQ.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ku_IQ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ky.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ky.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.lt_LT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.lt_LT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.lt_LT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.lt_LT.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.lt_LT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.mn_MN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.mn_MN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.mn_MN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.mn_MN.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.mn_MN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.mt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.mt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.mt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.mt.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.mt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.no.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.no.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.no.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.no.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.no.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ro_RO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ro_RO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ro_RO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ro_RO.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ro_RO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ru_RU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ru_RU.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ru_RU.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ru_RU.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ru_RU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sk_SK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sk_SK.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sk_SK.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sk_SK.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sk_SK.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sl_SI.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sl_SI.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sl_SI.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sl_SI.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sl_SI.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sq_AL.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sq_AL.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sq_AL.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sq_AL.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sq_AL.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale' to be distributed and are already explicitly excluding 'cms.locale' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.th_TH.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.th_TH.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.th_TH.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.th_TH.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.th_TH.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.tlh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.tlh.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.tlh.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.tlh.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.tlh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ug.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ug.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.vi_VN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.vi_VN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.vi_VN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.zh.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.zh.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.zh.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.zh_CN.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.zh_CN.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.zh_CN.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.locale.zh_TW.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.locale.zh_TW.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'cms.locale.zh_TW.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.css' to be distributed and are already explicitly excluding 'cms.static.cms.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.fonts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.fonts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.fonts' to be distributed and are already explicitly excluding 'cms.static.cms.fonts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.fonts.src' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.fonts.src' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.fonts.src' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.fonts.src' to be distributed and are already explicitly excluding 'cms.static.cms.fonts.src' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img' to be distributed and are already explicitly excluding 'cms.static.cms.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img.icons.filetypes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img.icons.filetypes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img.icons.filetypes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img.icons.filetypes' to be distributed and are already explicitly excluding 'cms.static.cms.img.icons.filetypes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img.icons.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img.icons.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img.icons.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img.icons.plugins' to be distributed and are already explicitly excluding 'cms.static.cms.img.icons.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img.pagetree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img.pagetree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img.pagetree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img.pagetree' to be distributed and are already explicitly excluding 'cms.static.cms.img.pagetree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.img.toolbar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.img.toolbar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.img.toolbar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.img.toolbar' to be distributed and are already explicitly excluding 'cms.static.cms.img.toolbar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js' to be distributed and are already explicitly excluding 'cms.static.cms.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.admin' to be distributed and are already explicitly excluding 'cms.static.cms.js.admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.dist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.dist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.dist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.dist' to be distributed and are already explicitly excluding 'cms.static.cms.js.dist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.libs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.libs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.libs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.libs' to be distributed and are already explicitly excluding 'cms.static.cms.js.libs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.libs.jstree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.libs.jstree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.libs.jstree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.libs.jstree' to be distributed and are already explicitly excluding 'cms.static.cms.js.libs.jstree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.modules' to be distributed and are already explicitly excluding 'cms.static.cms.js.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.modules.shortcuts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.modules.shortcuts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.modules.shortcuts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.modules.shortcuts' to be distributed and are already explicitly excluding 'cms.static.cms.js.modules.shortcuts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.polyfills' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.polyfills' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.polyfills' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.polyfills' to be distributed and are already explicitly excluding 'cms.static.cms.js.polyfills' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.select2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.select2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.select2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.select2' to be distributed and are already explicitly excluding 'cms.static.cms.js.select2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.js.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.js.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.js.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.js.widgets' to be distributed and are already explicitly excluding 'cms.static.cms.js.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass' to be distributed and are already explicitly excluding 'cms.static.cms.sass' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.components' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.components' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.components' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.components' to be distributed and are already explicitly excluding 'cms.static.cms.sass.components' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.components.pagetree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.components.pagetree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.components.pagetree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.components.pagetree' to be distributed and are already explicitly excluding 'cms.static.cms.sass.components.pagetree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.libs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.libs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.libs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.libs' to be distributed and are already explicitly excluding 'cms.static.cms.sass.libs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.mixins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.mixins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.mixins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.mixins' to be distributed and are already explicitly excluding 'cms.static.cms.sass.mixins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.static.cms.sass.settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.static.cms.sass.settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.static.cms.sass.settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.static.cms.sass.settings' to be distributed and are already explicitly excluding 'cms.static.cms.sass.settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.extensions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.extensions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.extensions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.extensions' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.extensions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.grouper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.grouper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.grouper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.grouper' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.grouper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.icons' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.icons' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.icons' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.icons' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.icons' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.mail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.mail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.mail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.mail' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.mail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.page' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.page' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.page' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.page' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.page' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.page.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.page.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.page.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.page.includes' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.page.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.page.plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.page.plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.page.plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.page.plugin' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.page.plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.page.tree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.page.tree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.page.tree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.page.tree' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.page.tree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.admin.cms.usersettings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.admin.cms.usersettings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.admin.cms.usersettings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.admin.cms.usersettings' to be distributed and are already explicitly excluding 'cms.templates.admin.cms.usersettings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms' to be distributed and are already explicitly excluding 'cms.templates.cms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.headless' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.headless' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.headless' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.headless' to be distributed and are already explicitly excluding 'cms.templates.cms.headless' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.plugins' to be distributed and are already explicitly excluding 'cms.templates.cms.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.toolbar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.toolbar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.toolbar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.toolbar' to be distributed and are already explicitly excluding 'cms.templates.cms.toolbar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.toolbar.items' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.toolbar.items' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.toolbar.items' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.toolbar.items' to be distributed and are already explicitly excluding 'cms.templates.cms.toolbar.items' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.widgets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.widgets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.widgets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.widgets' to be distributed and are already explicitly excluding 'cms.templates.cms.widgets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.wizards' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.wizards' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.wizards' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.wizards' to be distributed and are already explicitly excluding 'cms.templates.cms.wizards' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'cms.templates.cms.wizards.includes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cms.templates.cms.wizards.includes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'cms.templates.cms.wizards.includes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'cms.templates.cms.wizards.includes' to be distributed and are already explicitly excluding 'cms.templates.cms.wizards.includes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'menus.templates.menu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'menus.templates.menu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'menus.templates.menu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'menus.templates.menu' to be distributed and are already explicitly excluding 'menus.templates.menu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) running install_lib creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/__main__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/api.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/app_base.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/app_registration.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/apphook_pool.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/appresolver.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/cms_menus.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/cms_toolbars.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/cms_wizards.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/constants.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/context_processors.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/exceptions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/menu_bases.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/page_rendering.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/plugin_base.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/plugin_pool.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/plugin_processors.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/plugin_rendering.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/templates.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/toolbar_base.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/toolbar_pool.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms copying build/lib/cms/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/forms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/pageadmin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/permissionadmin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/placeholderadmin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/settingsadmin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/static_placeholder.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/useradmin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin copying build/lib/cms/admin/utils.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache copying build/lib/cms/cache/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache copying build/lib/cms/cache/choices.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache copying build/lib/cms/cache/page.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache copying build/lib/cms/cache/permissions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache copying build/lib/cms/cache/placeholder.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions copying build/lib/cms/extensions/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions copying build/lib/cms/extensions/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions copying build/lib/cms/extensions/extension_pool.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions copying build/lib/cms/extensions/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions copying build/lib/cms/extensions/toolbar.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms copying build/lib/cms/forms/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms copying build/lib/cms/forms/fields.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms copying build/lib/cms/forms/login.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms copying build/lib/cms/forms/utils.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms copying build/lib/cms/forms/validators.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms copying build/lib/cms/forms/widgets.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms copying build/lib/cms/forms/wizards.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management copying build/lib/cms/management/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management copying build/lib/cms/management/djangocms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands copying build/lib/cms/management/commands/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands copying build/lib/cms/management/commands/cms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands copying build/lib/cms/management/commands/startcmsproject.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands copying build/lib/cms/management/commands/subcommands/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands copying build/lib/cms/management/commands/subcommands/base.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands copying build/lib/cms/management/commands/subcommands/check.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands copying build/lib/cms/management/commands/subcommands/copy.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands copying build/lib/cms/management/commands/subcommands/delete_orphaned_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands copying build/lib/cms/management/commands/subcommands/list.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands copying build/lib/cms/management/commands/subcommands/tree.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands copying build/lib/cms/management/commands/subcommands/uninstall.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/aliaspluginmodel.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/apphooks_reload.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/contentmodels.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/fields.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/managers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/pagemodel.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/permissionmodels.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/placeholdermodel.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/placeholderpluginmodel.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/pluginmodel.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/query.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/settingmodels.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models copying build/lib/cms/models/static_placeholder.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware copying build/lib/cms/middleware/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware copying build/lib/cms/middleware/language.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware copying build/lib/cms/middleware/page.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware copying build/lib/cms/middleware/toolbar.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware copying build/lib/cms/middleware/user.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware copying build/lib/cms/middleware/utils.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0001_initial.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0002_auto_20140816_1918.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0003_auto_20140926_2347.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0004_auto_20140924_1038.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0005_auto_20140924_1039.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0006_auto_20140924_1110.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0007_auto_20141028_1559.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0008_auto_20150121_0059.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0008_auto_20150208_2149.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0009_merge.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0010_migrate_use_structure.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0011_auto_20150419_1006.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0012_auto_20150607_2207.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0013_urlconfrevision.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0014_auto_20160404_1908.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0015_auto_20160421_0000.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0016_auto_20160608_1535.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0017_pagetype.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0018_create_pagenode.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0019_set_pagenode.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0020_old_tree_cleanup.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0021_auto_20180507_1432.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0022_auto_20180620_1551.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0023_placeholder_source_field.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0024_set_plugin_absolute_position.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0025_remove_plugin_tree_fields.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0026_title_placeholders.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0031_remove_fields.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0027_title_placeholders_data_migration.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0028_remove_page_placeholders.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0029_create_title_fields_and_url_model.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0030_auto_20180810_0629.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0032_remove_title_to_pagecontent.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0033_placeholder_source_data_migration.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0034_remove_pagecontent_placeholders.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0035_auto_20230822_2208.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0035_auto_20230822_2208_squashed_0036_auto_20240311_1028.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0036_auto_20240311_1028.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0037_merge_page_treenode.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0038_alter_page_site.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0039_remove_page_languages_alter_pageurl_unique_together.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0040_alter_pageuser_created_by_and_more.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/0041_alter_pageurl_unique_together_pageurl_site_and_more.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations copying build/lib/cms/migrations/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/operations copying build/lib/cms/operations/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/operations copying build/lib/cms/operations/helpers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/operations creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals copying build/lib/cms/signals/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals copying build/lib/cms/signals/apphook.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals copying build/lib/cms/signals/log_entries.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals copying build/lib/cms/signals/pagecontent.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals copying build/lib/cms/signals/permissions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/sitemaps copying build/lib/cms/sitemaps/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/sitemaps copying build/lib/cms/sitemaps/cms_sitemap.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/sitemaps creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags copying build/lib/cms/templatetags/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags copying build/lib/cms/templatetags/cms_admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags copying build/lib/cms/templatetags/cms_alias_tags.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags copying build/lib/cms/templatetags/cms_js_tags.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags copying build/lib/cms/templatetags/cms_static.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags copying build/lib/cms/templatetags/cms_tags.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils copying build/lib/cms/test_utils/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils copying build/lib/cms/test_utils/runners.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils copying build/lib/cms/test_utils/testcases.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils copying build/lib/cms/test_utils/tmpdir.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures copying build/lib/cms/test_utils/fixtures/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures copying build/lib/cms/test_utils/fixtures/fakemlng.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures copying build/lib/cms/test_utils/fixtures/menus.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures copying build/lib/cms/test_utils/fixtures/navextenders.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures copying build/lib/cms/test_utils/fixtures/templatetags.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/cms_urls_for_apphook_tests.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/fourth_cms_urls_for_apphook_tests.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/fourth_urls_for_apphook_tests.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/noadmin_urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/nonroot_urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/placeholderapp_urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/second_cms_urls_for_apphook_tests.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/second_urls_for_apphook_tests.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/template_backends.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/third_cms_urls_for_apphook_tests.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/third_urls_for_apphook_tests.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/urls_2.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/urls_3.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/urls_for_apphook_tests.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project copying build/lib/cms/test_utils/project/urls_no18n.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature copying build/lib/cms/test_utils/project/app_using_non_feature/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature copying build/lib/cms/test_utils/project/app_using_non_feature/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature copying build/lib/cms/test_utils/project/app_using_non_feature/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature copying build/lib/cms/test_utils/project/app_using_non_feature/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature copying build/lib/cms/test_utils/project/app_using_non_feature/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature copying build/lib/cms/test_utils/project/app_using_non_feature/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file copying build/lib/cms/test_utils/project/app_with_bad_cms_file/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file copying build/lib/cms/test_utils/project/app_with_bad_cms_file/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file copying build/lib/cms/test_utils/project/app_with_bad_cms_file/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file copying build/lib/cms/test_utils/project/app_with_bad_cms_file/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file copying build/lib/cms/test_utils/project/app_with_bad_cms_file/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file copying build/lib/cms/test_utils/project/app_with_bad_cms_file/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config copying build/lib/cms/test_utils/project/app_with_cms_config/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config copying build/lib/cms/test_utils/project/app_with_cms_config/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config copying build/lib/cms/test_utils/project/app_with_cms_config/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config copying build/lib/cms/test_utils/project/app_with_cms_config/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config copying build/lib/cms/test_utils/project/app_with_cms_config/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config copying build/lib/cms/test_utils/project/app_with_cms_config/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature copying build/lib/cms/test_utils/project/app_with_cms_feature/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature copying build/lib/cms/test_utils/project/app_with_cms_feature/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature copying build/lib/cms/test_utils/project/app_with_cms_feature/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature copying build/lib/cms/test_utils/project/app_with_cms_feature/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature copying build/lib/cms/test_utils/project/app_with_cms_feature/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature copying build/lib/cms/test_utils/project/app_with_cms_feature/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config copying build/lib/cms/test_utils/project/app_with_cms_feature_and_config/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config copying build/lib/cms/test_utils/project/app_with_cms_feature_and_config/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config copying build/lib/cms/test_utils/project/app_with_cms_feature_and_config/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config copying build/lib/cms/test_utils/project/app_with_cms_feature_and_config/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config copying build/lib/cms/test_utils/project/app_with_cms_feature_and_config/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config copying build/lib/cms/test_utils/project/app_with_cms_feature_and_config/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented copying build/lib/cms/test_utils/project/app_with_feature_not_implemented/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented copying build/lib/cms/test_utils/project/app_with_feature_not_implemented/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented copying build/lib/cms/test_utils/project/app_with_feature_not_implemented/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented copying build/lib/cms/test_utils/project/app_with_feature_not_implemented/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented copying build/lib/cms/test_utils/project/app_with_feature_not_implemented/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented copying build/lib/cms/test_utils/project/app_with_feature_not_implemented/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes copying build/lib/cms/test_utils/project/app_with_two_cms_config_classes/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes copying build/lib/cms/test_utils/project/app_with_two_cms_config_classes/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes copying build/lib/cms/test_utils/project/app_with_two_cms_config_classes/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes copying build/lib/cms/test_utils/project/app_with_two_cms_config_classes/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes copying build/lib/cms/test_utils/project/app_with_two_cms_config_classes/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes copying build/lib/cms/test_utils/project/app_with_two_cms_config_classes/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes copying build/lib/cms/test_utils/project/app_with_two_cms_feature_classes/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes copying build/lib/cms/test_utils/project/app_with_two_cms_feature_classes/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes copying build/lib/cms/test_utils/project/app_with_two_cms_feature_classes/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes copying build/lib/cms/test_utils/project/app_with_two_cms_feature_classes/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes copying build/lib/cms/test_utils/project/app_with_two_cms_feature_classes/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes copying build/lib/cms/test_utils/project/app_with_two_cms_feature_classes/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class copying build/lib/cms/test_utils/project/app_without_cms_app_class/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class copying build/lib/cms/test_utils/project/app_without_cms_app_class/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class copying build/lib/cms/test_utils/project/app_without_cms_app_class/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class copying build/lib/cms/test_utils/project/app_without_cms_app_class/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class copying build/lib/cms/test_utils/project/app_without_cms_app_class/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class copying build/lib/cms/test_utils/project/app_without_cms_app_class/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file copying build/lib/cms/test_utils/project/app_without_cms_file/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file copying build/lib/cms/test_utils/project/app_without_cms_file/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file copying build/lib/cms/test_utils/project/app_without_cms_file/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file copying build/lib/cms/test_utils/project/app_without_cms_file/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file copying build/lib/cms/test_utils/project/app_without_cms_file/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/backwards_wizards copying build/lib/cms/test_utils/project/backwards_wizards/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/backwards_wizards copying build/lib/cms/test_utils/project/backwards_wizards/cms_wizards.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/backwards_wizards copying build/lib/cms/test_utils/project/backwards_wizards/wizards.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/backwards_wizards creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/brokenpluginapp copying build/lib/cms/test_utils/project/brokenpluginapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/brokenpluginapp copying build/lib/cms/test_utils/project/brokenpluginapp/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/brokenpluginapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/bunch_of_plugins copying build/lib/cms/test_utils/project/bunch_of_plugins/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/bunch_of_plugins copying build/lib/cms/test_utils/project/bunch_of_plugins/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/bunch_of_plugins creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/custom_templates copying build/lib/cms/test_utils/project/custom_templates/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/custom_templates creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/customuserapp copying build/lib/cms/test_utils/project/customuserapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/customuserapp copying build/lib/cms/test_utils/project/customuserapp/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/customuserapp copying build/lib/cms/test_utils/project/customuserapp/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/customuserapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp copying build/lib/cms/test_utils/project/emailuserapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp copying build/lib/cms/test_utils/project/emailuserapp/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp copying build/lib/cms/test_utils/project/emailuserapp/forms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp copying build/lib/cms/test_utils/project/emailuserapp/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp copying build/lib/cms/test_utils/project/extensionapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp copying build/lib/cms/test_utils/project/extensionapp/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp copying build/lib/cms/test_utils/project/extensionapp/cms_toolbars.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp copying build/lib/cms/test_utils/project/extensionapp/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/fakemlng copying build/lib/cms/test_utils/project/fakemlng/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/fakemlng copying build/lib/cms/test_utils/project/fakemlng/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/fakemlng creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/mti_pluginapp copying build/lib/cms/test_utils/project/mti_pluginapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/mti_pluginapp copying build/lib/cms/test_utils/project/mti_pluginapp/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/mti_pluginapp copying build/lib/cms/test_utils/project/mti_pluginapp/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/mti_pluginapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/nested_plugins_app copying build/lib/cms/test_utils/project/nested_plugins_app/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/nested_plugins_app copying build/lib/cms/test_utils/project/nested_plugins_app/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/nested_plugins_app creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/objectpermissionsapp copying build/lib/cms/test_utils/project/objectpermissionsapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/objectpermissionsapp copying build/lib/cms/test_utils/project/objectpermissionsapp/backends.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/objectpermissionsapp copying build/lib/cms/test_utils/project/objectpermissionsapp/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/objectpermissionsapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app copying build/lib/cms/test_utils/project/placeholder_relation_field_app/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app copying build/lib/cms/test_utils/project/placeholder_relation_field_app/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app copying build/lib/cms/test_utils/project/placeholder_relation_field_app/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app copying build/lib/cms/test_utils/project/placeholder_relation_field_app/urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app copying build/lib/cms/test_utils/project/placeholder_relation_field_app/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/cms_apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/cms_toolbars.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/exceptions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp copying build/lib/cms/test_utils/project/placeholderapp/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp copying build/lib/cms/test_utils/project/pluginapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins copying build/lib/cms/test_utils/project/pluginapp/plugins/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/caching copying build/lib/cms/test_utils/project/pluginapp/plugins/caching/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/caching copying build/lib/cms/test_utils/project/pluginapp/plugins/caching/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/caching copying build/lib/cms/test_utils/project/pluginapp/plugins/caching/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/caching creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/extra_context copying build/lib/cms/test_utils/project/pluginapp/plugins/extra_context/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/extra_context copying build/lib/cms/test_utils/project/pluginapp/plugins/extra_context/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/extra_context copying build/lib/cms/test_utils/project/pluginapp/plugins/extra_context/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/extra_context creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/link copying build/lib/cms/test_utils/project/pluginapp/plugins/link/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/link copying build/lib/cms/test_utils/project/pluginapp/plugins/link/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/link copying build/lib/cms/test_utils/project/pluginapp/plugins/link/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/link creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel copying build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel copying build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel copying build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel copying build/lib/cms/test_utils/project/pluginapp/plugins/manytomany_rel/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/meta copying build/lib/cms/test_utils/project/pluginapp/plugins/meta/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/meta copying build/lib/cms/test_utils/project/pluginapp/plugins/meta/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/meta copying build/lib/cms/test_utils/project/pluginapp/plugins/meta/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/meta creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn copying build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn copying build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn copying build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn/forms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn copying build/lib/cms/test_utils/project/pluginapp/plugins/multicolumn/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap copying build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap copying build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap copying build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap/forms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap copying build/lib/cms/test_utils/project/pluginapp/plugins/multiwrap/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/no_custom_model copying build/lib/cms/test_utils/project/pluginapp/plugins/no_custom_model/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/no_custom_model copying build/lib/cms/test_utils/project/pluginapp/plugins/no_custom_model/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/no_custom_model copying build/lib/cms/test_utils/project/pluginapp/plugins/no_custom_model/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/no_custom_model creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/one_thing copying build/lib/cms/test_utils/project/pluginapp/plugins/one_thing/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/one_thing copying build/lib/cms/test_utils/project/pluginapp/plugins/one_thing/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/one_thing creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/revdesc copying build/lib/cms/test_utils/project/pluginapp/plugins/revdesc/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/revdesc copying build/lib/cms/test_utils/project/pluginapp/plugins/revdesc/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/revdesc copying build/lib/cms/test_utils/project/pluginapp/plugins/revdesc/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/revdesc creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/style copying build/lib/cms/test_utils/project/pluginapp/plugins/style/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/style copying build/lib/cms/test_utils/project/pluginapp/plugins/style/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/style copying build/lib/cms/test_utils/project/pluginapp/plugins/style/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/style creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/validation copying build/lib/cms/test_utils/project/pluginapp/plugins/validation/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/validation copying build/lib/cms/test_utils/project/pluginapp/plugins/validation/cms_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/validation copying build/lib/cms/test_utils/project/pluginapp/plugins/validation/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/validation creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/cms_apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/cms_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/cms_menus.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/cms_toolbars.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/cms_wizards.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/forms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/ns_urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/urls2.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/urls_childapp.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/urls_example.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/urls_excluded.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/urls_extra.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/urls_parentapp.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/urls_sample_config.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp copying build/lib/cms/test_utils/project/sampleapp/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util copying build/lib/cms/test_utils/util/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util copying build/lib/cms/test_utils/util/context_managers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util copying build/lib/cms/test_utils/util/fuzzy_int.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util copying build/lib/cms/test_utils/util/grouper.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util copying build/lib/cms/test_utils/util/menu_extender.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util copying build/lib/cms/test_utils/util/mock.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util copying build/lib/cms/test_utils/util/static_analysis.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_api.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_app_registration.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_apphook_reload_language_variants.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_apphooks.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_cache.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_check.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_cms_config_wizards.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_extensions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_fixture_loading.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_forms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_grouper_admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_helpers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_i18n.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_log_entries.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_mail.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_management.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_menu.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_menu_page_viewperm.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_menu_page_viewperm_staff.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_menu_utils.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_migrations.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_multilingual.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_navextender.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_nested_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_no_i18n.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_nonroot.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_page.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_page_admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_page_user_admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_page_user_group_admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_permissions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_permmod.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_placeholder.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_placeholder_admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_placeholder_app_admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_placeholder_checks.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_placeholder_operation_signals.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_plugin_renderers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_po.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_rendering.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_security.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_settings.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_signals.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_site.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_sitemap.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_static_analysis.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_templates.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_toolbar.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_templatetags.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_toolbar_enabled_models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_toolbar_pool.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_urlutils.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_widgets.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests copying build/lib/cms/tests/test_wizards.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar copying build/lib/cms/toolbar/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar copying build/lib/cms/toolbar/items.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar copying build/lib/cms/toolbar/toolbar.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar copying build/lib/cms/toolbar/utils.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/admin.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/apphook_reload.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/check.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/conf.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/decorators.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/encoder.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/helpers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/i18n.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/mail.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/page.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/page_permissions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/permissions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/placeholder.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/plugins.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/request_ip_resolvers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/setup.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils copying build/lib/cms/utils/urlutils.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat copying build/lib/cms/utils/compat/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat copying build/lib/cms/utils/compat/dj.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat copying build/lib/cms/utils/compat/forms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat copying build/lib/cms/utils/compat/response.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat copying build/lib/cms/utils/compat/warnings.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards copying build/lib/cms/wizards/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards copying build/lib/cms/wizards/forms.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards copying build/lib/cms/wizards/helpers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards copying build/lib/cms/wizards/urls.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards copying build/lib/cms/wizards/views.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards copying build/lib/cms/wizards/wizard_base.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards copying build/lib/cms/wizards/wizard_pool.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/af creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/af/LC_MESSAGES copying build/lib/cms/locale/af/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/af/LC_MESSAGES copying build/lib/cms/locale/af/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/af/LC_MESSAGES copying build/lib/cms/locale/af/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/af/LC_MESSAGES copying build/lib/cms/locale/af/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/af/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar/LC_MESSAGES copying build/lib/cms/locale/ar/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar/LC_MESSAGES copying build/lib/cms/locale/ar/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar/LC_MESSAGES copying build/lib/cms/locale/ar/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar/LC_MESSAGES copying build/lib/cms/locale/ar/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar_SA creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar_SA/LC_MESSAGES copying build/lib/cms/locale/ar_SA/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar_SA/LC_MESSAGES copying build/lib/cms/locale/ar_SA/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar_SA/LC_MESSAGES copying build/lib/cms/locale/ar_SA/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar_SA/LC_MESSAGES copying build/lib/cms/locale/ar_SA/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ar_SA/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/be creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/be/LC_MESSAGES copying build/lib/cms/locale/be/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/be/LC_MESSAGES copying build/lib/cms/locale/be/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/be/LC_MESSAGES copying build/lib/cms/locale/be/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/be/LC_MESSAGES copying build/lib/cms/locale/be/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/be/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bg creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bg/LC_MESSAGES copying build/lib/cms/locale/bg/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bg/LC_MESSAGES copying build/lib/cms/locale/bg/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bg/LC_MESSAGES copying build/lib/cms/locale/bg/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bg/LC_MESSAGES copying build/lib/cms/locale/bg/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bg/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bn creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bn/LC_MESSAGES copying build/lib/cms/locale/bn/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bn/LC_MESSAGES copying build/lib/cms/locale/bn/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bn/LC_MESSAGES copying build/lib/cms/locale/bn/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bn/LC_MESSAGES copying build/lib/cms/locale/bn/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/bn/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ca creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ca/LC_MESSAGES copying build/lib/cms/locale/ca/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ca/LC_MESSAGES copying build/lib/cms/locale/ca/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ca/LC_MESSAGES copying build/lib/cms/locale/ca/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ca/LC_MESSAGES copying build/lib/cms/locale/ca/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ca/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cmn creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cmn/LC_MESSAGES copying build/lib/cms/locale/cmn/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cmn/LC_MESSAGES copying build/lib/cms/locale/cmn/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cmn/LC_MESSAGES copying build/lib/cms/locale/cmn/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cmn/LC_MESSAGES copying build/lib/cms/locale/cmn/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cmn/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs/LC_MESSAGES copying build/lib/cms/locale/cs/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs/LC_MESSAGES copying build/lib/cms/locale/cs/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs/LC_MESSAGES copying build/lib/cms/locale/cs/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs/LC_MESSAGES copying build/lib/cms/locale/cs/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs_CZ creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs_CZ/LC_MESSAGES copying build/lib/cms/locale/cs_CZ/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs_CZ/LC_MESSAGES copying build/lib/cms/locale/cs_CZ/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs_CZ/LC_MESSAGES copying build/lib/cms/locale/cs_CZ/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs_CZ/LC_MESSAGES copying build/lib/cms/locale/cs_CZ/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cs_CZ/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cy creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cy/LC_MESSAGES copying build/lib/cms/locale/cy/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cy/LC_MESSAGES copying build/lib/cms/locale/cy/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cy/LC_MESSAGES copying build/lib/cms/locale/cy/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cy/LC_MESSAGES copying build/lib/cms/locale/cy/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/cy/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/da creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/da/LC_MESSAGES copying build/lib/cms/locale/da/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/da/LC_MESSAGES copying build/lib/cms/locale/da/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/da/LC_MESSAGES copying build/lib/cms/locale/da/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/da/LC_MESSAGES copying build/lib/cms/locale/da/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/da/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/de creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/de/LC_MESSAGES copying build/lib/cms/locale/de/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/de/LC_MESSAGES copying build/lib/cms/locale/de/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/de/LC_MESSAGES copying build/lib/cms/locale/de/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/de/LC_MESSAGES copying build/lib/cms/locale/de/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/de/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/el creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/el/LC_MESSAGES copying build/lib/cms/locale/el/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/el/LC_MESSAGES copying build/lib/cms/locale/el/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/el/LC_MESSAGES copying build/lib/cms/locale/el/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/el/LC_MESSAGES copying build/lib/cms/locale/el/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/el/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en/LC_MESSAGES copying build/lib/cms/locale/en/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en/LC_MESSAGES copying build/lib/cms/locale/en/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en/LC_MESSAGES copying build/lib/cms/locale/en/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en/LC_MESSAGES copying build/lib/cms/locale/en/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_GB creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_GB/LC_MESSAGES copying build/lib/cms/locale/en_GB/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_GB/LC_MESSAGES copying build/lib/cms/locale/en_GB/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_GB/LC_MESSAGES copying build/lib/cms/locale/en_GB/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_GB/LC_MESSAGES copying build/lib/cms/locale/en_GB/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_GB/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_HK creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_HK/LC_MESSAGES copying build/lib/cms/locale/en_HK/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_HK/LC_MESSAGES copying build/lib/cms/locale/en_HK/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_HK/LC_MESSAGES copying build/lib/cms/locale/en_HK/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_HK/LC_MESSAGES copying build/lib/cms/locale/en_HK/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_HK/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_US creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_US/LC_MESSAGES copying build/lib/cms/locale/en_US/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_US/LC_MESSAGES copying build/lib/cms/locale/en_US/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_US/LC_MESSAGES copying build/lib/cms/locale/en_US/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_US/LC_MESSAGES copying build/lib/cms/locale/en_US/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/en_US/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eo creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eo/LC_MESSAGES copying build/lib/cms/locale/eo/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eo/LC_MESSAGES copying build/lib/cms/locale/eo/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eo/LC_MESSAGES copying build/lib/cms/locale/eo/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eo/LC_MESSAGES copying build/lib/cms/locale/eo/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eo/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es/LC_MESSAGES copying build/lib/cms/locale/es/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es/LC_MESSAGES copying build/lib/cms/locale/es/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es/LC_MESSAGES copying build/lib/cms/locale/es/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es/LC_MESSAGES copying build/lib/cms/locale/es/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_AR creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_AR/LC_MESSAGES copying build/lib/cms/locale/es_AR/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_AR/LC_MESSAGES copying build/lib/cms/locale/es_AR/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_AR/LC_MESSAGES copying build/lib/cms/locale/es_AR/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_AR/LC_MESSAGES copying build/lib/cms/locale/es_AR/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_AR/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_BO creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_BO/LC_MESSAGES copying build/lib/cms/locale/es_BO/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_BO/LC_MESSAGES copying build/lib/cms/locale/es_BO/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_BO/LC_MESSAGES copying build/lib/cms/locale/es_BO/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_BO/LC_MESSAGES copying build/lib/cms/locale/es_BO/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_BO/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_DO creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_DO/LC_MESSAGES copying build/lib/cms/locale/es_DO/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_DO/LC_MESSAGES copying build/lib/cms/locale/es_DO/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_DO/LC_MESSAGES copying build/lib/cms/locale/es_DO/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_DO/LC_MESSAGES copying build/lib/cms/locale/es_DO/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/es_DO/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/et creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/et/LC_MESSAGES copying build/lib/cms/locale/et/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/et/LC_MESSAGES copying build/lib/cms/locale/et/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/et/LC_MESSAGES copying build/lib/cms/locale/et/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/et/LC_MESSAGES copying build/lib/cms/locale/et/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/et/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eu creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eu/LC_MESSAGES copying build/lib/cms/locale/eu/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eu/LC_MESSAGES copying build/lib/cms/locale/eu/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eu/LC_MESSAGES copying build/lib/cms/locale/eu/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eu/LC_MESSAGES copying build/lib/cms/locale/eu/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/eu/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa/LC_MESSAGES copying build/lib/cms/locale/fa/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa/LC_MESSAGES copying build/lib/cms/locale/fa/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa/LC_MESSAGES copying build/lib/cms/locale/fa/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa/LC_MESSAGES copying build/lib/cms/locale/fa/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa_IR creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa_IR/LC_MESSAGES copying build/lib/cms/locale/fa_IR/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa_IR/LC_MESSAGES copying build/lib/cms/locale/fa_IR/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa_IR/LC_MESSAGES copying build/lib/cms/locale/fa_IR/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa_IR/LC_MESSAGES copying build/lib/cms/locale/fa_IR/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fa_IR/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi/LC_MESSAGES copying build/lib/cms/locale/fi/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi/LC_MESSAGES copying build/lib/cms/locale/fi/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi/LC_MESSAGES copying build/lib/cms/locale/fi/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi/LC_MESSAGES copying build/lib/cms/locale/fi/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi_FI creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi_FI/LC_MESSAGES copying build/lib/cms/locale/fi_FI/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi_FI/LC_MESSAGES copying build/lib/cms/locale/fi_FI/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi_FI/LC_MESSAGES copying build/lib/cms/locale/fi_FI/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi_FI/LC_MESSAGES copying build/lib/cms/locale/fi_FI/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fi_FI/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr/LC_MESSAGES copying build/lib/cms/locale/fr/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr/LC_MESSAGES copying build/lib/cms/locale/fr/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr/LC_MESSAGES copying build/lib/cms/locale/fr/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr/LC_MESSAGES copying build/lib/cms/locale/fr/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_CA creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_CA/LC_MESSAGES copying build/lib/cms/locale/fr_CA/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_CA/LC_MESSAGES copying build/lib/cms/locale/fr_CA/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_CA/LC_MESSAGES copying build/lib/cms/locale/fr_CA/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_CA/LC_MESSAGES copying build/lib/cms/locale/fr_CA/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_CA/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_FR creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_FR/LC_MESSAGES copying build/lib/cms/locale/fr_FR/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_FR/LC_MESSAGES copying build/lib/cms/locale/fr_FR/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_FR/LC_MESSAGES copying build/lib/cms/locale/fr_FR/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_FR/LC_MESSAGES copying build/lib/cms/locale/fr_FR/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/fr_FR/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ga creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ga/LC_MESSAGES copying build/lib/cms/locale/ga/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ga/LC_MESSAGES copying build/lib/cms/locale/ga/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ga/LC_MESSAGES copying build/lib/cms/locale/ga/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ga/LC_MESSAGES copying build/lib/cms/locale/ga/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ga/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gl creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gl/LC_MESSAGES copying build/lib/cms/locale/gl/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gl/LC_MESSAGES copying build/lib/cms/locale/gl/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gl/LC_MESSAGES copying build/lib/cms/locale/gl/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gl/LC_MESSAGES copying build/lib/cms/locale/gl/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gl/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gu creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gu/LC_MESSAGES copying build/lib/cms/locale/gu/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gu/LC_MESSAGES copying build/lib/cms/locale/gu/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gu/LC_MESSAGES copying build/lib/cms/locale/gu/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gu/LC_MESSAGES copying build/lib/cms/locale/gu/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/gu/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/he creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/he/LC_MESSAGES copying build/lib/cms/locale/he/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/he/LC_MESSAGES copying build/lib/cms/locale/he/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/he/LC_MESSAGES copying build/lib/cms/locale/he/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/he/LC_MESSAGES copying build/lib/cms/locale/he/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/he/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hi creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hi/LC_MESSAGES copying build/lib/cms/locale/hi/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hi/LC_MESSAGES copying build/lib/cms/locale/hi/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hi/LC_MESSAGES copying build/lib/cms/locale/hi/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hi/LC_MESSAGES copying build/lib/cms/locale/hi/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hi/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hr creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hr/LC_MESSAGES copying build/lib/cms/locale/hr/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hr/LC_MESSAGES copying build/lib/cms/locale/hr/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hr/LC_MESSAGES copying build/lib/cms/locale/hr/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hr/LC_MESSAGES copying build/lib/cms/locale/hr/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hr/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hu creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hu/LC_MESSAGES copying build/lib/cms/locale/hu/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hu/LC_MESSAGES copying build/lib/cms/locale/hu/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hu/LC_MESSAGES copying build/lib/cms/locale/hu/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hu/LC_MESSAGES copying build/lib/cms/locale/hu/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/hu/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/id creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/id/LC_MESSAGES copying build/lib/cms/locale/id/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/id/LC_MESSAGES copying build/lib/cms/locale/id/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/id/LC_MESSAGES copying build/lib/cms/locale/id/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/id/LC_MESSAGES copying build/lib/cms/locale/id/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/id/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is/LC_MESSAGES copying build/lib/cms/locale/is/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is/LC_MESSAGES copying build/lib/cms/locale/is/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is/LC_MESSAGES copying build/lib/cms/locale/is/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is/LC_MESSAGES copying build/lib/cms/locale/is/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is_IS creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is_IS/LC_MESSAGES copying build/lib/cms/locale/is_IS/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is_IS/LC_MESSAGES copying build/lib/cms/locale/is_IS/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is_IS/LC_MESSAGES copying build/lib/cms/locale/is_IS/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is_IS/LC_MESSAGES copying build/lib/cms/locale/is_IS/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/is_IS/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/it creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/it/LC_MESSAGES copying build/lib/cms/locale/it/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/it/LC_MESSAGES copying build/lib/cms/locale/it/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/it/LC_MESSAGES copying build/lib/cms/locale/it/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/it/LC_MESSAGES copying build/lib/cms/locale/it/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/it/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ja creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ja/LC_MESSAGES copying build/lib/cms/locale/ja/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ja/LC_MESSAGES copying build/lib/cms/locale/ja/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ja/LC_MESSAGES copying build/lib/cms/locale/ja/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ja/LC_MESSAGES copying build/lib/cms/locale/ja/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ja/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ka creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ka/LC_MESSAGES copying build/lib/cms/locale/ka/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ka/LC_MESSAGES copying build/lib/cms/locale/ka/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ka/LC_MESSAGES copying build/lib/cms/locale/ka/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ka/LC_MESSAGES copying build/lib/cms/locale/ka/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ka/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/kk creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/kk/LC_MESSAGES copying build/lib/cms/locale/kk/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/kk/LC_MESSAGES copying build/lib/cms/locale/kk/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/kk/LC_MESSAGES copying build/lib/cms/locale/kk/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/kk/LC_MESSAGES copying build/lib/cms/locale/kk/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/kk/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/km creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/km/LC_MESSAGES copying build/lib/cms/locale/km/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/km/LC_MESSAGES copying build/lib/cms/locale/km/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/km/LC_MESSAGES copying build/lib/cms/locale/km/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/km/LC_MESSAGES copying build/lib/cms/locale/km/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/km/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko/LC_MESSAGES copying build/lib/cms/locale/ko/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko/LC_MESSAGES copying build/lib/cms/locale/ko/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko/LC_MESSAGES copying build/lib/cms/locale/ko/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko/LC_MESSAGES copying build/lib/cms/locale/ko/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko_KR creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko_KR/LC_MESSAGES copying build/lib/cms/locale/ko_KR/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko_KR/LC_MESSAGES copying build/lib/cms/locale/ko_KR/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko_KR/LC_MESSAGES copying build/lib/cms/locale/ko_KR/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko_KR/LC_MESSAGES copying build/lib/cms/locale/ko_KR/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ko_KR/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ku_IQ creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ku_IQ/LC_MESSAGES copying build/lib/cms/locale/ku_IQ/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ku_IQ/LC_MESSAGES copying build/lib/cms/locale/ku_IQ/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ku_IQ/LC_MESSAGES copying build/lib/cms/locale/ku_IQ/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ku_IQ/LC_MESSAGES copying build/lib/cms/locale/ku_IQ/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ku_IQ/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ky creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ky/LC_MESSAGES copying build/lib/cms/locale/ky/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ky/LC_MESSAGES copying build/lib/cms/locale/ky/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ky/LC_MESSAGES copying build/lib/cms/locale/ky/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ky/LC_MESSAGES copying build/lib/cms/locale/ky/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ky/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt/LC_MESSAGES copying build/lib/cms/locale/lt/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt/LC_MESSAGES copying build/lib/cms/locale/lt/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt/LC_MESSAGES copying build/lib/cms/locale/lt/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt/LC_MESSAGES copying build/lib/cms/locale/lt/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt_LT creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt_LT/LC_MESSAGES copying build/lib/cms/locale/lt_LT/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt_LT/LC_MESSAGES copying build/lib/cms/locale/lt_LT/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt_LT/LC_MESSAGES copying build/lib/cms/locale/lt_LT/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt_LT/LC_MESSAGES copying build/lib/cms/locale/lt_LT/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lt_LT/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lv creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lv/LC_MESSAGES copying build/lib/cms/locale/lv/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lv/LC_MESSAGES copying build/lib/cms/locale/lv/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lv/LC_MESSAGES copying build/lib/cms/locale/lv/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lv/LC_MESSAGES copying build/lib/cms/locale/lv/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/lv/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ml creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ml/LC_MESSAGES copying build/lib/cms/locale/ml/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ml/LC_MESSAGES copying build/lib/cms/locale/ml/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ml/LC_MESSAGES copying build/lib/cms/locale/ml/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ml/LC_MESSAGES copying build/lib/cms/locale/ml/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ml/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn/LC_MESSAGES copying build/lib/cms/locale/mn/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn/LC_MESSAGES copying build/lib/cms/locale/mn/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn/LC_MESSAGES copying build/lib/cms/locale/mn/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn/LC_MESSAGES copying build/lib/cms/locale/mn/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn_MN creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn_MN/LC_MESSAGES copying build/lib/cms/locale/mn_MN/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn_MN/LC_MESSAGES copying build/lib/cms/locale/mn_MN/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn_MN/LC_MESSAGES copying build/lib/cms/locale/mn_MN/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn_MN/LC_MESSAGES copying build/lib/cms/locale/mn_MN/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mn_MN/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ms creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ms/LC_MESSAGES copying build/lib/cms/locale/ms/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ms/LC_MESSAGES copying build/lib/cms/locale/ms/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ms/LC_MESSAGES copying build/lib/cms/locale/ms/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ms/LC_MESSAGES copying build/lib/cms/locale/ms/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ms/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mt creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mt/LC_MESSAGES copying build/lib/cms/locale/mt/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mt/LC_MESSAGES copying build/lib/cms/locale/mt/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mt/LC_MESSAGES copying build/lib/cms/locale/mt/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mt/LC_MESSAGES copying build/lib/cms/locale/mt/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/mt/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nb creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nb/LC_MESSAGES copying build/lib/cms/locale/nb/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nb/LC_MESSAGES copying build/lib/cms/locale/nb/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nb/LC_MESSAGES copying build/lib/cms/locale/nb/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nb/LC_MESSAGES copying build/lib/cms/locale/nb/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nb/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nl creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nl/LC_MESSAGES copying build/lib/cms/locale/nl/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nl/LC_MESSAGES copying build/lib/cms/locale/nl/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nl/LC_MESSAGES copying build/lib/cms/locale/nl/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nl/LC_MESSAGES copying build/lib/cms/locale/nl/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/nl/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/no creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/no/LC_MESSAGES copying build/lib/cms/locale/no/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/no/LC_MESSAGES copying build/lib/cms/locale/no/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/no/LC_MESSAGES copying build/lib/cms/locale/no/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/no/LC_MESSAGES copying build/lib/cms/locale/no/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/no/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pap creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pap/LC_MESSAGES copying build/lib/cms/locale/pap/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pap/LC_MESSAGES copying build/lib/cms/locale/pap/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pap/LC_MESSAGES copying build/lib/cms/locale/pap/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pap/LC_MESSAGES copying build/lib/cms/locale/pap/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pap/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pl creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pl/LC_MESSAGES copying build/lib/cms/locale/pl/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pl/LC_MESSAGES copying build/lib/cms/locale/pl/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pl/LC_MESSAGES copying build/lib/cms/locale/pl/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pl/LC_MESSAGES copying build/lib/cms/locale/pl/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pl/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt/LC_MESSAGES copying build/lib/cms/locale/pt/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt/LC_MESSAGES copying build/lib/cms/locale/pt/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt/LC_MESSAGES copying build/lib/cms/locale/pt/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt/LC_MESSAGES copying build/lib/cms/locale/pt/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_BR creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_BR/LC_MESSAGES copying build/lib/cms/locale/pt_BR/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_BR/LC_MESSAGES copying build/lib/cms/locale/pt_BR/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_BR/LC_MESSAGES copying build/lib/cms/locale/pt_BR/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_BR/LC_MESSAGES copying build/lib/cms/locale/pt_BR/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_BR/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_PT creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_PT/LC_MESSAGES copying build/lib/cms/locale/pt_PT/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_PT/LC_MESSAGES copying build/lib/cms/locale/pt_PT/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_PT/LC_MESSAGES copying build/lib/cms/locale/pt_PT/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_PT/LC_MESSAGES copying build/lib/cms/locale/pt_PT/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/pt_PT/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro/LC_MESSAGES copying build/lib/cms/locale/ro/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro/LC_MESSAGES copying build/lib/cms/locale/ro/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro/LC_MESSAGES copying build/lib/cms/locale/ro/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro/LC_MESSAGES copying build/lib/cms/locale/ro/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro_RO creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro_RO/LC_MESSAGES copying build/lib/cms/locale/ro_RO/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro_RO/LC_MESSAGES copying build/lib/cms/locale/ro_RO/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro_RO/LC_MESSAGES copying build/lib/cms/locale/ro_RO/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro_RO/LC_MESSAGES copying build/lib/cms/locale/ro_RO/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ro_RO/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru/LC_MESSAGES copying build/lib/cms/locale/ru/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru/LC_MESSAGES copying build/lib/cms/locale/ru/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru/LC_MESSAGES copying build/lib/cms/locale/ru/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru/LC_MESSAGES copying build/lib/cms/locale/ru/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru_RU creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru_RU/LC_MESSAGES copying build/lib/cms/locale/ru_RU/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru_RU/LC_MESSAGES copying build/lib/cms/locale/ru_RU/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru_RU/LC_MESSAGES copying build/lib/cms/locale/ru_RU/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru_RU/LC_MESSAGES copying build/lib/cms/locale/ru_RU/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ru_RU/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk/LC_MESSAGES copying build/lib/cms/locale/sk/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk/LC_MESSAGES copying build/lib/cms/locale/sk/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk/LC_MESSAGES copying build/lib/cms/locale/sk/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk/LC_MESSAGES copying build/lib/cms/locale/sk/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk_SK creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk_SK/LC_MESSAGES copying build/lib/cms/locale/sk_SK/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk_SK/LC_MESSAGES copying build/lib/cms/locale/sk_SK/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk_SK/LC_MESSAGES copying build/lib/cms/locale/sk_SK/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk_SK/LC_MESSAGES copying build/lib/cms/locale/sk_SK/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sk_SK/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl/LC_MESSAGES copying build/lib/cms/locale/sl/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl/LC_MESSAGES copying build/lib/cms/locale/sl/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl/LC_MESSAGES copying build/lib/cms/locale/sl/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl/LC_MESSAGES copying build/lib/cms/locale/sl/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl_SI creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl_SI/LC_MESSAGES copying build/lib/cms/locale/sl_SI/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl_SI/LC_MESSAGES copying build/lib/cms/locale/sl_SI/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl_SI/LC_MESSAGES copying build/lib/cms/locale/sl_SI/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl_SI/LC_MESSAGES copying build/lib/cms/locale/sl_SI/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sl_SI/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq/LC_MESSAGES copying build/lib/cms/locale/sq/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq/LC_MESSAGES copying build/lib/cms/locale/sq/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq/LC_MESSAGES copying build/lib/cms/locale/sq/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq/LC_MESSAGES copying build/lib/cms/locale/sq/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq_AL creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq_AL/LC_MESSAGES copying build/lib/cms/locale/sq_AL/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq_AL/LC_MESSAGES copying build/lib/cms/locale/sq_AL/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq_AL/LC_MESSAGES copying build/lib/cms/locale/sq_AL/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq_AL/LC_MESSAGES copying build/lib/cms/locale/sq_AL/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sq_AL/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr/LC_MESSAGES copying build/lib/cms/locale/sr/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr/LC_MESSAGES copying build/lib/cms/locale/sr/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr/LC_MESSAGES copying build/lib/cms/locale/sr/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr/LC_MESSAGES copying build/lib/cms/locale/sr/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr@latin creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr@latin/LC_MESSAGES copying build/lib/cms/locale/sr@latin/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr@latin/LC_MESSAGES copying build/lib/cms/locale/sr@latin/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr@latin/LC_MESSAGES copying build/lib/cms/locale/sr@latin/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr@latin/LC_MESSAGES copying build/lib/cms/locale/sr@latin/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sr@latin/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sv creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sv/LC_MESSAGES copying build/lib/cms/locale/sv/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sv/LC_MESSAGES copying build/lib/cms/locale/sv/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sv/LC_MESSAGES copying build/lib/cms/locale/sv/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sv/LC_MESSAGES copying build/lib/cms/locale/sv/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/sv/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ta creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ta/LC_MESSAGES copying build/lib/cms/locale/ta/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ta/LC_MESSAGES copying build/lib/cms/locale/ta/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ta/LC_MESSAGES copying build/lib/cms/locale/ta/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ta/LC_MESSAGES copying build/lib/cms/locale/ta/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ta/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th/LC_MESSAGES copying build/lib/cms/locale/th/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th/LC_MESSAGES copying build/lib/cms/locale/th/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th/LC_MESSAGES copying build/lib/cms/locale/th/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th/LC_MESSAGES copying build/lib/cms/locale/th/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th_TH creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th_TH/LC_MESSAGES copying build/lib/cms/locale/th_TH/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th_TH/LC_MESSAGES copying build/lib/cms/locale/th_TH/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th_TH/LC_MESSAGES copying build/lib/cms/locale/th_TH/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th_TH/LC_MESSAGES copying build/lib/cms/locale/th_TH/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/th_TH/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tlh creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tlh/LC_MESSAGES copying build/lib/cms/locale/tlh/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tlh/LC_MESSAGES copying build/lib/cms/locale/tlh/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tlh/LC_MESSAGES copying build/lib/cms/locale/tlh/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tlh/LC_MESSAGES copying build/lib/cms/locale/tlh/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tlh/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr/LC_MESSAGES copying build/lib/cms/locale/tr/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr/LC_MESSAGES copying build/lib/cms/locale/tr/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr/LC_MESSAGES copying build/lib/cms/locale/tr/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr/LC_MESSAGES copying build/lib/cms/locale/tr/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr_TR creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr_TR/LC_MESSAGES copying build/lib/cms/locale/tr_TR/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr_TR/LC_MESSAGES copying build/lib/cms/locale/tr_TR/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr_TR/LC_MESSAGES copying build/lib/cms/locale/tr_TR/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr_TR/LC_MESSAGES copying build/lib/cms/locale/tr_TR/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/tr_TR/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ug creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ug/LC_MESSAGES copying build/lib/cms/locale/ug/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ug/LC_MESSAGES copying build/lib/cms/locale/ug/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ug/LC_MESSAGES copying build/lib/cms/locale/ug/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ug/LC_MESSAGES copying build/lib/cms/locale/ug/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ug/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/uk creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/uk/LC_MESSAGES copying build/lib/cms/locale/uk/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/uk/LC_MESSAGES copying build/lib/cms/locale/uk/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/uk/LC_MESSAGES copying build/lib/cms/locale/uk/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/uk/LC_MESSAGES copying build/lib/cms/locale/uk/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/uk/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ur creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ur/LC_MESSAGES copying build/lib/cms/locale/ur/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ur/LC_MESSAGES copying build/lib/cms/locale/ur/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ur/LC_MESSAGES copying build/lib/cms/locale/ur/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ur/LC_MESSAGES copying build/lib/cms/locale/ur/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/ur/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi/LC_MESSAGES copying build/lib/cms/locale/vi/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi/LC_MESSAGES copying build/lib/cms/locale/vi/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi/LC_MESSAGES copying build/lib/cms/locale/vi/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi/LC_MESSAGES copying build/lib/cms/locale/vi/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi_VN creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi_VN/LC_MESSAGES copying build/lib/cms/locale/vi_VN/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi_VN/LC_MESSAGES copying build/lib/cms/locale/vi_VN/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi_VN/LC_MESSAGES copying build/lib/cms/locale/vi_VN/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi_VN/LC_MESSAGES copying build/lib/cms/locale/vi_VN/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/vi_VN/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh-Hans creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh-Hans/LC_MESSAGES copying build/lib/cms/locale/zh-Hans/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh-Hans/LC_MESSAGES copying build/lib/cms/locale/zh-Hans/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh-Hans/LC_MESSAGES copying build/lib/cms/locale/zh-Hans/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh-Hans/LC_MESSAGES copying build/lib/cms/locale/zh-Hans/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh-Hans/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh/LC_MESSAGES copying build/lib/cms/locale/zh/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh/LC_MESSAGES copying build/lib/cms/locale/zh/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh/LC_MESSAGES copying build/lib/cms/locale/zh/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh/LC_MESSAGES copying build/lib/cms/locale/zh/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN.GB2312 creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN.GB2312/LC_MESSAGES copying build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN.GB2312/LC_MESSAGES copying build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN.GB2312/LC_MESSAGES copying build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN.GB2312/LC_MESSAGES copying build/lib/cms/locale/zh_CN.GB2312/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN.GB2312/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN/LC_MESSAGES copying build/lib/cms/locale/zh_CN/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN/LC_MESSAGES copying build/lib/cms/locale/zh_CN/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN/LC_MESSAGES copying build/lib/cms/locale/zh_CN/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN/LC_MESSAGES copying build/lib/cms/locale/zh_CN/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_CN/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_TW creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_TW/LC_MESSAGES copying build/lib/cms/locale/zh_TW/LC_MESSAGES/django.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_TW/LC_MESSAGES copying build/lib/cms/locale/zh_TW/LC_MESSAGES/django.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_TW/LC_MESSAGES copying build/lib/cms/locale/zh_TW/LC_MESSAGES/djangojs.mo -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_TW/LC_MESSAGES copying build/lib/cms/locale/zh_TW/LC_MESSAGES/djangojs.po -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/locale/zh_TW/LC_MESSAGES creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/css creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/css/5.0.6 copying build/lib/cms/static/cms/css/5.0.6/cms.admin.css -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/css/5.0.6 copying build/lib/cms/static/cms/css/5.0.6/cms.base.css -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/css/5.0.6 copying build/lib/cms/static/cms/css/5.0.6/cms.headless.css -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/css/5.0.6 copying build/lib/cms/static/cms/css/5.0.6/cms.pagetree.css -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/css/5.0.6 copying build/lib/cms/static/cms/css/5.0.6/cms.welcome.css -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/css/5.0.6 copying build/lib/cms/static/cms/css/5.0.6/cms.wizard.css -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/css/5.0.6 creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/5.0.6 copying build/lib/cms/static/cms/fonts/5.0.6/django-cms-iconfont.eot -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/5.0.6 copying build/lib/cms/static/cms/fonts/5.0.6/django-cms-iconfont.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/5.0.6 copying build/lib/cms/static/cms/fonts/5.0.6/django-cms-iconfont.ttf -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/5.0.6 copying build/lib/cms/static/cms/fonts/5.0.6/django-cms-iconfont.woff -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/5.0.6 copying build/lib/cms/static/cms/fonts/5.0.6/django-cms-iconfont.woff2 -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/5.0.6 creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/_template.svgz -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/advanced-settings.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/alias.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/apphook.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/archive.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/arrow-right.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/arrow-wide.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/arrow.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/bin.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/broadcast-off.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/broadcast-on.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/check-circle.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/check-o.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/check-square.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/check.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/close.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/cogs.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/comment.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/compare.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/copy.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/cut.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/edit.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/edit-new.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/eye.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/forbidden.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/handler.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/highlight.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/home.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/info.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/layers.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/list-ol.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/loader.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/lock.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/logo.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/manage-versions.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/menu.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/minimize.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/minus-circle.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/minus-square-o.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/minus-square.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/minus.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/moderate.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/paste.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/pencil.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/pin.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/plugins.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/plus-circle.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/plus-square-o.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/plus.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/publish.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/puzzle.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/redo.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/rename.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/scissors.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/search.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/settings.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/sitemap.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/squares.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/theme-auto.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/theme-dark.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/theme-light.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/undo.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/unlock.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/unpublish.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/view.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src copying build/lib/cms/static/cms/fonts/src/window.svg -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/fonts/src creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img copying build/lib/cms/static/cms/img/favicon.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img copying build/lib/cms/static/cms/img/loader.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img copying build/lib/cms/static/cms/img/loader@2x.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/flv.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/gif.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/html.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/java.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/jpg.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/mp3.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/ods.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/odt.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/pdf.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/php.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/png.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/swf.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/tgz.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/ttf.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/txt.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/txt.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/wav.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes copying build/lib/cms/static/cms/img/icons/filetypes/zip.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/filetypes creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/plugins copying build/lib/cms/static/cms/img/icons/plugins/file.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/plugins copying build/lib/cms/static/cms/img/icons/plugins/get_flash_player.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/plugins copying build/lib/cms/static/cms/img/icons/plugins/image.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/plugins copying build/lib/cms/static/cms/img/icons/plugins/link.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/plugins copying build/lib/cms/static/cms/img/icons/plugins/snippet.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/icons/plugins creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/pagetree copying build/lib/cms/static/cms/img/pagetree/tree-li-drag.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/pagetree creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/toolbar copying build/lib/cms/static/cms/img/toolbar/render_model_add.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/toolbar copying build/lib/cms/static/cms/img/toolbar/render_model_icon.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/toolbar copying build/lib/cms/static/cms/img/toolbar/render_model_placeholder.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/img/toolbar creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js copying build/lib/cms/static/cms/js/admin.base.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js copying build/lib/cms/static/cms/js/admin.changeform.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js copying build/lib/cms/static/cms/js/admin.pagetree.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js copying build/lib/cms/static/cms/js/toolbar.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/admin copying build/lib/cms/static/cms/js/admin/actions.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/admin copying build/lib/cms/static/cms/js/admin/language-selector.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/admin creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.admin.base.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.admin.changeform.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.admin.pagetree.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.admin.widget.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.forms.apphookselect.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.forms.pageselectwidget.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.forms.pagesmartlinkwidget.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.forms.slugwidget.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 copying build/lib/cms/static/cms/js/dist/5.0.6/bundle.toolbar.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/dist/5.0.6 creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/libs copying build/lib/cms/static/cms/js/libs/class.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/libs copying build/lib/cms/static/cms/js/libs/jquery.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/libs copying build/lib/cms/static/cms/js/libs/pep.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/libs creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/libs/jstree copying build/lib/cms/static/cms/js/libs/jstree/jstree.grid.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/libs/jstree copying build/lib/cms/static/cms/js/libs/jstree/jstree.min.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/libs/jstree creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.base.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.changeform.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.changetracker.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.clipboard.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.messages.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.modal.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.navigation.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.pagetree.dropdown.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.pagetree.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.pagetree.stickyheader.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.plugins.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.sideframe.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.structureboard.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.toolbar.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.tooltip.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/cms.wizards.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/dropdown.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/get-dist-path.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/jquery.noconflict.post.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/jquery.noconflict.pre.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/jquery.transition.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/jquery.trap.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/jquery.ui.custom.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/jquery.ui.nestedsortable.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/jquery.ui.touchpunch.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/keyboard.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/loader.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/nextuntil.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/preload-images.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/scrollbar.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/slug.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules copying build/lib/cms/static/cms/js/modules/tmpl.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules/shortcuts copying build/lib/cms/static/cms/js/modules/shortcuts/create-modal.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules/shortcuts copying build/lib/cms/static/cms/js/modules/shortcuts/help.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules/shortcuts copying build/lib/cms/static/cms/js/modules/shortcuts/help.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules/shortcuts copying build/lib/cms/static/cms/js/modules/shortcuts/index.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules/shortcuts copying build/lib/cms/static/cms/js/modules/shortcuts/placeholders.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules/shortcuts copying build/lib/cms/static/cms/js/modules/shortcuts/toolbar.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/modules/shortcuts creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/polyfills copying build/lib/cms/static/cms/js/polyfills/array.prototype.findindex.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/polyfills copying build/lib/cms/static/cms/js/polyfills/domparser.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/polyfills copying build/lib/cms/static/cms/js/polyfills/function.prototype.bind.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/polyfills creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/LICENSE -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/README.md -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2-bootstrap.css -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2-spinner.gif -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2.css -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ar.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_az.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_bg.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ca.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_cs.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_da.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_de.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_el.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_en.js.template -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_es.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_et.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_eu.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_fa.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_fi.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_fr.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_gl.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_he.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_hr.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_hu.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_id.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_is.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_it.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ja.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ka.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ko.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_lt.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_lv.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_mk.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ms.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_nl.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_no.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_pl.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_pt-BR.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_pt-PT.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ro.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_rs.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ru.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_sk.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_sv.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_th.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_tr.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_ug-CN.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_uk.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_vi.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_zh-CN.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2_locale_zh-TW.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 copying build/lib/cms/static/cms/js/select2/select2x2.png -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/select2 creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/widgets copying build/lib/cms/static/cms/js/widgets/forms.apphookselect.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/widgets copying build/lib/cms/static/cms/js/widgets/forms.pageselectwidget.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/widgets copying build/lib/cms/static/cms/js/widgets/forms.pagesmartlinkwidget.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/widgets copying build/lib/cms/static/cms/js/widgets/forms.slugwidget.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/widgets copying build/lib/cms/static/cms/js/widgets/wizard.pagetypeselect.js -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/js/widgets creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass copying build/lib/cms/static/cms/sass/cms.admin.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass copying build/lib/cms/static/cms/sass/cms.base.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass copying build/lib/cms/static/cms/sass/cms.headless.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass copying build/lib/cms/static/cms/sass/cms.pagetree.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass copying build/lib/cms/static/cms/sass/cms.welcome.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass copying build/lib/cms/static/cms/sass/cms.wizard.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_animation.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_button.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_clipboard.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_content.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_dark-mode-toggle.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_dialog.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_dropdown.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_general.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_hovertooltip.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_iconography.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_loader.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_modal.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_pluginpicker.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_reset.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_shortcuts.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_sideframe.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_structureboard.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_subnav.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_toolbar.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_tooltip.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components copying build/lib/cms/static/cms/sass/components/_welcome.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components/pagetree copying build/lib/cms/static/cms/sass/components/pagetree/_all.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components/pagetree copying build/lib/cms/static/cms/sass/components/pagetree/_dropdown.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components/pagetree copying build/lib/cms/static/cms/sass/components/pagetree/_legend.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components/pagetree copying build/lib/cms/static/cms/sass/components/pagetree/_node-state.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components/pagetree copying build/lib/cms/static/cms/sass/components/pagetree/_tree.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/components/pagetree creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/libs copying build/lib/cms/static/cms/sass/libs/_iconfont.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/libs copying build/lib/cms/static/cms/sass/libs/_rtl_patch.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/libs creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/mixins copying build/lib/cms/static/cms/sass/mixins/_all.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/mixins copying build/lib/cms/static/cms/sass/mixins/_buttons.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/mixins copying build/lib/cms/static/cms/sass/mixins/_custom.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/mixins copying build/lib/cms/static/cms/sass/mixins/_retina.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/mixins copying build/lib/cms/static/cms/sass/mixins/_zindex.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/mixins creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/settings copying build/lib/cms/static/cms/sass/settings/_all.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/settings copying build/lib/cms/static/cms/sass/settings/_cms.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/settings copying build/lib/cms/static/cms/sass/settings/_pagetree.scss -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/static/cms/sass/settings creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/extensions copying build/lib/cms/templates/admin/cms/extensions/change_form.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/extensions creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/grouper copying build/lib/cms/templates/admin/cms/grouper/change_form.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/grouper copying build/lib/cms/templates/admin/cms/grouper/change_list.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/grouper copying build/lib/cms/templates/admin/cms/grouper/content_inline.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/grouper creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/icons copying build/lib/cms/templates/admin/cms/icons/base.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/icons creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/mail copying build/lib/cms/templates/admin/cms/mail/base.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/mail copying build/lib/cms/templates/admin/cms/mail/base.txt -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/mail copying build/lib/cms/templates/admin/cms/mail/page_user_change.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/mail copying build/lib/cms/templates/admin/cms/mail/page_user_change.txt -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/mail creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page copying build/lib/cms/templates/admin/cms/page/change_form.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page copying build/lib/cms/templates/admin/cms/page/close_frame.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page copying build/lib/cms/templates/admin/cms/page/delete_confirmation.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page copying build/lib/cms/templates/admin/cms/page/delete_summary.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page copying build/lib/cms/templates/admin/cms/page/permissions.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page copying build/lib/cms/templates/admin/cms/page/submit_row.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/includes copying build/lib/cms/templates/admin/cms/page/includes/fieldset.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/includes creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/plugin copying build/lib/cms/templates/admin/cms/page/plugin/change_form.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/plugin copying build/lib/cms/templates/admin/cms/page/plugin/confirm_form.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/plugin copying build/lib/cms/templates/admin/cms/page/plugin/delete_confirmation.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/plugin copying build/lib/cms/templates/admin/cms/page/plugin/error_form.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/plugin copying build/lib/cms/templates/admin/cms/page/plugin/submit_line.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/plugin creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree copying build/lib/cms/templates/admin/cms/page/tree/actions_dropdown.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree copying build/lib/cms/templates/admin/cms/page/tree/base.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree copying build/lib/cms/templates/admin/cms/page/tree/copy_premissions.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree copying build/lib/cms/templates/admin/cms/page/tree/filter.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree copying build/lib/cms/templates/admin/cms/page/tree/indicator_legend.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree copying build/lib/cms/templates/admin/cms/page/tree/indicator_menu.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree copying build/lib/cms/templates/admin/cms/page/tree/legend.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree copying build/lib/cms/templates/admin/cms/page/tree/menu.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/page/tree creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/usersettings copying build/lib/cms/templates/admin/cms/usersettings/change_form.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/admin/cms/usersettings creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms copying build/lib/cms/templates/cms/content.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms copying build/lib/cms/templates/cms/dummy.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms copying build/lib/cms/templates/cms/noapphook.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms copying build/lib/cms/templates/cms/welcome.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/headless copying build/lib/cms/templates/cms/headless/placeholder.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/headless creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/plugins copying build/lib/cms/templates/cms/plugins/alias.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/plugins creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/clipboard.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/content.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/dragbar.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/dragitem.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/dragitem_extra_menu.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/dragitem_menu.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/plugin.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/render_plugin_block.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/structure.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/toolbar.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/toolbar_javascript.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar copying build/lib/cms/templates/cms/toolbar/toolbar_with_structure.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/break.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/button.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/button_list.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/button_modal.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/button_sideframe.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/dark_mode_toggle.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/dropdown.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/dropdown_button.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/item_ajax.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/item_link.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/item_modal.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/item_sideframe.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/live_draft.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/login.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/logo.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items copying build/lib/cms/templates/cms/toolbar/items/menu.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/toolbar/items creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/widgets copying build/lib/cms/templates/cms/widgets/applicationconfigselect.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/widgets copying build/lib/cms/templates/cms/widgets/pageselectwidget.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/widgets copying build/lib/cms/templates/cms/widgets/pagesmartlinkwidget.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/widgets creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/wizards copying build/lib/cms/templates/cms/wizards/base.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/wizards copying build/lib/cms/templates/cms/wizards/create.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/wizards copying build/lib/cms/templates/cms/wizards/start.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/wizards copying build/lib/cms/templates/cms/wizards/wizardoptionwidget.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/wizards creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/wizards/includes copying build/lib/cms/templates/cms/wizards/includes/form_fields.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates/cms/wizards/includes creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus copying build/lib/menus/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus copying build/lib/menus/apps.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus copying build/lib/menus/base.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus copying build/lib/menus/exceptions.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus copying build/lib/menus/menu_pool.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus copying build/lib/menus/models.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus copying build/lib/menus/modifiers.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus copying build/lib/menus/utils.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/migrations copying build/lib/menus/migrations/0001_initial.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/migrations copying build/lib/menus/migrations/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/migrations creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templatetags copying build/lib/menus/templatetags/__init__.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templatetags copying build/lib/menus/templatetags/menu_tags.py -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templatetags creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templates creating /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templates/menu copying build/lib/menus/templates/menu/breadcrumb.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templates/menu copying build/lib/menus/templates/menu/dummy.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templates/menu copying build/lib/menus/templates/menu/empty.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templates/menu copying build/lib/menus/templates/menu/language_chooser.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templates/menu copying build/lib/menus/templates/menu/menu.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templates/menu copying build/lib/menus/templates/menu/sub_menu.html -> /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templates/menu byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/__main__.py to __main__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/api.py to api.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/app_base.py to app_base.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/app_registration.py to app_registration.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/apphook_pool.py to apphook_pool.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/appresolver.py to appresolver.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cms_menus.py to cms_menus.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cms_toolbars.py to cms_toolbars.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cms_wizards.py to cms_wizards.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/constants.py to constants.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/context_processors.py to context_processors.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/exceptions.py to exceptions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/menu_bases.py to menu_bases.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/page_rendering.py to page_rendering.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/plugin_base.py to plugin_base.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/plugin_pool.py to plugin_pool.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/urls.py to urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/plugin_processors.py to plugin_processors.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/plugin_rendering.py to plugin_rendering.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templates.py to templates.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar_base.py to toolbar_base.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar_pool.py to toolbar_pool.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/forms.py to forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/pageadmin.py to pageadmin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/permissionadmin.py to permissionadmin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/placeholderadmin.py to placeholderadmin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/settingsadmin.py to settingsadmin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/static_placeholder.py to static_placeholder.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/useradmin.py to useradmin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/admin/utils.py to utils.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache/choices.py to choices.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache/page.py to page.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache/permissions.py to permissions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/cache/placeholder.py to placeholder.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions/extension_pool.py to extension_pool.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/extensions/toolbar.py to toolbar.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms/fields.py to fields.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms/login.py to login.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms/utils.py to utils.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms/validators.py to validators.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms/widgets.py to widgets.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/forms/wizards.py to wizards.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/djangocms.py to djangocms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/cms.py to cms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/startcmsproject.py to startcmsproject.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands/base.py to base.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands/check.py to check.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands/copy.py to copy.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands/delete_orphaned_plugins.py to delete_orphaned_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands/list.py to list.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands/tree.py to tree.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/management/commands/subcommands/uninstall.py to uninstall.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/aliaspluginmodel.py to aliaspluginmodel.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/apphooks_reload.py to apphooks_reload.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/contentmodels.py to contentmodels.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/fields.py to fields.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/managers.py to managers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/pagemodel.py to pagemodel.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/permissionmodels.py to permissionmodels.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/placeholdermodel.py to placeholdermodel.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/placeholderpluginmodel.py to placeholderpluginmodel.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/pluginmodel.py to pluginmodel.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/query.py to query.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/settingmodels.py to settingmodels.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/models/static_placeholder.py to static_placeholder.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware/language.py to language.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware/page.py to page.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware/toolbar.py to toolbar.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware/user.py to user.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/middleware/utils.py to utils.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0002_auto_20140816_1918.py to 0002_auto_20140816_1918.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0003_auto_20140926_2347.py to 0003_auto_20140926_2347.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0004_auto_20140924_1038.py to 0004_auto_20140924_1038.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0005_auto_20140924_1039.py to 0005_auto_20140924_1039.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0006_auto_20140924_1110.py to 0006_auto_20140924_1110.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0007_auto_20141028_1559.py to 0007_auto_20141028_1559.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0008_auto_20150121_0059.py to 0008_auto_20150121_0059.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0008_auto_20150208_2149.py to 0008_auto_20150208_2149.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0009_merge.py to 0009_merge.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0010_migrate_use_structure.py to 0010_migrate_use_structure.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0011_auto_20150419_1006.py to 0011_auto_20150419_1006.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0012_auto_20150607_2207.py to 0012_auto_20150607_2207.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0013_urlconfrevision.py to 0013_urlconfrevision.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0014_auto_20160404_1908.py to 0014_auto_20160404_1908.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0015_auto_20160421_0000.py to 0015_auto_20160421_0000.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0016_auto_20160608_1535.py to 0016_auto_20160608_1535.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0017_pagetype.py to 0017_pagetype.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0018_create_pagenode.py to 0018_create_pagenode.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0019_set_pagenode.py to 0019_set_pagenode.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0020_old_tree_cleanup.py to 0020_old_tree_cleanup.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0021_auto_20180507_1432.py to 0021_auto_20180507_1432.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0022_auto_20180620_1551.py to 0022_auto_20180620_1551.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0023_placeholder_source_field.py to 0023_placeholder_source_field.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0024_set_plugin_absolute_position.py to 0024_set_plugin_absolute_position.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0025_remove_plugin_tree_fields.py to 0025_remove_plugin_tree_fields.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0026_title_placeholders.py to 0026_title_placeholders.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0031_remove_fields.py to 0031_remove_fields.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0027_title_placeholders_data_migration.py to 0027_title_placeholders_data_migration.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0028_remove_page_placeholders.py to 0028_remove_page_placeholders.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0029_create_title_fields_and_url_model.py to 0029_create_title_fields_and_url_model.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0030_auto_20180810_0629.py to 0030_auto_20180810_0629.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0032_remove_title_to_pagecontent.py to 0032_remove_title_to_pagecontent.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0033_placeholder_source_data_migration.py to 0033_placeholder_source_data_migration.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0034_remove_pagecontent_placeholders.py to 0034_remove_pagecontent_placeholders.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0035_auto_20230822_2208.py to 0035_auto_20230822_2208.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0035_auto_20230822_2208_squashed_0036_auto_20240311_1028.py to 0035_auto_20230822_2208_squashed_0036_auto_20240311_1028.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0036_auto_20240311_1028.py to 0036_auto_20240311_1028.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0037_merge_page_treenode.py to 0037_merge_page_treenode.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0038_alter_page_site.py to 0038_alter_page_site.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0039_remove_page_languages_alter_pageurl_unique_together.py to 0039_remove_page_languages_alter_pageurl_unique_together.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0040_alter_pageuser_created_by_and_more.py to 0040_alter_pageuser_created_by_and_more.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/0041_alter_pageurl_unique_together_pageurl_site_and_more.py to 0041_alter_pageurl_unique_together_pageurl_site_and_more.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/operations/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/operations/helpers.py to helpers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals/apphook.py to apphook.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals/log_entries.py to log_entries.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals/pagecontent.py to pagecontent.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/signals/permissions.py to permissions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/sitemaps/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/sitemaps/cms_sitemap.py to cms_sitemap.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags/cms_admin.py to cms_admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags/cms_alias_tags.py to cms_alias_tags.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags/cms_js_tags.py to cms_js_tags.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags/cms_static.py to cms_static.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/templatetags/cms_tags.py to cms_tags.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/runners.py to runners.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/testcases.py to testcases.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/tmpdir.py to tmpdir.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures/fakemlng.py to fakemlng.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures/menus.py to menus.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures/navextenders.py to navextenders.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/fixtures/templatetags.py to templatetags.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/cms_urls_for_apphook_tests.py to cms_urls_for_apphook_tests.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/fourth_cms_urls_for_apphook_tests.py to fourth_cms_urls_for_apphook_tests.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/fourth_urls_for_apphook_tests.py to fourth_urls_for_apphook_tests.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/noadmin_urls.py to noadmin_urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/nonroot_urls.py to nonroot_urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp_urls.py to placeholderapp_urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/second_cms_urls_for_apphook_tests.py to second_cms_urls_for_apphook_tests.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/second_urls_for_apphook_tests.py to second_urls_for_apphook_tests.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/template_backends.py to template_backends.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/third_cms_urls_for_apphook_tests.py to third_cms_urls_for_apphook_tests.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/third_urls_for_apphook_tests.py to third_urls_for_apphook_tests.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/urls.py to urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/urls_2.py to urls_2.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/urls_3.py to urls_3.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/urls_for_apphook_tests.py to urls_for_apphook_tests.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/urls_no18n.py to urls_no18n.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_using_non_feature/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_bad_cms_file/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_config/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_cms_feature_and_config/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_feature_not_implemented/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_config_classes/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_with_two_cms_feature_classes/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_app_class/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/app_without_cms_file/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/backwards_wizards/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/backwards_wizards/cms_wizards.py to cms_wizards.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/backwards_wizards/wizards.py to wizards.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/brokenpluginapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/brokenpluginapp/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/bunch_of_plugins/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/bunch_of_plugins/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/custom_templates/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/customuserapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/customuserapp/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/customuserapp/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp/forms.py to forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/emailuserapp/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp/cms_toolbars.py to cms_toolbars.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/extensionapp/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/fakemlng/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/fakemlng/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/mti_pluginapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/mti_pluginapp/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/mti_pluginapp/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/nested_plugins_app/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/nested_plugins_app/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/objectpermissionsapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/objectpermissionsapp/backends.py to backends.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/objectpermissionsapp/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app/urls.py to urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholder_relation_field_app/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/cms_apps.py to cms_apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/cms_toolbars.py to cms_toolbars.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/exceptions.py to exceptions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/urls.py to urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/placeholderapp/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/caching/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/caching/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/caching/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/extra_context/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/extra_context/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/extra_context/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/link/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/link/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/link/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/manytomany_rel/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/meta/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/meta/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/meta/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn/forms.py to forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multicolumn/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap/forms.py to forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/multiwrap/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/no_custom_model/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/no_custom_model/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/no_custom_model/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/one_thing/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/one_thing/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/revdesc/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/revdesc/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/revdesc/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/style/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/style/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/style/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/validation/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/validation/cms_plugins.py to cms_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/pluginapp/plugins/validation/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/cms_apps.py to cms_apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/cms_config.py to cms_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/cms_menus.py to cms_menus.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/cms_toolbars.py to cms_toolbars.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/cms_wizards.py to cms_wizards.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/forms.py to forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/ns_urls.py to ns_urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/urls.py to urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/urls2.py to urls2.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/urls_childapp.py to urls_childapp.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/urls_example.py to urls_example.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/urls_excluded.py to urls_excluded.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/urls_extra.py to urls_extra.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/urls_parentapp.py to urls_parentapp.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/urls_sample_config.py to urls_sample_config.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/project/sampleapp/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util/context_managers.py to context_managers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util/fuzzy_int.py to fuzzy_int.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util/grouper.py to grouper.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util/menu_extender.py to menu_extender.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util/mock.py to mock.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/test_utils/util/static_analysis.py to static_analysis.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_admin.py to test_admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_api.py to test_api.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_app_registration.py to test_app_registration.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_apphook_reload_language_variants.py to test_apphook_reload_language_variants.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_apphooks.py to test_apphooks.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_cache.py to test_cache.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_check.py to test_check.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_cms_config_wizards.py to test_cms_config_wizards.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_extensions.py to test_extensions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_fixture_loading.py to test_fixture_loading.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_forms.py to test_forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_grouper_admin.py to test_grouper_admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_helpers.py to test_helpers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_i18n.py to test_i18n.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_log_entries.py to test_log_entries.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_mail.py to test_mail.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_management.py to test_management.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_menu.py to test_menu.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_menu_page_viewperm.py to test_menu_page_viewperm.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_menu_page_viewperm_staff.py to test_menu_page_viewperm_staff.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_menu_utils.py to test_menu_utils.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_migrations.py to test_migrations.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_multilingual.py to test_multilingual.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_navextender.py to test_navextender.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_nested_plugins.py to test_nested_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_no_i18n.py to test_no_i18n.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_nonroot.py to test_nonroot.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_page.py to test_page.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_page_admin.py to test_page_admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_page_user_admin.py to test_page_user_admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_page_user_group_admin.py to test_page_user_group_admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_permissions.py to test_permissions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_permmod.py to test_permmod.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_placeholder.py to test_placeholder.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_placeholder_admin.py to test_placeholder_admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_placeholder_app_admin.py to test_placeholder_app_admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_placeholder_checks.py to test_placeholder_checks.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_placeholder_operation_signals.py to test_placeholder_operation_signals.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_plugin_renderers.py to test_plugin_renderers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_plugins.py to test_plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_po.py to test_po.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_rendering.py to test_rendering.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_security.py to test_security.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_settings.py to test_settings.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_signals.py to test_signals.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_site.py to test_site.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_sitemap.py to test_sitemap.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_static_analysis.py to test_static_analysis.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_templates.py to test_templates.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_toolbar.py to test_toolbar.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_templatetags.py to test_templatetags.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_toolbar_enabled_models.py to test_toolbar_enabled_models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_toolbar_pool.py to test_toolbar_pool.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_urlutils.py to test_urlutils.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_views.py to test_views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_widgets.py to test_widgets.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/tests/test_wizards.py to test_wizards.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar/items.py to items.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar/toolbar.py to toolbar.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/toolbar/utils.py to utils.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/admin.py to admin.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/apphook_reload.py to apphook_reload.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/check.py to check.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/conf.py to conf.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/decorators.py to decorators.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/encoder.py to encoder.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/helpers.py to helpers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/i18n.py to i18n.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/mail.py to mail.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/page.py to page.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/page_permissions.py to page_permissions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/permissions.py to permissions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/placeholder.py to placeholder.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/plugins.py to plugins.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/request_ip_resolvers.py to request_ip_resolvers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/setup.py to setup.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/urlutils.py to urlutils.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat/dj.py to dj.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat/forms.py to forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat/response.py to response.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/utils/compat/warnings.py to warnings.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards/forms.py to forms.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards/helpers.py to helpers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards/urls.py to urls.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards/views.py to views.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards/wizard_base.py to wizard_base.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/cms/wizards/wizard_pool.py to wizard_pool.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/apps.py to apps.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/base.py to base.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/exceptions.py to exceptions.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/menu_pool.py to menu_pool.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/models.py to models.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/modifiers.py to modifiers.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/utils.py to utils.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templatetags/__init__.py to __init__.cpython-311.pyc byte-compiling /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/menus/templatetags/menu_tags.py to menu_tags.cpython-311.pyc writing byte-compilation script '/tmp/tmpmph79u17.py' /usr/local/bin/python3.11 /tmp/tmpmph79u17.py removing /tmp/tmpmph79u17.py running install_egg_info Copying django_cms.egg-info to /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/lib/python3.11/site-packages/django_cms-5.0.6-py3.11.egg-info running install_scripts Installing djangocms script to /wrkdirs/usr/ports/www/py-django-cms/work-py311/stage/usr/local/bin writing list of installed files to '/wrkdirs/usr/ports/www/py-django-cms/work-py311/.PLIST.pymodtmp' ====> Compressing man pages (compress-man) =========================================================================== =================================================== ===== env: 'PKG_NOTES=build_timestamp ports_top_git_hash ports_top_checkout_unclean port_git_hash port_checkout_unclean built_by' 'PKG_NOTE_build_timestamp=2026-06-06T07:53:31+0000' 'PKG_NOTE_ports_top_git_hash=a8b187544' 'PKG_NOTE_ports_top_checkout_unclean=yes' 'PKG_NOTE_port_git_hash=a8b187544' 'PKG_NOTE_port_checkout_unclean=no' 'PKG_NOTE_built_by=poudriere-git-3.4.4' NO_DEPENDS=yes USER=nobody UID=65534 GID=65534 ===> Building packages for py311-django-cms-5.0.6 ===> Building py311-django-cms-5.0.6 =========================================================================== =>> Cleaning up wrkdir ===> Cleaning for py311-django-cms-5.0.6 build of www/py-django-cms@py311 | py311-django-cms-5.0.6 ended at Sat Jun 6 16:58:51 JST 2026 build time: 00:06:48