=> "/opt/local/bin/bmake" ["-C", "/data/jenkins/workspace/pkgsrc-trunk-x86_64/www/py-djangocms-link", "all", "PYTHON_VERSION_REQD=311", "BATCH=1", "DEPENDS_TARGET=/nonexistent"]
===> Building for py311-djangocms-link-5.2.0
* Building wheel...
/opt/local/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated
!!

        ********************************************************************************
        Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both options available on setuptools>=77.0.0).

        By 2027-Feb-18, you need to update your project and remove deprecated calls
        or your builds will no longer be supported.

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  corresp(dist, value, root_dir)
/opt/local/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: BSD License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  dist._finalize_license_expression()
/opt/local/lib/python3.11/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: BSD License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  self._finalize_license_expression()
running bdist_wheel
running build
running build_py
creating build/lib/djangocms_link
copying djangocms_link/__init__.py -> build/lib/djangocms_link
copying djangocms_link/admin.py -> build/lib/djangocms_link
copying djangocms_link/apps.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/helpers.py -> build/lib/djangocms_link
copying djangocms_link/models.py -> build/lib/djangocms_link
copying djangocms_link/validators.py -> build/lib/djangocms_link
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 '*'
warning: no previously-included files matching '*' found under directory 'tests'
adding license file 'LICENSE'
writing manifest file 'djangocms_link.egg-info/SOURCES.txt'
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'djangocms_link.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'djangocms_link.locale.zh_Hans.LC_MESSAGES' as an importable package[^1],
        but it 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_Hans.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can 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_Hans.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'djangocms_link.locale.zh_Hans.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'djangocms_link.migrations' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'djangocms_link.migrations' as an importable package[^1],
        but it 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.migrations' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can 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.migrations' to be distributed and are
        already explicitly excluding 'djangocms_link.migrations' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'djangocms_link.static.djangocms_link' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'djangocms_link.static.djangocms_link' as an importable package[^1],
        but it 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.static.djangocms_link' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can 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.static.djangocms_link' to be distributed and are
        already explicitly excluding 'djangocms_link.static.djangocms_link' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'djangocms_link.templates.djangocms_link.admin' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'djangocms_link.templates.djangocms_link.admin' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.

        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'djangocms_link.templates.djangocms_link.admin' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can read more about "package discovery" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

        If you don't want 'djangocms_link.templates.djangocms_link.admin' to be distributed and are
        already explicitly excluding 'djangocms_link.templates.djangocms_link.admin' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************

!!
  check.warn(importable)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _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)
/opt/local/lib/python3.11/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'djangocms_link.templatetags' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'djangocms_link.templatetags' as an importable package[^1],
        but it 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.templatetags' is explicitly added
        to the `packages` configuration field.

        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).

        You can 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.templatetags' to be distributed and are
        already explicitly excluding 'djangocms_link.templatetags' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.

        You can read more about "package data files" on setuptools documentation page:

        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html


        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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_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/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/0017_link_link.py -> build/lib/djangocms_link/migrations
copying djangocms_link/migrations/0018_remove_link_anchor_remove_link_external_link_and_more.py -> build/lib/djangocms_link/migrations
copying djangocms_link/migrations/0019_alter_link_link.py -> build/lib/djangocms_link/migrations
copying djangocms_link/migrations/0020_rename_target_link_link_target.py -> build/lib/djangocms_link/migrations
copying djangocms_link/migrations/__init__.py -> build/lib/djangocms_link/migrations
creating build/lib/djangocms_link/static/djangocms_link
copying djangocms_link/static/djangocms_link/link-widget.css -> build/lib/djangocms_link/static/djangocms_link
copying djangocms_link/static/djangocms_link/link-widget.js -> build/lib/djangocms_link/static/djangocms_link
creating build/lib/djangocms_link/templates/djangocms_link/admin
copying djangocms_link/templates/djangocms_link/admin/link_widget.html -> build/lib/djangocms_link/templates/djangocms_link/admin
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
creating build/lib/djangocms_link/templatetags
copying djangocms_link/templatetags/__init__.py -> build/lib/djangocms_link/templatetags
copying djangocms_link/templatetags/djangocms_link_tags.py -> build/lib/djangocms_link/templatetags
installing to build/bdist.solaris-2.11-i86pc.64bit/wheel
running install
running install_lib
creating build/bdist.solaris-2.11-i86pc.64bit/wheel
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link
copying build/lib/djangocms_link/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link
copying build/lib/djangocms_link/admin.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link
copying build/lib/djangocms_link/apps.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link
copying build/lib/djangocms_link/cms_plugins.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link
copying build/lib/djangocms_link/fields.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link
copying build/lib/djangocms_link/helpers.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link
copying build/lib/djangocms_link/models.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link
copying build/lib/djangocms_link/validators.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/af
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/af/LC_MESSAGES
copying build/lib/djangocms_link/locale/af/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/af/LC_MESSAGES
copying build/lib/djangocms_link/locale/af/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/af/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ar
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ar/LC_MESSAGES
copying build/lib/djangocms_link/locale/ar/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ar/LC_MESSAGES
copying build/lib/djangocms_link/locale/ar/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ar/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/be
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/be/LC_MESSAGES
copying build/lib/djangocms_link/locale/be/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/be/LC_MESSAGES
copying build/lib/djangocms_link/locale/be/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/be/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/bg
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/bg/LC_MESSAGES
copying build/lib/djangocms_link/locale/bg/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/bg/LC_MESSAGES
copying build/lib/djangocms_link/locale/bg/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/bg/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/bn
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/bn/LC_MESSAGES
copying build/lib/djangocms_link/locale/bn/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/bn/LC_MESSAGES
copying build/lib/djangocms_link/locale/bn/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/bn/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ca
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ca/LC_MESSAGES
copying build/lib/djangocms_link/locale/ca/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ca/LC_MESSAGES
copying build/lib/djangocms_link/locale/ca/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ca/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/cs
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/cs/LC_MESSAGES
copying build/lib/djangocms_link/locale/cs/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/cs/LC_MESSAGES
copying build/lib/djangocms_link/locale/cs/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/cs/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/cy
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/cy/LC_MESSAGES
copying build/lib/djangocms_link/locale/cy/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/cy/LC_MESSAGES
copying build/lib/djangocms_link/locale/cy/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/cy/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/da
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/da/LC_MESSAGES
copying build/lib/djangocms_link/locale/da/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/da/LC_MESSAGES
copying build/lib/djangocms_link/locale/da/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/da/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/de
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/de/LC_MESSAGES
copying build/lib/djangocms_link/locale/de/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/de/LC_MESSAGES
copying build/lib/djangocms_link/locale/de/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/de/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/el
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/el/LC_MESSAGES
copying build/lib/djangocms_link/locale/el/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/el/LC_MESSAGES
copying build/lib/djangocms_link/locale/el/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/el/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/en
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/en/LC_MESSAGES
copying build/lib/djangocms_link/locale/en/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/en/LC_MESSAGES
copying build/lib/djangocms_link/locale/en/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/en/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/eo
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/eo/LC_MESSAGES
copying build/lib/djangocms_link/locale/eo/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/eo/LC_MESSAGES
copying build/lib/djangocms_link/locale/eo/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/eo/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/es
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/es/LC_MESSAGES
copying build/lib/djangocms_link/locale/es/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/es/LC_MESSAGES
copying build/lib/djangocms_link/locale/es/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/es/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/et
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/et/LC_MESSAGES
copying build/lib/djangocms_link/locale/et/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/et/LC_MESSAGES
copying build/lib/djangocms_link/locale/et/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/et/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/eu
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/eu/LC_MESSAGES
copying build/lib/djangocms_link/locale/eu/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/eu/LC_MESSAGES
copying build/lib/djangocms_link/locale/eu/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/eu/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/fa
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/fa/LC_MESSAGES
copying build/lib/djangocms_link/locale/fa/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/fa/LC_MESSAGES
copying build/lib/djangocms_link/locale/fa/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/fa/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/fi
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/fi/LC_MESSAGES
copying build/lib/djangocms_link/locale/fi/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/fi/LC_MESSAGES
copying build/lib/djangocms_link/locale/fi/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/fi/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/fr
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/fr/LC_MESSAGES
copying build/lib/djangocms_link/locale/fr/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/fr/LC_MESSAGES
copying build/lib/djangocms_link/locale/fr/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/fr/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ga
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ga/LC_MESSAGES
copying build/lib/djangocms_link/locale/ga/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ga/LC_MESSAGES
copying build/lib/djangocms_link/locale/ga/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ga/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/gl
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/gl/LC_MESSAGES
copying build/lib/djangocms_link/locale/gl/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/gl/LC_MESSAGES
copying build/lib/djangocms_link/locale/gl/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/gl/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/gu
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/gu/LC_MESSAGES
copying build/lib/djangocms_link/locale/gu/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/gu/LC_MESSAGES
copying build/lib/djangocms_link/locale/gu/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/gu/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/he
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/he/LC_MESSAGES
copying build/lib/djangocms_link/locale/he/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/he/LC_MESSAGES
copying build/lib/djangocms_link/locale/he/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/he/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/hi
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/hi/LC_MESSAGES
copying build/lib/djangocms_link/locale/hi/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/hi/LC_MESSAGES
copying build/lib/djangocms_link/locale/hi/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/hi/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/hr
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/hr/LC_MESSAGES
copying build/lib/djangocms_link/locale/hr/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/hr/LC_MESSAGES
copying build/lib/djangocms_link/locale/hr/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/hr/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/hu
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/hu/LC_MESSAGES
copying build/lib/djangocms_link/locale/hu/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/hu/LC_MESSAGES
copying build/lib/djangocms_link/locale/hu/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/hu/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/id
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/id/LC_MESSAGES
copying build/lib/djangocms_link/locale/id/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/id/LC_MESSAGES
copying build/lib/djangocms_link/locale/id/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/id/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/is
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/is/LC_MESSAGES
copying build/lib/djangocms_link/locale/is/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/is/LC_MESSAGES
copying build/lib/djangocms_link/locale/is/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/is/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/it
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/it/LC_MESSAGES
copying build/lib/djangocms_link/locale/it/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/it/LC_MESSAGES
copying build/lib/djangocms_link/locale/it/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/it/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ja
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ja/LC_MESSAGES
copying build/lib/djangocms_link/locale/ja/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ja/LC_MESSAGES
copying build/lib/djangocms_link/locale/ja/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ja/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ka
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ka/LC_MESSAGES
copying build/lib/djangocms_link/locale/ka/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ka/LC_MESSAGES
copying build/lib/djangocms_link/locale/ka/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ka/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/kk
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/kk/LC_MESSAGES
copying build/lib/djangocms_link/locale/kk/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/kk/LC_MESSAGES
copying build/lib/djangocms_link/locale/kk/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/kk/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/km
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/km/LC_MESSAGES
copying build/lib/djangocms_link/locale/km/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/km/LC_MESSAGES
copying build/lib/djangocms_link/locale/km/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/km/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ko
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ko/LC_MESSAGES
copying build/lib/djangocms_link/locale/ko/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ko/LC_MESSAGES
copying build/lib/djangocms_link/locale/ko/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ko/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/lt
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/lt/LC_MESSAGES
copying build/lib/djangocms_link/locale/lt/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/lt/LC_MESSAGES
copying build/lib/djangocms_link/locale/lt/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/lt/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/lv
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/lv/LC_MESSAGES
copying build/lib/djangocms_link/locale/lv/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/lv/LC_MESSAGES
copying build/lib/djangocms_link/locale/lv/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/lv/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/mn
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/mn/LC_MESSAGES
copying build/lib/djangocms_link/locale/mn/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/mn/LC_MESSAGES
copying build/lib/djangocms_link/locale/mn/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/mn/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ms
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ms/LC_MESSAGES
copying build/lib/djangocms_link/locale/ms/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ms/LC_MESSAGES
copying build/lib/djangocms_link/locale/ms/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ms/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/mt
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/mt/LC_MESSAGES
copying build/lib/djangocms_link/locale/mt/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/mt/LC_MESSAGES
copying build/lib/djangocms_link/locale/mt/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/mt/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/nb
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/nb/LC_MESSAGES
copying build/lib/djangocms_link/locale/nb/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/nb/LC_MESSAGES
copying build/lib/djangocms_link/locale/nb/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/nb/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/nl
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/nl/LC_MESSAGES
copying build/lib/djangocms_link/locale/nl/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/nl/LC_MESSAGES
copying build/lib/djangocms_link/locale/nl/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/nl/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/no
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/no/LC_MESSAGES
copying build/lib/djangocms_link/locale/no/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/no/LC_MESSAGES
copying build/lib/djangocms_link/locale/no/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/no/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/pl
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/pl/LC_MESSAGES
copying build/lib/djangocms_link/locale/pl/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/pl/LC_MESSAGES
copying build/lib/djangocms_link/locale/pl/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/pl/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/pt
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/pt/LC_MESSAGES
copying build/lib/djangocms_link/locale/pt/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/pt/LC_MESSAGES
copying build/lib/djangocms_link/locale/pt/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/pt/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ro
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ro/LC_MESSAGES
copying build/lib/djangocms_link/locale/ro/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ro/LC_MESSAGES
copying build/lib/djangocms_link/locale/ro/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ro/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ru
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ru/LC_MESSAGES
copying build/lib/djangocms_link/locale/ru/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ru/LC_MESSAGES
copying build/lib/djangocms_link/locale/ru/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ru/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sk
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sk/LC_MESSAGES
copying build/lib/djangocms_link/locale/sk/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sk/LC_MESSAGES
copying build/lib/djangocms_link/locale/sk/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sk/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sl
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sl/LC_MESSAGES
copying build/lib/djangocms_link/locale/sl/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sl/LC_MESSAGES
copying build/lib/djangocms_link/locale/sl/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sl/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sq
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sq/LC_MESSAGES
copying build/lib/djangocms_link/locale/sq/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sq/LC_MESSAGES
copying build/lib/djangocms_link/locale/sq/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sq/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sr
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sr/LC_MESSAGES
copying build/lib/djangocms_link/locale/sr/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sr/LC_MESSAGES
copying build/lib/djangocms_link/locale/sr/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sr/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sv
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/sv/LC_MESSAGES
copying build/lib/djangocms_link/locale/sv/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sv/LC_MESSAGES
copying build/lib/djangocms_link/locale/sv/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/sv/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ta
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ta/LC_MESSAGES
copying build/lib/djangocms_link/locale/ta/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ta/LC_MESSAGES
copying build/lib/djangocms_link/locale/ta/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ta/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/th
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/th/LC_MESSAGES
copying build/lib/djangocms_link/locale/th/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/th/LC_MESSAGES
copying build/lib/djangocms_link/locale/th/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/th/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/tr
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/tr/LC_MESSAGES
copying build/lib/djangocms_link/locale/tr/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/tr/LC_MESSAGES
copying build/lib/djangocms_link/locale/tr/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/tr/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ug
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ug/LC_MESSAGES
copying build/lib/djangocms_link/locale/ug/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ug/LC_MESSAGES
copying build/lib/djangocms_link/locale/ug/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ug/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/uk
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/uk/LC_MESSAGES
copying build/lib/djangocms_link/locale/uk/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/uk/LC_MESSAGES
copying build/lib/djangocms_link/locale/uk/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/uk/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ur
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/ur/LC_MESSAGES
copying build/lib/djangocms_link/locale/ur/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ur/LC_MESSAGES
copying build/lib/djangocms_link/locale/ur/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/ur/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/vi
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/vi/LC_MESSAGES
copying build/lib/djangocms_link/locale/vi/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/vi/LC_MESSAGES
copying build/lib/djangocms_link/locale/vi/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/vi/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/zh
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/zh/LC_MESSAGES
copying build/lib/djangocms_link/locale/zh/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/zh/LC_MESSAGES
copying build/lib/djangocms_link/locale/zh/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/zh/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/zh_Hans
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/locale/zh_Hans/LC_MESSAGES
copying build/lib/djangocms_link/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/zh_Hans/LC_MESSAGES
copying build/lib/djangocms_link/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/locale/zh_Hans/LC_MESSAGES
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0001_initial.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0002_auto_20140929_1705.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0003_auto_20150212_1310.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0004_auto_20150708_1133.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0005_auto_20151003_1710.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0006_remove_related_name_for_cmsplugin_ptr.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0007_set_related_name_for_cmsplugin_ptr.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0008_link_attributes.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0009_auto_20160705_1344.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0010_adapted_fields.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0011_fixed_null_values.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0012_removed_null.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0013_fix_hostname.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0014_link_file_link.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0015_auto_20190621_0407.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0016_alter_link_cmsplugin_ptr.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0017_link_link.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0018_remove_link_anchor_remove_link_external_link_and_more.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0019_alter_link_link.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/0020_rename_target_link_link_target.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
copying build/lib/djangocms_link/migrations/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/migrations
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/static
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/static/djangocms_link
copying build/lib/djangocms_link/static/djangocms_link/link-widget.css -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/static/djangocms_link
copying build/lib/djangocms_link/static/djangocms_link/link-widget.js -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/static/djangocms_link
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/templates
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/templates/djangocms_link
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/templates/djangocms_link/admin
copying build/lib/djangocms_link/templates/djangocms_link/admin/link_widget.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/templates/djangocms_link/admin
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/templates/djangocms_link/default
copying build/lib/djangocms_link/templates/djangocms_link/default/link.html -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/templates/djangocms_link/default
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link/templatetags
copying build/lib/djangocms_link/templatetags/__init__.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/templatetags
copying build/lib/djangocms_link/templatetags/djangocms_link_tags.py -> build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link/templatetags
running install_egg_info
Copying djangocms_link.egg-info to build/bdist.solaris-2.11-i86pc.64bit/wheel/./djangocms_link-5.2.0-py3.11.egg-info
running install_scripts
creating build/bdist.solaris-2.11-i86pc.64bit/wheel/djangocms_link-5.2.0.dist-info/WHEEL
creating '/tmp/work/www/py-djangocms-link/work/djangocms_link-5.2.0/dist/.tmp-9bhekeca/djangocms_link-5.2.0-py3-none-any.whl' and adding 'build/bdist.solaris-2.11-i86pc.64bit/wheel' to it
adding 'djangocms_link/__init__.py'
adding 'djangocms_link/admin.py'
adding 'djangocms_link/apps.py'
adding 'djangocms_link/cms_plugins.py'
adding 'djangocms_link/fields.py'
adding 'djangocms_link/helpers.py'
adding 'djangocms_link/models.py'
adding 'djangocms_link/validators.py'
adding 'djangocms_link/locale/af/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/af/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ar/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ar/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/be/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/be/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/bg/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/bg/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/bn/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/bn/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ca/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ca/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/cs/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/cs/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/cy/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/cy/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/da/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/da/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/de/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/de/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/el/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/el/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/en/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/en/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/eo/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/eo/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/es/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/es/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/et/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/et/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/eu/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/eu/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/fa/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/fa/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/fi/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/fi/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/fr/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/fr/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ga/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ga/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/gl/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/gl/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/gu/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/gu/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/he/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/he/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/hi/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/hi/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/hr/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/hr/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/hu/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/hu/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/id/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/id/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/is/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/is/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/it/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/it/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ja/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ja/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ka/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ka/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/kk/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/kk/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/km/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/km/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ko/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ko/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/lt/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/lt/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/lv/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/lv/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/mn/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/mn/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ms/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ms/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/mt/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/mt/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/nb/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/nb/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/nl/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/nl/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/no/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/no/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/pl/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/pl/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/pt/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/pt/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ro/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ro/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ru/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ru/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/sk/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/sk/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/sl/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/sl/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/sq/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/sq/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/sr/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/sr/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/sv/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/sv/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ta/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ta/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/th/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/th/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/tr/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/tr/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ug/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ug/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/uk/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/uk/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/ur/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/ur/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/vi/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/vi/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/zh/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/zh/LC_MESSAGES/django.po'
adding 'djangocms_link/locale/zh_Hans/LC_MESSAGES/django.mo'
adding 'djangocms_link/locale/zh_Hans/LC_MESSAGES/django.po'
adding 'djangocms_link/migrations/0001_initial.py'
adding 'djangocms_link/migrations/0002_auto_20140929_1705.py'
adding 'djangocms_link/migrations/0003_auto_20150212_1310.py'
adding 'djangocms_link/migrations/0004_auto_20150708_1133.py'
adding 'djangocms_link/migrations/0005_auto_20151003_1710.py'
adding 'djangocms_link/migrations/0006_remove_related_name_for_cmsplugin_ptr.py'
adding 'djangocms_link/migrations/0007_set_related_name_for_cmsplugin_ptr.py'
adding 'djangocms_link/migrations/0008_link_attributes.py'
adding 'djangocms_link/migrations/0009_auto_20160705_1344.py'
adding 'djangocms_link/migrations/0010_adapted_fields.py'
adding 'djangocms_link/migrations/0011_fixed_null_values.py'
adding 'djangocms_link/migrations/0012_removed_null.py'
adding 'djangocms_link/migrations/0013_fix_hostname.py'
adding 'djangocms_link/migrations/0014_link_file_link.py'
adding 'djangocms_link/migrations/0015_auto_20190621_0407.py'
adding 'djangocms_link/migrations/0016_alter_link_cmsplugin_ptr.py'
adding 'djangocms_link/migrations/0017_link_link.py'
adding 'djangocms_link/migrations/0018_remove_link_anchor_remove_link_external_link_and_more.py'
adding 'djangocms_link/migrations/0019_alter_link_link.py'
adding 'djangocms_link/migrations/0020_rename_target_link_link_target.py'
adding 'djangocms_link/migrations/__init__.py'
adding 'djangocms_link/static/djangocms_link/link-widget.css'
adding 'djangocms_link/static/djangocms_link/link-widget.js'
adding 'djangocms_link/templates/djangocms_link/admin/link_widget.html'
adding 'djangocms_link/templates/djangocms_link/default/link.html'
adding 'djangocms_link/templatetags/__init__.py'
adding 'djangocms_link/templatetags/djangocms_link_tags.py'
adding 'djangocms_link-5.2.0.dist-info/licenses/LICENSE'
adding 'djangocms_link-5.2.0.dist-info/METADATA'
adding 'djangocms_link-5.2.0.dist-info/WHEEL'
adding 'djangocms_link-5.2.0.dist-info/top_level.txt'
adding 'djangocms_link-5.2.0.dist-info/RECORD'
removing build/bdist.solaris-2.11-i86pc.64bit/wheel
Successfully built djangocms_link-5.2.0-py3-none-any.whl