=> 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'. ===> Building for py310-djangocms-link-3.1.1 (cd /tmp/www/py-djangocms-link/work/djangocms-link-3.1.1/ && /usr/bin/env 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.10 CC=gcc CFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.10 CPPFLAGS=-I/usr/include\ -I/usr/pkg/include/python3.10 CXX=c++ CXXFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.10 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-link/work/.cwrapper/bin:/tmp/www/py-djangocms-link/work/.buildlink/bin:/tmp/www/py-djangocms-link/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-link/work/.home CWRAPPERS_CONFIG_DIR=/tmp/www/py-djangocms-link/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-link/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/www/py-djangocms-link/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/www/py-djangocms-link/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/www/py-djangocms-link/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/www/py-djangocms-link/work/.buildlink/lib/pkgconfig:/tmp/www/py-djangocms-link/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/www/py-djangocms-link/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/www/py-djangocms-link/work/.cwrapper/config /usr/pkg/bin/python3.10 setup.py build -j4) running build running build_py creating build creating build/lib creating build/lib/djangocms_link copying djangocms_link/__init__.py -> build/lib/djangocms_link copying djangocms_link/cms_plugins.py -> build/lib/djangocms_link copying djangocms_link/fields.py -> build/lib/djangocms_link copying djangocms_link/fields_select2.py -> build/lib/djangocms_link copying djangocms_link/forms.py -> build/lib/djangocms_link copying djangocms_link/models.py -> build/lib/djangocms_link copying djangocms_link/validators.py -> build/lib/djangocms_link creating build/lib/djangocms_link/migrations copying djangocms_link/migrations/0001_initial.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0002_auto_20140929_1705.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0003_auto_20150212_1310.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0004_auto_20150708_1133.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0005_auto_20151003_1710.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0006_remove_related_name_for_cmsplugin_ptr.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0007_set_related_name_for_cmsplugin_ptr.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0008_link_attributes.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0009_auto_20160705_1344.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0010_adapted_fields.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0011_fixed_null_values.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0012_removed_null.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0013_fix_hostname.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0014_link_file_link.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0015_auto_20190621_0407.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/0016_alter_link_cmsplugin_ptr.py -> build/lib/djangocms_link/migrations copying djangocms_link/migrations/__init__.py -> build/lib/djangocms_link/migrations running egg_info writing djangocms_link.egg-info/PKG-INFO writing dependency_links to djangocms_link.egg-info/dependency_links.txt writing requirements to djangocms_link.egg-info/requires.txt writing top-level names to djangocms_link.egg-info/top_level.txt reading manifest file 'djangocms_link.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '*.py[co]' found under directory '*' adding license file 'LICENSE' writing manifest file 'djangocms_link.egg-info/SOURCES.txt' /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.cmn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.cmn.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.cs_CZ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.cs_CZ.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.cs_CZ.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.cs_CZ.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.cs_CZ.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.en_HK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.en_HK.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.en_HK.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.en_HK.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.en_HK.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.en_US.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.en_US.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.en_US.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.en_US.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.en_US.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.es_BO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.es_BO.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.es_DO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.es_DO.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.fa_IR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.fa_IR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.fa_IR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.fa_IR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.fa_IR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.fi_FI.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.fi_FI.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.fi_FI.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.fi_FI.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.fi_FI.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.fr_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.fr_CA.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.fr_CA.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.fr_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.fr_CA.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.fr_FR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.fr_FR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.fr_FR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.fr_FR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.fr_FR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.gu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.gu.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.is_IS.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.is_IS.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ko_KR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ko_KR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ku_IQ.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ku_IQ.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.lt_LT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.lt_LT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.lt_LT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.lt_LT.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.lt_LT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.mn_MN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.mn_MN.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.ms.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.ms.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.mt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.mt.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.no.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.no.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.pap.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.pap.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.pap.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.pap.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.pap.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.pt_PT.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.pt_PT.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.pt_PT.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ro_RO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.ro_RO.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.ro_RO.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.ro_RO.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.ro_RO.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.sk_SK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.sk_SK.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.sk_SK.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.sk_SK.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.sk_SK.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.sl_SI.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.sl_SI.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.sq_AL.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.sq_AL.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.th_TH.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.th_TH.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.tlh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.tlh.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.tr_TR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.locale.tr_TR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'djangocms_link.locale.tr_TR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'djangocms_link.locale.tr_TR.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.locale.tr_TR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.vi_VN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.vi_VN.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.zh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.zh.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.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_link.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_link.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'djangocms_link.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.10/site-packages/setuptools/command/build_py.py:204: _Warning: Package 'djangocms_link.templates.djangocms_link.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'djangocms_link.templates.djangocms_link.default' as an importable package[^1], but it 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_link.templates.djangocms_link.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can 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_link.templates.djangocms_link.default' to be distributed and are already explicitly excluding 'djangocms_link.templates.djangocms_link.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/djangocms_link/locale creating build/lib/djangocms_link/locale/af creating build/lib/djangocms_link/locale/af/LC_MESSAGES copying djangocms_link/locale/af/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/af/LC_MESSAGES copying djangocms_link/locale/af/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/af/LC_MESSAGES creating build/lib/djangocms_link/locale/ar creating build/lib/djangocms_link/locale/ar/LC_MESSAGES copying djangocms_link/locale/ar/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ar/LC_MESSAGES copying djangocms_link/locale/ar/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ar/LC_MESSAGES creating build/lib/djangocms_link/locale/be creating build/lib/djangocms_link/locale/be/LC_MESSAGES copying djangocms_link/locale/be/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/be/LC_MESSAGES copying djangocms_link/locale/be/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/be/LC_MESSAGES creating build/lib/djangocms_link/locale/bg creating build/lib/djangocms_link/locale/bg/LC_MESSAGES copying djangocms_link/locale/bg/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/bg/LC_MESSAGES copying djangocms_link/locale/bg/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/bg/LC_MESSAGES creating build/lib/djangocms_link/locale/bn creating build/lib/djangocms_link/locale/bn/LC_MESSAGES copying djangocms_link/locale/bn/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/bn/LC_MESSAGES copying djangocms_link/locale/bn/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/bn/LC_MESSAGES creating build/lib/djangocms_link/locale/ca creating build/lib/djangocms_link/locale/ca/LC_MESSAGES copying djangocms_link/locale/ca/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ca/LC_MESSAGES copying djangocms_link/locale/ca/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ca/LC_MESSAGES creating build/lib/djangocms_link/locale/cmn creating build/lib/djangocms_link/locale/cmn/LC_MESSAGES copying djangocms_link/locale/cmn/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/cmn/LC_MESSAGES copying djangocms_link/locale/cmn/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/cmn/LC_MESSAGES creating build/lib/djangocms_link/locale/cs creating build/lib/djangocms_link/locale/cs/LC_MESSAGES copying djangocms_link/locale/cs/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/cs/LC_MESSAGES copying djangocms_link/locale/cs/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/cs/LC_MESSAGES creating build/lib/djangocms_link/locale/cs_CZ creating build/lib/djangocms_link/locale/cs_CZ/LC_MESSAGES copying djangocms_link/locale/cs_CZ/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/cs_CZ/LC_MESSAGES copying djangocms_link/locale/cs_CZ/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/cs_CZ/LC_MESSAGES creating build/lib/djangocms_link/locale/cy creating build/lib/djangocms_link/locale/cy/LC_MESSAGES copying djangocms_link/locale/cy/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/cy/LC_MESSAGES copying djangocms_link/locale/cy/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/cy/LC_MESSAGES creating build/lib/djangocms_link/locale/da creating build/lib/djangocms_link/locale/da/LC_MESSAGES copying djangocms_link/locale/da/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/da/LC_MESSAGES copying djangocms_link/locale/da/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/da/LC_MESSAGES creating build/lib/djangocms_link/locale/de creating build/lib/djangocms_link/locale/de/LC_MESSAGES copying djangocms_link/locale/de/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/de/LC_MESSAGES copying djangocms_link/locale/de/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/de/LC_MESSAGES creating build/lib/djangocms_link/locale/el creating build/lib/djangocms_link/locale/el/LC_MESSAGES copying djangocms_link/locale/el/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/el/LC_MESSAGES copying djangocms_link/locale/el/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/el/LC_MESSAGES creating build/lib/djangocms_link/locale/en creating build/lib/djangocms_link/locale/en/LC_MESSAGES copying djangocms_link/locale/en/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/en/LC_MESSAGES copying djangocms_link/locale/en/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/en/LC_MESSAGES creating build/lib/djangocms_link/locale/en_GB creating build/lib/djangocms_link/locale/en_GB/LC_MESSAGES copying djangocms_link/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/en_GB/LC_MESSAGES copying djangocms_link/locale/en_GB/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/en_GB/LC_MESSAGES creating build/lib/djangocms_link/locale/en_HK creating build/lib/djangocms_link/locale/en_HK/LC_MESSAGES copying djangocms_link/locale/en_HK/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/en_HK/LC_MESSAGES copying djangocms_link/locale/en_HK/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/en_HK/LC_MESSAGES creating build/lib/djangocms_link/locale/en_US creating build/lib/djangocms_link/locale/en_US/LC_MESSAGES copying djangocms_link/locale/en_US/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/en_US/LC_MESSAGES copying djangocms_link/locale/en_US/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/en_US/LC_MESSAGES creating build/lib/djangocms_link/locale/eo creating build/lib/djangocms_link/locale/eo/LC_MESSAGES copying djangocms_link/locale/eo/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/eo/LC_MESSAGES copying djangocms_link/locale/eo/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/eo/LC_MESSAGES creating build/lib/djangocms_link/locale/es creating build/lib/djangocms_link/locale/es/LC_MESSAGES copying djangocms_link/locale/es/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/es/LC_MESSAGES copying djangocms_link/locale/es/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/es/LC_MESSAGES creating build/lib/djangocms_link/locale/es_AR creating build/lib/djangocms_link/locale/es_AR/LC_MESSAGES copying djangocms_link/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/es_AR/LC_MESSAGES copying djangocms_link/locale/es_AR/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/es_AR/LC_MESSAGES creating build/lib/djangocms_link/locale/es_BO creating build/lib/djangocms_link/locale/es_BO/LC_MESSAGES copying djangocms_link/locale/es_BO/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/es_BO/LC_MESSAGES copying djangocms_link/locale/es_BO/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/es_BO/LC_MESSAGES creating build/lib/djangocms_link/locale/es_DO creating build/lib/djangocms_link/locale/es_DO/LC_MESSAGES copying djangocms_link/locale/es_DO/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/es_DO/LC_MESSAGES copying djangocms_link/locale/es_DO/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/es_DO/LC_MESSAGES creating build/lib/djangocms_link/locale/et creating build/lib/djangocms_link/locale/et/LC_MESSAGES copying djangocms_link/locale/et/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/et/LC_MESSAGES copying djangocms_link/locale/et/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/et/LC_MESSAGES creating build/lib/djangocms_link/locale/eu creating build/lib/djangocms_link/locale/eu/LC_MESSAGES copying djangocms_link/locale/eu/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/eu/LC_MESSAGES copying djangocms_link/locale/eu/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/eu/LC_MESSAGES creating build/lib/djangocms_link/locale/fa creating build/lib/djangocms_link/locale/fa/LC_MESSAGES copying djangocms_link/locale/fa/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/fa/LC_MESSAGES copying djangocms_link/locale/fa/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/fa/LC_MESSAGES creating build/lib/djangocms_link/locale/fa_IR creating build/lib/djangocms_link/locale/fa_IR/LC_MESSAGES copying djangocms_link/locale/fa_IR/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/fa_IR/LC_MESSAGES copying djangocms_link/locale/fa_IR/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/fa_IR/LC_MESSAGES creating build/lib/djangocms_link/locale/fi creating build/lib/djangocms_link/locale/fi/LC_MESSAGES copying djangocms_link/locale/fi/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/fi/LC_MESSAGES copying djangocms_link/locale/fi/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/fi/LC_MESSAGES creating build/lib/djangocms_link/locale/fi_FI creating build/lib/djangocms_link/locale/fi_FI/LC_MESSAGES copying djangocms_link/locale/fi_FI/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/fi_FI/LC_MESSAGES copying djangocms_link/locale/fi_FI/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/fi_FI/LC_MESSAGES creating build/lib/djangocms_link/locale/fr creating build/lib/djangocms_link/locale/fr/LC_MESSAGES copying djangocms_link/locale/fr/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/fr/LC_MESSAGES copying djangocms_link/locale/fr/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/fr/LC_MESSAGES creating build/lib/djangocms_link/locale/fr_CA creating build/lib/djangocms_link/locale/fr_CA/LC_MESSAGES copying djangocms_link/locale/fr_CA/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/fr_CA/LC_MESSAGES copying djangocms_link/locale/fr_CA/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/fr_CA/LC_MESSAGES creating build/lib/djangocms_link/locale/fr_FR creating build/lib/djangocms_link/locale/fr_FR/LC_MESSAGES copying djangocms_link/locale/fr_FR/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/fr_FR/LC_MESSAGES copying djangocms_link/locale/fr_FR/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/fr_FR/LC_MESSAGES creating build/lib/djangocms_link/locale/ga creating build/lib/djangocms_link/locale/ga/LC_MESSAGES copying djangocms_link/locale/ga/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ga/LC_MESSAGES copying djangocms_link/locale/ga/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ga/LC_MESSAGES creating build/lib/djangocms_link/locale/gl creating build/lib/djangocms_link/locale/gl/LC_MESSAGES copying djangocms_link/locale/gl/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/gl/LC_MESSAGES copying djangocms_link/locale/gl/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/gl/LC_MESSAGES creating build/lib/djangocms_link/locale/gu creating build/lib/djangocms_link/locale/gu/LC_MESSAGES copying djangocms_link/locale/gu/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/gu/LC_MESSAGES copying djangocms_link/locale/gu/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/gu/LC_MESSAGES creating build/lib/djangocms_link/locale/he creating build/lib/djangocms_link/locale/he/LC_MESSAGES copying djangocms_link/locale/he/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/he/LC_MESSAGES copying djangocms_link/locale/he/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/he/LC_MESSAGES creating build/lib/djangocms_link/locale/hi creating build/lib/djangocms_link/locale/hi/LC_MESSAGES copying djangocms_link/locale/hi/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/hi/LC_MESSAGES copying djangocms_link/locale/hi/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/hi/LC_MESSAGES creating build/lib/djangocms_link/locale/hr creating build/lib/djangocms_link/locale/hr/LC_MESSAGES copying djangocms_link/locale/hr/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/hr/LC_MESSAGES copying djangocms_link/locale/hr/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/hr/LC_MESSAGES creating build/lib/djangocms_link/locale/hu creating build/lib/djangocms_link/locale/hu/LC_MESSAGES copying djangocms_link/locale/hu/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/hu/LC_MESSAGES copying djangocms_link/locale/hu/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/hu/LC_MESSAGES creating build/lib/djangocms_link/locale/id creating build/lib/djangocms_link/locale/id/LC_MESSAGES copying djangocms_link/locale/id/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/id/LC_MESSAGES copying djangocms_link/locale/id/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/id/LC_MESSAGES creating build/lib/djangocms_link/locale/is creating build/lib/djangocms_link/locale/is/LC_MESSAGES copying djangocms_link/locale/is/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/is/LC_MESSAGES copying djangocms_link/locale/is/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/is/LC_MESSAGES creating build/lib/djangocms_link/locale/is_IS creating build/lib/djangocms_link/locale/is_IS/LC_MESSAGES copying djangocms_link/locale/is_IS/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/is_IS/LC_MESSAGES copying djangocms_link/locale/is_IS/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/is_IS/LC_MESSAGES creating build/lib/djangocms_link/locale/it creating build/lib/djangocms_link/locale/it/LC_MESSAGES copying djangocms_link/locale/it/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/it/LC_MESSAGES copying djangocms_link/locale/it/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/it/LC_MESSAGES creating build/lib/djangocms_link/locale/ja creating build/lib/djangocms_link/locale/ja/LC_MESSAGES copying djangocms_link/locale/ja/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ja/LC_MESSAGES copying djangocms_link/locale/ja/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ja/LC_MESSAGES creating build/lib/djangocms_link/locale/ka creating build/lib/djangocms_link/locale/ka/LC_MESSAGES copying djangocms_link/locale/ka/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ka/LC_MESSAGES copying djangocms_link/locale/ka/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ka/LC_MESSAGES creating build/lib/djangocms_link/locale/kk creating build/lib/djangocms_link/locale/kk/LC_MESSAGES copying djangocms_link/locale/kk/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/kk/LC_MESSAGES copying djangocms_link/locale/kk/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/kk/LC_MESSAGES creating build/lib/djangocms_link/locale/km creating build/lib/djangocms_link/locale/km/LC_MESSAGES copying djangocms_link/locale/km/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/km/LC_MESSAGES copying djangocms_link/locale/km/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/km/LC_MESSAGES creating build/lib/djangocms_link/locale/ko creating build/lib/djangocms_link/locale/ko/LC_MESSAGES copying djangocms_link/locale/ko/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ko/LC_MESSAGES copying djangocms_link/locale/ko/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ko/LC_MESSAGES creating build/lib/djangocms_link/locale/ko_KR creating build/lib/djangocms_link/locale/ko_KR/LC_MESSAGES copying djangocms_link/locale/ko_KR/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ko_KR/LC_MESSAGES copying djangocms_link/locale/ko_KR/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ko_KR/LC_MESSAGES creating build/lib/djangocms_link/locale/ku_IQ creating build/lib/djangocms_link/locale/ku_IQ/LC_MESSAGES copying djangocms_link/locale/ku_IQ/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ku_IQ/LC_MESSAGES copying djangocms_link/locale/ku_IQ/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ku_IQ/LC_MESSAGES creating build/lib/djangocms_link/locale/lt creating build/lib/djangocms_link/locale/lt/LC_MESSAGES copying djangocms_link/locale/lt/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/lt/LC_MESSAGES copying djangocms_link/locale/lt/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/lt/LC_MESSAGES creating build/lib/djangocms_link/locale/lt_LT creating build/lib/djangocms_link/locale/lt_LT/LC_MESSAGES copying djangocms_link/locale/lt_LT/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/lt_LT/LC_MESSAGES copying djangocms_link/locale/lt_LT/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/lt_LT/LC_MESSAGES creating build/lib/djangocms_link/locale/lv creating build/lib/djangocms_link/locale/lv/LC_MESSAGES copying djangocms_link/locale/lv/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/lv/LC_MESSAGES copying djangocms_link/locale/lv/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/lv/LC_MESSAGES creating build/lib/djangocms_link/locale/mn creating build/lib/djangocms_link/locale/mn/LC_MESSAGES copying djangocms_link/locale/mn/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/mn/LC_MESSAGES copying djangocms_link/locale/mn/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/mn/LC_MESSAGES creating build/lib/djangocms_link/locale/mn_MN creating build/lib/djangocms_link/locale/mn_MN/LC_MESSAGES copying djangocms_link/locale/mn_MN/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/mn_MN/LC_MESSAGES copying djangocms_link/locale/mn_MN/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/mn_MN/LC_MESSAGES creating build/lib/djangocms_link/locale/ms creating build/lib/djangocms_link/locale/ms/LC_MESSAGES copying djangocms_link/locale/ms/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ms/LC_MESSAGES copying djangocms_link/locale/ms/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ms/LC_MESSAGES creating build/lib/djangocms_link/locale/mt creating build/lib/djangocms_link/locale/mt/LC_MESSAGES copying djangocms_link/locale/mt/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/mt/LC_MESSAGES copying djangocms_link/locale/mt/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/mt/LC_MESSAGES creating build/lib/djangocms_link/locale/nb creating build/lib/djangocms_link/locale/nb/LC_MESSAGES copying djangocms_link/locale/nb/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/nb/LC_MESSAGES copying djangocms_link/locale/nb/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/nb/LC_MESSAGES creating build/lib/djangocms_link/locale/nl creating build/lib/djangocms_link/locale/nl/LC_MESSAGES copying djangocms_link/locale/nl/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/nl/LC_MESSAGES copying djangocms_link/locale/nl/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/nl/LC_MESSAGES creating build/lib/djangocms_link/locale/no creating build/lib/djangocms_link/locale/no/LC_MESSAGES copying djangocms_link/locale/no/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/no/LC_MESSAGES copying djangocms_link/locale/no/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/no/LC_MESSAGES creating build/lib/djangocms_link/locale/pap creating build/lib/djangocms_link/locale/pap/LC_MESSAGES copying djangocms_link/locale/pap/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/pap/LC_MESSAGES copying djangocms_link/locale/pap/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/pap/LC_MESSAGES creating build/lib/djangocms_link/locale/pl creating build/lib/djangocms_link/locale/pl/LC_MESSAGES copying djangocms_link/locale/pl/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/pl/LC_MESSAGES copying djangocms_link/locale/pl/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/pl/LC_MESSAGES creating build/lib/djangocms_link/locale/pt creating build/lib/djangocms_link/locale/pt/LC_MESSAGES copying djangocms_link/locale/pt/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/pt/LC_MESSAGES copying djangocms_link/locale/pt/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/pt/LC_MESSAGES creating build/lib/djangocms_link/locale/pt_BR creating build/lib/djangocms_link/locale/pt_BR/LC_MESSAGES copying djangocms_link/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/pt_BR/LC_MESSAGES copying djangocms_link/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/pt_BR/LC_MESSAGES creating build/lib/djangocms_link/locale/pt_PT creating build/lib/djangocms_link/locale/pt_PT/LC_MESSAGES copying djangocms_link/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/pt_PT/LC_MESSAGES copying djangocms_link/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/pt_PT/LC_MESSAGES creating build/lib/djangocms_link/locale/ro creating build/lib/djangocms_link/locale/ro/LC_MESSAGES copying djangocms_link/locale/ro/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ro/LC_MESSAGES copying djangocms_link/locale/ro/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ro/LC_MESSAGES creating build/lib/djangocms_link/locale/ro_RO creating build/lib/djangocms_link/locale/ro_RO/LC_MESSAGES copying djangocms_link/locale/ro_RO/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ro_RO/LC_MESSAGES copying djangocms_link/locale/ro_RO/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ro_RO/LC_MESSAGES creating build/lib/djangocms_link/locale/ru creating build/lib/djangocms_link/locale/ru/LC_MESSAGES copying djangocms_link/locale/ru/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ru/LC_MESSAGES copying djangocms_link/locale/ru/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ru/LC_MESSAGES creating build/lib/djangocms_link/locale/sk creating build/lib/djangocms_link/locale/sk/LC_MESSAGES copying djangocms_link/locale/sk/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sk/LC_MESSAGES copying djangocms_link/locale/sk/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sk/LC_MESSAGES creating build/lib/djangocms_link/locale/sk_SK creating build/lib/djangocms_link/locale/sk_SK/LC_MESSAGES copying djangocms_link/locale/sk_SK/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sk_SK/LC_MESSAGES copying djangocms_link/locale/sk_SK/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sk_SK/LC_MESSAGES creating build/lib/djangocms_link/locale/sl creating build/lib/djangocms_link/locale/sl/LC_MESSAGES copying djangocms_link/locale/sl/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sl/LC_MESSAGES copying djangocms_link/locale/sl/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sl/LC_MESSAGES creating build/lib/djangocms_link/locale/sl_SI creating build/lib/djangocms_link/locale/sl_SI/LC_MESSAGES copying djangocms_link/locale/sl_SI/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sl_SI/LC_MESSAGES copying djangocms_link/locale/sl_SI/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sl_SI/LC_MESSAGES creating build/lib/djangocms_link/locale/sq creating build/lib/djangocms_link/locale/sq/LC_MESSAGES copying djangocms_link/locale/sq/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sq/LC_MESSAGES copying djangocms_link/locale/sq/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sq/LC_MESSAGES creating build/lib/djangocms_link/locale/sq_AL creating build/lib/djangocms_link/locale/sq_AL/LC_MESSAGES copying djangocms_link/locale/sq_AL/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sq_AL/LC_MESSAGES copying djangocms_link/locale/sq_AL/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sq_AL/LC_MESSAGES creating build/lib/djangocms_link/locale/sr creating build/lib/djangocms_link/locale/sr/LC_MESSAGES copying djangocms_link/locale/sr/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sr/LC_MESSAGES copying djangocms_link/locale/sr/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sr/LC_MESSAGES creating build/lib/djangocms_link/locale/sr@latin creating build/lib/djangocms_link/locale/sr@latin/LC_MESSAGES copying djangocms_link/locale/sr@latin/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sr@latin/LC_MESSAGES copying djangocms_link/locale/sr@latin/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sr@latin/LC_MESSAGES creating build/lib/djangocms_link/locale/sv creating build/lib/djangocms_link/locale/sv/LC_MESSAGES copying djangocms_link/locale/sv/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/sv/LC_MESSAGES copying djangocms_link/locale/sv/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/sv/LC_MESSAGES creating build/lib/djangocms_link/locale/ta creating build/lib/djangocms_link/locale/ta/LC_MESSAGES copying djangocms_link/locale/ta/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ta/LC_MESSAGES copying djangocms_link/locale/ta/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ta/LC_MESSAGES creating build/lib/djangocms_link/locale/th creating build/lib/djangocms_link/locale/th/LC_MESSAGES copying djangocms_link/locale/th/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/th/LC_MESSAGES copying djangocms_link/locale/th/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/th/LC_MESSAGES creating build/lib/djangocms_link/locale/th_TH creating build/lib/djangocms_link/locale/th_TH/LC_MESSAGES copying djangocms_link/locale/th_TH/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/th_TH/LC_MESSAGES copying djangocms_link/locale/th_TH/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/th_TH/LC_MESSAGES creating build/lib/djangocms_link/locale/tlh creating build/lib/djangocms_link/locale/tlh/LC_MESSAGES copying djangocms_link/locale/tlh/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/tlh/LC_MESSAGES copying djangocms_link/locale/tlh/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/tlh/LC_MESSAGES creating build/lib/djangocms_link/locale/tr creating build/lib/djangocms_link/locale/tr/LC_MESSAGES copying djangocms_link/locale/tr/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/tr/LC_MESSAGES copying djangocms_link/locale/tr/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/tr/LC_MESSAGES creating build/lib/djangocms_link/locale/tr_TR creating build/lib/djangocms_link/locale/tr_TR/LC_MESSAGES copying djangocms_link/locale/tr_TR/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/tr_TR/LC_MESSAGES copying djangocms_link/locale/tr_TR/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/tr_TR/LC_MESSAGES creating build/lib/djangocms_link/locale/ug creating build/lib/djangocms_link/locale/ug/LC_MESSAGES copying djangocms_link/locale/ug/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ug/LC_MESSAGES copying djangocms_link/locale/ug/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ug/LC_MESSAGES creating build/lib/djangocms_link/locale/uk creating build/lib/djangocms_link/locale/uk/LC_MESSAGES copying djangocms_link/locale/uk/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/uk/LC_MESSAGES copying djangocms_link/locale/uk/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/uk/LC_MESSAGES creating build/lib/djangocms_link/locale/ur creating build/lib/djangocms_link/locale/ur/LC_MESSAGES copying djangocms_link/locale/ur/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/ur/LC_MESSAGES copying djangocms_link/locale/ur/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/ur/LC_MESSAGES creating build/lib/djangocms_link/locale/vi creating build/lib/djangocms_link/locale/vi/LC_MESSAGES copying djangocms_link/locale/vi/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/vi/LC_MESSAGES copying djangocms_link/locale/vi/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/vi/LC_MESSAGES creating build/lib/djangocms_link/locale/vi_VN creating build/lib/djangocms_link/locale/vi_VN/LC_MESSAGES copying djangocms_link/locale/vi_VN/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/vi_VN/LC_MESSAGES copying djangocms_link/locale/vi_VN/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/vi_VN/LC_MESSAGES creating build/lib/djangocms_link/locale/zh-Hans creating build/lib/djangocms_link/locale/zh-Hans/LC_MESSAGES copying djangocms_link/locale/zh-Hans/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/zh-Hans/LC_MESSAGES copying djangocms_link/locale/zh-Hans/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/zh-Hans/LC_MESSAGES creating build/lib/djangocms_link/locale/zh creating build/lib/djangocms_link/locale/zh/LC_MESSAGES copying djangocms_link/locale/zh/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/zh/LC_MESSAGES copying djangocms_link/locale/zh/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/zh/LC_MESSAGES creating build/lib/djangocms_link/locale/zh_CN.GB2312 creating build/lib/djangocms_link/locale/zh_CN.GB2312/LC_MESSAGES copying djangocms_link/locale/zh_CN.GB2312/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/zh_CN.GB2312/LC_MESSAGES copying djangocms_link/locale/zh_CN.GB2312/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/zh_CN.GB2312/LC_MESSAGES creating build/lib/djangocms_link/locale/zh_CN creating build/lib/djangocms_link/locale/zh_CN/LC_MESSAGES copying djangocms_link/locale/zh_CN/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/zh_CN/LC_MESSAGES copying djangocms_link/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/zh_CN/LC_MESSAGES creating build/lib/djangocms_link/locale/zh_TW creating build/lib/djangocms_link/locale/zh_TW/LC_MESSAGES copying djangocms_link/locale/zh_TW/LC_MESSAGES/django.mo -> build/lib/djangocms_link/locale/zh_TW/LC_MESSAGES copying djangocms_link/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/djangocms_link/locale/zh_TW/LC_MESSAGES creating build/lib/djangocms_link/templates creating build/lib/djangocms_link/templates/djangocms_link creating build/lib/djangocms_link/templates/djangocms_link/default copying djangocms_link/templates/djangocms_link/default/link.html -> build/lib/djangocms_link/templates/djangocms_link/default