=> Bootstrap dependency digest>=20211023: found digest-20220214 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Installing for py312-djangocms-column-2.0.0 => Generating pre-install file lists => Creating installation directories (cd /tmp/www/py-djangocms-column/work/djangocms-column-2.0.0/ && /usr/bin/env DESTDIR=/tmp/www/py-djangocms-column/work/.destdir USETOOLS=no PTHREAD_CFLAGS=\ -pthread\ PTHREAD_LDFLAGS=\ -pthread PTHREAD_LIBS= PTHREADBASE=/usr DL_CFLAGS=\ -pthread\ DL_LDFLAGS=\ -pthread DL_LIBS= PYTHON=/usr/pkg/bin/python3.12 CC=gcc CFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.12 CPPFLAGS=-I/usr/include\ -I/usr/pkg/include/python3.12 CXX=c++ CXXFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.12 COMPILER_RPATH_FLAG=-Wl,-R F77=gfortran FC=gfortran FFLAGS=-O LANG=C LC_ALL=C LC_COLLATE=C LC_CTYPE=C LC_MESSAGES=C LC_MONETARY=C LC_NUMERIC=C LC_TIME=C LDFLAGS=-Wl,-zrelro\ -L/usr/lib\ -Wl,-R/usr/lib\ -Wl,-R/usr/pkg/lib LINKER_RPATH_FLAG=-R PATH=/tmp/www/py-djangocms-column/work/.cwrapper/bin:/tmp/www/py-djangocms-column/work/.buildlink/bin:/tmp/www/py-djangocms-column/work/.tools/bin:/usr/pkg/bin:/usr/bin:/bin:/usr/pkg/bin:/usr/local/bin:/usr/pkg/bin:/usr/X11R7/bin PREFIX=/usr/pkg MAKELEVEL=0 CONFIG_SITE= PKG_SYSCONFDIR=/usr/pkg/etc CPP=cpp CXXCPP=cpp HOME=/tmp/www/py-djangocms-column/work/.home CWRAPPERS_CONFIG_DIR=/tmp/www/py-djangocms-column/work/.cwrapper/config CPP=cpp LOCALBASE=/usr/pkg X11BASE=/usr/X11R7 PKGMANDIR=man PKGINFODIR=info PKGGNUDIR=gnu/ MAKECONF=/dev/null OBJECT_FMT=ELF USETOOLS=no BSD_INSTALL_PROGRAM=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL_MAN=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL=/usr/bin/install BSD_INSTALL_PROGRAM_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_MAN_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_GAME=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 2555 BSD_INSTALL_GAME_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 664 BSD_INSTALL_GAME_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 775 INSTALL_INFO= MAKEINFO=/tmp/www/py-djangocms-column/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/www/py-djangocms-column/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/www/py-djangocms-column/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/www/py-djangocms-column/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/www/py-djangocms-column/work/.buildlink/lib/pkgconfig:/tmp/www/py-djangocms-column/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/www/py-djangocms-column/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/www/py-djangocms-column/work/.cwrapper/config /usr/pkg/bin/python3.12 setup.py "install" -c -O1 --root=/tmp/www/py-djangocms-column/work/.destdir) running install /usr/pkg/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. 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 djangocms_column.egg-info/PKG-INFO writing dependency_links to djangocms_column.egg-info/dependency_links.txt writing requirements to djangocms_column.egg-info/requires.txt writing top-level names to djangocms_column.egg-info/top_level.txt reading manifest file 'djangocms_column.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*' under directory 'djangocms_column/south_migrations' warning: no previously-included files matching '*.pyc' found under directory '*' adding license file 'LICENSE.txt' writing manifest file 'djangocms_column.egg-info/SOURCES.txt' /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.cmn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.cmn.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.es_BO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.es_BO.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.es_DO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.es_DO.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.gu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.gu.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ko_KR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ko_KR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ku_IQ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ku_IQ.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.mn_MN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.mn_MN.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.mt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.mt.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.no.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.no.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.sl_SI.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.sl_SI.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.sq_AL.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.sq_AL.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.th_TH.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.th_TH.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.tlh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.tlh.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_column.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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'djangocms_column.templates.cms.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_column.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 'djangocms_column.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 'djangocms_column.templates.cms.plugins' to be distributed and are already explicitly excluding 'djangocms_column.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) running install_lib creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column copying build/lib/djangocms_column/__init__.py -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column copying build/lib/djangocms_column/cms_plugins.py -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column copying build/lib/djangocms_column/forms.py -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column copying build/lib/djangocms_column/models.py -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/migrations copying build/lib/djangocms_column/migrations/0001_initial.py -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/migrations copying build/lib/djangocms_column/migrations/0002_auto_20160915_0818.py -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/migrations copying build/lib/djangocms_column/migrations/__init__.py -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/migrations creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/af creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/af/LC_MESSAGES copying build/lib/djangocms_column/locale/af/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/af/LC_MESSAGES copying build/lib/djangocms_column/locale/af/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/af/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ar creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ar/LC_MESSAGES copying build/lib/djangocms_column/locale/ar/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ar/LC_MESSAGES copying build/lib/djangocms_column/locale/ar/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ar/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/be creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/be/LC_MESSAGES copying build/lib/djangocms_column/locale/be/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/be/LC_MESSAGES copying build/lib/djangocms_column/locale/be/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/be/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/bg creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/bg/LC_MESSAGES copying build/lib/djangocms_column/locale/bg/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/bg/LC_MESSAGES copying build/lib/djangocms_column/locale/bg/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/bg/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/bn creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/bn/LC_MESSAGES copying build/lib/djangocms_column/locale/bn/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/bn/LC_MESSAGES copying build/lib/djangocms_column/locale/bn/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/bn/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ca creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ca/LC_MESSAGES copying build/lib/djangocms_column/locale/ca/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ca/LC_MESSAGES copying build/lib/djangocms_column/locale/ca/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ca/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cmn creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cmn/LC_MESSAGES copying build/lib/djangocms_column/locale/cmn/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cmn/LC_MESSAGES copying build/lib/djangocms_column/locale/cmn/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cmn/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cs creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cs/LC_MESSAGES copying build/lib/djangocms_column/locale/cs/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cs/LC_MESSAGES copying build/lib/djangocms_column/locale/cs/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cs/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cy creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cy/LC_MESSAGES copying build/lib/djangocms_column/locale/cy/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cy/LC_MESSAGES copying build/lib/djangocms_column/locale/cy/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/cy/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/da creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/da/LC_MESSAGES copying build/lib/djangocms_column/locale/da/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/da/LC_MESSAGES copying build/lib/djangocms_column/locale/da/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/da/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/de creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/de/LC_MESSAGES copying build/lib/djangocms_column/locale/de/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/de/LC_MESSAGES copying build/lib/djangocms_column/locale/de/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/de/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/el creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/el/LC_MESSAGES copying build/lib/djangocms_column/locale/el/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/el/LC_MESSAGES copying build/lib/djangocms_column/locale/el/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/el/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/en creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/en/LC_MESSAGES copying build/lib/djangocms_column/locale/en/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/en/LC_MESSAGES copying build/lib/djangocms_column/locale/en/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/en/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es/LC_MESSAGES copying build/lib/djangocms_column/locale/es/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es/LC_MESSAGES copying build/lib/djangocms_column/locale/es/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_AR creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_AR/LC_MESSAGES copying build/lib/djangocms_column/locale/es_AR/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_AR/LC_MESSAGES copying build/lib/djangocms_column/locale/es_AR/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_AR/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_BO creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_BO/LC_MESSAGES copying build/lib/djangocms_column/locale/es_BO/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_BO/LC_MESSAGES copying build/lib/djangocms_column/locale/es_BO/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_BO/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_DO creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_DO/LC_MESSAGES copying build/lib/djangocms_column/locale/es_DO/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_DO/LC_MESSAGES copying build/lib/djangocms_column/locale/es_DO/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/es_DO/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/et creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/et/LC_MESSAGES copying build/lib/djangocms_column/locale/et/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/et/LC_MESSAGES copying build/lib/djangocms_column/locale/et/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/et/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/eu creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/eu/LC_MESSAGES copying build/lib/djangocms_column/locale/eu/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/eu/LC_MESSAGES copying build/lib/djangocms_column/locale/eu/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/eu/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fa creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fa/LC_MESSAGES copying build/lib/djangocms_column/locale/fa/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fa/LC_MESSAGES copying build/lib/djangocms_column/locale/fa/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fa/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fi creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fi/LC_MESSAGES copying build/lib/djangocms_column/locale/fi/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fi/LC_MESSAGES copying build/lib/djangocms_column/locale/fi/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fi/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fr creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fr/LC_MESSAGES copying build/lib/djangocms_column/locale/fr/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fr/LC_MESSAGES copying build/lib/djangocms_column/locale/fr/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/fr/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ga creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ga/LC_MESSAGES copying build/lib/djangocms_column/locale/ga/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ga/LC_MESSAGES copying build/lib/djangocms_column/locale/ga/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ga/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/gl creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/gl/LC_MESSAGES copying build/lib/djangocms_column/locale/gl/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/gl/LC_MESSAGES copying build/lib/djangocms_column/locale/gl/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/gl/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/gu creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/gu/LC_MESSAGES copying build/lib/djangocms_column/locale/gu/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/gu/LC_MESSAGES copying build/lib/djangocms_column/locale/gu/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/gu/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/he creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/he/LC_MESSAGES copying build/lib/djangocms_column/locale/he/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/he/LC_MESSAGES copying build/lib/djangocms_column/locale/he/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/he/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hi creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hi/LC_MESSAGES copying build/lib/djangocms_column/locale/hi/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hi/LC_MESSAGES copying build/lib/djangocms_column/locale/hi/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hi/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hr creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hr/LC_MESSAGES copying build/lib/djangocms_column/locale/hr/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hr/LC_MESSAGES copying build/lib/djangocms_column/locale/hr/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hr/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hu creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hu/LC_MESSAGES copying build/lib/djangocms_column/locale/hu/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hu/LC_MESSAGES copying build/lib/djangocms_column/locale/hu/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/hu/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/id creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/id/LC_MESSAGES copying build/lib/djangocms_column/locale/id/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/id/LC_MESSAGES copying build/lib/djangocms_column/locale/id/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/id/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/is creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/is/LC_MESSAGES copying build/lib/djangocms_column/locale/is/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/is/LC_MESSAGES copying build/lib/djangocms_column/locale/is/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/is/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/is_IS creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/is_IS/LC_MESSAGES copying build/lib/djangocms_column/locale/is_IS/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/is_IS/LC_MESSAGES copying build/lib/djangocms_column/locale/is_IS/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/is_IS/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/it creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/it/LC_MESSAGES copying build/lib/djangocms_column/locale/it/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/it/LC_MESSAGES copying build/lib/djangocms_column/locale/it/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/it/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ja creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ja/LC_MESSAGES copying build/lib/djangocms_column/locale/ja/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ja/LC_MESSAGES copying build/lib/djangocms_column/locale/ja/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ja/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ka creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ka/LC_MESSAGES copying build/lib/djangocms_column/locale/ka/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ka/LC_MESSAGES copying build/lib/djangocms_column/locale/ka/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ka/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/kk creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/kk/LC_MESSAGES copying build/lib/djangocms_column/locale/kk/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/kk/LC_MESSAGES copying build/lib/djangocms_column/locale/kk/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/kk/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/km creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/km/LC_MESSAGES copying build/lib/djangocms_column/locale/km/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/km/LC_MESSAGES copying build/lib/djangocms_column/locale/km/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/km/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ko creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ko/LC_MESSAGES copying build/lib/djangocms_column/locale/ko/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ko/LC_MESSAGES copying build/lib/djangocms_column/locale/ko/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ko/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ko_KR creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ko_KR/LC_MESSAGES copying build/lib/djangocms_column/locale/ko_KR/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ko_KR/LC_MESSAGES copying build/lib/djangocms_column/locale/ko_KR/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ko_KR/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ku_IQ creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ku_IQ/LC_MESSAGES copying build/lib/djangocms_column/locale/ku_IQ/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ku_IQ/LC_MESSAGES copying build/lib/djangocms_column/locale/ku_IQ/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ku_IQ/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/lt creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/lt/LC_MESSAGES copying build/lib/djangocms_column/locale/lt/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/lt/LC_MESSAGES copying build/lib/djangocms_column/locale/lt/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/lt/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/lv creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/lv/LC_MESSAGES copying build/lib/djangocms_column/locale/lv/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/lv/LC_MESSAGES copying build/lib/djangocms_column/locale/lv/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/lv/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mn creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mn/LC_MESSAGES copying build/lib/djangocms_column/locale/mn/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mn/LC_MESSAGES copying build/lib/djangocms_column/locale/mn/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mn/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mn_MN creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mn_MN/LC_MESSAGES copying build/lib/djangocms_column/locale/mn_MN/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mn_MN/LC_MESSAGES copying build/lib/djangocms_column/locale/mn_MN/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mn_MN/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mt creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mt/LC_MESSAGES copying build/lib/djangocms_column/locale/mt/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mt/LC_MESSAGES copying build/lib/djangocms_column/locale/mt/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/mt/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/nb creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/nb/LC_MESSAGES copying build/lib/djangocms_column/locale/nb/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/nb/LC_MESSAGES copying build/lib/djangocms_column/locale/nb/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/nb/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/nl creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/nl/LC_MESSAGES copying build/lib/djangocms_column/locale/nl/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/nl/LC_MESSAGES copying build/lib/djangocms_column/locale/nl/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/nl/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/no creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/no/LC_MESSAGES copying build/lib/djangocms_column/locale/no/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/no/LC_MESSAGES copying build/lib/djangocms_column/locale/no/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/no/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pl creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pl/LC_MESSAGES copying build/lib/djangocms_column/locale/pl/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pl/LC_MESSAGES copying build/lib/djangocms_column/locale/pl/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pl/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pt creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pt/LC_MESSAGES copying build/lib/djangocms_column/locale/pt/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pt/LC_MESSAGES copying build/lib/djangocms_column/locale/pt/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pt/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pt_BR creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pt_BR/LC_MESSAGES copying build/lib/djangocms_column/locale/pt_BR/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pt_BR/LC_MESSAGES copying build/lib/djangocms_column/locale/pt_BR/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/pt_BR/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ro creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ro/LC_MESSAGES copying build/lib/djangocms_column/locale/ro/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ro/LC_MESSAGES copying build/lib/djangocms_column/locale/ro/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ro/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ru creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ru/LC_MESSAGES copying build/lib/djangocms_column/locale/ru/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ru/LC_MESSAGES copying build/lib/djangocms_column/locale/ru/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ru/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sk creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sk/LC_MESSAGES copying build/lib/djangocms_column/locale/sk/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sk/LC_MESSAGES copying build/lib/djangocms_column/locale/sk/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sk/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sl creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sl/LC_MESSAGES copying build/lib/djangocms_column/locale/sl/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sl/LC_MESSAGES copying build/lib/djangocms_column/locale/sl/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sl/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sl_SI creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sl_SI/LC_MESSAGES copying build/lib/djangocms_column/locale/sl_SI/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sl_SI/LC_MESSAGES copying build/lib/djangocms_column/locale/sl_SI/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sl_SI/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sq creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sq/LC_MESSAGES copying build/lib/djangocms_column/locale/sq/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sq/LC_MESSAGES copying build/lib/djangocms_column/locale/sq/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sq/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sq_AL creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sq_AL/LC_MESSAGES copying build/lib/djangocms_column/locale/sq_AL/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sq_AL/LC_MESSAGES copying build/lib/djangocms_column/locale/sq_AL/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sq_AL/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sr creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sr/LC_MESSAGES copying build/lib/djangocms_column/locale/sr/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sr/LC_MESSAGES copying build/lib/djangocms_column/locale/sr/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sr/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sr@latin creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sr@latin/LC_MESSAGES copying build/lib/djangocms_column/locale/sr@latin/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sr@latin/LC_MESSAGES copying build/lib/djangocms_column/locale/sr@latin/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sr@latin/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sv creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sv/LC_MESSAGES copying build/lib/djangocms_column/locale/sv/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sv/LC_MESSAGES copying build/lib/djangocms_column/locale/sv/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/sv/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ta creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ta/LC_MESSAGES copying build/lib/djangocms_column/locale/ta/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ta/LC_MESSAGES copying build/lib/djangocms_column/locale/ta/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ta/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/th creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/th/LC_MESSAGES copying build/lib/djangocms_column/locale/th/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/th/LC_MESSAGES copying build/lib/djangocms_column/locale/th/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/th/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/th_TH creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/th_TH/LC_MESSAGES copying build/lib/djangocms_column/locale/th_TH/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/th_TH/LC_MESSAGES copying build/lib/djangocms_column/locale/th_TH/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/th_TH/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/tlh creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/tlh/LC_MESSAGES copying build/lib/djangocms_column/locale/tlh/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/tlh/LC_MESSAGES copying build/lib/djangocms_column/locale/tlh/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/tlh/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/tr creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/tr/LC_MESSAGES copying build/lib/djangocms_column/locale/tr/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/tr/LC_MESSAGES copying build/lib/djangocms_column/locale/tr/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/tr/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ug creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ug/LC_MESSAGES copying build/lib/djangocms_column/locale/ug/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ug/LC_MESSAGES copying build/lib/djangocms_column/locale/ug/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ug/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/uk creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/uk/LC_MESSAGES copying build/lib/djangocms_column/locale/uk/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/uk/LC_MESSAGES copying build/lib/djangocms_column/locale/uk/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/uk/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ur creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ur/LC_MESSAGES copying build/lib/djangocms_column/locale/ur/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ur/LC_MESSAGES copying build/lib/djangocms_column/locale/ur/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/ur/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/vi creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/vi/LC_MESSAGES copying build/lib/djangocms_column/locale/vi/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/vi/LC_MESSAGES copying build/lib/djangocms_column/locale/vi/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/vi/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/vi_VN creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/vi_VN/LC_MESSAGES copying build/lib/djangocms_column/locale/vi_VN/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/vi_VN/LC_MESSAGES copying build/lib/djangocms_column/locale/vi_VN/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/vi_VN/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh/LC_MESSAGES copying build/lib/djangocms_column/locale/zh/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh/LC_MESSAGES copying build/lib/djangocms_column/locale/zh/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh_CN creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh_CN/LC_MESSAGES copying build/lib/djangocms_column/locale/zh_CN/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh_CN/LC_MESSAGES copying build/lib/djangocms_column/locale/zh_CN/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh_CN/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh_TW creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh_TW/LC_MESSAGES copying build/lib/djangocms_column/locale/zh_TW/LC_MESSAGES/django.mo -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh_TW/LC_MESSAGES copying build/lib/djangocms_column/locale/zh_TW/LC_MESSAGES/django.po -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/locale/zh_TW/LC_MESSAGES creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/templates creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/templates/cms creating /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/templates/cms/plugins copying build/lib/djangocms_column/templates/cms/plugins/column.html -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/templates/cms/plugins copying build/lib/djangocms_column/templates/cms/plugins/column_edit.html -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/templates/cms/plugins copying build/lib/djangocms_column/templates/cms/plugins/multi_column.html -> /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/templates/cms/plugins byte-compiling /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/__init__.py to __init__.cpython-312.pyc byte-compiling /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/cms_plugins.py to cms_plugins.cpython-312.pyc byte-compiling /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/forms.py to forms.cpython-312.pyc byte-compiling /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/models.py to models.cpython-312.pyc byte-compiling /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/migrations/0001_initial.py to 0001_initial.cpython-312.pyc byte-compiling /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/migrations/0002_auto_20160915_0818.py to 0002_auto_20160915_0818.cpython-312.pyc byte-compiling /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column/migrations/__init__.py to __init__.cpython-312.pyc writing byte-compilation script '/tmp/tmpwa_zv2wu.py' /usr/pkg/bin/python3.12 /tmp/tmpwa_zv2wu.py removing /tmp/tmpwa_zv2wu.py running install_egg_info Copying djangocms_column.egg-info to /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column-2.0.0-py3.12.egg-info running install_scripts => Automatic manual page handling => Generating post-install file lists if test -d "/tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column-2.0.0-py3.12.egg-info"; then /usr/bin/find /tmp/www/py-djangocms-column/work/.destdir/usr/pkg/lib/python3.12/site-packages/djangocms_column-2.0.0-py3.12.egg-info -type f -exec /bin/chmod 644 '{}' ';' ; fi => Checking file-check results for py312-djangocms-column-2.0.0 => Checking for non-existent script interpreters in py312-djangocms-column-2.0.0 => Checking file permissions in py312-djangocms-column-2.0.0 warning: /tmp: group permissions (rwx) are higher than owner permissions (--x). warning: /tmp: group-writable directory. error: /tmp: world-writable directory. 1 errors and 2 warnings. *** Error code 1 Stop. make[1]: stopped in /amd/pkgsrc/CHROOT/P/pkgsrc/www/py-djangocms-column *** Error code 1 Stop. make: stopped in /amd/pkgsrc/CHROOT/P/pkgsrc/www/py-djangocms-column